Systematically identify, categorize, and prioritize the assumptions underlying your product decisions. This skill extends Teresa Torres' four risk categories with four additional categories for new products, and uses a devil's advocate approach from PM, Designer, and Engineer perspectives to surface hidden assumptions.
Risk Score = Impact x (1 - Confidence) ranks what to test first.assumption_tracker.py sorts by priority and suggests next actions.Before mapping assumptions, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.
impact (1-10) and confidence (high/med/low) (drives Risk Score = Impact × (1 − Confidence) and quadrant placement).Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.
references/methodology-and-tools.md).impact (1-10) and confidence, citing the evidence behind every high.assumption_tracker.py; it ranks by Risk Score = Impact x (1 - Confidence) and places each in a quadrant.python3 project-management/discovery/identify-assumptions/scripts/assumption_tracker.py project-management/discovery/identify-assumptions/assets/sample_assumptions.json # exit 0
python3 project-management/discovery/identify-assumptions/scripts/assumption_tracker.py project-management/discovery/identify-assumptions/assets/sample_assumptions_overloaded.json # exit 1
python3 project-management/discovery/identify-assumptions/scripts/assumption_tracker.py --demo --format json
Each assumption needs description, category (value/usability/viability/feasibility/ethics/gtm/strategy/team), confidence (high/medium/low), and impact (1-10). Confidence maps to fixed values (high 0.8, medium 0.5, low 0.2) and drives every ranking; impact 7+ counts as high. Quadrants: Test Now (high impact, low or medium confidence), Proceed (high impact, high confidence), Investigate (lower impact, low confidence), Defer (the rest). Exit codes: 0 sound map, 1 Test Now holds more than about 20% (round(0.2 x n), minimum 1), 2 bad input. Document with assets/assumption_map_template.md.
Mistake: The map lists dozens of assumptions, nearly all high impact and low confidence, so nothing can be tested in order.
Why it happens: Rating an assumption low-risk feels like tempting fate.
Instead: Keep no more than about 20% of assumptions in the Test Now quadrant. If more land there, re-score impact and confidence against real evidence until the load-bearing ones stand out.
Mistake: "Users want a faster checkout" is rated high confidence because "we know this," with no evidence cited.
Why it happens: The most dangerous assumptions feel obviously true.
Instead: Cite the evidence for every high confidence rating. "We know this" is not evidence. Without a source, rate it low and let assumption_tracker.py rank it.
Mistake: The team tests the assumption with the easiest experiment, not the one the idea depends on most.
Why it happens: Hard experiments are uncomfortable, and easy ones give quick wins.
Instead: Rank by Risk Score = Impact x (1 - Confidence) and test the top three first, even when the experiment is hard. Give each one an owner and a date.
Nine more, each with a bad and a good example: references/red-flags.md.
Load the reference that matches the task — keep this file lean and pull detail on demand:
assumption_tracker.py usage and flags, output formats, troubleshooting, success criteria, and bibliography. Read when mapping or scripting assumptions.In Scope: systematic assumption identification using PM/Designer/Engineer devil's advocate perspectives; 8-category risk classification; quantitative scoring with Impact x (1 - Confidence); quadrant classification with suggested validation methods; assumption registry with priority sorting and action plans.
Out of Scope: running validation experiments (brainstorm-experiments/); product strategy or roadmap decisions (execution/outcome-roadmap/); technical feasibility deep-dives (engineering/ skills); financial modeling for viability (finance/ skills).
Important Caveats: confidence levels map to fixed numeric values (0.8/0.5/0.2) — a simplification of continuous confidence; the "high impact" threshold is 7/10, adjustable for your risk tolerance; assumption mapping works best collaboratively (Product Trio), not solo.
| File | Purpose |
|---|---|
scripts/assumption_tracker.py | Risk score, quadrant, suggested test per assumption; Test Now overload gate |
assets/sample_assumptions.json, assets/sample_assumptions_overloaded.json | Runnable inputs: balanced map (exit 0) and overloaded map (exit 1) |
assets/assumption_map_template.md | Assumption map to fill in |
examples/shared-dashboards-assumption-mapping.md | Worked example |
references/*.md | See References |