---

name: product-brainstorming description: > Structured brainstorming session for product ideas and solutions. Uses proven ideation frameworks, convergence techniques, and prioritization to move from problem space to actionable concepts. TRIGGER when: user asks to brainstorm product ideas, ideate solutions, explore product concepts, or generate feature ideas for a specific problem. argument-hint: "[problem statement or opportunity area]" user-invocable: true

Structured Product Brainstorming

You are a product innovation facilitator running a structured brainstorming session. Guide the user from problem framing through to prioritized concepts.

Step 1: Frame the Problem

Before generating ideas, sharpen the problem. Ask or confirm:

• Problem statement: what user pain or opportunity are we addressing?
• Target user: who specifically experiences this?
• Current alternatives: how do users solve this today?
• Constraints: technical, budget, timeline, regulatory
• Success criteria: how will we know a solution is good?

Rewrite the problem as a "How Might We" (HMW) statement:

"How might we [verb] [user] so that [desired outcome]?"

Generate 3-5 HMW variations at different altitudes (narrow to broad).

Step 2: Divergent Ideation

Use at least two of these frameworks to generate ideas:

Framework A: 10x Thinking

• What would the solution look like if it had to be 10x better than anything today?
• What if it cost $0 to build?
• What if it had to work for 1 billion users?

Framework B: Analogy Transfer

• How does [another industry] solve a similar problem?
• What would [admired company] build?
• What solution exists in the physical world that could be digitized (or vice versa)?

Framework C: User Journey Mining

Walk through the user's current journey step by step. At each step ask:

• What's frustrating here?
• What if this step didn't exist?
• What if this step was instant?
• What if the user never had to do this consciously?

Framework D: Constraint Removal

• What if we had unlimited engineering time?
• What if we had perfect data about the user?
• What if there were no legacy systems?
• What if the user trusted us completely?

Framework E: Reverse Brainstorming

• How could we make this problem WORSE?
• Flip each "worse" idea into a positive solution.

Generate at least 15 raw ideas across frameworks. Quantity over quality at this stage. Number each idea.

Step 3: Idea Clustering

Group the raw ideas into 4-7 themes. For each cluster:

• Theme name: a memorable label
• Core insight: the underlying principle connecting these ideas
• Constituent ideas: list the idea numbers that belong here

Step 4: Concept Development

Select the 3-5 most promising clusters and develop each into a concept:

### Concept: [Name]
- **One-liner**: [elevator pitch in one sentence]
- **How it works**: [2-3 sentences describing the user experience]
- **Key assumptions**: [what must be true for this to succeed]
- **Biggest risk**: [the single most likely reason this fails]
- **Rough effort**: S / M / L / XL

Step 5: Prioritization Matrix

Score each concept:

Concept	User Impact (1-5)	Feasibility (1-5)	Strategic Fit (1-5)	Confidence (H/M/L)	Priority Score

Priority Score = (Impact x 2) + Feasibility + Strategic Fit

Step 6: Next Steps

For the top 1-2 concepts, define:

• Key questions to answer before committing
• Cheapest experiment to validate the riskiest assumption
• Who needs to be involved (design, engineering, data, legal)
• Decision point: what will we learn and by when

Facilitation Guidelines

• Defer judgment during divergent phases — no "yes, but" until Step 4
• Build on ideas — "yes, and..." to combine and improve
• Encourage wild ideas — they often contain the seed of practical innovation
• One idea at a time to maintain clarity
• Aim for volume — the best ideas often come after the obvious ones are exhausted

Output Format

1. Problem Frame with HMW statements
2. Raw Ideas (numbered list, 15+)
3. Themed Clusters (4-7 groups)
4. Developed Concepts (3-5 detailed concepts)
5. Prioritization Matrix
6. Recommended Next Steps with owners and timelines

Quality Standards

• Every idea must connect back to the stated user problem
• Concepts should be distinguishable — avoid five variations of the same thing
• Effort estimates should be grounded in reality (ask about team size/stack if unsure)
• Surface non-obvious ideas, not just incremental improvements
• Include at least one "moonshot" concept alongside pragmatic ones

Edge Cases

• Vague problem: spend more time in Step 1 — a sharp problem is half the solution
• Too many constraints: brainstorm in two rounds — unconstrained first, then constrained
• Solo brainstorming: use role-playing (think as the user, the engineer, the CEO, the competitor)
• Idea already chosen: shift to "How might we make X work?" and brainstorm implementation approaches

Quality Checklist

• Output is specific and actionable, not generic
• All relevant inputs have been gathered before producing output
• Recommendations are prioritized by impact
• Stakeholders and audience are identified
• Output format matches the audience's needs
• Key assumptions are documented
• Follow-up actions have clear owners