STEP 1 — Clarify the problem and decision
Assumption mapping works best when the symptom and the decision at hand are crystal clear.
A diagnostic tool for ruthlessly exposing, categorizing, and deliberately testing unspoken assumptions in architecture design.
Ideal when decisions are based on implicit assumptions and risks are difficult to grasp.
These steps lead from observing a symptom to a grounded intervention.
Symptoms worsen
Clarify decision-making framework
prioritize critical assumptions
Establish evidence and experiments
Start intervention
Assumption mapping works best when the symptom and the decision at hand are crystal clear.
Here the method makes the difference: we separate plausible assumptions from critical, risky assumptions.
Now we translate findings into concrete steps: what should we pause, what should we test, what should we change first?
This checklist is not a second form. It is a completeness check. If something is missing, add the information in the text fields above.
Use the export functions for workshop documentation and jump directly into related archetypes or interventions when diagnosis turns into action.