Gumshoe · Method reference

Assumption mapping

Surface the beliefs a plan depends on and sort them by risk so you test the scariest ones first.

Conceptual illustration of assumption mapping.
Effort
Low
Participants
Not required
Remote friendly
Yes
Evidence / output
Inference

What it is

A workshop technique that lists the assumptions underlying an idea and plots them on two axes, how much is known and how important, to reveal which unknowns are most dangerous.

When to use it

During Initiate and Synthesize, before committing to a direction whose success rests on unproven beliefs.

Why (value)

Makes hidden, high-risk assumptions visible so the team invests research where it matters most instead of testing what it already knows.

How to run it

  1. Brainstorm the assumptions behind the idea (desirability, viability, feasibility).
  2. Plot each on known-to-unknown and unimportant-to-important axes.
  3. Focus on the important-and-unknown quadrant.
  4. Turn those into hypotheses and plan experiments.
  5. Revisit as you learn.

Inputs and outputs

  • Inputs: A proposed idea or plan and a cross-functional group to surface beliefs.
  • Outputs: A prioritized map of risky assumptions and a testing plan.

Time and effort

Low. A single workshop session.

Evidence and limitations

Mapping organizes beliefs; it does not validate them. The output is a research agenda, not findings. See Evidence and limitations.

Tips and pitfalls

  • Include diverse roles, blind spots cluster by function.
  • Be honest about what is truly unknown vs. assumed-known.
  • Prioritize by risk, not by ease of testing.

Variations

Riskiest-assumption test, assumption slip method, desirability-viability-feasibility framing.

Need help choosing and applying a method?

Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.

Discuss your project with Gumshoe Explore Gumshoe services

Sources and further reading

Explore related methods

  • Lean hypotheses — State beliefs as testable predictions so you can learn quickly instead of debating opinions.
  • Premortem — Imagine the project has failed, then work backward to surface risks while you can still act.
  • Opportunity solution trees — Connect a desired outcome to the opportunities that drive it and the solutions that address them.

A general practice reference. This page does not establish that a method was used on a particular client project or that an outcome was measured.