Guide
How to run a one-hour design sprint
A one-hour design sprint works when the problem is already defined and the team needs a direction, not proof. Spend 5 minutes framing the problem, 10 on examples, 20 sketching or building alone, 10 reviewing in silence, 5 voting and 10 improving the winner. One person keeps time and one person has the final say. AppSprint's One-Hour Sprint runs this agenda, with AI building a working prototype for each person.
When one hour is enough
The design sprint described in the book Sprint by Jake Knapp, John Zeratsky and Braden Kowitz takes five days, including customer tests. An hour cannot hold that. What it can hold is the core of the method: work alone first, judge ideas without knowing whose they are, vote, and let one person decide.
Use it for one urgent, defined problem, such as a feature the team keeps debating. Do not use it when the team disagrees about what the problem is, or when you need evidence from customers. For that, see how to run a remote design sprint.
The 60-minute agenda
Frame the problem (5 minutes)
Read out a problem statement written before the session: who has the problem, what happens now, and what better looks like. Fix wording, not substance.
Share examples (10 minutes)
Each person shows up to three products, screens or screenshots that solve something similar. No debate; the point is shared raw material.
Work alone (20 minutes)
Everyone produces one concrete answer in silence: a sketch of the key screens on paper, or a prototype if your tools allow it. Words and boxes are fine.
Review in silence (10 minutes)
Post the work without names. Each person marks the parts they like with up to three dots per idea. No presenting or defending yet.
Vote and decide (5 minutes)
One private vote each, revealed together. The vote is advice. The person with the final say picks one direction, or up to three if they are worth combining.
Improve the winner (10 minutes)
One person edits while the others suggest changes. Finish by writing down the decision, the owner and the next step.
Common mistakes
- Arriving without a written problem. The first five minutes become thirty.
- Talking during solo time. Discussion feels productive and leaves you with one person's idea.
- Ending on the vote. A vote with no named decision and owner changes nothing.
- Calling the result validated. Nobody outside the team has seen it yet.
Running it remotely
Send the problem statement the day before. Keep one timer that everyone can see and hear. Use a voting method where nobody sees a count until all votes are in; see anonymous dot voting. Keep the group small, because each extra person adds work to review in the same ten minutes.
Doing this in AppSprint
The One-Hour Sprint has seven guided steps: Name Your Project (5 minutes), Examples & References (10), Prototype (20), Review Prototypes (10), Gallery: Choose Prototypes (5), Refine Together (10) and a session summary. In the Prototype step each person describes what people should be able to try and the AI builder returns a working prototype.
Review uses anonymous yellow dots, up to three per prototype. The Gallery vote is one private vote each, and the decision-maker keeps one to three prototypes. In Refine Together only the decision-maker prompts the AI while teammates send anonymous suggestions. The Sprint Coach, pre-recorded voice guidance, and AI teammates are on by default in this template. AppSprint says host for facilitator and decision-maker for Decider.
This template has no user testing step. If you need tester feedback, use the Focused Product Sprint. Prototypes are single-file HTML with no backend: right for a decision, wrong for a launch.