Key Takeaways
Build around a shared frustration, not the solution you already adore
Start with the irritation. Uri Levine’s Waze idea began during a family trip: ten cars faced a long drive home, and nobody knew which of two routes had less traffic. He called relatives already on the road for updates. The useful insight was not a clever navigation feature. It was a common problem drivers wanted gone. Levine uses the same approach for other ventures, from hidden retirement fees to the baffling experience of getting a car repaired.
Check that it matters. Ask who else experiences the problem, how painful it is, and how often it occurs. A large market with frequent or intense frustration is more promising than a universal nuisance that happens once every few years. Waze’s value also proved more emotional than its founders first assumed: drivers wanted peace of mind about arrival time, not merely the theoretically fastest route.
Personal frustration is a strong source of founder energy, but it is not market evidence. The useful move is converting a private irritation into a testable claim about other people’s lives. This resembles customer discovery and the jobs-to-be-done perspective: people adopt a product to make progress in a situation, not to admire its features. The discipline matters because founders can mistake familiarity for universality. A problem can be real and still be too rare, too mild, or too costly to solve profitably.
Treat every plan as a hypothesis, and make the cheapest test first
Learn before building. Start-ups make decisions without knowing whether their assumptions are true, so Levine treats product, marketing, pricing, and partnerships as experiments. A failed test is useful when it arrives quickly enough to inform another attempt. He calls the long stretch with little or no traction the desert of no traction: the product may work technically, yet users do not arrive, or they arrive and leave.
Simulate the service. Mego tested package pickup without writing software. Customers requested help through a WhatsApp group, while the team arranged pickups manually. Pontera’s early document-reading process was also done by people before automation. These tests revealed whether the service mattered without paying to build infrastructure first. The goal is not to avoid work; it is to avoid spending months perfecting an unproven assumption.
This approach turns entrepreneurship into applied experimentation. Its power comes from reducing the cost of being wrong, a principle shared with scientific research and software development. But speed alone is not learning: an experiment needs a clear question, a measurable outcome, and a decision rule. Otherwise, rapid testing becomes a succession of fashionable guesses. Manual prototypes work especially well when the underlying value can be delivered by people; they are less informative when reliability, safety, or automation itself is central to the proposition.
Measure product-market fit by repeat use, not applause or downloads
Retention is the proof. Product-market fit, or PMF, means a product consistently creates value for its intended users. Levine treats repeat use as its clearest evidence: consumer users return, while business customers renew or expand their use. Downloads, praise, and initial purchases can be encouraging, but they do not show that people keep receiving value.
Follow the drop-offs. Waze launched internationally in 2009 with incomplete maps and poor routes. More than 90 percent of users abandoned it. The team improved maps and routing through repeated releases, speaking with drivers to learn why the product failed them. By 2010, Waze had reached a usable level in key markets. Levine offers 30 percent retention after three months as a rule of thumb for products used several times monthly, not a universal threshold. The point is to measure cohorts and improve the specific steps where people leave.
Retention is a powerful antidote to vanity metrics because it asks whether value survives beyond the first impression. Cohort analysis makes that question more precise by tracking groups of users over time instead of averaging everyone together. Still, retention must be interpreted in light of the product’s natural cadence: a tax-filing tool and a daily navigation app should not be judged by identical return patterns. The metric is a signal, not a verdict. User interviews help explain what the curve cannot: why people returned, or why they disappeared.
Watch first-timers, because enthusiasts conceal the product's confusing parts
You are not the user. Levine calls an individual a sample of one. Founders and early adopters often tolerate glitches, explore settings, and understand what a product is supposed to do. The early majority is less comfortable with change and may simply quit when confused. In Waze, about 20 percent of users opened the app without entering a destination, while another 10 percent checked a route and then closed it. Their behavior differed from the team’s assumptions.
Observe, do not coach. Ask a person who has never used the product to try it while the team watches silently. Notice where they hesitate, what they misunderstand, and what they ignore. Levine argues that most people use only a few functions in their everyday apps, so unnecessary choices can make a useful product harder to adopt. Keep advanced functions available when they serve specific users, but do not make every newcomer navigate them.
Watching a novice use a product is a practical way to expose the gap between expert knowledge and everyday cognition. It connects to usability testing and cognitive-load theory: each unexplained choice asks users to spend attention they may not have. The method also counters confirmation bias, since enthusiastic users tend to validate the team’s hopes. Yet simplicity is not simply deleting features. Different user groups may need different capabilities, so the design challenge is to make the common path clear without hiding valuable options from people who depend on them.
Protect the current milestone by refusing attractive work that distracts
Choose the main task. Levine’s term for the most important thing at a given stage is the MIT. In the early stages, that usually means achieving PMF. Afterward, a company may focus on growth, monetization, or expansion. The team should concentrate on the current priority rather than trying to advance every part of the business at once.
Waze refused a million-dollar detour. In 2009, a logistics company offered to pay for truck-specific routes and features. The deal could have generated about $1 million annually, but serving truckers required data and product work that did not help Waze solve commuters’ problems. The team declined. Levine argues that focus includes deciding what not to do. He also warns that hiring sales or marketing teams before the product is ready can raise costs while sending dissatisfied users away.
Focus is a resource-allocation strategy, not a slogan. Every new customer segment creates demands on product design, support, and organizational attention, so even revenue can have hidden costs. The Waze decision illustrates how a lucrative contract can pull a young company away from the learning that makes its core offer work. The counterpoint is that rejecting adjacent opportunities can be costly if they reveal a stronger market. A disciplined team therefore needs a reasoned priority, plus evidence that would justify changing it.
Define your culture, then act quickly when a teammate violates it
Culture is built through decisions. Levine urges founders to state early what kind of workplace they want, including how decisions are made and what behaviors are unacceptable. At Waze, the founders wanted a place where people supported employees and drivers, and where a poor fit would be addressed rather than tolerated. He suggests revisiting a new hire after a month with one question: knowing what the team knows now, would it hire this person again?
Delay has a cost. In a small company, colleagues usually know when someone is underperforming or damaging trust. If a CEO avoids acting, strong employees may conclude that leadership cannot make hard calls. Levine recommends seeking candid peer feedback and checking references, not relying only on interviews. The principle is to correct mistakes promptly, while remembering that a poor onboarding or lack of training can be mistaken for a poor hire.
The strongest case for swift personnel decisions is that tolerance signals norms to everyone else. Organizational psychology emphasizes that fairness is not only about outcomes, but also about whether standards are applied consistently and explained clearly. A fast decision can protect trust when evidence is strong. The danger is treating one month or a peer ranking as a reliable verdict in every role. Performance may depend on training, management, or context. Clear expectations, direct feedback, and a real chance to improve make decisive action more credible, not less.
Use investor rejection as market noise, but scrutinize the partner you accept
Expect many noes. Levine calls early fundraising a dance of repeated rejection: a venture partner may meet 100 to 200 companies in a year and invest in only one or two. A refusal may reflect fit with a fund’s strategy, not proof that customers do not need the product. Founders should lead with the clearest, most emotionally engaging account of the problem and why it matters.
Choose the relationship carefully. Waze had dozens of investors decline before Microsoft led a $30 million round when the company was close to running out of cash. A term sheet is only a milestone, and its clauses can shape control and future returns. Levine advises founders to get experienced help negotiating and to speak with former portfolio-company CEOs, especially about how an investor behaved during trouble. Keeping potential investors informed also helps build relationships before the next round.
Investor rejection and customer rejection contain different information. A customer’s repeated indifference can challenge the problem hypothesis; a venture fund’s refusal may say more about its mandate, timing, or portfolio. Separating those signals prevents founders from treating every no as equally diagnostic. At the same time, access to capital creates a power imbalance, and a bad financing partner can impose lasting costs through governance and deal terms. The book’s emphasis on references is valuable because an investor’s conduct during a crisis is more revealing than a polished pitch meeting.
Price from customer value, not your cost spreadsheet
Start with willingness to pay. A product’s cost does not determine what the market will accept. Levine recommends first asking what value the customer receives, then whether the business can deliver that value profitably at a realistic price. As a rule of thumb for business-to-business products, a company may capture 10 to 25 percent of the value it creates. For example, a service saving a customer $1 million might support a fee in the range of $100,000 to $250,000.
Test the model in the market. Waze first expected to sell maps and traffic data, but slow sales and incomplete data made that difficult. It later tested advertising, beginning with local promotions. Customer interest, including a rival rental company asking why it was absent from the map, suggested the offer had traction. Levine favors recurring revenue when appropriate and uses a lifetime-value-to-acquisition-cost ratio above three as a sign of a sustainable model, while stressing that assumptions need validation.
Value-based pricing forces a company to articulate what changes for the customer, which improves both sales conversations and product design. It also exposes a common trap: a large theoretical benefit does not guarantee budget, urgency, or willingness to switch. The proposed 10 to 25 percent capture range is a heuristic, not a law; bargaining power and alternatives alter the share a supplier can command. Likewise, a lifetime-value ratio is only as trustworthy as its assumptions about retention, acquisition cost, and the time needed to recover spending.
Make growth repeatable before chasing billion-user scale
A headline is not a channel. When Apple’s CEO publicly recommended Waze after Apple Maps stumbled, Waze’s daily new users roughly doubled, but the full month’s increase was only about 10 percent. The bump faded. Levine distinguishes word of mouth from virality: viral products require other people to participate for the service to work, while word of mouth is a recommendation that can compound when use is frequent.
Build a repeatable path. Waze’s frequent use created many chances for passengers to ask about the app. Levine says growth should follow PMF; companies with frequent-use products can pursue growth before monetization, while lower-frequency products may need a business model first. Marketing includes finding the audience and testing channels, not just publicity. The author recommends lining up many acquisition experiments, measuring results, and retaining the approaches that produce users efficiently.
Growth is better understood as a system of repeatable inputs than as a single burst of attention. The distinction between virality and word of mouth is useful because it separates a product’s network dependence from its recommendation behavior. Both can compound, but neither rescues weak retention. Channel tests also need careful attribution: a surge may reflect seasonality, press coverage, or a concurrent product change. A healthy growth model tracks acquisition alongside retention and cost, so that new users represent durable progress rather than a larger leaking funnel.
Expand where you can win, rather than where prestige points
Let the home market set the timing. A start-up in a small country such as Israel cannot build a large company by serving only its local market, so it needs to consider international markets early. A company in a large market can often establish domestic traction first. Levine advises comparing target countries by market size, competition, customer-acquisition cost, cultural fit, and how clearly the problem exists there.
Pick winnable markets. Brazil, Mexico, Italy, Spain, Turkey, and Indonesia may offer large populations with lower competition or more effective local publicity than the US or UK. Moovit’s experience in Brazil showed the upside of local partnerships, while Waze’s partner Location World helped build regional traction. Levine recommends local operators or country managers over joint ventures, which can become difficult to exit. For a major expansion, a founder may need to commit substantial time on the ground.
International expansion is a portfolio of uncertain bets, not a prestige tour. A market’s size matters, but so do distribution costs, local habits, regulation, and the organization’s ability to learn there. Entering several markets in parallel can reveal differences sooner, provided the company has enough resources to support the tests. A local partner can supply context and access, but dependence on one partner may create new risk. The practical question is not simply where demand exists, but where the company can reach users and adapt without losing its core focus.
Judge an exit by its people, terms, and life after closing
A price is only part of the deal. Google acquired Waze for $1.15 billion in cash in 2013, with the Waze name and Israeli operations expected to continue. Earlier, Waze had rejected a $400 million offer. The eventual agreement depended not only on value but also on whether the teams shared a future. Levine advises founders to weigh personal consequences, employees’ outcomes, and the work and commitments that follow the transaction.
Protect the transition. An acquisition may include retention payments for employees, while earn-outs and holdbacks can make part of the price uncertain or difficult to collect. Legal and tax advice matters before signing, not after. The Moovit CEO’s individual calls to former employees before its sale made the reward tangible for people who had helped build the company. Levine also supports secondary share sales when sensible, giving founders and employees some liquidity before an all-or-nothing exit.
An acquisition is both a financial transaction and a transfer of control over an organization people have built. Evaluating only the headline price misses the value of cash versus stock, the conditions on deferred payments, and the effect of integration on employees. The emphasis on the day after is especially important because incentives diverge: investors may leave at closing, while founders and staff must live with the new structure. Secondary sales can reduce personal risk, though they also require careful governance and clear communication about who can participate.
Analysis
Levine’s central contribution is an operating logic for uncertainty: identify a consequential user problem, test the assumptions surrounding it, and concentrate resources on the next bottleneck rather than on the whole imagined company. The Waze story makes this logic concrete. A live map built from driver traces was not initially a polished product; it was a proposition that gained value as more people used it. The result depended on a tight loop between user behavior, data quality, product improvement, and eventually word of mouth.
The book is most useful when it turns slogans into observable questions. Do users return? Where do first-time users get stuck? Is the customer renewing? Does a proposed market entry produce measurable traction? These questions reduce the room for founder self-deception. The insistence on user observation is particularly strong because product creators are unusually poor judges of what novices find obvious.
Some prescriptions require context. Retention is an essential signal, but its meaning depends on how often a problem occurs. Rapid firing can protect a team from corrosive behavior, yet a short evaluation window can also confuse weak onboarding with weak performance. Similarly, refusing adjacent revenue can preserve strategic focus, but only if a team remains willing to revise its thesis when evidence changes. The book sometimes presents rules of thumb with the force of universal laws.
Its broader lesson is not that every start-up should imitate Waze’s choices. It is that ambition must be disciplined by feedback. Founders need enough conviction to persist through rejection, and enough intellectual humility to discard a favored feature, market, or business model when customers do not respond. Success then depends on more than a clever idea: it requires sequencing, organizational courage, adequate runway, and repeated proof that the company is creating value.
Review Summary
"Fall in Love with the Problem, Not the Solution" receives mostly positive reviews, praised for its practical insights into startup development. Readers appreciate the author's entrepreneurial experience and straightforward advice. The book covers various aspects of building a business, from problem identification to exit strategies. Some criticize its focus on externally-funded companies and repetitive themes. Overall, it's highly recommended for entrepreneurs and business leaders, offering valuable lessons on perseverance, customer focus, and navigating the challenges of startup life.
People Also Read
Glossary
Product-market fit (PMF)
Repeated value for usersThe point at which a product reliably creates value for its intended market. Levine treats continued use as the central evidence: consumers return to the product, while business customers renew or expand their engagement. Downloads, positive comments, and a first sale are not sufficient by themselves. A company searches for PMF through iterations that improve user conversion and retention.
all over phase
Early, unfocused planningThe initial period when a founder is considering many parts of a possible company at once, including the problem, product, market, business model, funding, and growth. Much of the plan remains theoretical. The phase ends when the founder has enough conviction about the core assumptions and sequence of work to begin focused execution, while accepting that those assumptions still need testing.
desert of no traction
Extended lack of momentumLevine’s metaphor for the long stretch when a start-up is making little visible progress. A product may not work, may fail to attract users, or may attract users who do not return. The company must keep learning without changing direction randomly or running out of funding. The metaphor highlights how incremental progress can be difficult to see while experiments accumulate.
MIT (the most important thing)
Current top priorityThe single most important objective for the company in its current operating phase. It may be product-market fit, fundraising, monetization, or growth, depending on the company’s circumstances. Levine argues that leaders should identify the MIT, align the organization around it, and avoid spending heavily on later-stage work before the current priority is achieved.
Qualification Matrix
Market size and painA way to assess a problem using two dimensions: the size of the addressable market and the problem’s pain, measured by intensity or frequency. Problems affecting many people and recurring often are potential winners. A small but severe problem may support a valuable niche, while a widely shared but rare inconvenience may not support a large business.
social+
Value grows with participationA product category in which users contribute to the information or activity that makes the service useful to everyone else. Waze is an example because drivers supply location traces and reports that improve maps and traffic guidance. The service becomes more valuable as participation expands, and its value may be limited where too few people contribute.
Key Investor Indicators (KIIs)
Signals of investor interestBehaviors Levine uses to judge whether a potential investor is seriously considering a deal. Examples include asking who else is interested, requesting the capitalization table, discussing deal terms, or advising on a presentation for other partners. These signals help founders distinguish active interest from general conversation, though they do not guarantee an investment.
First-time value (FTV)
Value from initial useThe revenue or economic value generated when a customer uses a product for the first time. Levine uses FTV as a useful reference for products with infrequent use, where lifetime value is hard to estimate because repeat behavior is unknown. Comparing FTV with customer-acquisition cost can help determine whether paid marketing is financially plausible.
DNA document
Written company valuesA document that makes a start-up’s intended culture explicit, including its values, decision practices, and expectations for how colleagues work together. Levine recommends creating it early, before habits become entrenched, and using it to guide hiring and organizational decisions. It is meant to make culture operational rather than leave it as an unstated aspiration.
FAQ
What's Fall in Love with the Problem, Not the Solution about?
- Entrepreneurial Focus: The book emphasizes the importance of focusing on the problem rather than the solution when building a start-up. Uri Levine shares insights from founding Waze and other companies.
- Structured Methodology: Levine outlines a structured approach to entrepreneurship, detailing phases such as achieving product-market fit, fundraising, and scaling.
- Real-World Examples: The book uses real-life examples from Levine's journey and other successful entrepreneurs to highlight key lessons and strategies.
Why should I read Fall in Love with the Problem, Not the Solution?
- Actionable Insights: The book provides practical advice that can be directly applied to entrepreneurial endeavors, helping readers avoid common pitfalls.
- Inspiration from Success: Levine's success with Waze and other ventures serves as a motivational backdrop for aspiring entrepreneurs.
- Mentorship Perspective: Written from a mentor's perspective, the book aims to educate and empower future entrepreneurs, encouraging them to mentor others.
What are the key takeaways of Fall in Love with the Problem, Not the Solution?
- Love the Problem: The central theme is to "fall in love with the problem, not the solution," encouraging a focus on solving real user issues.
- Embrace Failure: Failure is an integral part of the entrepreneurial journey, and Levine advocates for failing fast and learning from mistakes.
- Phased Approach: Operating in phases, focusing on one key aspect at a time, is crucial for effective progress in a start-up.
What is the Product-Market Fit (PMF) concept in Fall in Love with the Problem, Not the Solution?
- Definition of PMF: PMF is when a product meets market needs effectively, resulting in user retention. Levine states, "If you don’t figure out product-market fit (PMF), you will die."
- Key Metric: Retention is the primary metric for measuring PMF, indicating that the product provides value if users return.
- Focus on Value Creation: Achieving PMF requires understanding user needs and continuous iteration based on feedback.
How does Fall in Love with the Problem, Not the Solution address fundraising?
- Fundraising as a Journey: Levine describes fundraising as an ongoing process, requiring resilience and persistence.
- Dance of the One Hundred Noes: Entrepreneurs should expect many rejections before securing funding, highlighting the importance of perseverance.
- Investor Relationships: Managing investor relationships and keeping them informed is crucial for maintaining confidence and support.
How does Uri Levine suggest managing investors in Fall in Love with the Problem, Not the Solution?
- Keep Investors Informed: Regular updates build trust and can lead to continued support.
- Address Conflicts of Interest: Clear communication and alignment of interests are essential, especially during liquidation events.
- Engage with the Board: Effective management of the board of directors is crucial, with pre-briefing to avoid surprises.
What is the significance of firing fast in Fall in Love with the Problem, Not the Solution?
- Importance of Quick Decisions: Making hard decisions, like firing underperforming team members, is essential for maintaining a strong team.
- Impact on Team Dynamics: Firing fast helps reinforce a culture of accountability and high performance.
- Building the Right DNA: Establishing a strong company culture from the outset is crucial, and firing those who do not fit is part of this process.
How does Fall in Love with the Problem, Not the Solution define disruption?
- Disruption Explained: Disruption is a change in market equilibrium, driven by changes in behavior rather than technology.
- Examples of Disruption: Companies like Gmail, Uber, and Airbnb changed existing markets by offering new value propositions.
- Role of Newcomers: Disruptors are often newcomers who take risks that established companies are unwilling to take.
What are the phases of a start-up as outlined in Fall in Love with the Problem, Not the Solution?
- Phased Approach: A structured approach to building a start-up, focusing on one phase at a time, is emphasized.
- Focus on MIT: Each phase has a Most Important Thing (MIT) that needs prioritization, such as user retention during the PMF phase.
- Transitioning Between Phases: Challenges of transitioning between phases require careful management of resources and team dynamics.
How can I apply the lessons from Fall in Love with the Problem, Not the Solution to my own entrepreneurial journey?
- Identify a Big Problem: Engage with potential users to understand their frustrations and validate the problem's significance.
- Embrace Failure: Adopt a mindset that views failure as a learning opportunity, iterating based on feedback.
- Focus on Phases: Implement a phased approach, ensuring product-market fit before moving on to growth or scaling efforts.
What are some common pitfalls in the entrepreneurial journey highlighted in Fall in Love with the Problem, Not the Solution?
- Premature Scaling: Scaling too quickly before achieving PMF can lead to misalignment and wasted resources.
- Ignoring User Feedback: Failing to listen to user feedback can result in products that do not meet market needs.
- Overconfidence in Ideas: Falling in love with solutions rather than problems can lead to a disconnect with market needs.
What are the best quotes from Fall in Love with the Problem, Not the Solution and what do they mean?
- "I did my share.": Reflects Levine's commitment to mentorship and sharing knowledge with the entrepreneurial community.
- "If you don’t figure out product-market fit (PMF), you will die.": Underscores the critical nature of PMF in start-up success.
- "The main thing is to keep the main thing the main thing.": Encourages entrepreneurs to prioritize efforts on what truly matters for their business.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.