What Entrepreneurs Can Learn from Sprint
Priya spent four months building the first version of her subscription meal-kit service before a single stranger touched it. She and her cofounder debated recipes and delivery routes late into the night, sure that refinement would make the offering obviously good at launch. They hired a kitchen crew, leased refrigerated storage, and printed three thousand branded boxes. When orders finally opened, twenty households signed up, and twelve canceled after one delivery because the portions did not match how anyone actually cooked on a weeknight. Priya had spent four months building toward a guess nobody outside the founding team had confirmed. The unused lease, the unsold boxes, and a third of her runway were gone before she learned what one week of testing real families would have told her for free.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
Mapping the real problem before you sketch anything
Before sketching a solution, gather whoever understands the customer, operations, and money into one conversation and write down who the customer is, what moment the business interrupts, and what must be true for the idea to work. This keeps a founder from building toward a problem only they believe exists.
A solo founder assumes she already knows the problem because she has lived it, skips the conversation with her two employees, and builds a feature neither would have flagged as the real bottleneck.
Before writing a business plan, spend thirty minutes with everyone on your team listing the specific moment a customer would reach for your product and what makes that moment hard.
Sketching your own solution before pitching the group
Once the problem is mapped, resist an open-ended brainstorm. Ask each person, including yourself, to spend an hour alone sketching a concrete solution on paper before anyone speaks, so quieter or newer voices are not overwritten by whoever talks first.
A founder calls an open whiteboard session with his three-person team, describes his own idea first, and watches everyone else's suggestions quietly reshape to match what he already said.
Before your next product decision, give each teammate fifteen minutes to sketch a solution privately, then have everyone reveal their sketches at the same time.
Deciding on one direction quickly and on purpose
With several sketches on the table, a founder needs a deliberate way to pick one without letting debate run for days or the loudest voice win by default. A short structured review, where each person votes and the founder makes the final call, keeps the team moving toward something testable.
A two-person founding team disagrees for three weeks over which onboarding flow to build, neither side backing down, until the disagreement becomes the reason nothing ships.
Hold a one-hour meeting where every sketch gets a silent vote, then have the person with final authority commit to one direction before the meeting ends.
Building something rough and putting it in front of real people fast
A working prototype needs no real infrastructure, only enough realism that a stranger reacts to it honestly. A clickable mockup, a landing page collecting signups, or a founder quietly acting as the system behind the scenes can reveal whether five real prospects actually want what you propose, days after deciding rather than months after building. This will not guarantee success, but it tells you more than another week of internal debate ever could.
Deciding fast can fight with mapping the problem thoroughly: founders under runway pressure often skip straight to a decision because a full mapping conversation feels like a luxury. The balance is to timebox that conversation tightly rather than skip it, giving it an hour rather than a day, so the decision that follows is fast but not blind.
Name one thing, honestly
What would you have to admit about your current plan if you tested a rough version of it with five strangers this week instead of next quarter?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
Hold a one-hour meeting where every sketch gets a silent vote, then have the person with final authority commit to one direction before the meeting ends.