What problem does it solve?
Forces thorough design conversation before premature planning or implementation. Based on Frederick P. Brooks' "design tree" concept: walk down each branch, resolve dependencies between decisions one by one.
Core Features & Use Cases
- Phase 1 — Frame the problem: Identify the user pain point, audience, success criteria, and blockers.
- Phase 2 — Walk the design tree: For each major decision, explore both branches and establish upstream/downstream dependencies (data model, API, UI, permissions, migration, etc.).
- Phase 3 — Challenge assumptions: Probe hidden assumptions with targeted questions and explore alternative approaches.
- Phase 4 — Confirm shared understanding: Summarize decisions, open questions, risks, and next steps; decide if ready to proceed to ticketing.
- Style: Be relentless but constructive — the goal is clarity, not gotchas
- After the Interview: Provide a draft decision log, ticket ideas, and an alignment plan.
Quick Start
Start a guided design exploration interview by framing the problem and walking the design tree through all major branches before proposing any solution.