Speed is a strategy. This playbook compresses risk with a time‑boxed MVP approach.

Phase 1: Discovery (Weeks 1–3)

• Stakeholder interviews → define outcomes, guardrails.
• User journeys & JTBD → capture pains and moments that matter.
• Success metrics → adoption, cycle time, error rates.

Phase 2: Design (Weeks 4–5)

• Low‑fi wireframes → validate flows fast.
• Design system seeds → buttons, inputs, spacing, tokens.
• Acceptance criteria → Definition of Ready/Done.

Phase 3: Build (Weeks 6–10)

• Agile sprints (2 weeks); demo every Friday.
• CI/CD with automated tests; feature flags for safe releases.
• Data model: pick the simplest schema that works.

Phase 4: Pilot & Feedback (Weeks 11–12)

• UAT with 10–20 target users.
• Instrument analytics (events, funnels, NPS).
• Post‑launch backlog prioritized by impact.

Risk Controls

• Scope freeze mid‑build.
• Non‑functional requirements defined early (performance, security).
• Rollback and observability are non‑negotiable.