Are you actually ready for a Prototype Sprint?
Five honest questions, worth answering before anyone spends a design budget (yours or ours). Answer them here for free; enter your email if you'd like the one-page version to keep and share internally.
The five questions
Can you name the one decision this prototype needs to help you make?
“Validate the idea” isn't a decision. “Should we build the self-serve onboarding flow, or keep the sales-assisted one” is.
Do you know who's going to test it, before you start designing?
Not “users” in general, but named people or a named recruitment route. If that's still open, that's week one's job, not week three's.
Is there a version of this that could fail, and would you actually notice?
If every outcome will be reported as a win internally, you're not testing. You're rehearsing a decision you've already made.
Could you describe “done” in one sentence, today?
A Prototype Sprint runs 2–3 weeks precisely because the scope is fixed up front. If “done” is still fuzzy, that's the discovery conversation to have first.
Is there a next step already agreed if the prototype proves the idea?
Doesn't need to be signed or budgeted, just a real next step, so the evidence you get actually leads somewhere.
Answered yes to all five?
Let's talk about a Prototype Sprint.
Get in touch