← Back to blog

Rehearse the Future Before You Commit: A Creative Leader’s Guide to Testing Assumptions

Tucker Bryant · 10/5/2026

Before making a hard-to-reverse decision, imagine contrasting futures, expose the assumptions behind your plan, and design small tests that could change your mind.

To prepare for an uncertain future, I’d start with a decision rather than a prediction. Name the commitment you’re considering, imagine several contrasting futures in which it would have to work, and identify what you’re assuming in each one. Then choose a small, bounded test that could change your decision before you make the expensive or hard-to-reverse part.

I’m Tucker Bryant, an artist, keynote speaker, and former Google product marketer. My recommendation is to use creative thinking here not to generate more possibilities indefinitely, but to rehearse a few consequential ones. The question isn’t “Can we imagine the future?” It’s “What would we do differently if our favorite version of it never arrived?”

Start with a commitment, not a trend

Washington University’s leadership guide defines uncertainty in terms of limited knowledge about present conditions and future outcomes, making accurate prediction and planning difficult. That definition gives this exercise a useful starting point: what don’t we know that matters to the decision in front of us?

I’d avoid opening with “What will our industry look like in five years?” Start narrower:

  • What are we about to fund, launch, replace, or stop?
  • Which part would be difficult to undo?
  • When must we decide, and what could we learn before then?

For a hypothetical example, imagine a leadership team considering a self-service customer onboarding platform. The proposed commitment includes a multiyear technology contract and dissolving the specialist onboarding team.

Rather than debate whether self-service is “the future,” write the actual decision: “Should we commit to this platform and remove the staffed alternative?” That wording gives the rehearsal something specific to challenge.

Write the assumptions your plan needs

Next, finish this sentence several times: “This commitment makes sense if…” Keep each answer concrete enough to question.

For our hypothetical onboarding decision, the list might include:

  • Customers can complete essential setup tasks without specialist help.
  • Customer needs will remain simple enough for the proposed workflow.
  • The platform can accommodate changes without extensive custom work.
  • Enough customers will choose self-service to justify the commitment.

These are not findings. They are conditions the imagined plan depends on. Beside each, record what you actually have: direct observation, an estimate, an analogy, or no evidence yet.

I’d then ask two questions: “How much does the decision depend on this being true?” and “How little do we know about it?” Prioritize assumptions that combine high consequence with thin evidence.

This is where I’d apply Write By Erasing, one of the four principles in my keynote Do Different Things Differently. For this exercise, erase the least-supported premise temporarily. If customers do not prefer self-service, what remains of the business case? Don’t defend the missing premise yet. Examine what its absence exposes.

Imagine contrasting futures, not just better and worse ones

I’d resist making three versions of the same forecast: optimistic, expected, and pessimistic. Instead, choose two uncertainties that would change what you should do.

For the onboarding example, suppose those uncertainties are customer volume and setup complexity. Rehearse four possibilities:

  • High volume, simple needs: many customers arrive with straightforward requirements.
  • High volume, complex needs: many arrive, but their setups require substantial judgment.
  • Low volume, simple needs: the workflow fits, but fewer customers need it.
  • Low volume, complex needs: fewer customers arrive, and each needs considerable attention.

These are deliberately invented conditions, not forecasts. Make each concrete enough to discuss: What would customers need? Where would the proposed platform fit? What would the team regret removing?

Under each future, write three responses: what you would keep, what you would change, and what you would wish you had preserved.

Here I’d use Be Who You Aren’t: examine the same future from the position of a first-time customer, a support specialist, or the person responsible for the contract. Treat those imagined perspectives as prompts for questions, not substitutes for asking the actual people involved.

Separate preparation from prediction

An argument excerpted in MIT Sloan Management Review emphasizes sensing changing conditions and adapting rather than accurately predicting the future. That framing is the one I’d bring to this rehearsal.

Don’t ask the team to vote on which imagined future will happen. Ask what you would want to do across several futures, what should wait, and what observable change would warrant another look.

In our hypothetical case, documenting existing onboarding tasks might be worth doing in all four scenarios. A limited platform trial might be worth trying before the full contract. Dissolving the specialist team might remain conditional on evidence that complex needs can still be served.

For each conditional commitment, name a signal and an owner. For example: “The onboarding lead will review where trial participants request specialist help before we decide whether to remove that option.” “Watch customer behavior” is too vague for the exercise I’m proposing. Specify what someone will observe and which decision it could affect.

Design a test that could disappoint you

MIT Sloan Management Review presents treating decisions as experiments, including using hypothesis-oriented language, as an approach to acting under uncertainty. Its discussion offers a useful practice, not measured proof that this particular rehearsal method works.

My suggested test brief has six parts:

  • Assumption: What must be true?
  • Test: What limited activity could reveal relevant evidence?
  • Boundary: How much time, money, and exposure are acceptable?
  • Observation: What will you record, including exceptions?
  • Decision rule: What evidence would make you proceed, revise, pause, or stop?
  • Owner and date: Who will review the evidence, and when?

For the hypothetical platform, invite a small, opt-in group to try a prototype while preserving access to staffed help. Observe which essential tasks they complete, where they request assistance, and what kinds of needs the prototype cannot accommodate.

Before starting, define what would count as an unacceptable gap in essential service. Don’t choose the standard after seeing the results. Also record whom the trial includes and excludes; avoid treating a narrow trial as an answer about every customer.

I’d apply Think Inside the Box by setting deliberate constraints: a fixed budget, a short window, and no withdrawal of essential support. Then use Aim for the Trash Can by designing the test to expose a reason to discard or substantially revise the proposal—not merely collect encouraging reactions.

Decide what the rehearsal changes

At the review, put the original assumption beside the observations. Separate what happened from what you infer and what remains unknown.

Then make a decision at the scale the evidence supports. You might expand the trial without signing the full contract. You might keep specialist support for complex cases. You might abandon the platform proposal while retaining what you learned about onboarding needs.

Ask one final question: “What are we now willing to commit to, and what are we deliberately leaving open?”

For me, that is the point of rehearsing the future. Not postponing every commitment until certainty arrives, and not turning imagination into a forecast. Use imagination to identify the question worth testing. Use the test to decide what to do next.

FAQ

How is future rehearsal different from brainstorming?

In this exercise, the starting point is a pending commitment, not an open search for ideas. Generate only enough contrasting futures to examine that commitment. The intended output is an assumption to test and a decision rule—not a longer list of possibilities.

What if we have very little time before deciding?

Reduce the scope. Choose one consequential assumption and identify the smallest useful observation you can gather before the deadline. If no meaningful test is possible, document the uncertainty and consider whether you can narrow the commitment or preserve a way to revise it.

How does this connect to Tucker Bryant’s leadership keynote?

My signature keynote, Do Different Things Differently, centers on Write By Erasing, Think Inside the Box, Aim for the Trash Can, and Be Who You Aren’t. Here, I’ve applied those principles to a specific leadership task: questioning a commitment before locking it in. You can explore my speaking approach for more context.

What should I look for in a leadership and future-thinking speaker?

I’d start with the work you want leaders to do afterward. Ask how the proposed session connects imaginative thinking to your decisions, constraints, and next steps. For this topic, I’d also ask how the speaker distinguishes hypothetical scenarios from evidence and predictions.

If you’re thinking about how to bring this kind of creative discipline into a leadership gathering, I’d welcome a conversation about the decisions your team is facing. You can get in touch here.