design-opslisted

# Design Ops & Handoff Operational processes that make design teams effective — sprints, handoff, rituals, documentation, and quality assurance. --- ## Design Sprints A 5-day process for solving big problems and testing ideas before committing engineering resources. Based on Jake Knapp's Sprint methodology developed at Google Ventures. ### When to Sprint | Signal | Sprint Is Right | Sprint Is Wrong | |--------|----------------|-----------------| | Problem clarity | Big problem, unclear solution | Solution already known — just build it | | Stakes | High — wrong direction costs months | Low — easy to course-correct later | | Team alignment | Disagreement on approach | Team already aligned | | Time pressure | Need answers this week | Can run a longer discovery process | | Complexity | Cross-functional problem | Single-discipline task | ### The 5-Day Structure | Day | Focus | Key Activity | Output | |-----|-------|-------------|--------| | **Monday** | Map | Define the challenge, set a 2-year goal, map the problem space, pick a target | Sprint questions, problem map, target area | | **Tuesday** | Sketch | Review existing solutions, each person sketches solutions individually | Solution sketches (one per person) | | **Wednesday** | Decide | Present sketches, vote (dot voting + decider picks), create storyboard | Storyboard for prototype | | **Thursday** | Prototype | Build a realistic facade — just enough to test | Testable prototype | | **Friday** | Test | 5 user intervie