Strategic Finance · Corporate Governance · Enterprise Strategy

I bring structure to complexity.

Connecting strategic finance, corporate governance, and enterprise strategy to help large organisations make better decisions - faster

Feasibility Director for a PIF-backed master developer. Previously led Financial Planning & Strategy across a multi-billion pound portfolio. CFA · FCMA · MRICS

What I do

Most professionals stay inside one discipline. I work at the intersections.

Most organisations don't fail for lack of ambition. They fail in the space between strategy and execution - where decisions are made on incomplete information and the numbers drift from the plan. I work in that gap, bringing enterprise strategy, financial rigour, and delivery discipline into a single, governed approach across the GCC and UK.

The value is in how they combine: Finance + Governance · Strategy + Real Estate · Governance + AI

• Arrow Right
• Arrow Last

How I create value

Structure to complexity, systems that outlast individuals

My work sits where finance, governance, and strategy meet. I build the systems that turn data into decisions, and decisions into long-term value.
What drives me is durable: building planning and governance systems that outlast any individuals and let organisations make faster, better decisions.

• Arrow First
• Arrow Left
• Arrow Right
• Arrow Last

• Arrow First
• Arrow Left
• Arrow Right
• Arrow Last

Strategic Finance

Corporate Governance

Enterprise Strategy

• Arrow First
• Arrow Left
• Arrow Right
• Arrow Last

For advisory, board, speaking or leadership conversations - get in touch.

• Arrow First
• Arrow Left

Strategic FinanceFinancial models should be operating systems, not static tools

Most large organisations run on a financial model that is, in truth, a very expensive photograph. It captures a single moment - the budget signed off in the fourth quarter, the business case approved at investment committee - and from that moment it begins to age. The assumptions move, because assumptions always move, and before long the model describes a world that no longer exists. Decisions, meanwhile, keep being made against it.The problem is rarely the quality of the modelling. It is the category. We treat the model as a document - something produced, circulated and filed - when the organisation actually needs it to behave like a system: live, queryable and continuously updated. That distinction is not cosmetic. A document answers the question it was built to answer. A system answers the questions you have not asked yet.

Three Properties That Separate a Document from a System

The gap between a financial model that describes the past and one that steers the future comes down to three structural properties. Each one is achievable. Together, they are transformative.

Document World vs. System World

There is a common objection at this point: we already run scenarios. Most organisations do - occasionally, manually, and at great cost, usually in response to a specific question from above. That is precisely the symptom. When a scenario is a project rather than a keystroke, the organisation runs far fewer of them than it should, and it runs them late

The Competitive Advantage of Speed with Rigour

In an environment where conditions move faster than planning cycles, the ability to answer "what changed, and what should we do about it" in the room - rather than three weeks later - is a strategic asset in its own right. The payoff is not elegance. It is speed of decision with rigour intact.

The Instrument for the Next Decision

The spreadsheet is not the enemy. Treating it as the finished article is. The organisations that will make the best decisions in the years ahead are not those with the most sophisticated models in a technical sense - they are those that have elevated the model from document to system, and from record to instrument.

Building the model as a system changes the role of finance in the organisation. It changes the conversation in the boardroom from interrogating history to navigating the future. And it changes the value that a finance function delivers - from custodian of the record to architect of the decision.

Strategic FinanceThe Real Test of a Capital Allocation Decision

You are not judged on the return you underwrote. You are judged on the loss you did not see coming. Why the quality of a capital decision lives in its downside, not its base case.Capital allocation is usually presented as a contest of returns. The paper with the highest internal rate of return wins the money. It is a tidy way to decide, but a poor one, because the return in the base case is the least reliable number in the entire appraisal.

Why the Base Case Is the Wrong Number to Trust

The base case is the number every sponsor has an incentive to make attractive, and the one the future is least likely to honour. It tells you what a proposal looks like when the world cooperates. It says almost nothing about what happens when it does not - and it is the second scenario that determines whether an organisation survives its own ambition.That reframing changes what you interrogate. A decision that looks excellent in the base case and fatal in the downside is not a good decision with some risk attached. It is a bet. The real test is not the return you underwrote. It is the loss you did not see coming.

Three Lenses That Do More Work Than Any Single Return

Three analytical lenses do more work than any single-point return estimate. Together, they separate genuinely sound capital decisions from optimistic ones wearing the costume of rigour.

Reversibility: The Dimension Most Decisions Ignore

Behind downside, liquidity, and timing sits one further question that separates disciplined allocators from optimistic ones: is this decision reversible? It is the most underused variable in capital governance, and perhaps the most important.

Treating reversible and irreversible decisions with the same approval rigour is one of the most common and expensive mistakes in corporate finance. Applying identical scrutiny to a decision you can reverse next quarter and one you will live with for a decade is not consistency, it is a failure of calibration.

Allocating Capital on What You Can Defend

Take two proposals that clear the hurdle rate by the same margin.
On paper, they are equivalent, and capital gets allocated as though they are.

The headline number cannot tell them apart.
The downside, the liquidity profile, and the reversibility can - and they tell you these are entirely different risks wearing the same return.

The return is what you present. The downside is what you live with.
That asymmetry is the whole of the discipline.

Corporate GovernanceGovernance Before Viability: Why the Order Matter

A brilliant business case built on assumptions no one owns is a guess in a suit.Why how a decision gets made has to be settled before whether it is worth making.

The Danger of the Binary Verdict

There is a sequence most organisations follow when evaluating an opportunity. They ask whether it is viable - the returns, the market, the case - and only later, if at all, do they ask how the decision was actually made and whether the inputs behind it can be trusted. The order feels intuitive. It is also backwards.Governance should come before viability, because viability is a conclusion and governance is the thing that determines whether you can believe it.Consider what a business case really is: a structure of assumptions about price, cost, demand, timing, and funding assembled into an answer. Change the assumptions and the answer changes - often dramatically.The credibility of a case does not rest on the sophistication of the model. It rests on the quality and ownership of the inputs. A model can be beautifully constructed, internally consistent, and entirely fictional, because every critical driver within it was entered by someone who either did not own it, did not defend it, or quietly made it up.

Two Meetings, One Stark Difference

Picture the difference concretely. In the first meeting, a strong return is presented. The discussion moves immediately to whether the number is high enough, and an hour later a decision is taken - resting, unknowingly, on a cost assumption one analyst entered as a placeholder and no one ever confirmed. The decision feels rigorous. It settled nothing that mattered.In the second meeting, the same paper arrives with its critical assumptions listed, owned, and status-marked. The conversation spends its first ten minutes on the two inputs flagged as contested, resolves who will stand behind them, and only then turns to the return. The decision that follows is not only faster in the ways that matter - it is about something real.

Governance Is Not Bureaucracy

The distinction is worth defending, because the two are routinely conflated and the conflation is costly. Governance done badly is a tax on decisions - forms, approvals, delay. Governance done well is the opposite: it speeds decisions up, because it removes the endless re-litigation that happens when nobody trusts the numbers.When ownership is clear, a challenge to an assumption has somewhere to go. When it is not, every meeting reopens the same questions, and the organisation mistakes repetition for rigour. The meetings multiply; the confidence does not. Senior time is consumed not by advancing the decision but by relitigating the foundation - because the foundation was never secured in the first place.The practical distinction is simple. Bureaucracy adds process without reducing uncertainty. Governance adds accountability and thereby reduces it. A form that requires three signatures creates delay. An assumptions register that assigns ownership to each critical driver eliminates the most common source of organisational paralysis - the question, raised late and at cost, of whether the numbers were ever real.

The Practical Mechanism: A Tiered Assumptions Register

The tool that makes governance-first workable in practice is unglamorous and powerful.A tiered assumptions register;

It sounds like administration. It behaves like a brake on the single most common failure mode in large organisations.The most important feature of the register is not the documentation — it is the tiering. Not every assumption deserves the same scrutiny. The register forces a discipline that business cases typically avoid: identifying, upfront and explicitly, which inputs will actually move the decision if they are wrong. Those are the ones that need owners, rationale, and status. Everything else is supporting colour.

Material changes escalated rather than absorbed silently is the operative phrase.In most organisations, assumptions shift during the life of a case - market data updates, cost estimates are revised, timing assumptions quietly slip.Without a register, those changes are absorbed by the model invisibly.
With one, they surface. The decision-maker sees what changed, who changed it, and why.That is not bureaucracy. That is oversight.

What This Means for Boards and Chief Executives

For a chief executive, governance before viability is the difference between a decision the organisation can defend and one it simply hopes is right. When something goes wrong (and in large, complex organisations, things go wrong) the question that follows is always the same: what did you know, and when did you know it?An assumptions register is not a shield from accountability; it is a record of how accountability was exercised in real time.For a board, the stakes are even more direct. A board that reviews conclusions without governing the inputs is not exercising oversight. It is signing off on other people's optimism.
The business case arrives with a headline return; the board debates whether that return is attractive; no one asks who owns the revenue assumption in year three or whether the cost synergies have ever been stress-tested.
The meeting feels like governance. It is theatre.

Real oversight means asking, before the return is debated, which inputs are contested, who owns them, and what would have to be true for this case to fail.Those are not hostile questions.
They are the questions that distinguish a board from a ratification committee.

Moving on Something Real

Governance before viability is not about slowing the organisation down.Every serious objection to the principle dissolves under scrutiny:

The organisations that move fastest are not the ones with the fewest controls. They are the ones whose controls are well-designed, where accountability is clear, inputs are trusted, and decisions do not have to be relitigated in every subsequent meeting because nobody agreed the numbers in the first place.

.

Corporate GovernanceRisk Appetite vs Risk Tolerance - The Line Executives Miss

They are used interchangeably. They are not the same thing.One sets the ambition; the other sets the boundary.Miss the difference and teams either freeze or overreach, and the organisation discovers which failure mode it has only after the fact.

Two Ideas, Routinely Confuse

Few phrases appear more often in board papers, and are understood less precisely, than "risk appetite" and "risk tolerance".They are used as synonyms, nodded through, and quietly ignored, which is a problem, because the distinction between them is one of the more useful tools an executive team has for actually governing behaviour.They are not the same thing. An organisation that defines one without the other has done half the job - and it is usually the more dangerous half that is missing.

Risk Appetite: A Statement of Intent

Risk appetite is directional and strategic. It is a declaration of how much risk the organisation is willing to seek in pursuit of its goals - not how much it is prepared to suffer, but how much it is willing to pursue.Appetite is the organisation's posture toward uncertainty as a vehicle for value creation.

The Behavioural Test: Does It Change What a Manager Does on a Tuesday?

This is where a great deal of enterprise risk work quietly fails. It produces heat maps and registers - accurate, comprehensive, and entirely disconnected from the decisions people are actually making.The test of a risk appetite statement is not whether it reads well in the annual report. It is whether a manager, alone with a real decision, can use it to determine whether to proceed, pause, or escalate.When appetite and tolerance are both explicit, that test becomes passable.
The manager knows what the organisation is trying to pursue.
They know the limits that trigger a conversation upward.
Decision rights become legible. Authority has an edge.

When the two concepts are conflated - or when one exists without the other - that test cannot be passed.
The manager either escalates everything, because they have no confidence in their authority, or escalates nothing, because there is no defined line that tells them when to do so.Both outcomes impose costs: the first on speed; the second on control.Neither is a functioning governance framework

What This Means for Boards and Executive Teams

For a chief executive, defining both appetite and tolerance is what makes confident delegation possible.
People can move quickly inside a boundary that has been drawn deliberately. The speed comes not from loosening governance, but from making it precise enough that it does not need to be re-litigated at every decision point.A well-governed organisation is faster than a poorly governed one - not because it takes more risk, but because its people know exactly where the line is.For a board, the appetite and tolerance framework is the mechanism that turns "are we comfortable with the risk?" from a feeling into a test.
Without it, board risk oversight is impressionistic - dependent on the quality of the conversation in the room rather than on the quality of the framework being applied.With it, the board can ask precise questions:
Is current exposure within stated tolerances? Is the appetite still aligned with the strategy?Those are answerable questions. They are the basis of genuine oversight.

.

Corporate GovernanceExecutive Reporting That Drives Decisions

The test of an executive report is not how much it explains.
It is which decision it changes.Most reporting describes the past; the useful kind interrupts the future.

The Inertia Problem

Most executive reporting is built to inform. It is comprehensive, accurate and, in the way that matters most, inert. It tells leaders what happened, in impressive detail, and then leaves them exactly where they were - because describing the past is not the same as changing the next decision.There is a simple test that separates reporting that earns its place from reporting that merely fills a pack. It is this: what decision does this page change? If the honest answer is "none", the page is documentation, not reporting, however well produced it is.

Movement Over Levels

Most reports lead with where things stand - the position, the balance, the number.
But executives rarely need to be reminded of the level; they need to understand what moved and why.The instinct to open with the destination, rather than the change since last time, is the single most common reason board packs are read and forgotten.

The discipline of leading with movement rather than position changes the entire character of a board discussion.
Instead of a room confirming what the numbers are, the conversation starts at what they mean - and whether any of the underlying drivers require intervention.That shift, from confirmation to challenge, is where executive time earns its return.

Exception Over Completeness

A thorough report covers everything, which means the two things that actually require attention are buried among the forty that do not.Reporting built for decisions inverts the ratio: it surfaces the exceptions;

The rest is treated as available on request, not demanding of airtime.

The board's attention is the scarcest resource in the building. Spending it evenly is spending it badly.Every item given equal weight implicitly signals equal importance. And when everything is important, nothing is.The discipline of exception-based reporting is not about hiding information; everything remains available. It is about curating the surface of the pack around the decisions that are actually live.

Point of View Over Neutrality

There is a cultural instinct in finance to present the numbers and let leaders draw their own conclusions.It feels rigorous. In practice it abdicates the most valuable part of the job.
The person closest to the numbers has a view on what they mean and what should follow, and withholding it in the name of objectivity leaves a gap that gets filled by whoever is most confident in the room - informed or not.A good report says what changed, why it matters, and what it implies - and then invites challenge to that view rather than pretending not to have one.

The practical implication is simple:Every material finding should carry a brief, explicit interpretive sentence - not a recommendation dressed as opinion, but a clear statement of what the numbers imply and what question they put in front of the room.That sentence is the analyst's professional judgement. It is the most valuable thing on the page, and it is the thing most often left out.

Designing Every Page Around a Decision

None of this means shorter for the sake of it, or opinion in place of analysis.
It means designing every page around the decision it is meant to serve, and cutting what serves no decision at all.
The discipline is not aesthetic; it is about respecting the fact that executive time converts directly into the quality and speed of the organisation's decisions.Every minute a leader spends decoding a report is a minute not spent deciding. A report that requires explanation, that buries its point in coverage, that presents its conclusions as open questions - that report has already failed before the meeting begins.The cost is not the time lost in the room; it is the decision that arrives late, or not at all, because the signal was never made clear enough to act on.

The Move That Changes Everything

For a chief financial officer, this is the move from being the function that reports the business to the one that helps steer it.The distinction matters more than it sounds.

The reporting pack is the most visible expression of which one finance has chosen to be.For a board, it is the difference between a pack you endure and a pack that sharpens the two or three choices actually in front of you.
Most board members have sat through both. The difference is not volume, and it is not presentation quality. It is whether the author made a decision about what the pack is for - and then had the discipline to build everything around that answer.

The purpose of a report is not to be read.
It is to change what happens next.Every choice about what goes on the page - what leads, what is cut, what carries a point of view - is a choice about whether the organisation decides well or merely decides.That is not an aesthetic question. It is the whole job.

Enterprise StrategyAI Changes the Maths

The real strategic effect of AI is not cheaper analysis.
It is that when analysis becomes near-free, the binding constraint moves to the speed at which you can trust and act on it.

The Old Bottleneck: Analytical Capacity

The Constraint Has Moved

When analysis was slow and expensive, the competitive advantage lived in making the answer.Now that answers are cheap, the advantage lives in deciding on them - and that is a fundamentally different capability to build.

This is why "AI changes the maths" is more than a slogan.It changes which capability is scarce. In a world where analysis is fast and cheap, you optimise for decision velocity, the organisation's ability to convert an answer into a committed choice without losing rigour.The bottleneck has shifted from making the answer to deciding on it

The Constraint Has Moved

The New Scarce Skill: Discernment

There is a second-order consequence worth naming explicitly.When analysis is abundant, its quality becomes harder to judge - because plausible answers are now cheap to produce.A confident, well-formatted, entirely wrong answer has never been easier to generate.

The executive of the next decade will be flooded with answers and short on the judgement to weigh them.That judgement is the differentiator. It becomes more valuable, not less, as AI becomes more capable.

What Does Not Change

It is worth being precise about what AI does not alter.The cost of being wrong is unaffected, arguably it rises, because decisions can now be made faster and at greater scale.Cheap analysis does not make hard choices easy; it makes them more frequent and lowers the friction that used to slow a bad one down.

The Questions Leaders Must Now Answer

For a chief executive, the strategic question is no longer we produce the analysis" - increasingly, everyone can.
It is whether the organisation can decide faster than its competitors without deciding worse.For a board, this reframes the AI conversation away from tooling and towards decision-making: not what the technology can generate, but whether the organisation is governed well enough to move on it.

The maths has changed. The advantage has moved from the answer to the decision.The organisations that recognise this early - and rebuild their governance, culture, and leadership accordingly - will define the competitive landscape of the next decade.

Enterprise StrategyDesigning an Operating Model That Executes

Strategy rarely fails in the boardroom. It fails in the operating model - the wiring of who decides what, with what information, by when.Most operating models are org charts pretending to be answers. This document makes the case for treating execution as a design problem, and shows where the real fault lines lie.

Strategy Sets Direction. The Operating Model Determines Whether It Arrives.

When a strategy fails, the inquest usually focuses on the strategy itself - the market was misread, the thesis was wrong, the ambition was too great. Sometimes that is true. Far more often the strategy was sound and the organisation was simply unable to execute it, because the operating model underneath it was never designed to carry the load.Strategy sets direction. The operating model determines whether direction becomes action. And most operating models, examined honestly, are not designed at all. They are org charts - boxes and reporting lines - presented as though structure were the same thing as execution. It is not.

The Three Fault Lines: Where Operating Models Break Down

When strategies stall, the post-mortem almost always leads back to the same structural gaps.Three fault lines account for the vast majority of execution failures - not market misjudgement, not lack of effort, but design failures buried in the wiring of the organisation itself.

Decision Rights in Practice

The matrix organisation is so often blamed for organisational slowness. Yet the matrix is rarely the problem in itself; the problem is a matrix in which no one has specified who decides when two lines disagree.Hierarchy, geography, function - any of these can create productive tension when decision rights are explicit. The same configurations become paralysing when they are not

Information Flow: The Invisible Architecture

Information flow is unglamorous work, and it is where much of the real leverage in operating model design sits.The question is deceptively simple: does the person who owns the decision have access to the information they need to make it well, when they need to make it?In practice, the answer is frequently no - and the gap is structural rather than technical.

Accountability That Is Actually Accountable

This is where many operating models are weakest, and where the design challenge is most politically charged.Clarity about who owns an outcome requires naming individuals rather than functions, distinguishing primary accountability from contributing roles, and accepting that single ownership sometimes sits uncomfortably with collaborative culture.The discomfort is real but the alternative is worse.

The Test That Matters: Does the Decision Get Made on Tuesday?

The test of an operating model is not whether it looks coherent on a slide.
It is whether a decision that needs to be made on a Tuesday actually gets made on that Tuesday, by someone who owns it, with the information to make it well.Run that test against a real, recent decision that went slowly - one that should have been straightforward - and the fault line usually reveals itself immediately: no one owned it, or the owner could not see what they needed, or three people owned it equally and no one felt empowered to move.

Enterprise StrategyWhy Transformation Programmes Drift

Transformations rarely fail with a bang.
They drift quietly, as the baseline moves and no one re-anchors to it.A programme that is cancelled forces a reckoning. A programme that drifts absorbs the organisation's money and attention for years while slowly ceasing to matter.Drift does not announce itself. That is precisely why it wins.

The Quiet Failure Mode

Large transformation programmes are usually described as failing dramatically - cancelled, over budget, abandoned.
In practice, that is rarely how they die. The direction stays roughly right, the activity continues, the reporting stays green, and yet somewhere along the way the programme stops delivering what it was set up to deliver.No single decision caused it. That is precisely the problem.

For senior leaders, this is the most important distinction in programme governance. The visible failures are the ones that get managed. The invisible ones are the ones that consume organisations.

How the Baseline Moves

The mechanism behind drift is almost always the same: the baseline moves and no one re-anchors to it.A transformation is launched against a set of assumptions - about the starting position, the environment, the resources, the timeline.
Those assumptions were reasonable on day one. But the world does not hold still for the convenience of the programme plan.

Costs shift, priorities move, the organisation reorganises, the original sponsors leave.
Each change is small. None of them, on its own, seems worth reopening the plan for. The accumulation of unremarked small changes is exactly what drift is.It is not a single point of failure - it is the sum of many small accommodations, each of which felt entirely reasonable at the time.

The Sponsor Turnover Problem

Sponsor turnover deserves particular attention. It is the most reliable driver of drift and, paradoxically, the least discussed.
A transformation is commissioned by people who hold its logic in their heads - why it was scoped this way, what it was really for, which trade-offs were deliberate.Those people move on.

This is not a failure of individual capability. It is a structural vulnerability in how large programmes carry their founding logic across leadership transitions.
Without deliberate mechanisms to re-examine that logic, the programme simply continues — in the same direction, for reasons no one can any longer articulate.

Why Green Status Reports Are Not Evidence of Progress

What makes drift a governance failure rather than an execution failure is subtle, and the subtlety matters.
The people running the programme are usually working hard and hitting their milestones. The milestones simply no longer connect to the outcome, because the outcome was defined against a baseline that has quietly expired.

The Antidote: A Rhythm of Re-anchoring

The antidote to drift is not more control or more reporting. Drifting programmes often have plenty of both. The antidote is a deliberate rhythm of re-anchoring: a regular, honest re-examination of whether the assumptions the programme was justified on still hold, and a mechanism to escalate the ones that have moved.

This is the same discipline that governs a well-maintained financial model - assumptions owned, changes surfaced rather than absorbed, decisions made explicitly rather than by default.Applied to a change programme, it transforms periodic governance reviews from ceremonies of reassurance into genuine moments of accountability.

The Questions Boards and Chief Executives Should Be Asking

Reopening the baseline looks like admitting the plan was wrong. It is the opposite.The plan was right for the world it was written in. The discipline is noticing when that world has moved, and adjusting deliberately rather than drifting by default.An organisation that re-anchors on a rhythm is not being indecisive - it is refusing to let a plan outlive the reasons it was made.

The organisations that manage this well share a single characteristic: they have made re-anchoring normal rather than exceptional.The question is not treated as a sign of strategic weakness. It is treated as the most important question in the room. That cultural shift - from "proving the plan is working" to "testing whether the plan still applies" - is ultimately what separates programmes that deliver from programmes that drift.

Strategic FinanceFeasibility Under Uncertainty

A feasibility study that produces a single answer has hidden the most useful information it holds - the conditions under which that answer flips.
This article argues that real feasibility is not a verdict but a map, and that the discipline of breakeven thinking transforms appraisal from a formality into a genuine decision-making instrument.

The Danger of the Binary Verdict

Feasibility is usually treated as a gate: a study is commissioned, a verdict is returned, the project is viable or it is not, and the organisation moves on. The comfort of that binary is exactly what makes it dangerous.
A single answer conceals the one thing an executive actually needs to know - how fragile that answer is.The standard appraisal process rewards precision over honesty. A figure carried to two decimal places feels like knowledge; it is often just a tidy summary of a dozen contestable guesses, each compounding the next.

The apparent clarity of a single-point return masks the web of assumptions holding it up.

Real feasibility is not a yes or a no. It is a map of the conditions under which the answer changes. Until that map exists, the organisation has not completed its analysis - it has merely deferred the hard questions to the execution phase, where resolving them is far more costly.

Two Projects, One Number - A Dangerous Equivalence

Consider two projects that both clear the hurdle rate by the same margin. On a single-point appraisal they look identical, and capital gets allocated as though they are. But one clears the hurdle across almost any reasonable version of the future, and the other clears it only if sales prices hold, costs behave, and the programme runs to time.They are not the same proposition.

One is robust; the other is viable only in the base case - which is to say viable only on paper.
Treating them equivalently is not a minor analytical imprecision. It is a systematic misallocation of capital that compounds across a portfolio over time.

The discipline that separates these two propositions cannot be found in the headline return figure.
It can only be found by asking a different question entirely - not what the return is, but at what point it stops being a return worth having.

Breakeven Thinking: The Main Event

Rather than asking "what is the return", the more decision-useful question is: "at what point does this stop working?"

At what absorption rate, what cost overrun, what delay, what funding cost does the case break?
Those breakpoints are far more valuable than the headline figure, because they tell you which assumptions you are truly betting on and how much room you have before the bet fails.

This reframes the sensitivity analysis from a formality appended to the back of an appraisal into the main event.
Sensitivity is not a disclaimer - it is the analysis. The question is not whether the numbers are sensitive to assumptions (they always are), but precisely how sensitive, and whether the organisation has the capability to manage within those bounds.Breakeven thinking also imposes a useful discipline on the model-builder. When you must identify the point of failure rather than merely the base case, you are forced to confront which variables are genuinely load-bearing and which are cosmetic. That process of identification is itself strategically valuable, long before any numbers are presented to a board.

Changing the Conversation with Decision-Makers

The framing of a feasibility recommendation changes the quality of the decision it produces. Two formulations that convey equivalent underlying information produce entirely different executive responses and entirely different quality of governance.

The second version respects the intelligence of the people approving the capital. It transforms the feasibility paper from a document that seeks approval into a document that equips a decision. That is a meaningful distinction. Seeking approval is a transactional act; equipping a decision is a governance one.

For a chief executive weighing where to commit, the robust project and the fragile one demand different levels of oversight, different contractual protections, and different contingency provisions, not the same signature on the same approval form. The breakpoint framing makes that differentiation possible. The single-point framing obscures it entirely.

The Portfolio Consequence

There is a portfolio consequence that matters even more than the single-project view. When every feasibility study is expressed as a single point, projects cannot be compared on anything except that point - and so capital flows to the highest number, not the best risk. The most aggressive modeller wins, not the most credible proposition.When each project is expressed as a range with its breakpoints exposed, comparability improves enormously. You can see which assets are robust and which are fragile. You can identify which projects cluster their risk in the same place, all exposed to construction cost inflation, say, or all dependent on the same absorption assumption, and where the real concentration in the portfolio sits.

That is a strategic view a stack of point estimates can never provide. The portfolio managed through breakpoint thinking is not just better analysed, it is better constructed, because the selection criteria reward resilience alongside return.

Feasibility as Decision Instrument

None of this makes feasibility slower or more academic. The additional work required to identify breakpoints is modest relative to the modelling effort already invested. What changes is not the volume of analysis but its orientation - away from producing a verdict and towards equipping a decision.Decisions in the real world are never made under certainty. They are made by people who need to understand what has to be true for a plan to hold, and what they will do if it does not. A feasibility study that answers only the first half of that question has done half the job.

The purpose of a feasibility study is not to produce a verdict. It is to equip a decision. And the most powerful thing it can equip a decision-maker with is an honest answer to the question: what has to be true for this to hold?