Prioritize Assumptions

What Is This?

Overview

Assumption prioritization is a structured method for evaluating the beliefs that underpin a product, feature, or strategy before committing significant resources to building or testing them. Every product decision rests on a set of assumptions, ranging from user behavior expectations to technical feasibility claims. Without a systematic way to rank these assumptions, teams risk spending time validating low-stakes beliefs while ignoring the ones that could invalidate the entire initiative.

The Impact × Risk matrix provides a two-dimensional framework for sorting assumptions by how much they matter and how uncertain they are. Impact measures the consequence of an assumption being wrong, while Risk measures the probability that the assumption is incorrect. Assumptions that score high on both dimensions demand immediate attention and targeted experiments. Those that are low on both can be safely deprioritized or accepted without testing.

This skill integrates the assumption prioritization canvas approach, which combines matrix scoring with experiment design. Rather than stopping at ranking, it pushes teams to define a concrete validation action for each high-priority assumption, closing the gap between analysis and execution.

Who Should Use This

• Product managers triaging a backlog of assumptions before a discovery sprint
• Startup founders deciding which hypotheses to test before committing to a build cycle
• UX researchers planning which user beliefs to probe in upcoming interviews or usability sessions
• Engineering leads assessing technical assumptions before architecture decisions are finalized
• Business analysts working through feasibility assumptions in a new market or product line
• Agile coaches facilitating assumption mapping workshops with cross-functional teams

Why Use It?

Problems It Solves

• Teams waste discovery cycles testing assumptions that have minimal impact on the outcome, leaving critical unknowns unaddressed until late in development.
• Without a shared prioritization framework, stakeholders argue about what to test next based on personal preference rather than structured reasoning.
• High-risk assumptions get buried in long lists and are never assigned an experiment, allowing them to silently undermine a product launch.
• Experiment design is often disconnected from assumption ranking, so even when teams identify risky beliefs, they lack a clear path to validation.
• Assumption lists grow stale because there is no mechanism to revisit and re-rank them as new information arrives.

Core Highlights

• Uses a two-axis Impact × Risk matrix to produce a clear, defensible ranking of assumptions
• Suggests a targeted experiment type for each high-priority assumption
• Supports input from raw assumption lists, research notes, or structured files
• Applies consistently across product, technical, business model, and user behavior assumptions
• Produces output that can feed directly into a sprint planning session or research roadmap
• Separates assumptions that need testing from those that can be accepted or monitored
• Encourages teams to quantify uncertainty rather than rely on gut instinct
• Compatible with the assumption prioritization canvas methodology

How to Use It?

Basic Usage

Provide a list of assumptions as plain text or a structured file. The skill will score each assumption on Impact and Risk, place it in the matrix quadrant, and suggest an experiment.

Input:
- Users will share the app with colleagues after onboarding
- The API can handle 10,000 concurrent requests
- Customers are willing to pay $49/month for the pro tier
- Users understand the difference between workspaces and projects

Output (example):
| Assumption                        | Impact | Risk | Quadrant       | Suggested Experiment          |
|-----------------------------------|--------|------|----------------|-------------------------------|
| Willingness to pay $49/month      | High   | High | Test First     | Fake door pricing page test   |
| API handles 10k concurrent users  | High   | Med  | Validate Early | Load test in staging          |
| Users share app after onboarding  | Med    | High | Monitor        | Referral tracking cohort      |
| Workspace vs project distinction  | Low    | Low  | Accept         | No experiment needed          |

Specific Scenarios

Scenario 1: Pre-sprint assumption triage. Before a two-week discovery sprint, a product manager pastes 12 assumptions into the skill. The output ranks them and identifies the top three for the sprint backlog, each with a proposed experiment format.

Scenario 2: Investor pitch preparation. A founder uses the skill to stress-test the assumptions embedded in a pitch deck, identifying which ones an investor is most likely to challenge and designing pre-emptive validation evidence.

Real-World Examples

A SaaS team assumed that users would self-serve through documentation. Scoring this as High Impact and High Risk led to a five-user interview study that revealed most users expected live chat support, reshaping the onboarding budget.

A fintech startup ranked payment trust assumptions above feature preference assumptions, redirecting two weeks of research toward trust-building signals rather than UI preferences.