Assumption
An unverified belief that a product decision or plan depends on being true.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/assumption/
01What it means
An assumption is a belief treated as true for the purpose of making a decision, despite incomplete evidence. Product assumptions may concern users, problems, behavior, value, feasibility, viability, or risk; an assumption is not automatically a hypothesis until it is made testable.[1][2]
- Implicit beliefA plan depends on something unstated
- Explicit assumptionClaim, rationale, owner, and affected decision
- Prioritized riskUncertainty multiplied by consequence
- Test in contextCollect evidence capable of changing the decision
- Supported, revised, or rejectedRecord confidence and implications
Changing conditions can make a previously supported assumption uncertain again
Not every assumption deserves equal research; prioritize beliefs that combine high uncertainty with severe consequences for the plan.
02Why it matters
Making assumptions visible reveals uncertainty and helps teams spend learning effort where being wrong would materially change a decision.
03When to use it
Use assumption mapping before committing to a solution, business model, or major delivery investment. Do not turn every minor detail into a formal test.
04How it works
- State the decision and its dependencies.
- Write each belief in observable terms.
- Estimate its importance and uncertainty.
- Choose evidence that could change confidence.
- Run a proportionate test and update the decision.
05A practical example
A marketplace assumes that independent tutors will accept a new scheduling flow without lowering booking completion; interviews and a prototype test challenge that belief before engineering work begins.
06Where it breaks
Tests can be weak, proxies misleading, and assumptions interdependent; evidence reduces uncertainty but rarely proves a universal truth.
Common mistakes
- Hiding assumptions inside requirements.
- Testing easy assumptions instead of consequential ones.
- Treating stakeholder confidence as evidence.
07Sources
- Plan user research for your serviceGOV.UK Service Manual · Government service guidancePlan user research for your service
- Assumption MappingStrategyzer · Practitioner methodAssumption Mapping