Develop: Explore and Document Solutions

Documents solution exploration and technical decisions to capture design intent and reasoning. Preserves the rationale behind solution choices so teams understand trade-offs and context for future reference.

1. After problem and opportunity framing, use solution-brief to pitch the proposed approach, key decisions, and trade-offs to stakeholders. 2. Run spike-summary after time-boxed explorations to capture findings and recommendations. 3. Document significant technical choices with develop-adr (Architecture Decision Records) following the Nygard format to record context, alternatives, and consequences. 4. Use design-rationale to explain UX decisions, alternatives considered, and principles applied. Output: solution overview, exploration results, technical decisions, and design reasoning all grounded in the problem and opportunity frame.

ADR and design-rationale focus on preserving context and rationale for future teams. solution-brief and spike-summary are short-form artifacts meant for quick stakeholder digestion. All refuse to project confidence beyond what evidence supports.