# Define Decision Making: What It Actually Means at Work Canonical URL: https://headwayskills.com/knowledge/decision-making/define-decision-making/ Markdown URL: https://headwayskills.com/knowledge/decision-making/define-decision-making.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving decision-making at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer Decision making is the process of choosing one action from the alternatives. See what the definition covers, the main types, and which decisions are yours. ## Key facts - Title: Define Decision Making: What It Actually Means at Work - Category: Decision Making - Primary skill: Decision-Making - Related skills: Working with Your Manager, Teamwork - Primary keyword: define decision making - Source page: https://headwayskills.com/knowledge/decision-making/define-decision-making/ ## What this page covers - Decision making is the process of choosing one action from the alternatives. See what the definition covers, the main types, and which decisions are yours. - Practical guidance for define decision making - How this topic connects to Decision-Making ## Detailed explanation Decision making is [the process of choosing](/knowledge/decision-making/decision-making-process/) one course of action from the alternatives available to you: working out what has to be decided, gathering what you can, weighing the options against each other, committing to one, and then acting on it. At work that process runs many times a week, mostly on things small enough that you never notice you ran it. Most people looking the term up already have a rough sense of that much. What the one-line version leaves out is the part that determines whether you are actually any good at it — whether the decision was yours to make, and how much of it you were meant to work out alone. That is why the same short definition can describe a two-second call and a two-month one. ## What decision making is: a process, not a moment The word makes it sound instantaneous, which is misleading and is probably why so many people assume they ought to be faster at it. Both the dictionary and the encyclopedic sources define it as a cognitive *process* resulting in the selection of a course of action — a sequence with a beginning and an end, in which the choosing is one step among several rather than the whole thing. The explainers converge on almost the same sequence. TechTarget and Indeed both lay it out as: define the problem specifically enough that it can actually be decided; gather information from your own experience and from outside it; generate and weigh the alternatives; choose; implement the decision and tell the people it affects; then review it and collect feedback. The first and last steps are the ones that get skipped. A problem defined too broadly ("we should do something about the backlog") cannot be decided, only discussed. And the review tail — going back afterward to see what the decision actually produced — is what turns a decision into [something you learn from](/knowledge/confidence/learn-from-mistakes/) rather than a one-off gamble. Skip it and you accumulate experience without accumulating judgment. It is worth knowing where you probably met this term. Career-skill sources like WGU and Coursera present decision making as a competency employers screen for, which is why it turns up in job ads and competency reviews. Some of them describe it as an umbrella assembled from a handful of other abilities, which blurs it; it is more useful, and more accurate, to treat it as one distinct thing you can get deliberately better at. ## The types of decision making the definition covers The reason a single definition stretches so far is that workplace decisions sort along three separate axes: how much precedent exists, where in the organization the decision sits, and who owns it. Any real decision has a position on all three, and knowing where it sits tells you most of what you need to know about how to handle it. ### Programmed decisions Routine, repetitive decisions the organization has already answered in advance through a policy, rule, or standing procedure. The textbook example is reordering stock when it drops to a set threshold: the same situation recurs, so a fixed response is attached to it. The defining feature is that reasoning it out from scratch is the wrong move — the work is finding the existing rule and applying it consistently. Most of the difficulty here is not judgment but discovery: knowing that the policy exists at all. ### Non-programmed decisions New, unusual, or complex situations where no standard procedure applies, so the judgment has to be built on the spot. This is the older half of the most durable distinction in the field, which traces back to Herbert Simon and still anchors the management textbooks. Because there is no rule to fall back on, the quality of your outcome depends almost entirely on the quality of your process and on who you brought into it. ### Strategic decisions Long-horizon decisions made at the top of an organization that set or change its direction: which markets to enter, which products to build, how to allocate significant resources. They are almost always non-programmed, and they carry the heaviest process because they are the hardest to reverse. You are unlikely to make one early on. Understanding the category is still useful, because it explains why some things in your organization move slowly. ### Tactical decisions Mid-level decisions about how an already-agreed goal will be reached — resourcing, sequencing, method, what gets cut when the time runs short. These typically sit with managers and directors, over weeks or months. The direction is fixed; the decision is about the route to it. You will usually be consulted on these well before you own one. ### Operational decisions The everyday decisions that keep work running: what to do first, whether something is finished, whether to flag a problem now or wait. They are largely routine, they are made in high volume, and — this is the part the search results tend not to say — they are where essentially all early-career decision making happens. Individually each one is low-stakes. Collectively they are how a reputation for reliability gets built. ### Who decides: individual, consultative, and group This axis cuts across the other two and is often the one that matters most in practice. Sources like Management Study Guide describe three modes: authoritarian, where one person decides without consulting anyone; consultative, where input is gathered from the people affected but one person still decides; and democratic, where the group decides together. The practical value of knowing which mode you are in is that it tells you what your job is in the room — whether you are there to advise or there to choose. Mistaking one for the other is a common and avoidable source of friction. ## Why the definition doesn't tell you how to decide well Here is the gap the definitional sources leave. Read the top results and you come away with a clean procedure, which implies that deciding well is a matter of following the steps carefully enough. In practice the steps are rarely the obstacle. The first real obstacle is authority. Before any process applies, someone has to be the person deciding, and early in a career that is genuinely unclear. Checking everything feels like the safe option and is not: it is slow, and it reads as an unwillingness to carry anything. The fix is a conversation rather than a deduction — agreeing explicitly with your manager [which calls you make alone](/knowledge/decision-making/decision-making-authority/), which you make and report afterward, and which you bring before deciding. The second is that a complete picture almost never arrives. Accepting [an answer that is good enough](/knowledge/decision-making/satisficing/), and allowing some uncertainty to stand, is part of the skill rather than a failure of it. Waiting until you feel certain is itself a decision, usually a worse one. The third is that your own mind interferes with the evidence. The serious sources name this and the dictionary tier leaves it out entirely. Four traps are worth knowing by name: confirmation bias, where you notice the evidence that agrees with you; anchoring, where the first figure or first suggestion quietly sets the frame for everything after it; overconfidence, where you are more certain than the information supports; and the sunk-cost trap, where you keep defending a call because of what you have already put into it. Sunk cost is the most expensive of the four, because from the inside it feels like commitment rather than error. A procedure will not catch any of them for you, but knowing [how you currently operate](https://assessment.headwayskills.com/) makes them considerably easier to spot in yourself — and none of these habits is fixed. One more distinction, which the definition never supplies: a good decision and a good outcome are not the same thing. You can decide well and get unlucky. Judging your decisions purely by how they turned out teaches you the wrong lessons. ## The skills that sit behind a decision you can defend Look back at what that section actually asked of you. Almost none of it was analytical. Knowing where your authority ends is a conversation. Committing on an unfinished picture is a matter of nerve. Handling a group that lands somewhere you disagree with is neither. **Decision-Making** as a skill is largely the material this article has been circling. It means knowing the limits of your own authority and the guidelines you are working inside; slowing down deliberately when you are rushed or emotional, because those are exactly the conditions under which the obvious answer turns out to be wrong; getting another opinion, including from someone likely to disagree with you; accepting good enough over perfect; and recognizing the traps before they cost you. It is a working skill, exercised inside a job — not a method for choosing a career. **Working with Your Manager** supplies the half of the definition no dictionary includes: your decision authority is something you agree on, out loud, rather than infer. Treating the relationship as a partnership makes that conversation ordinary instead of awkward — you can raise it in a regular one-on-one, agree which calls sit with you, and come back with a solution attached when you do bring something upward. Being honest about a decision that went badly belongs here too. Checking first is not a sign of weakness; guessing silently is what causes the damage. **Teamwork** determines what happens once other people are in the room. Most of the decisions you touch will not be yours alone, and the hard moment is not gathering opinions — it is the group settling somewhere you would not have. The move is to raise the disagreement while the question is still open, keep it on the substance rather than on the person, and then genuinely commit to what the group decided and implement it properly. Dragging your feet on a decision you did not win costs far more trust than the disagreement ever did. Deciding well leans on more of these than the definition suggests, and the free Work Skills Test covers all twelve that this framework treats as buildable — so rather than guessing which of them is holding you back, you can see [where your gaps sit](https://assessment.headwayskills.com/). ## What this means for you Some of this probably already describes how you work. Plenty of people sort decisions by how reversible they are without ever having put a name to it, and read a room's decision mode accurately on instinct. The version of you who decides comfortably at work is not a different person with a different temperament. It is you, with a clearer sense of where your authority ends and more practice at committing on an incomplete picture. Those are behaviors, which is why they respond to being worked on. Decisions also become less optional as you go. The further into a career you get, the more of your week consists of calls nobody else is going to make for you — which is a reason to build the habit now, while being wrong is still cheap. Reading past the definition to the question of what actually makes a decision hard is the step most people skip, and you have already taken it. ## See where your work skills stand The only thing left is to find out where you are starting from. The Work Skills Test is a **free** self-assessment of your skills at work. You answer a set of straightforward questions about how you actually operate day to day, and it shows you where you stand across all twelve skills and which of them would make the biggest difference to you right now. It takes about 7 minutes, and decision making is one of the twelve it looks at. ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? Decision making is the process of choosing one action from the alternatives. See what the definition covers, the main types, and which decisions are yours. ### Which Headway skill does this connect to? This guide connects primarily to Decision-Making. It also relates to Working with Your Manager, Teamwork. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/decision-making.md - https://headwayskills.com/knowledge/working-with-your-manager.md - https://headwayskills.com/knowledge/teamwork.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/decision-making/define-decision-making/ Preferred summary: "Decision making is the process of choosing one action from the alternatives. See what the definition covers, the main types, and which decisions are yours." ## Change log - 2026-07-07: Content collection version published.