methodatlas
RunsheetDecision Making

Assumption Surfacing

ComplexityLow
Time45-90 min
Participants2-8
FormatWorkshop + async
MaturityEstablished
01

Prerequisite

What needs to be finished first

Complete firstProblem Framing Workshopnot in catalog

The initiative, idea, or decision is described in one sentence and its wording is stable.

Without: Without a clear anchor idea, assumptions turn into generic strategy theater with no link to the initiative.
02

Preparation

What needs to be ready before start

Materials

Whiteboard or Miro board with a two-axis grid (importance, uncertainty); sticky notes; pens; timer; prepared list of typical assumption categories (users, market, technology, business model, organization).

People / roles

One facilitator who separates assumptions sharply and leads the rating; two to eight participants with different perspectives; one scribe for the learning plan.

Pre-read

Initiative in one sentence; existing arguments and rationales; known data or research; time horizon and budget for assumption tests.

Time needed

45-90 min

Setup

Put the initiative at the top of the board. Prepare the two-axis grid (X: uncertainty, Y: importance). Make the assumption categories visible. Rule: an assumption is anything we believe without knowing.

03

Core question

The one question this method answers

Which implicit assumptions hold up the initiative, and which of them are so important and uncertain that we need to test them before implementation?

04

Flow

Marker: Phase

StepDurationActionHint
1Phase 1: Clarify the initiative
5-10 minRead the initiative or decision aloud and clear up misunderstandings. Agree on one sentence that will not change for the rest of the workshop.If the initiative still changes during the workshop, the set of assumptions changes with it. Fix it first.
2Phase 2: Collect assumptions
20-30 minFor each category (users, market, technology, business model, organization), do 5 min of solo writing, then place the notes on the board. Aim for at least three assumptions per category.Assumptions often start with 'of course', 'naturally', or 'everyone knows'. Saying those phrases out loud helps reveal them.
3Phase 3: Rate importance and uncertainty
15-20 minFor each assumption, make two ratings: how important if wrong (1-5)? How uncertain (1-5)? Place the assumptions in the grid. Mark the top quadrant (high x high).Uncertain is not the same as unknown. If we believe it is true but do not have evidence, it is uncertain. Gut feeling is not evidence.
4Phase 4: Choose critical assumptions
10-15 minSelect the top 3 assumptions from the 'important and uncertain' quadrant. For each one, ask: what would we do if it were false?If the answer is 'then the initiative fails', testing before implementation is mandatory. If the answer is 'then we adapt', testing is useful but not mandatory.
5Phase 5: Learning plan
10-15 minChoose one test per critical assumption: interview, smoke test, data analysis, spike, expert review. Note owner, date, and success criterion.Tests must be cheaper than being wrong about the assumption. Anyone proposing a 6-week pilot for an assumption that could be tested in a 30-minute interview is optimizing badly.
05

Artifact

What comes out at the end

Form

Importance-uncertainty grid as an image plus structured Markdown with the initiative, full assumption list per category, ratings, top 3 critical assumptions, and a learning plan with owner and date per test.

Versioning / ownership

One entry per initiative with date. After each assumption test, update the assumption status: confirmed, disproved, or modified. Keep old assumptions and set a status instead of deleting them.

Tool alternatives
  • Miro with a 2x2 grid
  • Notion database with filters for importance and uncertainty
  • Google Sheet with sorting
  • Whiteboard with photo export

assumption-surfacing-working-template.md

Compact working template for Assumption Surfacing with context, input, output artifacts, and next step.

Assumption Surfacing Working Template

Goal

Makes implicit assumptions behind ideas, decisions, or strategies visible.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • Assumption List:
  • Critical Assumptions:
  • Learning Plan:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

06

Example output

Concrete filled scenario, fictional example

assumption-surfacing-beispiel.md

Concrete filled scenario, fictional example

Assumption Surfacing - New customer activation via the Sabine persona (20.05.2026)

Initiative: We are building a 5-day onboarding flow for solo tax advisors like Sabine to increase activation from 22% to 38%.

Assumption excerpt:

  • Users: Sabine has at least 3 x 10 minutes available for onboarding in the first 7 days (importance 5, uncertainty 4).
  • Market: There are enough solo tax advisors in the tier-1 segment to justify the effort (5, 3).
  • Technology: Inline email linking with app deep links works in Outlook (3, 5).
  • Business model: Activation translates into 25% higher retention after 90 days (5, 5).
  • Organization: Support has capacity to handle onboarding-related tickets in the first 4 weeks (4, 2).

Critical (top 3, quadrant 4-5 x 4-5):

  1. Sabine's time window. Test: 8 interviews with solo tax advisors, asking about onboarding time budget. Owner: @anna, by 30.05. Success: at least 5 of 8 report 30 min in week 1.
  2. Activation -> retention. Test: Cohort analysis of existing data. Owner: @lisa, by 25.05.
  3. Deep links in Outlook. Test: spike with 3 Outlook versions. Owner: @ben, by 22.05.
07

Pitfalls

Recognize symptoms and steer against them

Trap

Assumptions sound like facts

Symptom

The list contains statements like 'users want X' even though nobody has spoken to users.

What to do

Check every assumption: is there evidence that supports it? If not, it remains an assumption. If yes, it becomes a fact with a source.

Trap

All assumptions become critical

Symptom

There are 15 assumptions on the top quadrant and the learning plan becomes unrealistic.

What to do

Limit the method to at most 5 critical assumptions. Repeat the method if there are more, instead of weakening the filter.

Trap

Rating turns into discussion

Symptom

Phase 3 takes 45 min because the group debates every assumption one by one.

What to do

Use dot voting or star distribution in parallel, not sequentially. Discuss only the assumptions that remain disputed.

Trap

Learning plan without success criterion

Symptom

Tests are named, but nobody knows what counts as passed.

What to do

Define a concrete success criterion for each test ('at least 5 of 8 report X'). Otherwise the test becomes gut-feel confirmation.

Trap

The method becomes routine theater

Symptom

An assumption workshop is scheduled for every small initiative and energy drops.

What to do

Use the method only for substantial initiatives. For routine decisions, a 10-minute checklist per assumption category is enough.

08

Stop criteria

Done signals checkable in under a minute

The initiative cannot be written in one sentence or keeps changing during the workshop.
The assumption list stays below 8 items, which means the initiative is too trivial or the group is missing the implicit work.
There is no diversity in the group and only one function is represented, leaving blind spots.
The workshop is scheduled for less than 30 min, so the five phases cannot be done.
No resources are available for assumption tests, so the learning plan remains theory.
The initiative is a routine decision, so the method would only create bureaucracy.

Finished the runsheet?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.