A leadership team can fall in love with a strategic idea long before it has earned confidence. The stronger the sponsor, the more easily enthusiasm becomes certainty.
Pressure-testing is not about killing bold ideas. It is about finding the assumptions that could break the bet while the organization can still learn cheaply.
Playing to Win uses the question “What would have to be true?” to move strategy discussion from opinion toward assumptions that can be tested. In a workshop, that question is especially useful when leaders are confident but the evidence is still incomplete.
Turn confidence into assumptions you can examine
A leadership team wants to expand a premium service into a new region. The proposal is persuasive, the market looks large, and the sponsor is enthusiastic. Instead of asking whether people “support the strategy,” ask what must be true for the bet to work. Customers must value the premium enough to pay for it. The company must recruit or redeploy scarce specialists. Delivery costs must stay inside a workable range. Competitors must not be able to copy the promise too easily.
The workshop changes when those assumptions are written separately. A leader who is uncomfortable with the expansion no longer has to attack the whole idea. The leader can say, “I am not convinced the talent assumption is true,” and the group can decide what evidence would reduce that uncertainty.
Some assumptions can be researched. Others need a small test. The practical discipline is to identify the few assumptions that are both uncertain and capable of breaking the bet, then match the evidence burden to the size and reversibility of the commitment.
Ask what must be true
Instead of debating whether the strategy is right, ask what must be true for it to work. What must be true about customers, competitors, economics, capabilities, technology, regulation, timing, and management support?
Write the assumptions separately from the bet. This makes it possible to challenge the logic without attacking the person who proposed it.
Not every assumption deserves equal analysis. Identify the ones that are both uncertain and capable of destroying the strategy. Then ask what evidence already exists and what could be tested quickly. A bold bet becomes more intelligent when the team knows where it is most vulnerable.
Assign a small group to search for disconfirming evidence and plausible failure modes. Their job is not to be cynical. It is to protect the organization from one-sided confidence.
After the challenge, the original team must be allowed to revise the bet. Pressure-testing should improve strategy, not become a debate competition.
Turn assumptions into a test plan
After identifying the critical assumptions, separate those that can be researched from those that need real-world testing. Customer willingness may require interviews or a pilot. Operational feasibility may require a process simulation. Economics may require a simple model with ranges rather than a single forecast.
Give each high-risk assumption an owner, a near date, and a decision it could change. This converts uncertainty from a reason to delay into a learning agenda.
Pressure-testing can become another hiding place. If the decision is reversible and the downside is contained, the better move may be a small strategic test rather than another month of debate. Match the evidence burden to the size, risk, and reversibility of the commitment. The purpose is to shorten the odds, not eliminate uncertainty.
When two strategic options are competing, ask what would have to be true for each to succeed. Then compare the assumptions. One option may depend on customer behavior that can be tested quickly; another may depend on a capability that will take years to build. The comparison becomes more useful than asking which proposal sounds more persuasive.
This approach also gives minority views a legitimate place. A participant can challenge an assumption without having to oppose the whole strategy.
For every unresolved critical assumption, write the question the organization needs reality to answer. “Will priority customers pay for guaranteed recovery?” is better than “validate the model.” The more concrete the learning question, the easier it becomes to design credible evidence. That question should travel with the bet into execution so the organization remembers what it is trying to learn.
Build a What-Must-Be-True board
Draw three columns: Assumption, Evidence We Have, and Evidence We Need. Ask participants to write assumptions individually before discussion, then cluster them under customer, competitor, capability, economics, and execution. This prevents the loudest skeptic from defining the entire risk picture and gives supporters permission to name uncertainties in their own proposal.
Next, mark the assumptions that are both highly uncertain and capable of breaking the bet. Those become the learning priorities. Some may be resolved with existing data; others need interviews, a pilot, a prototype, or a limited market test. The workshop should leave with a smaller set of questions the organization genuinely needs reality to answer.
What should travel with the bet
The team can name the critical assumptions, what evidence would change its mind, and what should be tested before larger commitment. A strategy that survives unchanged because nobody challenged it has not necessarily become stronger.
Write the three assumptions most capable of breaking the bet, then name the evidence that could change the decision. For the strategy-side logic, see Choose the First Strategic Bet. Then identify what the strategy requires with Name the Capabilities the Strategy Depends On.