02 — Identify Critical Assumptions
Purpose: Identify what must be true for success and prioritize by risk.
Outcome
A ranked list of critical assumptions with clear rationale.
This is where the team moves from “What is the problem?” to “What are we actually betting on?”
Time to complete
30-60 minutes.
Inputs
Problem statement from Step 01.
Current constraints and context.
Steps in SwiftCNS
List assumptions across desirability, viability, and feasibility.
Remove duplicates and vague statements.
Rank assumptions by risk and decision impact.
Select the top assumptions for immediate testing.
Why this stage matters
Every initiative contains more assumptions than most teams realize. Some are about users. Some are about value. Some are about operational reality, timing, or technical feasibility.
The purpose of this stage is not to document every possible assumption. It is to identify the assumptions that are most likely to change the trajectory of the work if they turn out to be wrong.
That is what keeps the learning loop efficient. Without prioritization, teams often test what is easiest instead of what is most important.
Role lenses
Startup: focus on assumptions that can kill the bet quickly.
Program manager: ensure risk ranking is explicit and comparable across teams.
Mentor: challenge hidden assumptions and weak prioritization logic.
What strong output looks like
A strong assumption list is:
clear instead of vague,
prioritized instead of exhaustive,
tied to decision impact,
usable as direct input for hypotheses.
Weak vs strong pattern
Weak
long lists with no prioritization,
assumptions written as broad themes,
no rationale for why one assumption matters more than another,
assumptions mixed together with solutions or tasks.
Strong
a small set of high-risk assumptions,
visible ranking logic,
clear link to the problem statement,
obvious candidates for immediate testing.
Outputs
Prioritized assumptions list.
Rationale for why top assumptions were selected.
Definition of done
Team agrees on top assumptions to test first.
Each selected assumption can be converted into a hypothesis.
Common failure mode
The most common issue here is mistaking completeness for quality. Teams often believe a large list means better thinking. In practice, a shorter list of sharper assumptions is much more useful.
If blocked
Use Cycle Anatomy to re-anchor on decision-oriented sequence.
Next step
Continue to 03 — Form Testable Hypotheses.
Last updated