ideationlisted

# Ideation ## Usage **When to use:** - **Standard mode** — moving from a high-level goal to specific, testable solutions. Breaks first-idea bias using PM, Design, and Eng lenses. - **Constraint mode** — team is stuck in incremental thinking. Imposes opposing extreme constraints to force unconventional solutions. **Inputs:** A desired outcome (e.g. "Reduce churn") or problem area (e.g. "Onboarding drop-off") **Output:** Standard → prioritised idea shortlist across 3 lenses. Constraint → transferable insights and experiment hypothesis from constraint pairs. --- ## THINK: Choose your mode | Mode | When to use | |---|---| | `standard` | Starting fresh or exploring a problem area | | `constraint` | Team keeps generating the same ideas; roadmap feels incremental; need breakthrough thinking | Default to **standard**. Switch to **constraint** when the output of standard looks like what you already had. --- ## STANDARD MODE ### Setup: problem-first framing Before ideating, anchor on the opportunity — the specific customer pain, need, or desire. - **Outcome**: the business metric you want to move - **Opportunity**: the "why" behind the behaviour (e.g. "Users don't understand the value of Feature X") - **JTBD**: "When [situation], I want to [motivation], so I can [outcome]." ### The three lenses **PM lens — Viability & Strategy** Focus: business outcomes, market gaps, user value. Sources: churn reasons, sales/support feedback, analogous industries. Question: "What would cr