The decision making process is the sequence of steps used to move from a problem to a committed choice: define the decision, gather information, generate options, weigh them, choose, act, and review the result. A clear process matters more than clever analysis, because most poor decisions come from skipped steps, not from bad math.
Research backs this up. In a McKinsey study of 1,048 major business decisions, Lovallo and Sibony found that process mattered more than analysis by a factor of six. This guide lays out the steps, shows how they apply in a team setting, and explains where the process usually breaks down.
The 7 steps of the decision making process
- Define the decision. State exactly what is being decided, why now, and what is out of scope. A vague question produces a vague answer.
- Clarify who decides. Name the decision owner, who gives input, and who must agree. Unclear decision rights cause more delay than hard trade-offs.
- Gather relevant information. Collect the facts that would change the choice, and stop there. More data is not always better data.
- Generate real alternatives. Aim for at least three options, including “do nothing.” A single option is a proposal, not a decision.
- Weigh the options against criteria. Agree on the criteria (cost, risk, speed, values, reversibility) before scoring the options, so the preferred answer does not shape the yardstick.
- Choose and commit. Make the call, record the reasoning, and turn it into specific commitments: who does what, by when.
- Implement and review. Track whether the commitments were kept and whether the outcome matched the reasoning. Feed what you learn into the next decision.
The steps at a glance
| Step | Key question | Common failure |
|---|---|---|
| 1. Define | What exactly are we deciding? | Solving a symptom instead of the real problem |
| 2. Decision rights | Who decides, who advises, who must agree? | Everyone thinks someone else owns it |
| 3. Information | What facts would change our choice? | Analysis paralysis or confirmation bias |
| 4. Alternatives | What else could we do? | Only one option on the table |
| 5. Weigh | Which option best fits our criteria? | Criteria chosen after the answer |
| 6. Commit | Who does what, by when? | A decision with no owner or deadline |
| 7. Review | Did it work, and what did we learn? | No follow-up, so nothing is learned |
Match the process to the type of decision
Not every decision deserves all seven steps at full depth. Two questions help set the level of effort.
- Is it reversible? Jeff Bezos described reversible decisions as “two-way doors” that can be made quickly by a small group, and irreversible ones as “one-way doors” that need careful deliberation. Spend process time on one-way doors.
- Is the situation clear or complex? When cause and effect are known, a quick analysis works. When they are not, small experiments and fast feedback beat long debate. Our guide to decision making frameworks compares models such as Cynefin, RAPID, and OODA for these situations.
The decision making process in teams
Group decisions add a layer: people need to know how the decision will be made before they argue about what it should be. Bain’s RAPID model, for example, separates the roles of Recommend, Agree, Input, Decide, and Perform, and recommends a single person in the Decide role. Whatever model you use, agree on it up front.
The other team risk is silent disagreement. People nod in the meeting, then act on their own view afterward. That is not a decision; it is a postponed conflict. A good process ends with explicit commitments from each person whose work is affected, and a clear way to raise concerns later.
Where decisions break down
A 2018 McKinsey survey found only 20 percent of respondents said their organization excels at decision making, and that managers spend a large share of their time on decisions they see as ineffective. In our experience, the breakdown rarely sits in the analysis. It sits in step 6.
From DorWay’s perspective, every decision creates new agreements inside a Network of Agreements™. If those agreements are not specific (who, what, by when, and how we will renegotiate if things change), the decision quietly unravels. Keeping and openly renegotiating those commitments is what accountability means in practice, and it is how decisions become results.
Personal factors matter too: pressure, bias, and leadership style all shape the choice. Our article on decision making in leadership covers those factors, and decision quality explains how to judge a decision by its process, not just its outcome.
A simple checklist before you decide
- Can you state the decision in one sentence?
- Is one person clearly accountable for the final call?
- Did you consider at least three options?
- Were criteria agreed before options were scored?
- Does every affected person know their next commitment and deadline?
- Is there a date to review the result?
FAQ
What are the steps of the decision making process?
The common steps are: define the decision, clarify who decides, gather information, generate alternatives, weigh them against criteria, choose and commit, then implement and review.
Why is the decision making process important?
A consistent process reduces bias and missed options. McKinsey research on more than 1,000 decisions found process quality had a far bigger effect on results than the depth of analysis.
What is the most important step in decision making?
Defining the decision clearly is the foundation, but turning the choice into specific commitments is where most decisions succeed or fail.
How do you make decisions as a team?
Agree on decision rights before debating, invite real dissent, name one decider, and close with explicit commitments from everyone whose work is affected.