Business & Organizations · Entrepreneurship & innovation
Testing whether a problem is worth solving
See how Zappos tested its idea with photographs of other shops' shoes, and learn to turn an idea into a problem, an assumption and a small test that could change your mind.

What you will learn
- Tell a description of a problem apart from a proposed product.
- Write a question about a specific, recent experience.
- Identify the assumption in an early idea that a decision depends on.
- Tell evidence of stated interest apart from evidence of actual use or purchase.
Lesson 1 of 4 · 4 min
Describe the problem before you pick a solution
In 2016 a company called Juicero began selling a $699 juicer. It connected to Wi-Fi and pressed sealed packs of chopped fruit. Investors put in $120 million. Then reporters squeezed the packs by hand and got nearly the same juice. Juicero ceased operations in 2017.
The press solved a problem its buyers didn't have. Founders make the same mistake in smaller ways. One says, "People need an app that reminds them about bicycle maintenance." That sentence has already picked a solution.
The real problem might be finding time for repairs, not knowing what needs attention or having no way to move a broken bike. Starting with the app narrows the search before anyone understands the obstacle.
A useful problem description names a person, a situation and an unwanted outcome. For example, "Commuters lose travel time when a small bike fault turns into a breakdown."
That doesn't prove the problem is common or important. It gives you a claim you can check, by watching people, interviewing them, reading existing evidence and looking at what they already use.
To check the claim, don't ask people whether they'd like your app. Ask about a specific, recent experience and what they did about it.
Three questions do most of the work. "Tell me about the last time your bike wasn't usable for a trip you needed to make." "What did you do instead that day?" "What did it cost you, in money or time?" None mentions an app.
Say ten commuters answer, in a made-up round of interviews. Two say they forgot a service was due. Seven say the bike broke without warning and the hard part was getting it to a shop without a car. Each of them lost half a day. One had no problem worth mentioning.
The reminder idea fits two of ten stories. Transport to repair fits seven. A question about real events can show you that. A question about an imagined app can't.
Look for what it costs people, in time, money, effort or missed chances, and for patterns across people. A rare but serious disruption can matter more than a frequent small one, so don't judge importance by frequency alone.
Ten interviews can't show how common a problem is across a city. They show which problem is worth measuring next.
Try to recallWrite an interview question that explores someone's recent bicycle problem without asking whether they like a proposed app.
For example, "Tell me about the last time your bike was unavailable for a trip. What happened, and what did you do instead?"
Lessons in this topic
Describe the problem before you pick a solution
See why a $699 juicer failed, and learn to describe a customer's difficulty without building your solution into the question.
Pick the test that could change your mind
Find the assumption a decision depends on, set the result that would change your plan before you test, and count what people do instead of what they say.
People want it, but can you deliver it?
Separate proof that customers want a service from proof that you can staff it and pay for it, and choose the next test to match.
How to size a market and doubt the answer
Turn a count of customers into a sales projection, then find the guess inside it that changes the result most.
Three quick stories from this topic
How Zappos began
Zappos began as photos of shoes in local stores, bought only after a customer ordered
Founder Nick Swinmurn wanted to know whether people would buy shoes online, so he tested it before stocking a single pair. Each order sent him back to the store to pay full price. In 2009 Amazon bought Zappos in a deal worth about $1.2 billion.
Orders beat opinions
Saying you'd buy something costs nothing. Placing an order does. A test that counts real purchases shows what a survey of intentions can't.
Test the assumption that matters
The whole business rested on one assumption, that people would buy shoes online. Swinmurn tested that one first and built the rest later.
The $699 juicer
A $699 Wi-Fi juicer failed after reporters squeezed its juice packs by hand
Juicero raised $120 million from investors. In 2017 Bloomberg found that squeezing the packs by hand gave nearly the same juice as the machine. The press solved a problem its buyers didn't have, and the company ceased operations that year.
Start with the problem
A useful problem description names a person, a situation and an unwanted outcome. It leaves the solution open until the evidence points to one.
Ask about real events
Asking people about the last time something went wrong shows what they did about it. Asking whether they'd like your product tells you much less.
Quibi's projection
Quibi projected 7.4 million subscribers in year one and had about 500,000 when it gave up
The short-video service raised $1.75 billion and launched in April 2020. Six months later it announced it was shutting down. A sales projection multiplies guesses about how many people will pay, and funding doesn't make the guesses true.
A projection is a multiplication
A sales projection multiplies target customers by revenue per customer. Each input is an assumption until someone tests it.
Test the boldest guess
Find the input that changes the result most and test that one first, on a small scale, before spending on the rest.
Sources
- 6.1 Problem Solving to Find Entrepreneurial Solutions - Entrepreneurship | OpenStax, OpenStax, Rice University
- 11.2 Designing the Business Model - Entrepreneurship | OpenStax, OpenStax, Rice University
- Plan your business - Small Business Administration, US Small Business Administration
- Juicero, Wikipedia
- Lean startup, Wikipedia
- Zappos, Wikipedia
- Quibi, Wikipedia





