Skip to content

borghei/Claude-Skills / project-management/discovery/brainstorm-ideas

brainstorm-ideas

Verified

Generates product ideas from PM, design and engineering angles, ties each to an opportunity and ranks the top five. Use when brainstorming features for an outcome, exploring a new product, or choosing which ideas to test first.

references/ideation-frameworks.md

View on GitHub
# Ideation Frameworks Reference

## Product Trio Methodology

The Product Trio is a cross-functional team of three roles collaborating continuously on product discovery:

- **Product Manager** -- Owns the "why" and "what." Brings business context, customer research, strategic goals, and market intelligence.
- **Designer** -- Owns the experience. Brings user empathy, interaction patterns, visual communication, and usability expertise.
- **Engineer** -- Owns the "how." Brings technical feasibility, system knowledge, data awareness, and build/buy/partner perspective.

### Why Three Perspectives Matter

Each role has a distinct blind spot:
- PMs can overweight business value and underweight user experience.
- Designers can overweight delight and underweight technical cost.
- Engineers can overweight feasibility and underweight customer need.

The trio structure ensures every idea is stress-tested from all three angles before it advances.

### Running a Trio Ideation Session

1. **Timebox**: 60-90 minutes maximum.
2. **Diverge first**: Each person generates 5 ideas independently (15 minutes, silent).
3. **Share and clarify**: Present ideas round-robin (20 minutes). No critique yet.
4. **Cluster**: Group related ideas on a board (10 minutes).
5. **Converge**: Dot-vote or score to select top 5 (15 minutes).
6. **Document**: Capture idea cards for top 5 (15 minutes).

---

## Opportunity Solution Tree (Teresa Torres)

The Opportunity Solution Tree (OST) is a visual framework from *Continuous Discovery Habits* that connects business outcomes to customer opportunities to solutions.

### Structure

```
Desired Outcome (metric to move)
├── Opportunity A (customer need, pain, or desire)
│   ├── Solution 1
│   ├── Solution 2
│   └── Solution 3
├── Opportunity B
│   ├── Solution 4
│   └── Solution 5
└── Opportunity C
    └── Solution 6
```

### Key Principles

- **One outcome at a time.** Focus the tree on a single measurable outcome.
- **Opportunities come from research.** Interview customers weekly to discover opportunities; do not brainstorm them.
- **Solutions compete within a branch.** Compare solutions that address the same opportunity, not across different opportunities.
- **Small experiments, not big bets.** Test assumptions behind solutions before building full features.

### When to Use

- Existing products with an active user base and interview pipeline.
- Teams that have a clear outcome metric assigned by leadership.
- Continuous discovery (ongoing), not one-off ideation events.

---

## SCAMPER Technique

SCAMPER is a structured creativity checklist. Apply each prompt to an existing product, feature, or competitor offering:

| Letter | Prompt | Example Question |
|--------|--------|-----------------|
| **S** | Substitute | What component, material, or process could we replace? |
| **C** | Combine | What features or products could we merge? |
| **A** | Adapt | What idea from another industry could we borrow? |
| **M** | Modify | What could we enlarge, shrink, or change the shape of? |
| **P** | Put to other use | Who else could use this? What other problem could it solve? |
| **E** | Eliminate | What could we remove and still deliver value? |
| **R** | Reverse | What if we did the opposite? What if we reversed the order? |

### Tips for SCAMPER Sessions

- Apply each letter as a separate round (2 minutes per letter).
- Use a specific subject: "Our onboarding flow" not "our product."
- Combine SCAMPER with Product Trio: each person applies SCAMPER from their role's perspective.

---

## How Might We (HMW) Questions

HMW is a reframing technique that converts problems, pain points, and observations into open-ended opportunity questions.

### Formula

**"How might we [verb] [desired change] for [user segment]?"**

### Examples

| Observation | HMW Question |
|------------|--------------|
| Users abandon checkout at shipping cost screen | How might we reduce shipping cost anxiety before checkout? |
| Engineers spend 30% of sprint fixing regressions | How might we catch regressions before they reach production? |
| New users do not discover the API within the first week | How might we introduce the API during onboarding? |

### Rules for Good HMW Questions

1. **Not too broad.** "How might we make users happy?" is useless.
2. **Not too narrow.** "How might we add a tooltip to the settings gear icon?" is a solution, not a question.
3. **Implies no solution.** The question should invite multiple possible answers.
4. **Grounded in evidence.** Each HMW should trace back to a real observation or data point.

---

## Idea Evaluation Criteria

When comparing ideas, use these five criteria:

### 1. Customer Impact (Weight: 30%)

- How many users are affected?
- How severe is the current pain?
- How much better is the proposed experience?

### 2. Strategic Alignment (Weight: 25%)

- Does this advance a company or team OKR?
- Does it strengthen our competitive position?
- Is it consistent with our product vision?

### 3. Feasibility (Weight: 20%)

- Can we build this with current technology and team skills?
- Are there external dependencies or blockers?
- What is the technical risk?

### 4. Speed to Validate (Weight: 15%)

- Can we test the core assumption in under 2 weeks?
- Is there an existing proxy metric we can measure?
- Can we run a lightweight experiment before building?

### 5. Differentiation (Weight: 10%)

- Does this create a unique advantage competitors cannot easily copy?
- Does it leverage a proprietary asset (data, network, expertise)?
- Will users perceive this as meaningfully different?

### Scoring

Rate each criterion 1-10. Compute weighted score:

```
Score = (Impact x 0.30) + (Strategy x 0.25) + (Feasibility x 0.20)
      + (Speed x 0.15) + (Differentiation x 0.10)
```

Ideas scoring 7.0+ are strong candidates. Ideas scoring below 5.0 should be deprioritized unless they have exceptional strategic value.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall