Rule No. 1 📔 Solve a Real Problem.

What Eric Ries figured out (and what took most of us years of expensive mistakes to learn) is that building a great product the wrong customer doesn’t want is just organized waste. The Lean Startup gives you a system to treat every business idea as a hypothesis, test it cheaply, and pivot before you’ve burned your runway. The framework borrows from lean manufacturing, but its real insight is about decision velocity: the faster you move from assumption to evidence, the less you lose when you’re wrong.

—Validate before you build

Most founders build for months before talking to a real customer. Ries calls this “success theater” — activity that looks like progress but generates no learning. Your first job is to find out whether the problem you’re solving actually exists, and whether your target customer feels it urgently enough to change their behavior. A conversation beats a prototype; a prototype beats a full product.

—The MVP is a learning tool, not a launch

A minimum viable product is the smallest experiment that answers your most critical assumption. It is not a rough version of your final product — it’s a probe. Executives who’ve spent careers on polished launches struggle with this. Let go of pride of craft at the hypothesis stage. You’ll rebuild everything anyway once you know what customers actually need.

—Measure what changes behavior, not what feels good

Ries distinguishes between vanity metrics — page views, downloads, press mentions — and actionable metrics that reveal whether customers are truly engaged. If your numbers go up but no one can explain what action caused it or what to do next, those numbers are decorative. Instrument your business around the questions that actually drive decisions.

—Pivot is a strategic correction, not a failure

In traditional business culture, changing direction is an admission of defeat. Ries reframes it as disciplined responsiveness to evidence. The best pivots preserve what you’ve learned while redirecting where you apply it — a new customer segment, a different channel, a repositioned feature. The failure isn’t pivoting; it’s waiting too long to do it once the data is telling you to.

—Build-Measure-Learn must become a cultural rhythm

The loop only works if your organization is structured to run it continuously. That means small autonomous teams, short cycle times, and leaders who reward learning — not just results. The bottleneck is almost always culture: teams that fear being wrong will hide bad data, avoid experiments, and optimize for looking busy. Your job as a leader is to make it safe to be wrong early and loud about it.

The core argument of this book can be boiled down to one uncomfortable truth most seasoned executives have learned the hard way: the confidence you feel about a new idea is not the same thing as evidence that it’s right. Ries gives you the discipline to close that gap before it costs you real money.

The Build-Measure-Learn loop isn’t just a startup concept, it applies every time you’re entering a new market, launching a product line, or testing a strategy inside an established business. The executives who get the most out of this book are the ones willing to apply the same rigor they’d demand of a financial model to every assumption underneath their strategy.

Build-Measure-Learn Loop

• Start with a Minimum Viable Product (MVP)—the simplest version of your idea.
• Release it quickly to test assumptions and gather real-world feedback.
• Use the data to learn what works and what doesn’t, then iterate.

Validated Learning

• Don’t just guess or assume—test hypotheses with customers.
• Every product, feature, or campaign should contribute to validated learning.

Pivot or Persevere

• Be willing to make a pivot (a fundamental change in strategy) if something isn’t working.
• Or persevere if data shows you’re on the right track—just refine and scale.

Innovative Accounting

• Traditional metrics (like vanity metrics) can mislead.
• Focus on actionable metrics that directly relate to user behavior and product success.

Continuous Deployment & Split Testing

• Launch small, frequent changes and test variations (A/B testing) to understand user preferences and behavior.

Entrepreneurship = Management

• Startups need a new kind of management system—one focused on agility, learning, and adaptability rather than control and planning.

Lean Thinking Isn’t Just for Startups

• Established businesses can use lean principles to innovate internally and launch new products with less waste and better customer alignment.

1. If people are customizing your product more than using it as-is. They’re adapting it to their real need, not yours.
2. If your “value proposition” takes more than 30 seconds to explain. Confusion means you’re solving something too weird or irrelevant.
3. If you’re adding features faster than you’re gaining traction. This is often a symptom of solving symptoms, not causes.
4. If your sales team is improvising your messaging. If they can’t sell it cleanly, the problem may not feel urgent or real to customers.
5. If your most engaged users aren’t your original target audience. You may have discovered a different (and better) problem to solve.
6. If your “problem” is from your past, not your customer’s present. Founders often create solutions from personal pain points, maybe the market shifted.
7. If user behavior contradicts what they say they want. People may tell you the problem, but their actions show something different.
8. If customer retention is low, even though satisfaction surveys look good A quick-fix solution can earn good reviews and still miss the mark.
9. If the “problem” you’re solving feels theoretical, not felt. If it doesn’t show up in their calendar, wallet, or stress level, it’s not urgent.
10. If you’re focused on differentiation, not relevance. Being different doesn’t matter if you’re not solving something real and useful

Maybe solving a real problem isn’t enough. Every business solves a problem, but that doesn’t automatically make it a good business. Some problems are real but too small. Some customers aren’t willing to pay to solve them. Some problems disappear when the market changes. And sometimes customers don’t even know they have a problem until someone shows them a better way. There’s an old line that says, “If Henry Ford asked people what they wanted, they would have asked for a faster horse.”

So here’s the challenge: Should a business always solve a problem customers already recognize, or should great businesses sometimes create a better solution before customers even know they need it?

Let’s go around the table:

1. Can you think of a successful product or company that created demand rather than responded to an obvious problem?
   • AN EXAMPLE: Sony Walkman, 1979. At the time, portable music meant big boom boxes or bulky radios that disturbed other people. No widespread consumer surveys showed people demanding private, high-quality music on the go. Akio Morita and the team pushed the industry and created the personal listening experience. The product sold tens of millions of units in its early years and fundamentally changed how people related to music and public space. Competitors scrambled to catch up; the category did not exist until Sony made it real.
2. Is customer feedback always the best guide, or can listening too much keep your company trapped in the past?
3. When does “solving a real problem” become an excuse for playing it safe?
4. Should entrepreneurs solve the problem customers are asking about, or the problem they haven’t figured out how to articulate yet?
5. What if, instead, we don’t start with the problem, we start with what people are already doing and just make it easier.

Challenging the Rules isn’t intended to defeat them, just to pressure test them. Does “Solve a real problem” mean solving a problem customers already know they have? Or does it mean having the vision to identify a problem or opportunity they haven’t recognized yet?

Here, at The Institute, we believe this Rule still stands. But maybe “real” doesn’t always mean obvious.

Staying problem-oriented is one of the most powerful disciplines a team can adopt. It keeps work grounded in purpose, guides better decisions, and prevents wasted effort.

1. Start with your Core Problem Statement

• Ensure every project, feature, or sprint begins with a clearly articulated customer problem.
• Use frameworks like Jobs To Be Done or problem-centric user stories: “As a [user], I need to [do X] so that I can [achieve Y].”
• Ask: “What pain point are we solving?” — and who feels it most?

2. Make Customer Empathy a Ritual

• Use real customer quotes, videos, or complaints in team meetings.
• Regularly schedule customer interviews or shadowing sessions.
• Share “Customer of the Week” stories that highlight struggles and feedback.

3. Ask “Why?” — Relentlessly

• Use the 5 Whys method to get to the root of every request.
• Don’t take feature requests at face value; ask what problem it solves.
• Teach teams to be skeptical of solutions not tied to a problem.

4. Measure Problem Impact, Not Just Output

• Use KPIs that reflect problem-solving: reduction in support tickets, task completion rate, NPS tied to specific workflows.
• Reward impact, not activity. Praise when problems are avoided or simplified, not when features are just “shipped.”

5. Say “No” — Clearly and Often

• Create a public “Not Doing List” to document shiny object requests you’ve declined and why.
• Train your team to defend focus with data, not opinions.
• Protect roadmaps from bloat by tying every initiative back to a validated problem.

6. Close the Feedback Loop

• After launching a feature, circle back to the original problem: Did we solve it? How do we know?
• If not, iterate or remove the feature. Let the team see that solving is the goal, not just shipping.

7. Instill a “Problem-First” Culture

• Celebrate questions more than answers in team discussions.
• Appoint a “Problem Owner” for initiatives — someone whose job is to ensure the team doesn’t drift into solution-for-solution’s-sake mode.
• Make your value proposition about customer outcomes, not product bells and whistles.

It’s not enough to avoid the warning signs. Strong businesses regularly confirm they’re still aligned with the fundamentals. Use the indicators below as an annual check-in to assess whether your organization is truly living out this Rule, or simply assuming it is.

1. Customers can clearly explain why they need you.
   They describe the value of your business in practical terms, not vague praise.
2. Your product or service is tied to a recurring pain point.
   The problem you solve isn’t occasional—it shows up regularly in your customer’s operations or life.
3. Referrals happen naturally.
   Customers recommend you because your solution meaningfully improved their situation.
4. Retention is strong because your offering stays relevant.
   Customers continue buying because the problem persists and your solution continues delivering value.
5. Your team understands the customer’s pain better than your competitors do.
   Internally, your people can articulate the real-world problem you solve and why it matters.

Following a business principle isn’t about saying the right things—it’s about seeing the evidence. If these signs describe your organization, you’re likely applying this Rule well. If not, it may be time for a harder look.

“Do these still describe us honestly—or are we slipping?”

Zappos – Validating Online Shoe Sales – Instead of investing in inventory, founder Nick Swinmurn tested demand by photographing shoes from local stores and posting them online. When someone bought a pair, he purchased it at retail and shipped it himself. The demand was real—Zappos was born.

Dropbox – Testing Demand with a Simple Video – Before building the product, Dropbox created a short explainer video to demonstrate how it would work. It led to thousands of sign-ups overnight, validating interest before a single line of backend code was written.

Stripe – Simplifying Online Payments – Online payments were a developer’s nightmare. Stripe’s founders launched with a few lines of code that made integration effortless. Solving that technical bottleneck made Stripe the go-to platform for startups.

GitHub – Streamlining Code Collaboration – Developers were emailing code back and forth—inefficient and error-prone. GitHub built a collaborative platform around Git, making version control easy and enabling open-source to thrive.

Wagestream – Reducing Financial Stress Between Paychecks – Recognizing that many workers live paycheck to paycheck, Wagestream let employees access earned wages instantly. A simple fix to a widespread problem—and a hit with employers and workers alike.

The Origin Story Example: Sara Blakely (Spanx) solved the problem of uncomfortable or unflattering undergarments by cutting the feet off her pantyhose. Real problem, scrappy solution, massive outcome.

The Market Misalignment Example: Airbnb – Monetizing Extra Living Space – Struggling to pay rent, the founders hosted guests on air mattresses during a local conference. The experience uncovered a huge demand for affordable, short-term stays—and led to the creation of a hospitality giant. Airbnb solved the problem of trust in home-sharing — not just lodging access.

The Strategic Shift Example: Slack began as an internal tool at a gaming company solving communication issues — the game failed, but the real problem solved was how teams talk.

Before scaling, these founders took one critical step: they solved a real problem. Whether it was hosting guests during a conference or simplifying a nightmare integration, these companies found pain points and built with purpose. Their stories prove that timeless principles, like solving something real, still drive the most lasting results.