"I'm sorry — what did you say?"
Shaun, one of our field service network agents, swallowed nervously. He repeated what he'd heard: Bob, our new service manager, had been negotiating pay rates and area changes directly with one of our providers.
We ran a tight operation. Pay rates weren't up for discussion except in narrow, pre-agreed circumstances. Area allocation followed a defined process. Both existed for a reason — cost control was a core pillar of the strategic plan, and every manager knew it.
Bob hadn't asked. He'd just decided.
What made it worse was how we found out. The call hadn't come from Bob or the provider he'd been speaking to. It had come from a different provider, whose areas were apparently being offered out in the same conversation. He wasn't happy.
We now had a service manager who had bypassed the process, a provider relationship under strain, and a hire we needed to reconsider.
A strategic leadership decision-making process only holds when everyone inside it knows the boundaries. Bob knew ours. He'd chosen to ignore them.
The question that stayed with me afterwards wasn't about Bob. It was about us. Had we ever actually agreed how decisions would be made — before anyone started making them?
There's a Decision in Front of You. Start Here.
You'll finish the week with a decision — knowing what to do and why.
What Most Leadership Decision-Making Processes Get Wrong
Most leadership teams have a decision-making process. Very few have agreed how decisions will be made before they start making them.
That gap is where most process failures live.
The steps themselves — gather data, weigh options, choose — are rarely the problem. The problem is what happens before Step 1. Who is actually making this call? What constraints are they working within? What method will be used when people disagree? These questions are almost never asked. Teams skip straight to the options and then wonder why the same arguments keep surfacing in every meeting.
Nobel laureate Herbert Simon called this bounded rationality — the idea that decision-makers work within limits they often haven't examined. Most leaders assume their process is clear because they've described it. But describing a process and agreeing a process are different things. Bob had heard the process described. He hadn't agreed to it in any meaningful sense.
The fix isn't a better framework. It's a step that runs before the framework begins.
The Strategic Leadership Decision-Making Process: 7 Steps That Hold Under Pressure
Most decision-making frameworks start at the wrong place.
They begin with options — what are we choosing between? — when the first question should be: how are we going to make this choice? That meta-decision shapes everything that follows. Skip it and you're building on sand.
The 7-step process below starts where most processes don't. Use the infographic as your reference; the sections that follow show each step under real pressure.
Step 1 — Decide How to Decide
Before you decide what, decide how.
This is the meta-decision — the step Bob skipped. Before any option is discussed, a leader needs to be clear on four things: who is involved in this decision, how reversible the choice is, what information will be needed, and what timeline you're working to.
In practice, this sounds like one question asked out loud before the meeting moves: "Have we agreed how we'll make this call?" Most rooms haven't. Most rooms assume they have.
The meta-decision also clarifies ownership. Bob's mistake wasn't rogue creativity — it was a vacuum. Nobody had told him explicitly that pay rate negotiations sat above his authority. A clear meta-decision makes that boundary visible before someone crosses it.
Step 2 — Widen Options
Every either/or choice is a signal that options haven't been explored.
Binary framing narrows your thinking before you've done the work. When a decision presents as A or B, the first move is to look for C — a different scope, a different timeline, a partial approach that tests the logic before full commitment. The article on non-binary decisions covers why this matters and how to find the third option most teams miss.
Pause deciding. Find more options first.
Step 3 — Gather Intelligence
Intelligence gathering has four moves: brainstorm, explore, test, narrow.
Brainstorm identifies where the intelligence lives — what you need to know and who has it. Explore scans those sources broadly before committing depth to any of them. Test runs small experiments and stress-tests assumptions: what does failure look like from the start, what if revenue drops 20%? Narrow cuts what doesn't hold up and eliminates options that fail basic tests.
The sequence is the point. Most leaders jump from brainstorm to narrow — collecting information that confirms what they already think, then cutting everything that challenges it. Explore and test exist to prevent that.
One question that forces honest intelligence gathering: "What simple test would make you more confident in this choice?"
From Decision to Outcome: The Steps Most Leaders Rush
The first three steps build the conditions for a good decision. These four execute it — and learn from it. Most leaders treat Step 4 as the finish line. It's the midpoint.
Step 4 — Make the Decision
Step 1 gave you the method. Now use it.
Apply the criteria you agreed in the meta-decision. Where trade-offs are complex and multiple stakeholders have stakes, weighted decision-making scores options objectively rather than letting the loudest voice win.
Uncertainty will remain. That's not a reason to wait — not deciding is still a decision, and it carries its own costs. What Step 1 built was a process sound enough to decide with incomplete information. Trust it.
Step 5 — Implement
A decision isn't real until something moves.
The first visible action is what makes it real. Who needs to know? What's the first concrete step? Clear role assignment prevents the failure mode that kills most implementations: everyone thought someone else was handling it.
A simple RACI structure names who is responsible for doing the work, who is accountable for the outcome, who needs to be consulted, and who needs to be kept informed. Built in from the start, it turns a decision into a plan. The RACI matrix covers how to apply it.
Step 6 — The Outcome
Every decision drives an outcome. Not always the one you planned for.
A sound process accounts for most eventualities. It doesn't prevent the unexpected. What the process gives you is not certainty. It's the position to respond.
Step 7 — The Learning Loop
This is the step most process articles don't include. It's the one that compounds.
Outcomes are noisy. Good decisions produce bad results. Bad decisions occasionally work out. Your job after any significant call isn't to judge the outcome — it's to capture what happened, what you predicted, and where the gap was.
A decision journal makes this systematic. Record the decision, the reasoning behind it, and the outcome. Over time, patterns emerge: the same biases, the same intelligence gaps, the same meta-decisions you forgot to make. That learning feeds directly back into Step 1 of your next significant call.
The loop isn't a review meeting. It's a discipline. And it's the difference between a leader who gets better at deciding over time and one who keeps repeating the same mistakes with more experience.
One Decision, Seven Steps: A Leadership Process in Practice
Bob's story is one version of a process failure. Here is another — larger in scale, more expensive in consequence, and recognisable to almost any leader who has been inside a significant organisational decision.
A mid-size company needed to replace its ERP system. The legacy platform was failing. The pressure to act was real. What followed was a decision-making process that skipped Steps 1, 2, and 3 entirely — and paid for it through every step that came after.
Decide how to decide
The board never asked how the decision would be made.
No agreed goal, no defined criteria, no clarity on who held final authority. The CEO assumed the CTO was leading. The CTO assumed finance had a view. Finance assumed someone had already chosen a vendor.
A single meta-decision conversation — goal: replace ERP by Q3, under £2m, zero service disruption; roles: CEO decides, CTO and finance execute — would have stopped three months of circular debate before it started.
Widen options
The team went from problem to vendor shortlist in two weeks.
Nobody asked what a partial solution looked like — integrating old and new systems temporarily, shifting low-risk teams to the new platform first, running a single-region pilot before full rollout. None of those options was discussed. The binary framing was accepted without question.
Gather intelligence
The legacy ERP was more like a haunted house than software. Nobody knew how the parts connected.
What should have happened: map every system dependency with every department, benchmark vendors against actual requirements, run a gap analysis before selecting anyone. What actually happened: the vendor was chosen first. Developers had to reverse-engineer the old system while building the new one.
Months into the project, the team produced a gap spreadsheet — a list of functions the new system couldn't handle. By then they were locked in, paying millions to fix problems that a four-week intelligence-gathering phase would have surfaced before the contract was signed.
Make the decision
With no agreed criteria, vendor selection came down to subjective preference.
A weighted decision table would have made the trade-offs visible: Vendor A, cheaper but higher implementation risk; Vendor B, stronger integrations, higher cost; Vendor C, proven track record, longer timeline. The table would have forced the board to name what they were optimising for. Instead, they picked Vendor A and discovered the trade-offs when they couldn't be undone.
Implement
Urgency replaced structure.
With no RACI in place, accountability fragmented. IT assumed operations was managing the change communications. Operations assumed IT was handling training. The first production issues surfaced when teams who hadn't been informed tried to use a system they hadn't been trained on.
The outcome
Projects overran. Teams were exhausted. Client relationships took a hit.
None of that was inevitable. Most of it was traceable to the meta-decision that never happened — the conversation in Week 1 where someone should have asked: have we agreed how we'll make this call?
The learning loop
The board moved on.
That's the most expensive decision-making mistake of all — treating a painful outcome as something to get past rather than something to learn from. A simple review, documented and shared, would have turned a £4m problem into a playbook. The biases that drove the binary framing, the intelligence gaps that were assumed away, the implementation failures that came from unclear roles — all of it was recoverable. None of it was captured.
The learning loop feeds Step 1 of the next decision. Without it, the same mistakes compound.
Use This Process on Your Next Strategic Decision
Pick one decision you're currently sitting on.
Not a hypothetical — a real call, with real pressure behind it. Walk it through the seven steps. Start with the meta-decision: have you agreed how this choice will be made, and who holds the authority to make it? That question alone will surface most of what's slowing you down.
The full framework is part of the Leader's Guide to Decision Making — the wider context for every call you make as a leader.
The decision you've been building a process around: has anyone actually agreed how it will be made?
FAQs
Why does a leadership decision-making process fail before anyone decides anything?
Most process failures happen at the meta-decision — the step that runs before the framework begins. Who is making this call, by what method, under what constraints? When those questions aren't answered first, teams argue options without agreeing how the choice will be made. The process doesn't break at Step 4. It breaks before Step 1.
How do I know if my team is skipping the meta-decision?
The signal is familiar: the same arguments keep surfacing in every meeting, options are debated before anyone has agreed who is deciding, and decisions get relitigated after they're made. If your team moves straight to "what are we choosing between?" without first asking "how are we going to make this choice?", the meta-decision is being skipped.
What's the difference between describing a decision-making process and agreeing one?
Describing a process means explaining how decisions will be made. Agreeing one means every person inside it has understood the boundaries and accepted them. Most leaders do the first and assume the second has followed. It hasn't. The gap between description and agreement is where most process violations — and most avoidable decision failures — live.
How do I apply a strategic decision-making process to a real decision I'm facing now?
Start with the meta-decision before anything else. Write down who is making this call, what constraints they're working within, and what method will be used if people disagree. That single step surfaces most of what's slowing you down. If you want to work through a live decision in seven days, One Good Decision is built exactly for that.
How does emotional pressure affect a leadership decision-making process?
Emotional pressure doesn't just affect the decision — it affects the process. Under stress, leaders skip the meta-decision entirely and jump to options because acting feels more decisive than agreeing how to act. That's the moment the process collapses. Understanding how emotional decision-making distorts the process before it begins is where the deeper work lives.
There's a Decision in Front of You. Start Here.
You'll finish the week with a decision — knowing what to do and why.
Written by
