MVP
What happens in a Discovery Sprint, step by step
Oluwole Olarewaju
CEO, 24 Design Co. · · 5 min read
In this guide
A Discovery Sprint is a short, focused project, usually one to two weeks, that turns an idea into a clear plan: a prototype, a defined first version, a technical approach and a fixed quote. This guide shows what happens day by day, what you receive, who should take part, and how to tell whether you are ready.
Why do a Discovery Sprint?
The most expensive mistakes in software happen before any code is written: building the wrong thing, building too much, or building without a shared understanding of what "done" means. A Discovery Sprint reduces those risks by answering the hard questions first, when changes are cheap.
- It reduces risk. You test your idea with real people before you pay for a full build.
- It saves money. A clear scope prevents surprises and rework.
- It aligns everyone. You, your partners and the team build the same thing.
- It gives you something to use. A prototype and a plan help you raise money, recruit partners and brief any team.
Who should take part
- You, or the main decision-maker, because decisions made quickly keep the sprint short.
- People who know the problem well, such as an operations lead or a subject expert.
- A few target users, for feedback on the prototype.
- The 24 Design Co. team: a product lead, a designer and an engineer.
What happens, step by step
The exact schedule depends on the project. This is a typical one-to-two-week plan.
- Days 1 and 2: the workshop. We work with you on the problem, the users, your business model, existing alternatives and what success looks like. We ask the hard questions, such as who will pay, why they would switch and what could go wrong.
- Days 3 to 5: journeys and features. We map how each type of user moves through the product, and list every feature that might be needed. Then we sort them into must-have, should-have and later, so version one stays small.
- Days 4 to 7: the prototype. Our designer builds a clickable prototype of the key screens. It looks and feels like the real product, but it is quick to change.
- Days 6 to 8: feedback from real users. We show the prototype to a handful of target users, watch how they use it and note what confuses them. This is often where an idea changes for the better.
- Days 8 to 10: technical approach, timeline and quote. Our engineer describes in plain language how the product will be built, which integrations it needs and what the risks are. We then give you a timeline and a fixed quote for the build.
- The final session. We present everything to you, answer questions and agree what happens next.
What you receive
| Deliverable | What it is | How you use it |
|---|---|---|
| Workshop summary | Problem, users, goals and success measures | A shared reference for everything |
| User journeys | How each user moves through the product | Aligns design and development |
| Prioritized feature list | What is in version one, and what waits | Controls scope and cost |
| Clickable prototype | A realistic preview of the product | Test with users, show to investors |
| Technical approach | How it will be built, in plain language | Brief any development team |
| Timeline and fixed quote | When it will be ready and what it costs | Plan your budget and launch |
The documents are yours to use, whether or not you build with us.
What to prepare
- A one-page description of your idea, however rough
- Examples of products you like or compete with
- Names of a few people who could be your first users
- Availability for the workshop days and short check-ins afterwards
- The name of the person who can make decisions
What happens next
You choose:
- Build with us. We start the MVP, usually 8 to 12 weeks, with milestone payments.
- Take the plan to another team, or build it in-house.
- Pause and test further, using the prototype with more users or investors.
Are you ready?
You are ready for a Discovery Sprint if you have an idea you believe in, can describe the problem you solve, can give the sprint a few hours in the first two days, and have some budget or funding in mind.
You may want to wait if you do not yet know who your users are, or cannot decide anything without a long approval chain. A free idea review can help you work out the right next step.
Common mistakes
- Arriving with a fixed solution instead of an open mind
- Sending a delegate who cannot make decisions
- Skipping user feedback
- Trying to put every feature into version one
- Treating the sprint as a formality instead of a chance to change the plan
Frequently asked questions
Do I have to build with you afterwards? No. The plan and prototype are yours, and you can take them to any team.
Who owns the documents? You do.
Can it be done remotely? Yes. The workshops and feedback sessions work well over video, and we use shared boards for the rest.
What if my idea changes during the sprint? That is normal, and often the point. We adjust the plan as we learn.
Can I use the prototype to raise money? Yes. Many founders use it in investor conversations.
Oluwole Olarewaju
CEO, 24 Design Co.
Leads every product from idea review to launch, and stays on as CTO partner.
More about Oluwole