Most leaders don't have a decision problem. They have a clarity problem. I've sat across the table from executives paralysed over calls that were, underneath the noise, actually simple — and I've watched other leaders move fast and wrong because they mistook speed for conviction. Good decision-making isn't a personality trait. It's not something you're born with. It's a discipline you build, deliberately, the same way you'd build a habit in the gym.
Here's my actual position, and it cuts against most of what gets written on this topic: the quality of a leader's decisions has almost nothing to do with how smart they are, and almost everything to do with how honestly information reaches them. I've coached leaders with formidable intellects who made consistently poor calls — not because they reasoned badly, but because nobody around them was willing to tell them the truth. And I've coached leaders of average analytical horsepower who outperformed their more brilliant peers because they built teams that pushed back. Intelligence is overrated in this conversation. Structure is underrated.
So this isn't a listicle of decision-making "best practices" — the kind you've read a dozen times, that could apply to anyone, in any role, in any decade. This is what I actually tell the leaders I work with, including where the conventional advice gets it wrong.
How I evaluate a leader's decision-making — the four questions I actually ask
- Who's allowed to disagree with you, and have they, this month?: If nobody has pushed back on you in weeks, that's not evidence you're right. It's evidence people have stopped bothering. I treat an absence of dissent as a red flag, not a green one.
- Is this decision reversible?: I split every decision in two: cheap-to-reverse and expensive-to-reverse. Leaders who apply the same amount of deliberation to both are wasting their best thinking time on decisions that don't deserve it, and rushing the ones that do.
- Are you deciding, or are you ratifying?: A huge number of "leadership decisions" are actually the leader rubber-stamping whatever was pre-agreed in the corridor before the meeting. That's not decision-making. It's theatre. I ask leaders to name, honestly, which of their recent calls were real.
- What would you have to see to change your mind?: If a leader can't answer this before they decide, they've already decided — and everything after that is confirmation-seeking dressed up as analysis. I ask for the answer in writing, before the decision, not after.
- Who pays if this goes wrong, and do they know it's coming?: Decisions made without naming who absorbs the downside tend to be decisions nobody truly owns. I want a name attached before the call is made, not after it's gone badly.
Choose the process, don't inherit it
Every leader has a default decision-making style, usually shaped by whatever worked earlier in their career. Some default to data and logic. Some default to gut instinct built on pattern recognition from years in the role. Neither is wrong — but applying your default indiscriminately, regardless of the situation, is where leaders get into trouble. A leader who is naturally analytical needs to notice when a decision calls for speed and intuition instead of another round of modelling. A leader who trusts their gut needs to notice when the stakes demand slower, more rigorous scrutiny. The skill isn't having a good default. It's knowing when to override it.
I see this most clearly with founders who scale into larger organisations. The instinct-led style that got them from zero to fifty people is precisely the style that starts producing expensive mistakes at five hundred — because the decisions have changed shape even though the leader hasn't. Early on, most calls are cheap to reverse and the person deciding has direct, first-hand context. Later, the same leader is deciding on markets they've never operated in, based on secondhand information, with consequences that take a year to become visible. Recognising that the terrain has shifted under you, and adjusting your process accordingly, is a specific, learnable skill — and one that most leaders never consciously practise, because nobody tells them the rules have changed.
Input isn't consensus, and conflating the two is a mistake
Leaders are told to "get input from others," and most take that to mean surveying the room until a comfortable majority view emerges. That's not input — that's outsourcing the decision to avoid owning it. Real input means actively seeking out the person most likely to disagree with your instinct, particularly subject matter experts who see risks you don't, and asking them directly rather than waiting for them to volunteer a dissenting view in a meeting where silence is the safer option. I tell leaders: if you can't name the person on your team most likely to tell you that you're wrong, you don't have real input — you have an echo chamber with extra steps.
Weigh the consequences before you weigh the options
Most decision frameworks ask leaders to list options first and consequences second. I run it backwards. Before comparing choices, name the worst plausible outcome of getting this wrong, and decide whether the organisation can absorb it. That single question reframes almost every decision. Some choices that feel urgent turn out to be low-stakes once you've named the downside honestly — which frees you to decide faster. Others that feel routine turn out to carry real exposure, and deserve more scrutiny than the leader was initially giving them. Naming the worst case isn't pessimism. It's the fastest way I know to correctly size a decision, and it also forces the pre-mortem question every executive team should be asking but rarely does: if this fails in six months, what will the post-mortem say we ignored today?
Defend it, don't just announce it
A decision without a stated rationale is an instruction, not leadership. Leaders should expect — and welcome — being asked to explain their reasoning. Communicating the "why," not just the "what," is what sustains an aligned team through the discomfort of implementation. This matters more the higher the stakes: teams will execute a decision they disagree with far more effectively if they understand the reasoning behind it than if they're simply told what to do. Transparency here isn't a soft skill. It's the mechanism that keeps the decision from quietly unravelling three weeks later when the first obstacle appears and people start asking, privately, whether leadership actually thought this through.
Set a deadline, and mean it
Indecision is itself a decision — it just delegates the outcome to whoever moves fastest, which is rarely the wisest party in the room. Leaders should set a clear deadline for when a decision will be made and stick to it, treating the deadline as a forcing function that ensures competing priorities get resolved rather than left to drift. Being open to new information afterwards is not the same as leaving the decision perpetually open. Good leaders can hold both: commit on schedule, and revise if genuinely new information demands it. Weak leaders use "staying open to feedback" as a permanent excuse not to commit at all — and their teams learn, quickly, to stop bringing them decisions that require an actual answer.
Guiding values are a filter, not a slogan
Every leader claims to have guiding principles. Few actually use them to filter decisions before they're made — most only reach for them afterwards, to justify a call they'd already settled on instinctively. Used properly, an organisation's stated values and mission should function as a pre-decision filter: does this option even qualify for consideration, given what we say we stand for? Applied consistently, that filter does something more useful than aligning language — it narrows the option set before the harder analytical work even begins, which saves time, reduces the number of options a leader has to weigh in detail, and produces more defensible outcomes when someone later asks why a particular path was chosen.
A decision matrix earns its keep on the hard calls
For genuinely difficult, multi-variable decisions, a simple weighted matrix — listing options against the criteria that actually matter, scored and weighted by importance — forces a kind of honesty that unstructured debate doesn't. It exposes when a leader's preferred option is winning on charisma rather than merit, because the numbers on the page don't care who argued the loudest in the room. I don't recommend this for every decision; using a matrix for routine calls is overkill and slows the organisation down without adding useful rigour. But for the decisions that will define a quarter or a year, the fifteen minutes it takes to build one is well spent, and it gives the leader a defensible artefact to point back to later.
The part most leaders skip is agreeing the weighting before they see how each option scores. Set the criteria and their relative importance first, lock them, and only then fill in the scores. Do it the other way round — score first, weight second — and you'll find the weighting mysteriously shifts until it produces the answer the leader already wanted. That's not a hypothetical. I've watched it happen in the room, in real time, more than once. The matrix only earns its keep as an honesty device if the leader commits to the criteria before they know which option wins.
How Do You Improve Executive Team Decision Making?
Executive team decision making improves when three things change: clarity on who owns which decisions, conditions that allow better information into the room, and a team culture that can withstand genuine disagreement. Most executive teams struggle with decision quality not because leaders lack intelligence but because the structure of the team discourages honesty — senior leaders defer to the CEO, junior executives protect their function, and dissent is professionally risky. Improving decision quality requires explicit decision-right frameworks (which decisions need the whole team, which do not), deliberate practices for surfacing dissent (pre-mortems, anonymous polling, red-team advocates), and a CEO who models intellectual humility by actively inviting challenge rather than treating disagreement as a loyalty test.
The distinction I actually want you to take from this
If you remember one thing from this article, make it this: decision quality is a property of the system around the leader, not a property of the leader's intellect. I say this to every executive team I work with, and it usually lands uncomfortably, because it's much more flattering to believe your organisation's decisions are only as good as your smartest person's judgement. They're not. They're only as good as the worst piece of information that gets deliberately withheld from the room.
That's why I don't start executive coaching engagements by teaching decision frameworks. I start by mapping who tells the truth to whom, and where that breaks down. Frameworks are useful once the information flow is honest. Applied to a dishonest information environment, they just make bad decisions look more rigorous — a decision matrix built on flattering inputs is still a bad decision, dressed up with a spreadsheet and a false sense of precision.
So the ownable claim, the one I'd defend in any room: you cannot coach your way to better decisions by working only on the leader. You have to work on the conditions the leader decides inside — who's rewarded for disagreeing, how fast bad news travels upward, and whether reversing course is treated as weakness or as competence. Fix those conditions and average leaders start making good calls. Leave them broken and your best leader will still, eventually, get it wrong, no matter how good their personal judgement is.
That's the whole of my method, stated plainly: I don't fix decisions. I fix the conditions decisions are made in. Everything else in this article — the frameworks, the deadlines, the matrices — is downstream of that one distinction, and none of it works reliably until the information reaching the leader is honest.
Do you need executive coaching? Stuart Andrews can help you and your team with effective and efficient decision-making. We help executives and business leaders drive successful initiatives while their teams consistently perform at the highest level.
Get your copy of “The Leadership Shift” now to help you orchestrate successful transformations.
Further reading: 10 Essential Characteristics for Successful Leaders, How to Train and Align Emerging Leaders Across Departments, The Importance of Training New Leaders and How to Do So