On this page5
Colleagues lining up cards in order along a long desk
Test strategy assumptions that could change your strategic choice before you commit: focus on the beliefs that would make you choose a different path if they proved wrong. Compare plausible futures, identify what evidence would distinguish them, and set a review point before you act.
What you’ll learn
- How to name the assumptions behind a strategic choice
- How to rank assumptions by whether they could change the decision
- How to compare plausible futures and the evidence each would require
- How to set review points before committing
Which assumptions sit underneath your strategy?
Start by writing the strategic choice in one sentence. Then list the beliefs that must hold for that choice to make sense. The list is not a case for the strategy. It is a set of claims that evidence could support or weaken.
Separate what you have observed from what you believe. A change in orders may be observed company state. The belief that a new customer group will buy at a sustainable price is an assumption. So is the belief that your team can serve that group without slowing work for existing customers.
For each assumption, name the evidence that would change your view. Avoid statements that can explain any result after the fact. A useful assumption points to something observable: a customer response, a signed order, a delivery cost, or a missed deadline.
Example: A small fictional design firm is choosing between serving local shops and larger regional groups. Its choice depends on whether regional buyers will pay for a longer project, whether the firm can meet their review requirements, and whether its current referral channel can reach them. A buyer asking for a proposal is weak support for demand; a signed project at the intended price is stronger evidence.
Tip: Write each assumption so that a specific piece of evidence could change your view.
Company state helps keep observations distinct from beliefs. Brainis maintains a live model of company state with sources, freshness, and confidence. Read about company state and what company state means before you use the record to test a strategic idea.
How do you test strategy assumptions that could change the choice?
To test strategy assumptions well, begin with the decision, not with the easiest thing to measure. Ask whether a different answer to this assumption would lead you to choose a different strategy. If not, it may still matter for execution, but it should not outrank a belief that could change the path.
Then consider two things: the consequence of being wrong and how uncertain the evidence is. A belief with high consequences and weak evidence deserves attention before commitment. A low-impact belief with clear evidence can wait. This is a judgment, not a precise score. Write down why you ranked each assumption where you did.
For the fictional design firm, customer demand, delivery cost, and channel access do not carry the same risk. If regional buyers will not pay the intended price, the segment may not be worth choosing. If delivery costs are higher than expected, the firm might change its offer or price. If the referral channel is weak, it might test another route after a limited first step. The demand question may block commitment; channel access may be checked during a small launch.
Separate what must be known before choosing from what can be learned without making a large commitment. A limited test is useful only if its result can change what you do next. Otherwise, it is activity that leaves the central assumption untouched.
A small team mapping a project plan on a glass wall
How can you compare plausible futures before committing?
A comparison of futures is not a confident prediction about which one will happen. It is a way to make the conditions behind each strategic path visible. Describe each future as a conditional case: if these assumptions hold, this path may make sense; if they do not, a different path may be better.
Connect each case to the assumptions it depends on. Then name evidence that would help distinguish the cases. The evidence should be relevant to the choice, not just easy to collect. If two futures differ mainly in customer demand, more internal discussion will not settle the question. A customer response at the intended price may help.
| Assumption | Future if it holds | Evidence to check |
|---|---|---|
| Regional buyers will pay the intended price | The firm can serve a larger project segment | A buyer accepts a proposal at that price |
| Delivery reviews fit the team's capacity | The firm can meet the segment's requirements | Time spent on review and rework |
| The current referral channel reaches buyers | The firm can find customers without changing its route to market | Qualified introductions from that channel |
Brainis models alternative futures before recommending a path. Its predictions carry ranges and a model version, and remain unchanged when reality arrives. That record makes it possible to compare what was expected with what happened, rather than adjusting the old forecast to fit the result. See the world model, why ranges beat certainty, and what a business world model predicts.
Important: Keep the evidence and assumptions visible beside each future, so a preferred story does not stand in for a tested choice.
What evidence should trigger a review of the strategy?
For each high-impact assumption, choose an observable signal and decide what result would make you keep, change, or pause the strategy. A review point is not a promise that the answer will be clear. It is a commitment to look at the evidence and reconsider the choice when the agreed signal arrives.
Choose a signal that bears on the assumption. If the question is whether buyers will pay, track responses at the intended price, not general interest in the offer. If the question is delivery capacity, look at the work and cost required to meet the promised service. Decide in advance what would count as enough support, what would weaken the case, and what remains inconclusive.
Name who will review the evidence and where the decision will be recorded. Without an owner, a signal can arrive without anyone acting on it. Without a record, the team may later remember its expectations differently from what it actually wrote down.
Brainis records predicted and actual outcomes in the Decision Ledger, where they improve the next recommendation. You can use memory and the guide to writing predictions down to see the relevant material. Keep the original forecast intact when you review it; compare it with the result rather than rewriting what you expected.
A project lead moving task cards across a planning board
What should you do before you commit?
Before committing, write down the choice and the assumptions that could make you choose differently. For each one, record what you know, what remains uncertain, and what evidence would change your view. Keep observed company state separate from assumptions about customers, competitors, and execution.
Next, compare the plausible futures. State the conditions each path depends on and the evidence that would distinguish them. Identify which assumption blocks commitment and which can be checked through a limited first step.
Set a review point before acting. Name the signal, the person who will review it, and the result that would keep, revise, or stop the chosen path. Record the expected outcome before the evidence arrives, so the later comparison stays fair.
Then make the decision with the evidence you have, not with certainty you do not have. At the review, compare the result with the original expectation and decide whether the strategy still fits. Brainis's strategy engine is the relevant page for this part of the process.
Brainis Team
Notes on running a company with Brainis, from the people building it and running on it.