What is it?

Assumption Busting is a structured process where a group identifies the hidden beliefs they hold about a problem, product, service, or situation, then systematically challenges each one to open up fresh thinking. You start by listing everything the group takes for granted, then pick the most important assumptions and ask "What if this weren't true?" The result is a set of new possibilities that the group would never have reached through conventional brainstorming, because conventional brainstorming tends to stay inside the boundaries that assumptions create. It is a surprisingly energising exercise because people discover that the real constraints on their thinking are often self-imposed.

Also Known As

• Assumption Surfacing
• Challenge Assumptions

When to Use It

• The group is stuck in "we've always done it this way" thinking and needs a jolt
• You are working on innovation, product development, or service redesign where breakthrough thinking matters more than incremental improvement
• A team keeps generating the same types of ideas and you suspect unexamined beliefs are limiting their range
• The group needs to challenge an existing strategy, business model, or process before committing further resources
• You want to surface the mental models that different team members hold, especially when those models conflict
• A project is about to enter a new phase and the team needs to check whether the assumptions from the last phase still hold
• You are working with a cross-functional group where different departments hold different (and possibly contradictory) assumptions about how things work

When NOT to Use It

• The group needs quick answers. Assumption Busting requires time to list, prioritise, and challenge assumptions properly. If you rush it, you get a shallow list and superficial challenges that do not generate real insight.
• The problem is well-defined and the solution path is clear. If the team already knows what to do and just needs to plan the execution, this technique adds unnecessary complexity.
• Participants are not willing to question the status quo. If senior leaders are in the room and have already committed to a direction, asking the group to challenge the underlying assumptions can create political tension unless those leaders have given explicit permission.
• The topic is too abstract. Assumption Busting works best when you can tie assumptions to something concrete: a product, a process, a customer, a market. If the topic is vague ("How might we be more innovative?"), the assumptions list will be too scattered to work with.
• Trust is low. Surfacing assumptions can feel exposing. If team members are worried about being judged for what they believe, the exercise will stay surface-level.

Assumption Busting as a facilitation technique draws on several traditions. The formal academic roots lie in Richard O. Mason and Ian I. Mitroff's Strategic Assumption Surfacing and Testing (SAST), published in their 1981 book Challenging Strategic Planning Assumptions. Their method was developed for strategic planning and involved forming competing groups, surfacing assumptions, and debating them dialectically. Over time, practitioners simplified the approach into the more accessible "Assumption Busting" format used in workshops today, influenced by creative thinking practitioners such as Michael Michalko (author of Thinkertoys) and the broader creative problem-solving community. The technique now appears in many innovation toolkits and is widely used outside its original strategic planning context.

What You Need

Group size: 4-20 people. Works best with 6-12. Below 4, you do not get enough diversity of assumptions. Above 20, the prioritisation and challenge steps become unwieldy without breaking into sub-groups.

Time required:

• 45 minutes minimum for a focused session
• 60-90 minutes is typical and allows proper depth
• Extended versions (half-day) can include prototyping or action planning after the challenge phase

Space:

• A room with wall space for posting assumptions (flip charts, whiteboards, or large sticky notes)
• Enough table space for small group work during the challenge phase
• Good sight lines so the whole group can see the assumption list during prioritisation

Materials:

• Flip chart paper (at least 3 sheets)
• Markers (multiple colours)
• Sticky notes (two colours: one for assumptions, one for "What if?" ideas)
• Dot stickers for prioritisation voting (5 per person)
• Timer
• Printed assumption categories prompt sheet (optional but helpful for Step 1)

The Process

Setup

1. Define the focus question before the session. This should be specific enough to anchor the group's thinking. Good examples: "What assumptions do we hold about our customer onboarding process?" or "What do we take for granted about how this product reaches the market?" Write this on a flip chart and post it where everyone can see it.
2. Prepare three flip charts labelled: "Our Assumptions," "Priority Assumptions," and "What If?"
3. If using category prompts, prepare a sheet with four to six assumption categories relevant to your focus question (for example: customers, resources, process, technology, competition, regulations).
4. Arrange the room so the group can easily move between seated work and standing at the flip charts.
5. Brief yourself on the focus area so you can probe shallow assumptions during the listing phase.

Step 1: Generate Assumptions

Time: 10-15 minutes

Purpose: Surface as many hidden beliefs as possible before the group starts filtering.

1. Present the focus question and explain the task: "We are going to list everything we take for granted about this topic. Not opinions or ideas, but the beliefs we hold that we never question. The things we assume to be true."
2. Give participants 3 minutes of silent individual thinking. Ask them to write one assumption per sticky note. Prompt them with categories if they stall: "Think about what you assume about the people involved, the resources available, the process, the timeline, the technology, and the external environment."
3. Go round-robin, asking each person to share one assumption at a time. Post each sticky note on the "Our Assumptions" flip chart. Continue rounds until the group has exhausted their list.
4. As assumptions come in, read each one back to the group and check: "Is this actually an assumption, or is it a known fact?" Push the group to distinguish between the two. If someone says "Our customers want fast delivery," ask "Do we know that for certain, or do we assume it?"
5. Aim for 15-30 assumptions. If the list is thin, prompt with: "What would a brand new employee assume about this?" or "What would a competitor assume about us?"

Watch for:

• People listing problems instead of assumptions. Redirect: "That sounds like a problem. What assumption sits underneath it?"
• The group converging too quickly on obvious assumptions. Push for the less comfortable ones: "What do we assume about our own team's capabilities?"

Step 2: Cluster and Prioritise

Time: 10-15 minutes

Purpose: Focus energy on the assumptions that matter most, because challenging every assumption equally leads to shallow results.

1. Ask the group to help you cluster related assumptions together. Move sticky notes into natural groupings and give each cluster a label.
2. Once clustered, explain the prioritisation criteria: "We are looking for assumptions that are both important to our success and uncertain. If an assumption is important but we are confident it is true, it is less interesting. If an assumption is uncertain but does not matter much, it is also less interesting. We want the ones that are both high-stakes and shaky."
3. Give each person 5 dot stickers. Ask them to place their dots on the assumptions they believe are most important to challenge. They can spread their dots across five assumptions or stack them on fewer.
4. Count the dots and identify the top 3-5 assumptions. Transfer these to the "Priority Assumptions" flip chart.

Watch for:

• Groupthink in voting. If the first person to vote puts all their dots on one assumption, others may follow. Ask everyone to vote simultaneously or use a blind voting approach (turn away from the chart, then place dots).

Step 3: Challenge Assumptions

Time: 15-25 minutes

Purpose: This is where the real creative work happens. The group tests each priority assumption by imagining what would be possible if it were not true.

1. Take the first priority assumption. Read it aloud and ask: "What if this were not true? What would be possible then?"
2. Give the group 2-3 minutes to brainstorm silently on sticky notes, writing one "What if?" idea per note.
3. Share ideas round-robin, posting each one on the "What If?" flip chart next to the relevant assumption.
4. After sharing, facilitate a brief discussion: "Which of these feel like genuine opportunities? Which ones make you uncomfortable?" The uncomfortable ones are often the most valuable.
5. Repeat for each priority assumption.
6. For each assumption, you can also ask the group: "What evidence would we need to see to confirm or disprove this assumption? Where could we find that evidence?"

Watch for:

• The group dismissing ideas too quickly with "That would never work." Remind them: "We are not committing to anything yet. We are opening up the thinking space."
• Energy dropping on the third or fourth assumption. If this happens, pick the most provocative remaining assumption and skip to it.

Closing

Time: 5-10 minutes

1. Review the "What If?" flip chart as a whole. Ask the group: "Looking at everything here, what are the two or three most exciting possibilities we have surfaced?"
2. For each exciting possibility, ask: "What is one concrete thing we could do in the next two weeks to test whether this possibility is real?"
3. Capture these actions with owners and deadlines.
4. Close with a reflection: "Which assumption surprised you the most when it came up today?"

Facilitator Guidance

What Makes This Work

Assumption Busting works because it separates the act of identifying beliefs from the act of evaluating them. In most meetings, people jump straight to solutions without ever examining the mental framework they are working inside. By making assumptions visible first and then challenging them deliberately, you give the group permission to think outside boundaries they did not even know existed. The technique taps into the same principle that makes Reverse Brainstorming effective: people find it easier to question and critique than to create from nothing. The prioritisation step is critical because it prevents the group from spreading their energy too thin. And the "What if?" framing keeps the challenge constructive rather than defensive.

Common Pitfalls

• Staying too safe: The group lists only obvious, comfortable assumptions and avoids the politically sensitive ones. Prevent this by modelling courage yourself. Name an uncomfortable assumption early to set the tone: "One assumption I notice is that leadership is fully committed to this project. Is that actually true?"
• Confusing assumptions with facts: Participants list things that are demonstrably true ("We have 200 employees") rather than beliefs they hold ("Our employees prefer working in the office"). Keep testing: "Is this something we know, or something we believe?"
• Skipping prioritisation: It is tempting to challenge every assumption equally. Resist this. The technique loses power when spread across 20 assumptions at surface level. Depth on 3-5 beats breadth across 20.
• Not converting insights to action: The biggest risk is that the session generates fascinating "What if?" ideas that never go anywhere. Always close with specific next steps, owners, and a deadline. Without this, the exercise becomes an interesting intellectual game with no practical value.
• Facilitator leading the assumptions: Your job is to draw assumptions out of the group, not to provide them. If you plant assumptions, the group will not feel ownership of the insights that follow.

Adaptations

• Virtual delivery: Use a digital whiteboard (Miro, Mural, FigJam) with columns for Assumptions, Priority Assumptions, and What If. Silent sticky note generation works well online since participants are already at keyboards. Use the voting feature built into most whiteboard tools for prioritisation. Allow slightly more time for each step (add 5 minutes to Steps 1 and 3).
• Larger groups (20+): Split into sub-groups of 5-7 for the assumption generation phase, then bring the full group together for prioritisation and challenge. Each sub-group posts their assumptions, and the facilitator de-duplicates before voting.
• Shorter timeframe (30 minutes): Skip the clustering step. After generating assumptions, go straight to dot voting, then challenge only the top 2 assumptions. This works as a quick warm-up before a strategy session.
• Longer timeframe (half-day): Add a prototyping or experiment design step after the "What if?" phase. Ask groups to design a low-cost experiment to test whether the most promising "What if?" idea could work.
• Combined with other techniques: Assumption Busting pairs well with Reverse Brainstorming (challenge assumptions first, then reverse-brainstorm solutions), SCAMPER (use the SCAMPER prompts to challenge assumptions from different angles), and Pre-Mortem (surface assumptions about what could go wrong).

Real-World Applications

Product team challenging pricing assumptions: A SaaS product team listed 22 assumptions about their pricing model, including "customers compare us to competitors on price" and "annual contracts reduce churn." Challenging the second assumption led them to discover that their annual contract customers actually churned at the same rate, they just churned in larger batches. This insight reshaped their retention strategy.

NHS service redesign: A hospital team used Assumption Busting to challenge beliefs about patient discharge. One assumption was "patients want to leave hospital as soon as possible." Challenging this surfaced that many elderly patients were anxious about going home and would benefit from a structured transition programme, leading to a new supported discharge service.

Startup pivot decision: A founder used the technique with their team of six to challenge the assumption that "enterprise clients need a dedicated account manager." The "What if?" discussion revealed that a well-designed self-service portal with smart onboarding could serve 80% of enterprise needs, freeing resources for product development.

School leadership strategy day: A secondary school leadership team challenged the assumption that "parents judge the school primarily on exam results." Surfacing this opened up a conversation about wellbeing, community engagement, and what parents actually valued, leading to a revised communication strategy.

Manufacturing process improvement: A factory team assumed "our production line sequence is optimised." Challenging this during an Assumption Busting session revealed that the sequence had not been reviewed in seven years, and three steps could be reordered to reduce waste by 15%.