product-concept
Product Concept
Study before inventing, then diverge for real. Patterns exist to seed divergence — not to copy, but to know which conventions carry user understanding worth preserving and which persist because everyone copies everyone; the best raw material is often outside the category entirely (claims review owes more to GitHub code review or Stripe reconciliation than to competing estimating tools). Then the divergence itself, where LLMs fail catastrophically: cards, cards-with-sidebar, cards-with-tabs is one idea in three outfits. Concepts are different answers to how should this problem fundamentally work. Divergence is cheap here and unaffordable after code exists — so storm wide first, then converge.
Part of the product-define suite. Read design/problem.md (Desire, sandbox card, aging) and model.md; write design/patterns.md and design/concepts.md; update context.md's Current concept after selection. Gate 1 must pass first. Low-uncertainty routes may run the patterns pass alone. Full diverge: patterns → storm → shortlist → specs → Browse → Cut 1 → Compare → Cut 2 → Commit → subtract.
Quick Reference
| Topic | File | Read when |
|---|---|---|
| Pattern sources + labels | assets/pattern-sources.md | Before storming |
| Mechanism storm bands | assets/ideation-ladder.md | Diverging mechanisms |
| Pairwise mechanism disagreement | assets/difference-test.md | Shortlist matrix |
| Progressive fidelity ladder | assets/wireframe-recipe.md | Browse → Compare → Commit |
| Designer handoff cards | assets/sweep-briefs-template.md | With wireframes |
| Subtract + Care on winner | assets/subtract-pass.md | After cut 2, before flow |
| What Care must protect | assets/care-criteria.md | Selected brief Care line |