Inspired by Google's Design Sprint and adapted for early-stage founders trying to validate a product idea fast. The whole exercise takes a working week.

## the five days

- **Day 1 — Map.** Talk to experts, draw the customer's process on a whiteboard. Identify the actual pain.
- **Day 2 — Inspire.** Look at how other products solve adjacent problems. Sketch.
- **Day 3 — Decide.** Pick the version you'll prototype. Write a one-page product outline.
- **Day 4 — Prototype.** Build a clickable mock with whatever's quickest. Google Slides is enough.
- **Day 5 — Validate.** Show it to five potential customers. Listen.

## why it works

You compress two months of research, design, and gut-checking into a week. If the problem you're solving is big enough, customers will be willing to pay just based on Google Slides — that's the level of pain that justifies a startup.

If they aren't willing to pay for the slides, the problem isn't big enough yet. Better to find that out in a week than in a year.

## resources

- The Sprint book by Jake Knapp — original methodology.
- Remote-first variants exist; the Miro template communities have several.

If you've tried this — what blocked the implementation in your team? The most common stuck-point I've seen is the prototype day, where teams over-engineer and miss the point.