Discovery sprints that don't waste two weeks of your team's life.
A short, opinionated playbook for running product discovery that ends in a decision, not a slide deck.
Discovery has a reputation problem. Teams book two weeks, run workshops, fill a wall with sticky notes and finish with a presentation nobody acts on. Done well, discovery is the cheapest way to avoid building the wrong thing. Here's how we run it.
Start with the decision, not the activities
Before day one, write down the decision the sprint has to support. "Should we build a customer portal, and if so what's in version one?" is a good one. "Explore customer needs" is not. Every activity has to earn its place by helping make that decision.
A five-day shape that works
- Day 1 - What we know. Gather existing data, support tickets, sales notes and previous research. You usually know more than you think.
- Day 2 - Talk to people. Five to eight short interviews with real users or customers. Ask about the last time they hit the problem, not what they'd like in theory.
- Day 3 - Map it. Draw the current process end to end and mark where time, money or trust is lost.
- Day 4 - Sketch and test. Make a rough clickable prototype of the most promising idea and put it in front of three or four people.
- Day 5 - Decide. Agree what to build first, what to park, and what you still don't know.
What you should walk away with
- A one-page summary of the problem in your users' words
- A prioritised list for version one, with what's out of scope written down
- A tested prototype people can react to
- The two or three risks you still need to check
Common traps
Inviting too many people to every session. Interviewing only internal stakeholders. Treating the prototype as a design to be polished. And the big one: no clear owner for the decision on day five.
Business analysis is at the heart of this work, and it's what we teach at TemTed Academy. If you'd like us to run a discovery sprint with your team, let's talk.