why completed projects often fail to deliver value
Most organisations are good at delivering projects. Many are much less effective at realising the value those projects intended to create. This distinction matters more than it first appears.
Many are much less effective at realising the value those projects were intended to create.
This distinction matters more than it first appears.
A project can be delivered on time, within budget, and exactly to specification. The agreed output can be produced. The final report can be completed. The project team can be congratulated and disbanded. And yet, months later, the organisation may still be asking a simple question:
And yet, months later, the organisation may still be asking a simple question:
What actually improved?
This is an uncomfortable question because it challenges a widely held assumption that successful delivery automatically leads to successful outcomes.
In practice, it rarely does.
The completion illusion
Most organisations place significant emphasis on delivery. Delivery is visible. Progress can be measured, milestones can be tracked, budgets can be monitored. Governance can be applied. Success can be formally declared. All of this is important.
The difficulty begins when delivery becomes a proxy for value. A new system is implemented; a training programme is completed. A process is redesigned. A project reaches its planned conclusion.
The organisation sees evidence of activity and assumes value will naturally follow. Sometimes it does, but often it does not.
The project may have created capability, but capability alone does not guarantee benefit.
The gap between capability and value is where many organisations quietly lose the return they expected from their investment.
Delivery creates capability
One of the most useful distinctions senior leaders can make is understanding that projects generally create capability, not value. A project delivers the ability to do something differently. It does not automatically ensure that different behaviour occurs. A new customer relationship management (CRM) system, for example, creates the capability for improved customer management. A training programme creates the capability for improved performance. A redesigned process creates the capability for greater efficiency.
None of these outcomes are guaranteed. The project creates the possibility of improvement. The organisation must still turn that possibility into a reality. This is where value is either realised or lost.
Behaviour is the bridge
There is a simple relationship that sits behind success change initiatives. Capability leads to behaviour, which in turn, leads to value. The capability may already exist. The challenge is whether people behave differently because of it. An organisation may invest in extensive training to remove operational bottlenecks. The project can be delivered exactly as planned. Staff can attend sessions. Materials can be completed. Competency assessments can be passed. Delivery is achieved.
But if teams continue working in the same way, making the same decisions, and following the same habits, the bottlenecks remain. The capability exists, however, the value does not. The missing link is behaviour.
This is one reason that realised value often arrives much later than delivery. Behavioural change takes time. Habits need to adapt. Processes need to stabilise. New ways of working need to become normal rather than exceptional.
Without this transition, successful delivery simply creates unused potential.
Why value disappears
Most value does not disappear through major failure. It leaks away. Small assumptions accumulate. Accountability becomes unclear. Attention moves elsewhere. Benefits are assumed rather than verified. The project concludes and everyone moves on to the next priority.
Meanwhile, the expected value remains largely undecided. This happens because project structures are usually designed to deliver outputs rather than project benefits. The project team is accountable for producing something.
Very few people are accountable for ensuring the organisation obtains the value that justified the investment in the first place. This creates a predictable gap. The work is completed. The benefit remains unowned.
Project ownership is not benefit ownership
One of the most overlooked questions in any initiative is: Who owns the benefit?
Many organisations can immediately identify the project owner. They know who approved the work, who managed delivery, who controlled the budget, and who reported progress.
Far fewer can identify who owns the outcome. This matters because ownership often ends too early. The project manager delivers the work. The sponsor signs off the completion. The project team celebrates success. The expected benefit is left to emerge on its own. Sometimes it does. Frequently it does not. At principal level, this distinction is critical. The project owner is not the benefit owner.
The person accountable for delivering the project is not the person accountable for the value of the project. Until someone owns the benefit, value remains a vulnerability.
Measuring the wrong thing
Another common source of value loss is measurement. Organisations naturally track what is easily seen. Training sessions delivered, system users onboarded, processes completed, the number of projects closed.
These measurements are useful, but they are measurements of activity. They do not necessarily indicate whether value has been realised.
For example, the training delivered does not prove that throughput has improved. System implementation does not prove that the customer experience has improved. Process redesign does not prove efficiency improvement.
These activity measures tell us whether something happened, they do not tell us whether the original objective was achieved. The distinction is subtle but important.
Value emerges when the organisation behaves differently and obtains a different result. Anything less is evidence of activity, not evidence of activity, not evidence of benefit.
Why organisations celebrate too early
One reason value is often overlooked is that delivery creates a visible moment of completion. Humans naturally prefer closure. Projects provide exactly that. A clear finish line, a clear report, a clear success declaration. Benefits rarely behave in the same way.
Value tends to emerge gradually. It develops through improved decisions, better behaviours, stronger performance, and reduced waste over time.
This means value is quieter than delivery. And because it is quieter, it often attracts less attention.
The organisation celebrates the completion of the work while paying little attention to whether the promised outcome materialises.
That creates a dangerous gap between effort and result.
The practical test
A simple test exposes whether value is genuinely being realised:
A benefit is not real until the organisation behaves differently because of it.
This shifts the conversation immediately.
Instead of asking:
· Was the project delivered?
· Was the budget controlled?
· Were the milestones achieved?
The organisation asks:
· What is being done differently?
· What has measurably improved?
· What problem has been reduced?
· What value is now visible that was not visible before?
These questions move attention away from completion and towards consequence.
That is where value lives.
The role of leadership
Senior leaders often assume value appears automatically once delivery is complete. In reality, value usually requires active attention. It requires benefit ownership, it requires monitoring of outcomes rather than activity, it requires a willingness to revisit assumptions and confirm that expected improvements are emerging. Most importantly, it requires recognising that projects do not create value directly. Projects create capability. People create value through the way that capability is used.
Conclusion
Many organisations are highly effective at delivering projects. Far fewer are equally effective at realising benefits. The difference often comes down to one simple misunderstanding. Completion is treated as success. It is not. Successful delivery creates the opportunity for value. Value only emerges when behaviour changes and outcomes improve. That is why completed projects can still fail economically. The project may be finished. The work may be complete. The capability may exist. But until the organisation behaves differently because of it, the value remains unrealised.
Projects create capability.
People create value.
Why waiting is rarely free
Most organisations understand the cost of action.
Far fewer understand the cost of waiting.
When a significant decision is proposed, the costs are usually visible immediately. There may be financial investment, disruption, management attention, implementation effort, or short-term risk. These costs can be identified, discussed, challenged, and measured.
Because they are visible, they become the focus of the conversation.
Waiting, by contrast, often appears cost-free.
Nothing changes. No money leaves the organisation. No difficult implementation begins. No commitment has to be made. The problem remains where it is, and the decision can be revisited later.
At least, that is how it appears.
In reality, waiting is rarely free. It simply presents its costs differently.
The absence of action is still a decision. Like every decision, it creates consequences.
Why delay feels responsible
One reason delay is so common in senior environments is that it often feels prudent.
Leaders are expected to be careful. They are expected to avoid unnecessary risk and challenge assumptions before committing resources. There is genuine value in thoughtful decision-making, particularly when the consequences are significant.
The difficulty arises when caution becomes comfortable.
A decision that is delayed for legitimate reasons can be sensible. A decision that is delayed because nobody wants to commit is something else entirely.
The distinction is rarely obvious at the time.
Additional analysis feels responsible. Waiting for more information feels sensible. Deferring a decision until the next budget cycle appears disciplined.
Each of these reasons may be valid.
The problem is that delay itself is rarely neutral.
While a decision is being postponed, the conditions that created the need for the decision continue to exist. Problems do not pause while organisations think about them.
They continue to generate cost.
The hidden costs organisations overlook
Most delay costs are not recorded in obvious places.
They appear indirectly.
Operational inefficiencies remain embedded. Bottlenecks continue to restrict flow. Work-in-progress accumulates. Customers experience the same service problems. Rework continues. Teams create workarounds.
Because these costs arrive gradually, they are often accepted as normal.
The organisation becomes familiar with them.
This familiarity creates a dangerous illusion. Costs that are experienced every day stop attracting attention. They disappear into the background while the proposed solution receives intense scrutiny.
The visible cost is challenged.
The existing cost is tolerated.
Over time, this reverses the way decisions should be evaluated.
The proposed action appears expensive because it is new, visible, and measurable.
The cost of doing nothing appears cheap because it is familiar.
Neither perception is necessarily accurate.
A familiar example
Consider an organisation experiencing recurring operational bottlenecks.
Work accumulates. Delivery dates are becoming less predictable. Staff spend increasing amounts of time managing exceptions rather than improving flow. Customers are becoming frustrated.
A proposal is made to invest in training.
The cost is immediately visible:
investment in training delivery
time away from productive work
management effort
short-term disruption
These costs become the focus of discussion.
Questions quickly emerge:
Can the training wait?
Is there a cheaper option?
Should we revisit this next quarter?
Do we really need to act now?
All reasonable questions.
What is often missing is an equivalent examination of the alternative.
What happens while the decision waits?
The bottleneck remains.
Work-in-progress continues to grow.
Delivery uncertainty persists.
Customer confidence weakens.
Staff continue operating in an inefficient environment.
In other words, the organisation continues paying.
It is simply paying in a form that is less visible than a training budget.
Why leaders underestimate the cost of delay
Human beings tend to give greater weight to immediate, visible costs than to future or distributed ones.
Organisations are no different.
A £50,000 investment attracts attention because it appears in a budget.
The cumulative impact of reduced productivity, avoidable rework, and delayed delivery rarely receives the same scrutiny, even when the total effect is greater.
This is one reason why some organisations become trapped in cycles of recurring problems.
Each proposed intervention appears expensive in isolation.
Each delay appears harmless in isolation.
Over time, however, the organisation repeatedly chooses the cost of waiting.
The total becomes significant, even though none of the individual decisions looked particularly consequential.
The result is a business that feels busy, works hard, and remains stuck.
Delay is a decision
One of the most useful shifts in commercial judgement is recognising that delay is not the absence of a decision.
Delay is a decision.
It has an owner.
It has consequences.
It creates winners and losers.
It changes outcomes.
When viewed in that way, delaying an important choice becomes something that must be justified in exactly the same way as taking action.
This does not mean every decision must be accelerated.
Some delays are entirely legitimate.
Information may genuinely be incomplete. Dependencies may need to be resolved first. Timing may make implementation unrealistic.
The key point is that delay should be evaluated with the same discipline as action.
Both create consequences.
Both carry risk.
Both consume resources.
The cost of waiting is often the real business case
Many business cases focus heavily on the benefits of action.
They describe efficiency gains, reduced risk, higher revenue, improved customer experience, or stronger operational performance.
All of these are relevant.
But experienced leaders often look for something else.
They ask:
What happens if we do nothing?
This is frequently where the real business case emerges.
Not because the proposed solution becomes more attractive, but because the current situation becomes easier to understand.
The true comparison is rarely:
Cost versus no cost.
More often it is:
Cost of action versus cost of inaction.
Once that comparison becomes visible, many decisions become clearer.
Why this matters for non-finance leaders
Many non-finance leaders assume that financial thinking requires detailed models, forecasts, and spreadsheets.
Sometimes those things are necessary.
Often they are not.
The most important financial question is frequently much simpler:
What is the economic consequence of waiting?
Answering that question requires curiosity more than technical knowledge.
Where is money being trapped?
What inefficiencies are persisting?
What opportunities are being missed?
Which risks are increasing?
What becomes harder if we wait another month?
These are commercial questions, not accounting questions.
And they are often the difference between a decision that appears expensive and one that is clearly worthwhile.
The test
A simple test makes delay visible:
If waiting has no meaningful consequence, it is probably not an important decision.
The reverse is also true.
If waiting creates increasing cost, increasing complexity, or increasing risk, then delay is already affecting the outcome.
Whether the organisation recognises it or not.
Conclusion
Many organisations are highly disciplined when evaluating the cost of action.
Fewer apply the same discipline to the cost of waiting.
That imbalance creates predictable behaviour. Visible costs are challenged. Hidden costs accumulate. Important decisions remain unresolved while the underlying problem continues to generate consequences.
The reality is straightforward.
Waiting is not the absence of a decision.
Waiting is a decision with consequences.
The cost of delay is still a cost.
And in many cases, it is far larger than people realise.
finance is not about numbers. it is about consequences
Finance is often treated as a specialist language.
For many non‑finance leaders, it can feel like a world of accounts, spreadsheets, ratios, models, forecasts, and terminology that belongs somewhere else. Finance becomes something to consult after the decision has been shaped, or something that arrives late in the process to challenge, constrain, or approve.
That separation is understandable. It is also expensive.
At senior level, finance is not just about numbers. It is about understanding the economic consequences of decisions.
A decision may be operational, commercial, strategic, or organisational. But once it is made, it will almost always have financial consequences. It will affect cost, revenue, cash, capacity, risk, or the way resources are tied up in the business.
The question is not whether a decision is “financial”.
The question is whether its financial meaning has been understood.
Finance translates decisions into consequence
It begins with a simpler question:
What happens economically if we do this — and what happens if we do not?
That question changes the conversation.
A decision to invest in training, for example, may not look financial at first. It may be described as an operational decision, a capability decision, or a people decision. But if the purpose of the training is to remove bottlenecks, improve throughput, reduce work‑in‑progress, and make delivery more predictable, then the financial implications are immediate.
Better throughput can improve revenue stability.
Lower work‑in‑progress can reduce cash tied up in the system.
Less rework can reduce cost.
More predictable delivery can improve customer confidence.
The decision is still operational in form.
But its consequences are financial.
This is the first shift non‑finance leaders need to make. Finance is not separate from the decision. It is one way of understanding what the decision will actually do.
Good financial thinking does not need to begin with a spreadsheet.
It begins with a simple question:
Finance is not about numbers. It is about consequences.
Finance is often treated as a specialist language.
For many non‑finance leaders, it can feel like a world of accounts, spreadsheets, ratios, models, forecasts, and terminology that belongs somewhere else. Finance becomes something to consult after the decision has been shaped, or something that arrives late in the process to challenge, constrain, or approve.
That separation is understandable. It is also expensive.
At senior level, finance is not just about numbers. It is about understanding the economic consequences of decisions.
A decision may be operational, commercial, strategic, or organisational. But once it is made, it will almost always have financial consequences. It will affect cost, revenue, cash, capacity, risk, or the way resources are tied up in the business.
The question is not whether a decision is “financial”.
The question is whether its financial meaning has been understood.
What happens economically if we do this — and what happens if we do not?
That question changes the conversation.
A decision to invest in training, for example, may not look financial at first. It may be described as an operational decision, a capability decision, or a people decision. But if the purpose of the training is to remove bottlenecks, improve throughput, reduce work‑in‑progress, and make delivery more predictable, then the financial implications are immediate.
Better throughput can improve revenue stability.
Lower work‑in‑progress can reduce cash tied up in the system.
Less rework can reduce cost.
More predictable delivery can improve customer confidence.
The decision is still operational in form.
But its consequences are financial.
This is the first shift non‑finance leaders need to make. Finance is not separate from the decision. It is one way of understanding what the decision will actually do.
The three lenses that matter
There are many ways to describe financial performance, but senior decision‑making often begins with three simple lenses:
· profit
· cash
· capital
These are not accounting abstractions. They are practical ways of seeing whether a decision strengthens or weakens the business.
Profit asks whether the decision improves the relationship between revenue and cost.
Cash asks when money moves, and whether the decision releases or traps it.
Capital asks where resources are tied up, and whether they are being used well.
A bottleneck in production, for example, is not only an operational inconvenience. It may mean work sits unfinished for longer. That work may consume labour, materials, management attention, and cash before it creates value. The business may still be busy, but money is trapped inside the system.
Seen through an operational lens, this is a flow problem.
Seen through a financial lens, it is also a capital efficiency problem.
Both views are true. The financial view simply makes the consequence clearer.
Cost is visible. Impact is often hidden.
One reason financial conversations become distorted is that cost is usually visible before value is.
Cost appears quickly. It has a number. It can be approved, challenged, reduced, delayed, or rejected.
Impact is different.
Impact often emerges over time. It may appear to be higher reliability, fewer mistakes, shorter lead times, better customer retention, less rework, or more stable workload. These effects matter, but they are less immediately visible than the cost of acting.
That imbalance creates predictable behaviour.
When the cost is clear, but value is not, the decision will be challenged.
The challenge may sound like financial discipline:
· “Isn’t this expensive?”
· “Can we delay it?”
· “Is there a cheaper option?”
· “Can we do less for now?”
Those are legitimate questions. But they become dangerous when they are asked before the value has been framed properly.
A decision cannot be judged only by what it costs. It must also be judged by what it prevents, enables, releases, or protects.
The hidden cost of doing nothing
One of the most useful financial disciplines for non‑finance leaders is learning to compare the cost of action with the cost of inaction.
Too often, only one side of that comparison is visible.
The cost of action is usually obvious. It may include spend, disruption, time, temporary productivity loss, or management attention.
The cost of inaction is often harder to see. It may include delay, instability, duplicated work, missed revenue, rising work‑in‑progress, avoidable rework, customer dissatisfaction, or additional pressure on already stretched teams.
Because the cost of inaction is less visible, it is often treated as if it does not exist.
That is a mistake.
Doing nothing is rarely free. Delaying a decision is rarely neutral. Choosing not to invest may avoid immediate spend, but it may also allow the underlying problem to compound.
In financial terms, the business may still be paying. It is just paying in a less visible currency.
Cheap decisions are not always efficient decisions
This is where many organisations confuse cost control with economic judgement.
A cheap decision can be sensible. But a decision is not good because it is cheap. It is good if it produces the intended outcome at an acceptable level of cost, risk, and consequence.
There is a difference between reducing cost and creating value.
Reducing the scope of training may lower immediate spend. But if the bottleneck remains, the business may continue paying through delayed delivery, avoidable overtime, rework, and customer frustration.
Delaying investment may protect cash in the short term. But if the delay extends instability, increases work‑in‑progress, or reduces revenue confidence, the apparent saving may be temporary.
A financially mature conversation does not ask only:
“What will this cost?”
It also asks:
“What will this cost us if we do not act?”
That second question is often where the real economics of the decision appear.
Finance should clarify, not intimidate
Finance is most useful when it helps leaders see the consequences of choices more clearly.
It becomes less useful when it intimidates the conversation, narrows it too early, or makes non‑finance leaders feel that judgement must pause until a spreadsheet is complete.
There is a place for modelling. There is a place for detailed financial analysis. There is a place for forecasts, sensitivities, and investment cases.
But those are not always the starting point.
The starting point is often much simpler:
· What outcome are we trying to create?
· What economic effect should follow?
· What hidden cost are we currently tolerating?
· What is the cost of acting?
· What is the cost of not acting?
Those questions create financial clarity without requiring technical complexity.
They also prevent the most common failure: treating finance as a late-stage approval mechanism rather than an early-stage decision lens.
Financial literacy is really decision literacy
For non‑finance leaders, their aim is not to become accountants.
The aim is to think clearly about the consequences.
A leader does not need to build the model personally to understand the economic shape of a decision. They do need to understand enough to ask better questions, challenge false economies, and avoid mistaking visible cost for total cost.
That is the practical value of financial literacy.
It helps leaders connect operational reality to economic consequence. It helps them see whether a decision improves profit, releases cash, uses capital better, reduces waste, or protects future value.
Most importantly, it helps them hold a decision steady when cost pressure rises.
Because when value is unclear, leaders are forced to defend cost.
When value is clear, cost can be judged in context.
The test
A simple test exposes whether a decision has been financially understood:
If you cannot explain the economic effect of the decision, the decision is not fully understood.
This does not mean every decision needs a full financial model before it can proceed.
It means the relationship between action and consequence must be clear enough to support judgement.
What changes if we act? What persists if we do not? Where does cost show up? Where does value appear? What becomes more stable, more efficient, or less wasteful?
If those questions cannot be answered in plain language, the financial thinking is not yet clear.
Conclusion
Finance is not separate from decision‑making. It is one of the ways decisions become real.
Numbers matter, but they are not the point. The point is the consequence.
A decision that looks sensible operationally but cannot explain its economic effect is incomplete. A decision that looks expensive but prevents greater hidden cost may be the better choice. A cheap decision that leaves the underlying problem untouched may be expensive in everything but name.
Finance should not dominate decisions. It should clarify them.
At senior level, that is the real purpose of financial thinking: not to make decisions more complicated, but to make their consequences harder to ignore.
What I have learned about senior decisions
What I’ve learned about senior decisions (without frameworks)
Most senior decisions do not fail because intelligent people are involved. They fail because intelligent people are operating under pressure, with incomplete information, mixed incentives, and too many things competing for attention at once.
That is not a criticism. It is simply the environment in which senior decisions are made.
Over time, I have become less interested in how decisions are described in theory and more interested in how they actually behave in practice: what causes them to become clearer, what causes them to drift, and why some survive while others quietly disappear.
The longer I work around senior teams, the more I return to a simple conclusion: good decision‑making is rarely about having more material, more options, or more process. More often, it is about removing what is unnecessary, holding what matters steady, and being clear about what the decision is really for.
That sounds simple. In practice, it is not.
Decisions usually become unclear before they become wrong
One of the more common errors in organisations is the assumption that poor outcomes must have come from poor decisions. Sometimes that is true. Often it is not.
Many decisions are sound when they are taken. The logic is reasonable. The intent is clear. The discussion has been thorough. The decision may even have broad support.
The problem is what happens next.
A decision starts to lose shape long before it is formally reversed. New concerns are introduced. Exceptions are made. Workarounds appear. Additional context is brought in “for completeness”. A decision that was previously bounded becomes more open to interpretation.
At no point does anyone necessarily say, “We are changing the decision.” Yet the decision changes anyway.
This is one of the most important things I have learned: senior decisions do not usually fail dramatically. They drift, soften, and fragment. By the time the organisation notices something is wrong, what has been lost is not only momentum, but clarity.
The damage often begins when people stop protecting the decision frame.
Too many options rarely improve a senior discussion
There is a persistent belief in organisations that better decisions come from seeing more options. On the surface, this feels sensible. A broad option set suggests rigour, openness, and diligence.
In practice, too many options often do the opposite.
They diffuse attention. They encourage false balance. They make it easier to avoid choosing because the discussion can remain broad, nuanced, and unfinished. A meeting can feel thorough while still producing no real movement.
What I have seen repeatedly is that senior teams do not usually need more options. They need more confidence in removing weaker ones.
That requires judgement. It also requires restraint.
Presenting three credible options that genuinely deserve airtime is useful. Presenting eight theoretical possibilities often looks responsible while quietly avoiding the real work. The work is not to collect all conceivable choices. The work is to decide which choices are mature enough, relevant enough, and consequential enough to deserve discussion now.
That distinction matters more than most people realise.
Timing matters more than people admit
Another lesson that becomes increasingly important at senior level is that the quality of a decision depends not just on what it is, but when it is being made.
Some decisions are expensive because they are delayed too long. Others are expensive because they are taken too early.
The second category is often harder to spot.
Early decisions can look decisive. They reduce uncertainty. They create movement. They reassure stakeholders that leadership is “doing something”. This is one reason premature commitment is so attractive under pressure.
But a decision taken before the relevant constraints are understood, before the variability in the system has stabilised, or before dependencies are visible often creates more cost than it removes. It has to be revisited later, worked around, or quietly undone. The organisation then pays twice: once for the original decision, and again for correcting it.
That is why I have become increasingly cautious of urgency when it is expressed without a clear explanation of value.
Delay is not always a failure of nerve. Sometimes it is the correct expression of judgement.
Agreement is not the same as ownership
A surprising number of decisions fail after they appear to have been made successfully.
The room agrees. Heads nod. The conclusion is recorded. In principle, the matter is closed.
And yet little changes.
This is often explained away as weak execution. Sometimes that is true. More often, the more immediate cause is that accountability was assumed rather than made explicit.
Agreement is not ownership.
A decision without a clearly accountable owner is not secure, no matter how clearly it was articulated in the room. When progress stalls, ambiguity returns quickly. People begin to ask who is responsible for moving it forward, for defending it when challenged, and for answering when the intended outcome does not materialise. If no one can answer those questions in plain language, the decision was never as settled as it first appeared.
At principal level, this matters enormously. Many organisations mistake consensus for commitment. They are not the same thing.
People do not follow decisions — they follow incentives
One of the more uncomfortable truths of senior decision‑making is that decisions do not exist in clean air. They live inside systems of incentives, pressures, targets, local priorities, and personal exposure.
That means behaviour will rarely align with the decision simply because the decision was agreed.
People behave in line with what they are measured on, rewarded for, or protected from. If those incentives pull in a different direction from the decision, the decision will weaken, even if nobody openly opposes it.
This is not a moral failure. It is a structural reality.
A sales leader may support an operational improvement in principle, but still prioritise short‑term revenue. A finance leader may understand the logic of investment, yet remain under pressure to reduce visible spend. A local manager may agree with the strategic direction, while still protecting local continuity over broader change.
The organisation may sincerely believe it is aligned. The incentives, however, tell a different story.
This is why so many good decisions drift. They are not broken by argument. They are pulled off course by competing incentives that were never made visible.
Cost is usually clearer than value
Senior conversations often become distorted when money enters the room.
A proposed decision may make perfect sense in operational or strategic terms, but once cost is raised, the conversation can change completely. It becomes less about what the decision will produce and more about what it will cost now.
This is understandable. Cost is visible, immediate, and measurable. Value is often slower, broader, and more dependent on conditions. When the value of a decision is not clear enough, cost becomes the dominant signal by default.
That is when false economies appear.
An organisation delays a necessary intervention because it seems expensive. It cuts a decision back to reduce immediate spend. It chooses the cheaper path because the visible outlay is smaller.
And then it pays in another form: instability, rework, delay, poor service, or unresolved structural waste.
One of the most useful shifts in senior work is learning to make the value of a decision clearer than its cost. Not with theatre, not with inflated benefit claims, but with calm, credible explanation of what the decision changes and what happens if nothing changes at all.
Reporting is not assurance
There is another category error that appears often in organisations, particularly after a decision has been made: the assumption that measuring activity is enough to show the decision is working.
It is not.
A dashboard can confirm that work is being done. It can show sessions delivered, plans completed, milestones achieved, meetings held, or initiatives launched. What it often cannot show is whether the decision has improved the thing it was taken to improve.
That is the difference between reporting and assurance.
Reporting shows activity. Assurance shows whether the decision is actually working.
This distinction matters because senior leaders are often flooded with visibility and still left uncertain about whether a decision should stand, be adjusted, or be challenged. More measurement does not necessarily increase control. It can just as easily increase noise.
The same rule appears again: what matters is not quantity of information, but whether it sharpens judgement.
The lesson underneath all of this
If I had to reduce what I have learned about senior decisions into one observation, it would be this:
Good decisions are rarely the result of having more.
They are usually the result of removing what weakens the decision.
That may mean:
removing options
removing scope
removing assumptions
removing unnecessary reporting
removing the illusion that more visibility is the same as more control
The work is not to make decisions feel bigger or more comprehensive. It is to make them clearer, more durable, and more capable of surviving contact with reality.
That requires discipline. It requires judgement. And increasingly, I think it requires a willingness to be quieter than many organisations are comfortable with.
The most reliable senior decision‑making I have seen is not dramatic. It does not rely on theatre, constant reinforcement, or an excess of process. It is characterised by clarity, proportion, and consistency. It names what matters, excludes what does not, and resists the pressure to make everything bigger than it needs to be.
Why most dashboards don’t improve decisions
Most dashboards fail for a simple reason:
They show activity, not whether a decision is working.
In many organisations, dashboards are treated as a natural extension of governance. Once a decision is made, measurement follows. Metrics are defined, reports are built, and activity is tracked. Visibility increases. Information becomes readily available. Leadership receives regular updates.
On the surface, this looks like control.
In practice, it often achieves something else.
The organisation becomes more informed about what is happening, but no clearer about whether the original decision has delivered what it was intended to.
That distinction matters.
Activity is easy to measure
Most dashboards begin with what is available.
Activity is visible, countable, and reassuring. It can be presented consistently and tracked over time. It creates a sense of movement and progress.
For example, if an organisation decides to invest in training to remove operational bottlenecks, the dashboard will typically show:
how many sessions have been delivered
how many people attended
how much time has been spent
whether the training programme is on schedule
These metrics are accurate. They are also insufficient. They answer the question, “is the work being done?” They do not answer the question, “Is the decision working?”
That gap is where most dashboards fail.
Outcomes are harder to define
The decision to invest in training was not taken to deliver training. It was taken to change the performance of the system.
If the decision is working, you would expect to see:
throughput stabilising
work‑in‑progress reducing
delivery becoming more predictable
rework declining
These are not measures of activity. They are indicators of effect.
They are also harder to define, and harder to track, because they depend on how the system behaves over time rather than what individuals do in isolation.
As a result, many dashboards give greater weight to activity than to outcome. The organisation becomes confident that work is being completed, without being certain that the underlying decision has achieved anything.
The illusion of control
This is where dashboards become misleading.
The presence of information creates an impression of oversight. Leaders can see what is happening. Reports are reviewed. Exceptions are highlighted. Updates are provided on a regular cadence.
This feels responsible. But visibility is not the same as understanding.
A dashboard can become more detailed, more comprehensive, and more frequently updated without ever answering the critical question, is the decision working?
When that question is not answered clearly, organisations default to a form of passive assurance. They assume that if activity continues and no major issues are reported, the decision must be holding.
This assumption is often wrong.
More metrics do not create clarity
When clarity is low, the instinct is to add more data.
Additional indicators are introduced. More categories are tracked. The dashboard expands to include more perspectives and more detail. The intention is sound: to capture the full picture.
The effect is predictable.
As the number of metrics increases, the ability to interpret them decreases. Signal is lost in volume. Attention fragments. Leaders spend more time reviewing information and less time deciding what needs to change.
A familiar pattern emerges:
More metrics → less clarity
At that point, the dashboard has ceased to support decision‑making. It has become a record of activity.
The missing link: from measurement to action
The fundamental flaw in most dashboards is not the data they contain. It is the absence of a clear link between what is observed and what should happen next.
Measurement, on its own, does very little.
It becomes useful only when it is connected to judgement.
Consider two approaches:
Approach one — reporting:
Throughput is fluctuating
Work‑in‑progress is slightly higher than last month
Rework is broadly unchanged
The information is accurate. It is presented clearly. It may even be discussed in detail.
Nothing changes.
Approach two — assurance:
Throughput unstable → investigate bottleneck re‑emergence
Work‑in‑progress rising → intervene in flow design
Rework unchanged → reassess training effectiveness
The difference is not the data. The difference is that measurement leads directly to action.
This is what distinguishes reporting from assurance.
Assurance is selective by design
At principal level, assurance is not created by measuring more. It is created by measuring less, more deliberately.
The starting point is not the metric. It is the decision.
For any decision, three things must be clear:
What “working” looks like
Which small number of indicators make that visible
What condition would require intervention
Everything else is optional.
This approach produces dashboards that are smaller, simpler, and far more useful. They do not attempt to represent reality exhaustively. They focus attention on what matters enough to change behaviour.
Why simplicity is difficult
Minimal assurance is harder than complex reporting.
It requires leaders to:
define success explicitly
agree what matters most
ignore information that does not change outcomes
act when thresholds are met
There is less room for comfort in this model. There are fewer places to hide behind data. The connection between observation and decision becomes visible.
This is why organisations tend to drift towards complexity. It feels safer to measure more than to decide less.
But complexity does not improve assurance. It weakens it.
The test that reveals failure
A simple test exposes whether a dashboard is doing its job:
If nothing changes when a metric moves, it should not be measured.
This is not a statement about efficiency. It is a statement about purpose.
If measurement does not trigger a decision, an intervention, or a reassessment, it is not supporting governance. It is documenting activity.
What good dashboards actually do
Good dashboards do not look comprehensive. They look focused. They:
make it clear what success looks like
show only the indicators that reflect that success
highlight variance early
connect conditions directly to action
They do not tell the organisation everything that is happening. They tell the organisation what matters enough to respond to.
Conclusion
Most dashboards fail because they are designed to show progress rather than to test whether a decision is working. They make organisations more informed, but not more decisive.
Assurance requires something different. It requires clarity about what matters, restraint about what is measured, and discipline in how measurement is used.
Reporting shows activity. Assurance shows whether the decision is working.
Only one of those improves decision quality over time.
Why cheap decisions are often the most expensive
Most cost challenges in senior decision-making are not really about cost.
They are about uncertainty.
A decision is proposed. The logic is sound. The intent is clear. Then the question appears, almost automatically:
“Isn’t this expensive?”
From that point, the entire conversation shifts. What was a discussion about outcomes becomes a discussion about cost. What was previously framed in terms of improvement or change becomes framed in terms of spend, reduction, and justification.
This is where many good decisions begin to weaken.
The instinctive response is to defend the number. To explain why the spend is justified. To introduce additional analysis, comparative figures, or projections. The decision becomes increasingly financial in tone, even when the original issue was operational, strategic, or behavioural.
And yet the problem is rarely the number itself.
The problem is that the value has not been made clear enough to carry the weight of the decision.
Cost is visible. Value often isn’t.
Cost is straightforward. It is quantified, immediate, and easily compared. It appears early in the discussion and is understood in exactly the same way by everyone in the room.
Value behaves differently.
Value is often:
distributed over time
dependent on conditions
expressed in outcomes rather than inputs
harder to isolate in a single figure
As a result, when cost and value are placed side by side without careful framing, cost dominates the conversation. Not because it is more important, but because it is more visible.
This imbalance creates a predictable pattern:
The clearer the cost, and the less clear the value, the more likely the decision is to be challenged.
That challenge is then misinterpreted as resistance to change or unwillingness to invest. In many cases, it is neither. It is a sign that the decision has not yet been explained in terms that align value with consequence.
The quiet shift in the conversation
There is a subtle but important shift that happens in these moments.
The question moves from:
What is the right decision?
to:
Should we spend this money?
This seems reasonable. In practice, it changes everything.
When the conversation is anchored on cost, two things happen:
The decision is reframed in terms of affordability rather than effectiveness
The focus moves to reducing the cost, rather than understanding the outcome
This is where false economies begin to form.
The nature of false economy
A false economy is not simply a bad financial decision. It is a decision that appears cheaper in isolation but creates greater cost elsewhere.
This happens most often when a necessary investment is avoided, delayed, or reduced to satisfy immediate cost pressure.
Consider a situation where operational bottlenecks are reducing throughput and increasing work‑in‑progress. The decision to invest in targeted training is sound. It addresses the underlying constraint and improves stability across the system.
The cost challenge emerges immediately.
Training carries visible cost. It may temporarily reduce productivity while it is delivered. It may delay short‑term outputs.
In response, the decision begins to shift:
training is reduced or shortened
exceptions are introduced for “critical” workloads
alternative shortcuts are explored
investment is deferred
Each of these actions appears financially prudent in the moment.
Individually, they reduce immediate cost. Collectively, they preserve the original problem.
The bottleneck remains. Work‑in‑progress continues to accumulate. Delivery stays inconsistent. Rework increases. Customer confidence weakens. The organisation pays repeatedly for a problem it chose not to resolve when it had the opportunity.
What looked like cost control becomes cost multiplication.
This is the defining characteristic of false economy:
it trades visible cost for hidden cost, and nearly always at a higher price.
Delay is not neutral
One of the most persistent misconceptions in senior decision‑making is that delaying a decision is a neutral act.
It is not.
Delay changes the economics of the decision, even when nothing appears to happen.
When a necessary investment is deferred:
existing inefficiencies continue
problems compound rather than pause
local workarounds become embedded
the eventual solution often becomes more complex and more expensive
The cost is simply not recognised as a line item.
This is why delay often feels safer than it is. There is no immediate outflow. There is no approval process. There is no visible commitment. The organisation can continue operating without taking a stance.
But the cost of delay accumulates quietly.
Work‑in‑progress increases. Delivery reliability remains unstable. Customer expectations start to shift downward. Teams adapt in ways that are difficult to reverse.
By the time the organisation returns to the decision, the context has changed. The problem is larger, the cost is higher, and the options are fewer.
Delay has done its work.
Why “cheap” decisions are attractive
Cheap decisions are appealing for understandable reasons.
They:
reduce immediate pressure
minimise visible commitment
allow optionality to remain open
signal financial discipline
In environments where cost is under scrutiny, these are powerful signals.
The difficulty is that cheap decisions often succeed on the basis of what they avoid, not on the basis of what they achieve.
They avoid:
immediate spend
visible risk
difficult conversations
short‑term disruption
What they do not avoid is consequence.
When the underlying issue remains unresolved, the organisation continues to experience:
inefficiency
inconsistency
rework
drift in performance
These costs are harder to attribute, and therefore easier to ignore. But they are rarely smaller.
Value is the anchor
The role of commercial judgement at principal level is not to eliminate cost from decisions. That would be unrealistic. Nor is it to produce increasingly detailed financial models in order to justify a choice.
It is to ensure that the value of the decision is clear enough that cost can be understood in context.
When value is clearly articulated:
cost becomes relative
delay becomes visible as a choice, not an absence
trade‑offs become explicit
discussion moves from “can we afford this?” to “what happens if we don’t do this?”
This changes the nature of the conversation.
The decision is no longer defended as an expense. It is understood as an exchange.
The practical shift
The most important shift is a simple one.
Replace:
“Should we spend this?”
with:
“What is the cost of not doing this?”
This is not rhetorical. It is analytical.
It forces the organisation to recognise that every decision includes both:
a cost of action
and a cost of inaction
Only one of these is typically visible at the outset.
The diagnostic
A simple test exposes whether a decision has been framed properly:
If cost is debated more clearly than value, the decision has not yet been understood.
This is not a critique of the finance function. It is a test of how the decision has been presented.
When value is clear, cost can be assessed proportionately. When value is unclear, cost becomes the dominant signal by default.
The role of finance
Finance plays a critical role in decision‑making. It brings discipline, constraint, and perspective. It ensures that trade‑offs are recognised and that resources are allocated intentionally.
But finance is at its most effective when it clarifies decisions, not when it overwhelms them.
When financial detail is introduced before value is understood, it can obscure rather than illuminate. The conversation becomes more precise, but less decisive.
At principal level, the aim is not to avoid financial discussion. It is to ensure that financial discussion occurs in the right order.
First value. Then cost.
Conclusion
Cheap decisions are rarely cheap in the long run. They are often decisions where cost has been made visible and value has not.
The result is predictable. The organisation reduces visible spend while continuing to incur invisible cost.
Over time, those costs compound.
A decision is not justified by how little it costs. It is justified by what it produces, and what it avoids.
When value is clear, cost becomes a manageable part of the decision.
When value is unclear, cost becomes the decision.
why good decisions fail when incentives don’t align
Good decisions rarely fail because people disagree with them openly.
More often, they fail because the incentives surrounding them point in a different direction.
The decision is made. It is discussed, documented, and, for a time, treated as settled. Yet over the following weeks or months, behaviour begins to shift. Exceptions appear. Workarounds become normal. The language around the decision changes. What was once clear becomes conditional.
From the outside, this can look like weak execution or fading commitment. In reality, the more common cause is simpler: the decision conflicts with the way people are rewarded, measured, or protected.
Incentives pull harder than intent.
This is not a cynical observation. It is a structural one. Most organisations assume that once a decision has been agreed, behaviour will naturally align behind it. That assumption is appealing because it treats decisions as self‑executing. If the room agreed, if the logic was sound, and if the owner was clear, then the rest should follow.
But organisations do not move according to decisions alone. They move according to the incentives embedded in roles, targets, relationships, and local pressures.
This is where decision drift begins.
A sales function may be rewarded for immediate revenue, even when a decision depends on operational stability. A finance function may be incentivised to reduce short‑term spend, even when the decision requires measured investment. Team leaders may optimise for local continuity, even when the organisation needs temporary disruption to fix a deeper problem.
None of these actors need to reject the decision in principle. They only need to behave rationally within their own incentive system.
Once that happens, the decision is slowly pulled away from its original intent.
This is why alignment in the room is never enough. Agreement does not neutralise incentive tension. It simply masks it for a while.
Senior leaders often underestimate this because incentives are rarely discussed in direct terms. People do not usually say, “I intend to undermine this decision because my targets point elsewhere.” What appears instead are smaller, more acceptable behaviours:
the “temporary” exception
the local workaround
the request to reconsider timing
the reframing of the issue in more convenient terms
the quiet preference for a different interpretation
These behaviours are not random. They are where incentives surface in practical form.
A decision, for example, may require bottlenecks to be removed through staff training before any technology investment is considered. The logic may be sound and widely accepted. But if sales performance is deteriorating and revenue pressure is high, that decision will quickly come under strain. A sales leader incentivised around short‑term recovery may begin to push for price reductions, client exceptions, or immediate technology changes — not because the original decision was incomprehensible, but because the commercial incentives now pull harder than the operational sequence.
This is the point at which many organisations misdiagnose the problem. They treat the drift as communication failure, resistance to change, or lack of discipline. Sometimes those things are present. More often, however, the issue is that the decision was never designed with incentive reality in mind.
This matters because incentives do not merely shape behaviour after the decision. They shape the conditions under which the decision can survive.
A principal‑level response to this is not to demand perfect alignment. That is unrealistic. Nor is it to moralise about organisational politics. The task is more disciplined than that.
Experienced advisers and senior leaders ask a quieter set of questions:
Who benefits if this decision holds?
Who is exposed if it does?
What local pressure will make reinterpretation most attractive?
Where will exceptions first appear?
These questions move the conversation from abstract agreement to practical survival.
At this level, the quality of a decision is not judged only by whether it is right in principle. It is judged by whether it can hold in an environment where incentives are uneven, competing, and often invisible.
This is why durable decisions usually require more than a clear argument. They require some understanding of where the decision will come under pressure and why.
Without that understanding, organisations rely on reinforcement. Leaders restate the decision. Governance tracks it. Exceptions are challenged. Variance is reviewed. All of that can help, but if the incentive structure remains misaligned, the decision will continue to be pulled off course. The organisation spends energy defending a decision that was never fully supported by the system around it.
That is expensive.
It creates delay, rework, duplicated effort, and the slow accumulation of local behaviour that no longer fits the original intent. Eventually the organisation begins to talk as though the decision itself was flawed, when in reality the failure sat in the environment surrounding it.
A simple test makes this visible:
If behaviour consistently diverges from the decision, incentives are elsewhere.
That line matters because it shifts the diagnosis. Instead of asking why people are not following the decision, it asks what in the system is rewarding them for doing something else.
This is not about distrust. It is about realism.
Good decisions hold when the surrounding environment makes them easier to sustain than to erode. That does not require perfect harmony. It does require leaders to understand that incentives are not background conditions. They are active forces.
Senior decisions do not usually drift because people forget them. They drift because people are pulled, in quieter and more persistent ways, towards something else.
Where incentives and decisions diverge, decisions weaken first.
Why most governance fails
and what good governance actually does
Most governance fails not because organisations lack visibility, but because they mistake visibility for control.
When something important is at stake, the instinct is understandable. Leaders want assurance. They want decisions to remain visible, risks to be surfaced, and problems to be escalated before they become expensive. Governance appears to offer exactly that. It promises order, oversight, and confidence that nothing important will be missed.
In practice, it often produces something else.
A decision is taken. A governance layer is added. Reporting expands. Status meetings appear. Dashboards are circulated. Over time, the organisation creates more visibility around the decision than action from it. Judgement is diluted in the effort to remain informed. What looks like control becomes theatre.
This is not because governance is unnecessary. It is because governance is frequently misdesigned.
The common error is to treat governance as a reporting exercise rather than a decision‑protection mechanism. Information is collected because it is available, not because it changes anything. Meetings recur because they are scheduled, not because they are required. Escalation becomes habitual rather than exceptional. The organisation becomes increasingly well informed about its own lack of movement.
The result is familiar: governance generates work, but not clarity.
Part of the problem is that bad governance feels responsible. It looks rigorous. It reassures senior leaders that important matters are being watched. More detail appears safer than less. More visibility appears more responsible than selective attention.
But this is where weak governance hides.
Good governance does not exist to make leadership feel informed. It exists to protect decision quality after the decision has been taken. That requires less structure than many organisations assume, and far more judgement.
At its strongest, governance does only a small number of things. It keeps a critical decision visible. It shows where drift or variance is emerging. It distinguishes routine review from genuine escalation. And it triggers action when specific conditions are met.
That is all.
Anything beyond this needs to justify itself. If it does not sharpen judgement or change behaviour, it is not governance. It is administration.
This distinction matters because review and escalation are not the same. Review is routine. It checks whether the decision still holds, whether assumptions remain true, and whether small variances are beginning to matter. Escalation is exceptional. It should occur only when the decision is blocked, the owner changes, a threshold is breached, or the original frame no longer holds.
When these two things are blurred, everything becomes urgent and nothing becomes clear.
Many governance models fail because they are designed to increase visibility rather than reduce ambiguity. They create the appearance of control by widening the field of attention. More metrics are added. More stakeholders are included. More reporting categories are introduced. Yet the essential question remains unanswered: what, specifically, would make us act differently?
If governance cannot answer that, it is not protecting the decision. It is surrounding it.
Good governance, by contrast, is intentionally sparse. It identifies the owner, the decision, the small set of indicators that matter, the warning signs that suggest drift, and the specific triggers that require escalation. It does not monitor everything. It monitors what can prompt a different judgement.
This is why strong governance is often quieter than weak governance. It produces less paper, fewer conversations, and less reassurance. It asks leaders to tolerate not knowing everything all the time. It relies on thresholds, not theatre.
That makes it harder.
Minimal governance requires leaders to be explicit about what really matters. It forces them to define the few things that would justify intervention and to ignore the rest. There is nowhere to hide in that model. If governance exists only to reassure, its weakness becomes obvious very quickly.
A simple test exposes the difference:
If governance creates more work than clarity, it has failed.
This is not an argument against governance. It is an argument for governance that is proportionate to the decision it exists to protect.
The strongest governance does not increase visibility for its own sake. It reduces noise so that decisions are harder to lose. It creates enough structure to trigger judgement when judgement is required, and no more.
Good governance is not a heavier overlay on leadership. It is disciplined restraint around what must remain visible, what must trigger action, and what can safely be ignored.
That is what actually protects decisions once they leave the room.
Why most decision frameworks fail (and what actually scales)
Most decision frameworks do not fail because they are wrong. They fail because they are asked to do a job they cannot do.
They are often introduced with good intent: to bring rigour, consistency, and shared language to senior decision-making. They promise to make complex choices easier, to ensure risks are considered, and to prevent blind spots. On paper, they look like progress.
In practice, the failure mode is quieter.
The framework is applied. The sections are completed. The analysis expands. The document grows. Yet the underlying decision does not become clearer. It is deferred, softened, or broadened to accommodate what the framework has surfaced. The organisation becomes busier around the decision – not more decisive about it.
This is not a failure of effort. It is a category error: structure is mistaken for judgement.
Structure is not decision quality. A framework can create order. It can make information legible. It can provide a common vocabulary. But it cannot perform the decisive act that senior work ultimately requires choosing, excluding, sequencing, and owning.
Frameworks do not usually fail at the level of content. They fail at the level of behaviour.
When a framework becomes the centre of gravity, something subtle happens. The decision migrates from being a judgement exercised by accountable people to being an output produced by a process. The emphasis shifts from “what do we need to decide?” to “what have we completed?” The team becomes oriented towards filling structure rather than converging on a choice.
This is why many frameworks scale activity rather than clarity.
Why frameworks persist even when they don’t work
If decision frameworks were obviously ineffective, they would disappear. They persist because they satisfy a set of psychological and organisational needs that are very real in senior environments.
Frameworks feel rigorous. They look professional. They create a shared artefact that can be circulated and referenced. They reduce anxiety by providing something tangible to do before committing. They allow senior teams to remain in a zone of apparent responsibility without accepting the exposure that comes with judgement.
The deeper truth is that frameworks are often used as a safety mechanism. They provide a place to put additional detail, alternative options, and risk considerations without forcing a call. They create cover for uncertainty.
That cover is not malicious. It is human.
But the cost is predictable: the framework becomes a shelter, and the decision remains unfinished.
The “Completion Illusion”
One of the most common patterns in senior decision work is what you might call the completion illusion.
· The document is complete.
· The workshop has been held.
· The options have been enumerated.
· The risks have been identified.
· The assumptions have been listed.
Everyone feels something has been accomplished.
Yet the decision still cannot be made cleanly because the structure has expanded the surface area faster than it has reduced uncertainty. The meeting ends with “we need one more piece of analysis” or “we should consider one additional angle” or “lets bring in one more stakeholder”.
The framework has produced a sense of thoroughness – but it has not produced a decision.
Real-world example: software investment vs capability
A common instance of this is the decision between investing in new software and improving capability in what already exists. It appears, superficially, as a simple binary choice. In practice it becomes a magnet for option sprawl.
A mid-sized organisation was experiencing operational bottlenecks. Work-in-progress was increasing, throughput was inconsistent, and staff frustration was rising. The senior team convened a decision meeting with a clear intent: determine whether the organisation should invest in additional software to address the bottlenecks.
A framework was applied. It was well-constructed and well-facilitated. The team surfaced an extensive list of “options” and “solutions”:
· Additional modules
· Replacement platforms
· Process redesign
· Hiring specialist staff
· Automation
· Outsourcing
· Training to improve existing usage.
· New governance arrangements
· Creating dedicated teams
Everything was captured. Risks were noted. Stakeholders were consulted. The resulting pack was thorough.
And the organisation remained stuck.
Why? Because the framework did not force the team to narrow what mattered. It allowed them to remain in breadth. It created symmetry between options that were not equally mature or equally relevant to the immediate decision.
The organisation did not need twelve options. It needed a staged judgement:
· What decision must be made now?
· What decision should be made later?
· What decisions should not exist yet?
The bottleneck issue did not require a complete technology strategy on day one. It required a narrower judgement: are bottlenecks caused by tooling limitations or capability gaps? Once that decision is framed, most options fall away naturally.
This is the point. The failure was not that the framework produced bad analysis. The failure was that it did not constrain the decision environment. It allowed the organisation to generate choices faster than it could act on them.
The lesson is not “don’t use frameworks.” The lesson is that frameworks are not enough. The decisive work happens outside the framework: narrowing, sequencing, and ownership.
What actually scales: systems that preserve judgement
Experienced leaders and principal advisers do not reject structure. They use structure differently.
The do not reach for more sections or more completeness. They reach for minimal structure that preserves judgement.
This is the difference between a framework and a system:
· A framework tends to expand thinking.
· A system tends to compress thinking to a decision-ready form.
Frameworks scale work. Systems scale judgement.
A decision system does not aim to be comprehensive. It aims to be sufficient. It focuses attention on a small number of questions that reliably produce clarity:
· What is the decision?
· What is explicitly not the decision?
· Why now (what blocks progress)?
· What has been removed?
· Who answers after the meeting ends?
· When is revisit legitimate?
Everything else is optional.
This is not minimalism for its own sake. It is restraint applied to protect decision-making in environments where complexity will always expand unless constrained.
Why minimal systems are more senior than complete frameworks
At senior levels, the scarcest resource is not information. It is attention.
A complete framework competes for attention. It invites more participation, more inputs, more qualifiers, and more “just one thing”. It provides many places to hide.
A minimal system does the opposite. It makes avoidance harder. It forces the decision to be named early and revisited repeatedly. It makes exclusions explicit. It creates a path from “discussion” to “choice”.
This is why principals prefer systems. Systems leave less room for theatre.
The test that reveals failure
A simple test exposes whether a decision framework is doing it’s intended job:
If the framework produces documents instead of decisions, it has failed.
That does not mean the document is useless. It means the structure has become the output rather than the decision.
This often shows up in how people talk:
· “We’ve completed the pack.”
· “We’ve filled in the template.”
· “We’ve done the analysis.”
But the room still cannot answer, cleanly:
· What are we deciding?
· What are we not deciding?
· Who owns the outcome?
· What happens next?
Clarity scales through removal
Frameworks tend to accumulate. Each addition feels justified: a section for risk, a section for assumptions, a section for benefits, a section for stakeholder impact. Over time the pack becomes heavier, and the decision becomes harder to see.
The impulse is understandable: completeness is comforting.
But senior clarity rarely comes from adding more. It comes from removing what does not sharpen the decision.
That removal is the principal’s work.
The frameworks that endure are those that remain deliberately incomplete. They provide just enough structure to support judgement, and no more. They are easy to use, difficult to hide behind, and fast to repeat. They create consistency of decision quality, not just consistency of output.
At senior level, that is what scales.
why most decisions don’t survive change
Most senior decisions are not overturned. They simply fade.
The meeting ends. A decision is taken. It is recorded, communicated, and, for a time, followed. There is often a brief period of order: actions are assigned, slides are circulated, and the organisation behaves as though the matter is settled. Yet weeks later, the edges begin to soften. Exceptions appear. Interpretations vary. Work proceeds, but in different directions. What was once a clear decision becomes a negotiable agenda item, again.
Eventually, the decision still exists in name, but no longer in practice.
This is rarely because the decision was wrong. More often, it was not designed to survive.
Decisions don’t fail loudly — they erode quietly
Senior decisions do not operate in stable environments. Context shifts. Pressures emerge. Leadership changes. New information arrives. Competing priorities resurface. None of this is unusual. What is unusual is how often organisations treat decisions as if they are made in a vacuum—complete and self‑sustaining once announced.
Most decisions are challenged indirectly. They are not confronted in a formal meeting with a clear argument for reversal. They are eroded through a series of small, seemingly reasonable movements:
“Just this once” becomes “for now.”
“Temporary” becomes “until further notice.”
“Local variation” becomes “the way it’s done here.”
“We agreed” becomes “we interpreted it differently.”
The decision doesn’t collapse; it degrades.
A decision that depends on being restated, defended, or continually reinforced is already fragile. When it is challenged repeatedly in small ways, it consumes leadership attention simply to remain intact. That is not durability; it is ongoing negotiation.
Documentation is not durability
One reason decision erosion is so common is that organisations mistake recording for resilience. A decision is written down, placed in a deck, added to a log, or referred to in an email chain. This is treated as proof that the decision will hold.
It is not.
Documentation can preserve memory, but it does not prohibit reinterpretation. It does not resist pressure. It does not stop exceptions being granted or scope drifting by degrees. A decision can be perfectly documented and still decay if the conditions that keep it alive are not made explicit.
There are three common false assumptions that appear in senior environments:
Agreement will translate into continuity.
Governance will preserve intent.
A decision, once made, will remain the “default” unless explicitly reversed.
None of these assumptions is reliable under pressure.
Durability is designed at the moment of decision
Durability is not an attribute of strong decisions. It is an attribute of well‑designed decisions.
Disciplined leaders and principal advisers tend to do something subtle at the point a decision is taken: they anticipate how it will be challenged. They treat future pressure as normal, not as a failure of alignment. They ask, implicitly or explicitly: What will try to erode this?
This is not pessimism. It is realism.
Durable decisions tend to have three features that fragile decisions lack:
Explicit conditions that keep the decision true
Clear boundaries that prevent quiet reinterpretation
Defined triggers for legitimate revisit
These features do not make decisions rigid. They make them resilient.
The pressures that erode decisions are predictable
Decision erosion often looks like a sudden loss of discipline, but it is more often a predictable response to predictable forces. Some of the most common include:
Cost pressure: when budgets tighten, teams seek exceptions or shortcuts that are framed as temporary.
Operational instability: when a system is under strain, “workarounds” multiply and become standard practice.
Leadership churn: when owners, sponsors, or senior stakeholders change, prior intent is reinterpreted through new priorities.
Competing priorities: when decisions compete for attention, enforcement weakens, and local incentives dominate.
Late data: when new information arrives, it is used to widen the frame rather than refine it.
The problem is rarely the existence of pressure. The problem is failing to anticipate it.
The difference between flexibility and drift
A useful distinction at principal level is this: flexibility is intentional; drift is accidental.
Flexibility is when the organisation legitimately adjusts because the conditions that made the decision sensible have changed. Drift is when the decision is reshaped without anyone acknowledging that the decision has, in effect, been rewritten.
The distinction is not semantic. It is economic.
When decisions drift, the organisation accumulates hidden costs: rework, duplicated effort, conflicting priorities, inconsistent customer experience, and competing narratives of what is “supposed” to happen. These costs often appear as “delivery problems” when the underlying issue is decision decay.
Durability, therefore, is less about control and more about preventing accidental rewrite.
Why boundaries matter
Decisions erode because boundaries are rarely made explicit. When boundaries are unclear, people adapt. Adaptation is not malicious; it is rational. Individuals and teams respond to local constraints. They optimise for their context. In doing so, they create exceptions. Over time, exceptions become the new rule.
Clear boundaries reduce the need for negotiation. They make it obvious what is within scope and what is not, what is part of the decision and what is adjacent. They reduce the temptation to “interpret generously” when pressure arises.
A durable decision does not need to be defended every week if it is bounded in a way that survives everyday pressure.
Why triggers for revisit protect decisions
A principal-level insight is that decisions do not become durable by pretending they will never be revisited. Decisions become durable when the organisation agrees what legitimate revisit looks like.
Without explicit revisit triggers, decisions are constantly re-opened informally. People challenge them opportunistically, when pressure is high or incentives shift. The decision becomes a soft target. The organisation spends time arguing about whether the decision still stands rather than executing it.
Defined revisit triggers change the pattern. They create an agreed mechanism for reassessment. They protect the decision from constant informal challenge and ensure that change happens deliberately, not by stealth.
This is why a durable decision can withstand pressure without becoming brittle.
The test that reveals durability
A simple test exposes whether a decision has been designed to endure:
If a decision needs to be constantly restated to remain effective, it was never designed to endure.
This is not a complaint about communication. It is a diagnosis of fragility.
When a decision is durable, it becomes the default. People do not need frequent reminders because the boundaries and conditions are implicit in the way work is organised. When a decision is fragile, leadership attention is spent sustaining it.
Durable decisions behave like assets, not events
At senior level, it is easy to treat decisions as moments: a meeting, a vote, an agreement. In reality, decisions are better treated as assets: constructs that carry intent forward through time, pressure, and change.
Assets require design.
That design is not bureaucracy. It does not require heavy governance or complex control mechanisms. It requires clarity at the point the decision is taken what must remain true, what must not change, and what would legitimately cause reconsideration.
The quality of a decision is not only revealed at the moment it is taken. It is revealed later—in whether it still exists, unchanged, three months from now.
Why most decisions fail after they’re made
Most senior decisions fail after they are taken, not during the discussion that leads to them.
The meeting ends. There is agreement. Heads nod. The decision is declared. On the surface, progress has been made. Yet weeks later, nothing has shifted. The decision is revisited, quietly diluted, or overtaken by events.
This is rarely an execution problem. More often, it is an accountability problem.
Senior teams commonly conflate three things that are not the same: decision, agreement, and ownership. Agreement creates alignment in the room, but alignment does not automatically translate into accountability once people leave it. A decision can be stated clearly, supported unanimously, and still fail to exist in any meaningful sense.
The failure pattern is familiar. A decision is taken, agreement is recorded, and accountability is assumed rather than named. Responsibility spreads across the group. No single person is answerable when progress stalls. What felt collaborative at the moment of agreement becomes ambiguous afterwards.
This ambiguity is rarely accidental. Naming an accountable owner can feel confrontational in senior settings, particularly where relationships matter and authority is distributed. Shared ownership sounds inclusive. Deferring ownership feels polite. Both reduce friction in the meeting.
Both increase it later.
Without a named owner, decisions drift. Execution slows. Issues are rediscovered rather than resolved. Over time, the organisation expends more energy maintaining the fiction that a decision has been made than it would have taken to act on it decisively.
Experienced leaders handle this differently. At the moment a decision is taken, accountability is made explicit. Not who will do the work, but who will answer for the outcome. The boundaries of that accountability are clear: what the owner is responsible for, and equally, what they are not.
This distinction matters. Accountability is retained even when delivery is delegated. It survives time, escalation, and organisational change. It anchors the decision once the meeting ends.
A simple test exposes the difference:
If no one can say who answers for the decision, the decision does not exist.
Clear accountability is not about control. It is about clarity. Decisions only endure when someone owns them beyond the moment of agreement. Without that ownership, consensus becomes commentary, and leadership intent dissolves into activity.
Decisions fail less often when leaders recognise that agreement is not the end of the work. It is the point at which accountability begins.
Why the most expensive decisions are the ones made too early
Decisions made too early are among the most expensive mistakes senior leaders make.
The problem is rarely poor intent or weak analysis. It is timing. Decisions taken before constraints are understood, before variability has stabilised, or before dependencies are visible often create more cost than those taken later.
Senior environments place significant pressure on leaders to act quickly. Fast decisions are praised. Urgency is frequently mistaken for progress. Early commitment looks decisive, but it often results in rework, reversals, and downstream distortion. Speed becomes a signal, not a source of insight.
Premature decisions feel responsible for familiar reasons. They create visibility. They reassure stakeholders. They reduce anxiety. They signal action. In the moment, all of this feels constructive.
Over time, the cost appears elsewhere.
Early decisions become expensive when they need to be undone, when dependent decisions have to be reshaped around them, or when sunk costs create inertia. What looked like leadership at the outset turns into constraint later on.
Disciplined senior leaders approach decision‑making sequentially. Deferral is not treated as hesitation but as judgement. They are explicit about what cannot yet be decided and resist the pressure to name outcomes before decisions have matured. Decisions are allowed to come into existence only when the necessary learning has occurred.
This restraint is not passive. It is deliberate. It reduces rework, protects momentum, and ensures that when decisions are taken, they endure.
The most expensive decisions are rarely the ones made too late. They are the ones made before they were ready.
Agenda Collapse Under pressure
Why smart decisions fail when agendas collapse under pressure
Senior decisions rarely fail because of weak analysis. More often, they fail because the decision framework collapses once it comes under pressure.
That pressure usually arrives in familiar forms: late‑arriving data, senior stakeholders introducing new concerns, artificial urgency driven by forecasts or optics, and deference that widens scope rather than holding it.
At senior levels, agendas collapse under pressure for three recurring reasons: fear of exclusion, fear of appearing rigid, and fear of being wrong in a public arena.
Fear of exclusion
Senior teams often fall into the belief that every part of the organisation must have equal input into every decision. While inclusion matters, this principle is frequently misapplied. What begins as a desire for representation becomes a mechanism for delay, consensus‑seeking, or avoidance of judgement.
When the agenda is widened to accommodate all perspectives, decision clarity is often the price.
Fear of appearing rigid
There is a persistent assumption that decisions must solve problems completely and immediately. In reality, many senior decisions require time to settle, evidence to emerge, or further sequencing.
When this is misunderstood, agendas stretch to absorb uncertainty rather than contain it. Scope expands not to improve the decision, but to avoid the discomfort of partial resolution.
Fear of being wrong in a public arena
Senior decisions are rarely taken in private. Whether the audience is a peer group, the organisation, or the wider market, fear of visible error exerts a powerful influence.
This often produces a culture where safe or popular options are explored first, even when bolder decisions carry greater long‑term value. Accountability is diffused, and responsibility is shared rather than exercised.
To manage these fears, leadership teams often widen debate rather than hold the frame. Stretching the agenda feels safer than pausing it. The result is reduced accountability and delayed execution.
A common pressure point arises when new data appears late in the process. For example, quarterly sales figures show deterioration, overheads rise, and profit forecasts worsen. A senior stakeholder challenges a decision focused on operational efficiency and argues instead for price reductions.
A disciplined response acknowledges the data as relevant to understanding operational cost and work‑in‑progress, while holding the boundary that pricing is not the decision being taken. The information informs the decision; it does not redefine it. If pricing genuinely becomes the decision, the session should pause and reset rather than stretch to absorb it.
If new information widens the agenda rather than sharpening the decision, the agenda has failed.
why fewer options lead to better senior decisions
Senior decisions improve not when more options are presented, but when weak or premature choices are removed early.
This feels counterintuitive. Many leadership teams equate a large set of options with rigour and responsibility. Over time, the opposite effect appears: decisions slow, discussions become circular, and the original issue deepens.
This is not a failure of intelligence or experience, but a predictable consequence of how senior decisions are framed.
Senior decisions are rarely small or isolated. They involve cost, people, reputation, and long‑term consequences. When too many options remain in play, discussions broaden, responsibility diffuses, and meetings generate analysis but little movement.
Leaders often tolerate this “option sprawl” longer than they should. An excess of options creates for: when everything is possible, nothing is clear. The organisation stalls, costs mount, and the underlying problem becomes more entrenched.
Excess options persist not because leaders are careless, but because narrowing feels risky. Keeping options open signals due diligence, inclusivity, and thoroughness. There is reluctance to exclude options early for fear of later criticism: “Why wasn’t this considered?”
Sometimes, structured thinking tools are referenced but not fully applied. Breadth is achieved, but prioritisation is lost.
The cost of too many options is rarely visible in a single meeting. It accumulates over time. As options multiply, attention dilutes, cognitive load increases, and conversations lead to deferral rather than commitment.
Discussion replaces decision. Leaders leave meetings appearing aligned but privately unconvinced, knowing the issue will return. What feels like careful governance slowly turns into costly inertia.
Principal consultants approach senior decisions with discipline, not just decisiveness. Three behaviours stand out:
Early narrowing: Strong decision‑makers reduce the option set early, removing ideas that are theoretically interesting but practically weak, poorly timed, or misaligned with current constraints.
Protecting the decision: Once a decision is ready, principal consultants protect it from unnecessary re‑expansion, knowing that reopening discarded options later undermines confidence and momentum.
Sequencing exclusions deliberately: Excluded options are parked and sequenced – acknowledged as “not now” rather than “never”. This reinforces trust while allowing progress.
Consider the decision between investing in new software or training existing employees on underused features. Both options can appear equally valid, and teams may spend months debating them side by side. Clarity emerges once premature options - those exceeding current maturity, budget, or capacity for change - are removed. The decision becomes simpler, not because the issue is trivial, but because attention is no longer diluted.
Too many choices rarely lead to better decisions. They delay commitment, increase cost, and allow problems to deepen.
By removing weaker options early, senior teams create focus, shorten discussions, and make progress more likely. The discipline is not in generating ideas, but in curating them, so that when a decision is taken, it is taken clearly, deliberately, and with conviction.
Good consultants add analysis. Trusted advisers remove decisions.
Too many organisations assume that better decisions come from deeper analysis and a wider set of options. In practice, senior decisions improve when unnecessary choices are removed early.
At a recent strategy day, the aim was to set the direction of the organisation for the next three to five years. As usual, the day began with teams being split into groups for short brainstorming sessions. Each group was given a different topic. After several rounds of discussion, the groups presented seven or eight recommendations each. Many conflicted with one another.
It became clear early on that no decision could be made. None of the options were being discarded, and the conversation kept widening. The meeting felt busy, but it was not converging on a choice. With different framing, the outcome could have been very different.
A good consultant brings structure to a problem. They analyse the situation, explore alternatives, and test options against evidence and context. That work is valuable. It builds understanding and creates a shared view of the landscape.
A trusted adviser does something subtly different. Before the meeting begins, they decide which decisions actually matter. They narrow the field of options to a small, credible set and recommend the one that best fits the agreed criteria. In doing so, they protect both the focus of the conversation and the time of the people in the room.
This approach can feel uncomfortable. Reducing options can look like doing less. Presenting a recommendation and then staying quiet while it is considered can feel abrupt. But this is professional restraint, not disengagement.
If a meeting feels productive but all options remain on the table, no decision has been made. In that case, the meeting may have generated activity, but it has not created progress.
A trusted adviser exercises judgement quietly. When they do their job well, the client feels they have made the right decision — without needing to see all the decisions that were removed along the way.
This article was originally published on LinkedIn