design-productlisted

# Design Product When you need a **product design blueprint** (app, game, SaaS, marketing automation, or similar), run one design cycle. User intent is **design a product**, not pick an engine brand. Shape-specific depth lives in references. ## When to use - Greenfield or major redesign of a product experience - Need jobs/IA, loops, tenancy, journeys, or system blueprint before build - Not for implementing a single screen (use craft-product-interface) or shipping code (use build-product) ## Method 1. **Frame** the product promise, users, surfaces, non-goals, success criteria. 2. **Stance (Quality North Star Layer A):** prefer one deep core concept over many half-concepts; simplify by composition without cutting user-facing capability. Name 1–2 quality attributes this design intentionally strengthens or sacrifices. Open `../build-product/references/engineering-standard/` when quality tradeoffs or precedence matter. 3. **Choose shape** and open only the matching reference: - App / multi-surface client → [references/app/METHOD.md](references/app/METHOD.md) - Game → [references/game/METHOD.md](references/game/METHOD.md) - SaaS web platform → [references/saas-web-platform/METHOD.md](references/saas-web-platform/METHOD.md) - Marketing automation → [references/marketing-automation/METHOD.md](references/marketing-automation/METHOD.md) - Space map before choosing → [references/space-exploration/METHOD.md](references/space-exploration/METHOD.md) -