How to Test Strategic Assumptions Before Committing Capital

Most strategic failures in financial services are not caused by bad execution. They are caused by assumptions that were never tested, or were tested too late to matter. By the time a distribution partnership underperforms, a new product misses its adoption curve, or an acquisition fails to generate the expected cross-sell, the capital is spent and the reputational cost of reversing is high. Testing assumptions before committing is the discipline of finding out what you are wrong about while it is still cheap to be wrong.

Key Executive Takeaways

• Every strategy rests on a small number of load-bearing assumptions; identify them explicitly and rank them by how much of the thesis collapses if they are false.
• The goal of testing is not to build confidence in the plan, it is to find the fastest, cheapest way to disprove the assumptions most likely to be wrong.
• Set decision triggers and kill criteria before you start testing, otherwise evidence gets reinterpreted to justify the direction you already prefer.

Start by separating assumptions from decisions

Most strategy papers blur the two. A proposal to enter a new client segment might contain twenty statements presented as fact. In reality, perhaps four of them are load-bearing: assumptions where, if wrong, the whole case collapses. The rest are either well-evidenced or immaterial. Your first job is to strip the document down and list the assumptions the strategy actually depends on. Be honest about which ones are inherited from the person championing the deal.

A useful test: for each assumption, ask what would have to be true for this to hold, and what evidence you currently have. If the answer is "industry reports" or "management judgement," flag it. Those are not evidence, they are placeholders.

Rank assumptions by fragility and consequence

Not all assumptions deserve equal scrutiny. Rank them on two axes: how confident you are that the assumption holds, and how much of the strategy fails if it does not. The assumptions that are both uncertain and consequential are where you spend your testing budget. Everything else can be monitored rather than tested.

Where teams go wrong is testing what is easy to test rather than what matters. Market sizing gets three analysts and a McKinsey report. The assumption that intermediaries will actually recommend the product gets a conversation at a conference.

Design tests that can fail

A test that cannot produce a disconfirming result is not a test, it is a rehearsal. For each load-bearing assumption, design the cheapest possible way to generate evidence that could kill it. Options include:

• Structured interviews with the actual decision-makers you need to win, not their deputies, using questions designed to elicit reasons they would say no.
• Small pilots with real money and real clients, not simulations. A ten-client pilot with genuine commercial terms tells you more than a hundred-client survey.
• Pre-mortems where the team assumes the initiative has failed in three years and works backwards to plausible causes.
• Reverse due diligence: brief an internal or external team to build the strongest case against the strategy and present it to the sponsor.

The common failure is confirmation-shaped testing. If your pilot is designed around friendly clients, sympathetic distributors, and a subsidised price, you will learn nothing about whether the strategy works in the wild.

Set decision triggers before evidence arrives

Before testing begins, write down what result would cause you to proceed, pause, or stop. Specificity matters: "conversion rate below 8 percent in the pilot" is a trigger, "weaker than expected performance" is not. Circulate these criteria to the investment committee or board before the tests run. This is the single most effective defence against motivated reasoning later.

Bring the sceptics in early

Risk, compliance, and second-line functions are usually consulted after the strategy is formed. That is too late. Invite them into the assumption-mapping stage. They see failure patterns across the firm and will often flag the assumption that nobody in the business unit wanted to question. This is also how you build a defensible record that the decision was tested, not sold.

The decision point

Before your next major commitment, ask: what are the three assumptions this strategy depends on, what evidence do we actually have for each, and what would change our mind? If you cannot answer those questions in a page, you are not ready to commit capital. You are ready to start testing.

Frequently Asked Questions

How long should assumption testing take?

Weeks, not quarters. The point is speed and cost, not exhaustiveness. If testing takes as long as executing, you have designed the wrong tests. Time-box each test and accept that some answers will be directional rather than definitive.

Who should own the testing process?

Not the strategy sponsor. Ownership should sit with someone whose reputation is not tied to the decision proceeding, typically a strategy function, a designated challenge team, or a board sub-committee for the largest bets.

What if the tests are inconclusive?

Inconclusive is a result. It usually means the assumption is more uncertain than the strategy paper implied, which should change the size of the initial commitment rather than the direction. Stage the investment so early tranches generate the evidence needed to release the next.

How do we avoid analysis paralysis?

Test only the load-bearing assumptions, and only to the point where the answer changes what you would do. If a test result would not alter the decision, do not run it.