| name | itk-stormdraining |
| description | The inverse of brainstorming, reduce a large collection of ideas, activities, or components to a smaller collection of the most valuable or promising ideas. |
| intent | Bring clarity to the results of a brainstorming session that generated a large collection of ideas. Thoughtfully prioritize ideas and discard ideas with less value. Increase the team’s mental agility by safely explore risky ideas. |
| type | component |
| phase | evaluate |
| outcome | evaluate |
| difficulty | beginner |
| group_size | 2+ people |
| time_required | 60+ minutes |
| best_for | ["Post-brainstorm backlog triage when a discovery sprint generated dozens of feature ideas with no clear prioritization","Trimming a bloated MVP scope down to the core hypothesis before committing engineering capacity","Roadmap planning sessions where competing stakeholder asks have inflated the candidate list beyond delivery capacity","Reducing PRD requirements to the essential job-to-be-done before handing off to design and engineering","OKR planning when too many key results dilute focus and the team needs to converge on a few high-leverage bets"] |
| sources | ["MITRE Innovation Toolkit (ITK)","https://itk.mitre.org/toolkit-tools/stormdraining/"] |
Stormdraining
What Is It
The inverse of brainstorming, reduce a large collection of ideas, activities, or components to a smaller collection of the most valuable or promising ideas.
Why Use It
Bring clarity to the results of a brainstorming session that generated a large collection of ideas. Thoughtfully prioritize ideas and discard ideas with less value. Increase the team’s mental agility by safely explore risky ideas.
When to Use It
When a team confronts a high level of complexity after a brainstorming. When a team has a lot of ideas and no clear sense of direction. When a team’s activities lack prioritization or focus.
How to Do It
- As a group, assemble a large collection of ideas, requirements, design components, process steps, or other design elements. This may be an existing collection or the result of a fresh brainstorming session.
- Invite the team to distill the large collection into a smaller, more focused set. Remove items from the collection by using the following Five Rules of Stormdraining: RULE 1: Everything Is on the Table. No sacred cows, please. Every single item is fair game for going down the drain. RULE 2: Delete Is the Default. Turn the pencil around and make liberal use of the eraser. Not sure if something should be deleted? Only one way to find out.… RULE 3: Build on Other People’s Deletions. Your teammate’s suggestion to remove one thing likely points to other parts to remove. The objective is to reduce quantity and hone in on the essentials, so practice “Yes, and…” RULE 4: Make It Fun. Celebrate and encourage the deletions. Compliment people’s creativity and courage when they propose sending something down the drain. RULE 5: When You Delete Something, Really Delete It. Don’t set it aside and save it for posterity. Don’t take a photo to preserve the moment. Erase it. Drain it. Make it go away.
Key Concepts
Convergent Thinking — The disciplined narrowing of a wide idea set toward a few high-value options, the necessary counterpart to divergent brainstorming. PMs need this to avoid scope sprawl and turn raw ideation into a deliverable plan.
Delete Is the Default — The bias-toward-removal stance where items must justify their survival rather than their deletion. This inverts the usual reluctance to cut and forces explicit defense of what stays in scope.
Sacred Cows — Ideas or features protected by emotional attachment, sunk cost, or executive ownership that escape honest evaluation. Stormdraining explicitly puts everything on the table to neutralize these protections.
Psychological Safety in Cutting — Making deletion celebrated and fun so contributors don't defend ideas out of ego or fear. Without it, the team converges on the loudest voice rather than the highest-value work.
Irreversible Removal — Genuinely discarding deleted items rather than parking them in a 'maybe later' list. The discipline prevents a shadow backlog that quietly re-inflates scope and undermines the focus the exercise created.
PM Applications
- Run stormdraining on a backlog grooming session to cut speculative epics and stories that lack a clear link to a current OKR or validated user need.
- Use it to converge an MVP definition by draining nice-to-have features until only the riskiest assumption-testing functionality remains.
- Apply it during roadmap reviews to reduce a quarter's candidate initiatives to the few that fit realistic team capacity.
- Distill a sprawling PRD's requirements list down to the must-haves that directly serve the primary job-to-be-done before design handoff.
- Facilitate stormdraining after a stakeholder workshop to collapse dozens of conflicting requests into a focused, defensible set for executive sign-off.
- Trim a set of proposed OKRs or key results so the team commits to a small number of measurable, high-leverage outcomes rather than diluting effort.
Benefits
- Excellent introduction to convergent thinking, helps teams prioritize and simplify
Common Pitfalls
- Treating deletions as 'parked for later' and creating a shadow backlog, which re-inflates scope and defeats the convergence the exercise was meant to produce.
- Letting the HiPPO or feature sponsor shield their pet ideas, so the cuts fall on weaker contributors' work instead of the genuinely low-value items.
- Running stormdraining with no prioritization criteria, so deletions reflect personal taste rather than user value, strategic fit, or effort-to-impact.
- Stopping too early and leaving the set nearly as large as it started because the team flinches at cutting anything emotionally invested in.
- Skipping the divergent phase first, so the team prunes a thin, unconsidered idea pool and converges prematurely on mediocre options.
- Failing to record the rationale for what survived, leaving the team unable to defend scope decisions when stakeholders later challenge them.
Combine With
Lotus Blossom or Mindmapping to come up with the initial set of ideas
Assets
Metadata
| Field | Value |
|---|
| ITK Phase | EVALUATE |
| Difficulty | Beginner |
| Group Size | 2+ people |
| Time Required | 60+ minutes |
| Source | itk.mitre.org |
