tool-design-sprint-sketch

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 --> # Design Sprint Sketch (Tuesday) Structure Tuesday's solo-but-together work. Each team member, working independently and silently, produces lightning demos in the morning and a four-step solution sketch in the afternoon. The skill structures the activity; the humans produce the sketches. Wednesday's heat-map orientation depends on having a cohort of independent sketches that did NOT contaminate each other through group brainstorming. Family contract: [`docs/reference/skill-families/design-sprint-skills-contract.md`](../../docs/reference/skill-families/design-sprint-skills-contract.md). This skill is a member of `design-sprint-skills`. ## When to Use - It is Day 2 of the Design Sprint and Monday's Map and Target artifact is signed off. - Each team member brings at least 3 lightning demo sources (existing products, references, analogies that bear on the challenge). - The team has accepted the silent-independent-sketching constraint and will NOT lapse into group brainstorming. - Sketches are due Tuesday end-of-day for Wednesday morning heat-map. ## When NOT to Use - Monday is not closed. Return to `tool-design-sprint-map-and-target`. - The team's instinct is to brainstorm as a group. Sprint method explicitly avoids this; if the team will not commit to independent work, the sprint will not produce diverse sketches and the heat-map becomes a popularity contest. - The sketch step is being treat...