There is a particular kind of organisational exhaustion that sets in around the third quarter of a difficult year. The team has been working hard — genuinely hard — and yet the results feel thin, the direction feels murky, and someone in a leadership meeting eventually says it: "I think we need to rethink our strategy." The room nods. A consultant gets called. A two-day offsite gets booked. And six weeks later, the new strategy document sits in a shared drive, largely unread, while the same problems quietly reassert themselves. The strategy was never the problem. What most teams are actually suffering from is a decision-making failure — a structural confusion about who decides what, when, and with whose input. Learning to tell the difference between these two distinct ailments is not a semantic exercise. It is, in practice, the difference between spending four months and considerable money on a strategy refresh and spending four hours redesigning a meeting cadence.
The Diagnostic Question You Are Not Asking ¶
When a team feels stuck, the instinct is to look outward — at the market, at competitors, at the product roadmap — and ask whether the direction is right. That is a strategy question, and it is sometimes the correct one. But before you go there, there is a prior question worth sitting with: in the last ninety days, have good ideas inside this organisation died not because they were wrong, but because no one could get a decision made about them? If the answer is yes — and in most organisations it is — you are looking at a decision-making problem wearing a strategy costume. The two are genuinely different things. Strategy is about choice at the level of direction: which markets, which customers, which bets. Decision-making structure is about the plumbing through which all subsequent choices flow. You can have a luminous strategy and watch it rot inside a decision-making system that is too slow, too centralised, or too ambiguous about ownership to act on it.
What a Strategy Problem Actually Looks Like ¶
A genuine strategy problem has a specific texture. The team broadly agrees on how decisions get made — who has authority, what the process is, what a good outcome looks like — but the decisions themselves keep pointing in directions that do not cohere. You approve a new product feature in January that quietly contradicts a pricing decision made in March. You pursue enterprise clients in one business unit while another unit is building a self-serve tool designed to undercut that same customer relationship. The moves are being made cleanly enough; they simply do not add up to a coherent whole. In these cases, the underlying issue is usually one of three things: the strategic priorities were never actually ranked and forced into conflict with each other, the strategy was written at too high a level of abstraction to guide real choices, or the strategy has become genuinely outdated by a shift in conditions that the organisation has not yet named out loud. Any of these warrant serious strategic work — not another mission statement, but a hard conversation about which bets the organisation is actually making and which ones it is implicitly abandoning.
What a Decision-Making Problem Actually Looks Like ¶
A decision-making problem is more common and, in some ways, more quietly corrosive. Its symptoms are recognisable: decisions that were made in a meeting get unmade in the corridor afterwards; the same question keeps returning to leadership because no one at the working level feels empowered to close it; projects stall not at the idea stage but at the approval stage, waiting for a sign-off that never quite arrives. There is a specific pattern worth naming here — the distributed veto, where any one of six stakeholders can block a decision but none of them has the clear authority to make it. Teams in this condition often read their stuckness as a strategy failure because the output of their indecision — slow movement, missed opportunities, contradictory signals to the market — looks from the outside like strategic incoherence. It is not. The strategy may be perfectly sound. What is broken is the mechanism by which the organisation converts that strategy into daily choices. Fixing it does not require a new vision. It requires a RACI, a ruthlessly pruned approval list, and probably a hard conversation about which leaders are holding onto decisions they should be releasing.
A Practical Test: The Decision Audit ¶
One of the most clarifying exercises a leadership team can do takes less than two hours and requires only honesty. Take the last ten significant decisions your organisation made — not announcements, but actual choices that involved trade-offs and meaningful disagreement. For each one, write down: who made it, how long it took from first identification to closure, whether it was revisited after the fact, and whether the outcome matched the strategic priority it was supposed to serve. The pattern that emerges will tell you almost everything. If decisions are being made quickly and with clear ownership but the outcomes keep drifting from stated priorities, you have a strategy problem. If decisions are slow, contested, or frequently reopened — regardless of whether the eventual choices were good ones — you have a decision-making problem. If decisions are both slow and incoherent, you may have both, but it is almost always worth fixing the decision-making structure first. Clarity of process creates the conditions under which strategic clarity becomes possible. The reverse is rarely true.
How to Fix a Decision-Making Structure Without Starting a Politics War ¶
The resistance to decision-making reform is rarely intellectual — most leaders will agree in the abstract that decisions should be made faster and with clearer ownership. The resistance is political, because clarifying who decides something is also clarifying who does not decide it, and that subtraction of authority is what makes the work hard. A few principles make it more navigable. First, start with the decisions that are visibly costing the organisation — the ones where delay has a measurable price, in time or money or team morale. These are easier to reform because the case for change is concrete. Second, separate the question of who is consulted from who decides. A decision can involve eight people's input and still be made cleanly by one. What breaks organisations is the conflation of consultation with consent — the implicit assumption that because someone was asked for their view, they have an effective veto over the outcome. Third, once ownership is assigned, protect it. The fastest way to undo a decision-making reform is for senior leadership to quietly override the people they have just empowered. It happens within weeks, usually with good intentions, and it poisons the well for months afterwards.
When You Need to Do Both — and How to Sequence It ¶
Occasionally, and genuinely, an organisation needs both strategic renewal and decision-making reform at the same time. The risk is that attempting both simultaneously produces neither — the strategic conversation gets muddied by process debates, while the process redesign lacks the strategic context to prioritise correctly. The sequencing that tends to work is this: spend the first four to six weeks on the decision-making structure alone, with a narrow and explicit scope. Get clear on who owns what categories of decision, at what threshold does something escalate, and what the review cadence looks like. Then, once the plumbing is in order, bring the strategy question into the newly functioning system. You will find that strategic conversations become dramatically more productive when they happen inside an organisation that has recently demonstrated it can actually make and hold decisions. The act of fixing the process is itself a trust-building exercise, and that trust — between leadership and the working levels of the organisation — is the precondition for serious strategic thinking.
The Deeper Discomfort This Diagnosis Surfaces ¶
There is a reason teams reach for the strategy problem even when the evidence points clearly to decision-making. Strategy work feels expansive — it is visioning and possibility and the imagined future. Decision-making reform is narrow, operational, and often uncomfortable, because it requires leaders to explicitly name the limits of their own authority and to tolerate decisions being made without them. There is also a cultural dimension that is worth naming honestly: in many organisations, involvement in decisions is itself a form of status. The executive who is consulted on everything is, in a legible social sense, more important than the one who is consulted only on the things that genuinely require their perspective. Asking people to give that up — even in the service of organisational effectiveness — is asking them to accept a reduction in visible status. That is not a strategy conversation. It is a culture conversation, and it is usually the conversation that actually needed to happen all along.
The whiteboard full of strategic frameworks is not the problem, and it is not the solution. Before the next offsite, before the next consultant engagement, before the next strategy deck gets built, ask the simpler and harder question: does this organisation know how to make a decision and hold it? If the answer is uncertain, start there. Everything else — the strategy, the roadmap, the ambitions — will follow more cleanly than you expect.