The Lean Startup – Identifying Your Leap-of-Faith Assumptions

---

Overview: What Are Leap-of-Faith Assumptions?

In Chapter 4, we learned how to design experiments. But which assumptions should we test FIRST?

Eric Ries introduces the concept of Leap-of-Faith Assumptions – the riskiest, most critical assumptions your entire business depends on.

What is a Leap-of-Faith Assumption?

A leap-of-faith assumption is an unproven hypothesis that, if wrong, will cause your entire business to fail.

Examples:

• For Facebook (early days): “College students want to connect with each other online”
• For Uber: “People will get into cars driven by strangers”
• For Airbnb: “People will let strangers sleep in their homes”

These seem obvious NOW, but they were huge leaps of faith at the time!

“The two most important assumptions entrepreneurs make are what I call the value hypothesis and the growth hypothesis. These give rise to tuning variables that control a startup’s engine of growth.”

---

Why Leap-of-Faith Assumptions Matter

Most startups fail not because of bad execution, but because they built something nobody wanted.

The Danger of Untested Assumptions

When you don’t test your leap-of-faith assumptions early:

• You waste months (or years!) building the wrong product
• You spend money on features nobody wants
• You only discover the truth when it’s too late

The solution: Identify and test your riskiest assumptions FIRST, before investing heavily in building.

☕ Hamed’s Analysis: The Most Expensive Mistake

I’ve seen this mistake SO many times in my consulting work:

The Pattern:

• Someone has a “great idea”
• They spend 6-12 months building it
• They launch with excitement
• Nobody uses it

Why did this happen? They never tested their leap-of-faith assumption!

Real example – Social Fitness App:

I consulted for a team building a “social fitness app” where friends could challenge each other to workouts.

Their untested assumption: “People want to compete with friends for fitness motivation.”

What actually happened: After building for 8 months, they discovered people felt EMBARRASSED sharing their workouts with friends! The core assumption was wrong.

Cost: $50,000 and 8 months wasted.

How to avoid this: Test your leap-of-faith assumption in WEEK 1, not month 12!

---

How to Identify Your Leap-of-Faith Assumptions

Eric Ries provides a framework for finding your most critical assumptions:

The 3-Question Framework

Question 1: What must be true about your customers?
Example: “Restaurant owners want to save time on inventory management”

Question 2: What must be true about your product?
Example: “Our automated inventory system will actually save them time”

Question 3: What must be true about your market?
Example: “Enough restaurants struggle with inventory to make this a viable business”

Your leap-of-faith assumptions are the answers that, if FALSE, kill your business!

Example: Identifying Leap-of-Faith for an Online Tutoring Service

Let’s say you want to start an online tutoring platform for high school math.

Potential assumptions:

• “Parents will pay for online tutoring” → Leap-of-faith? MAYBE
• “Students will engage with tutors on video calls” → Leap-of-faith? YES!
• “Online tutoring is as effective as in-person” → Leap-of-faith? YES!
• “We can recruit qualified tutors” → Leap-of-faith? NO (easy to test)

The two biggest leaps: Will students actually engage online? Is it effective?

Test these FIRST before building anything!

☕ Hamed’s Analysis: How I Find Leap-of-Faith Assumptions With Clients

When I work with startups, I use this simple exercise:

The “What if we’re wrong?” Test

I ask: “If this assumption is wrong, does your entire business fail?”

• If YES → That’s a leap-of-faith assumption. Test it NOW!
• If NO → It’s important but not critical. Test it later.

Example – My Restaurant Website Client:

When we discussed their online ordering system, I asked about their assumptions:

• “Customers want to order online” → If wrong? Business fails. LEAP-OF-FAITH!
• “They’ll pay by credit card” → If wrong? We can accept cash. Not leap-of-faith.
• “They want delivery” → If wrong? They can pick up. Not leap-of-faith.

We tested the FIRST assumption (online ordering demand) by adding a WhatsApp button – validated in 1 week!

---

Case Study: Facebook’s Leap of Faith

Eric Ries discusses Facebook (then called “The Facebook”) as a perfect example of testing leap-of-faith assumptions.

Facebook’s Early Leap-of-Faith Assumption

The assumption: “College students want a digital directory to connect with classmates.”

In 2004, this was NOT obvious! Remember:

• MySpace focused on music and entertainment
• Friendster was for meeting new people online
• The idea of a “digital yearbook” was unproven

How Mark Zuckerberg Tested It

Instead of building a global platform, Mark did something brilliant:

• Step 1: Built a simple version just for Harvard students
• Step 2: Launched it in one dorm first
• Step 3: Watched: Did students actually sign up and use it?

The result: Within 24 hours, over 1,200 Harvard students had signed up!

Key insight: This validated the leap-of-faith assumption. ONLY THEN did he expand to other schools.

☕ Hamed’s Analysis: The Power of Starting Small

Notice what Mark Zuckerberg did: He started with ONE college, not all colleges!

Why is this brilliant?

• If the assumption was WRONG, he’d know in days (not years)
• Low cost to test (just one school’s worth of effort)
• Easy to pivot if needed
• Fast feedback loop

Lesson: Test your leap-of-faith assumption in the SMALLEST possible market first!

My example – Women’s Clothing Store Website:

I worked with a boutique owner who wanted to sell online nationwide. But we started small:

• Week 1: Posted 10 items on Instagram for local customers only
• Week 2: Offered local delivery for orders via DM
• Week 3: Got 23 orders from her existing customer base!

This validated: “My customers WILL buy online.” THEN we built a proper e-commerce website.

If it had FAILED? We’d know after investing just 3 weeks – not 6 months building a fancy website nobody would use!

---

The Two Critical Leap-of-Faith Assumptions

While every startup has multiple assumptions, Eric Ries emphasizes that two are almost always the most critical:

1. The Value Hypothesis (Revisited)

The question: Do customers find enough value in your product to actually use it?

NOT just “Would you use this?” but “Will you KEEP using this?”

How to test:

• Give your MVP to 50 people
• Track: How many use it more than 3 times?
• If less than 40% → Your value hypothesis is likely wrong

2. The Growth Hypothesis (Revisited)

The question: How will your product grow? Will customers tell others?

This determines your entire business model!

How to test:

• Give your MVP to your first 100 customers
• Don’t do ANY marketing
• Track: Do they naturally tell their friends?
• If NO → You’ll need to rely on paid marketing (expensive!)

“The point is not to find the average customer but to find early adopters: the customers who feel the need for the product most acutely. Those customers tend to be more forgiving of mistakes and are especially eager to give feedback.”

---

End of Part 1

In Part 2 we’ll cover:
• How to find and engage with early adopters
• The role of analogs and antilogs in identifying leaps of faith
• Practical exercises for testing your assumptions
• Five Key Takeaways from Chapter 5

📖 Chapter 5: Leap – PART 2

---

Finding and Engaging Early Adopters

Eric Ries emphasizes that when testing leap-of-faith assumptions, you should NOT target average customers. Instead, focus on early adopters.

Who Are Early Adopters?

Early adopters are customers who:

• Feel the problem most acutely
• Are actively looking for solutions RIGHT NOW
• Are willing to try imperfect products
• Will give you honest feedback
• Will forgive early mistakes

Example: For Dropbox, early adopters were tech-savvy people who already struggled with file syncing across multiple computers.

How to Find Early Adopters

Step 1: Identify where people with your problem hang out

• Online forums and communities
• Social media groups
• Industry events
• Professional networks

Step 2: Look for people actively complaining about the problem

• Search Twitter for keywords related to your problem
• Read Reddit threads where people ask for solutions
• Join Facebook groups where your target customers gather

Step 3: Engage directly and offer your MVP

• Send personal messages
• Offer free access in exchange for feedback
• Be transparent that your product is early-stage

☕ Hamed’s Analysis: How I Help Clients Find Early Adopters

Most founders make this mistake: They try to launch to EVERYONE at once.

Better approach: Find 10-20 people who DESPERATELY need your solution!

Real example – Meal Prep Service for Busy Professionals:

My client wanted to launch a healthy meal delivery service. Instead of spending money on ads, we did this:

• Week 1: Posted in local Facebook groups: “Who struggles to eat healthy because you’re too busy to cook?”
• Week 2: Got 47 responses! We messaged the 15 most engaged people
• Week 3: Offered them 1 week of free meals in exchange for honest feedback
• Week 4: 12 out of 15 said they’d pay for it!

Cost: Just the food for 15 people for one week. Validation: Confirmed people WOULD pay for this service!

Lesson: Early adopters are often HAPPY to be your guinea pigs if you’re solving a real problem for them!

---

Using Analogs and Antilogs

Eric Ries introduces a powerful tool for identifying leap-of-faith assumptions: looking at analogs (similar successes) and antilogs (similar failures).

What Are Analogs?

Analogs: Other companies or products that succeeded by solving a similar problem.

How to use them: Study what worked for them and apply those lessons to your startup.

Example – Airbnb’s Analog:

• Analog: eBay (proved people will trust strangers in online transactions)
• Insight: If eBay could build trust for buying/selling, Airbnb could build trust for home rentals
• Leap-of-faith assumption validated: Trust can be created through ratings and reviews

What Are Antilogs?

Antilogs: Companies that failed trying something similar to what you’re attempting.

How to use them: Study WHY they failed so you can avoid the same mistakes.

Example – Uber’s Antilog:

• Antilog: Traditional taxi dispatch services (slow, unreliable, poor customer experience)
• Insight: The old model failed because it lacked real-time tracking and transparent pricing
• Leap-of-faith assumption to test: People want to see their driver’s location and know the price upfront

☕ Hamed’s Analysis: How I Use Analogs and Antilogs With Clients

When I work with startups, I always ask two questions:

Question 1: “Who has succeeded doing something similar?” (Find your analog)

Question 2: “Who has FAILED doing something similar?” (Find your antilog)

Example – Online Tutoring Platform:

My client wanted to launch an online tutoring service for high school students.

Analogs we studied:

• Khan Academy (proved students will learn online)
• Coursera (proved video-based learning works)
• Duolingo (proved gamification increases engagement)

Antilogs we studied:

• Several failed tutoring platforms that tried to be “Uber for tutors” (failed because no quality control)
• Platforms that relied only on pre-recorded videos (failed because students need live interaction)

Insight: We needed LIVE tutoring (analog: Khan Academy’s success) WITH quality control (antilog: Uber-for-tutors failures).

Result: We designed an MVP that focused on live, vetted tutors – and it worked!

---

Practical Exercise: Identifying Your Leap-of-Faith Assumptions

Eric Ries provides a step-by-step process for identifying and testing your leap-of-faith assumptions.

The 5-Step Process

Step 1: List all your assumptions
Write down EVERY assumption your business depends on.

Step 2: Identify the riskiest ones
Ask: “If this assumption is wrong, does my business fail?” If YES, it’s a leap-of-faith assumption.

Step 3: Find analogs and antilogs
Research similar companies to learn what worked and what didn’t.

Step 4: Design a test for your riskiest assumption
Create the simplest possible experiment to validate or invalidate this assumption.

Step 5: Run the test and learn
Execute the test, collect data, and decide whether to pivot or persevere.

Example: Testing a Leap-of-Faith for a Fitness App

Let’s say you’re building a fitness app that connects users with personal trainers via video calls.

Step 1: List assumptions

• People want to work out at home
• People will pay for virtual training
• Video call workouts are effective
• Personal trainers want to work remotely

Step 2: Identify riskiest assumption

“Video call workouts are effective” → If this is false, nobody will use your app!

Step 3: Find analogs and antilogs

• Analog: Peloton (proved people will work out at home with guidance)
• Antilog: Many failed “live workout streaming” apps (people got bored without personal interaction)

Step 4: Design a test

Offer 10 people free sessions with a personal trainer via Zoom. After 4 weeks, ask: “Was this as effective as in-person training?”

Step 5: Run the test

• If 8+ out of 10 say YES → Assumption validated! Build your app.
• If 5 or fewer say YES → Assumption INVALID. Pivot or abandon.

☕ Hamed’s Analysis: The Power of Testing Small

Notice in the fitness app example: We’re testing with just 10 people!

Why so few?

• If your assumption is BADLY wrong, you’ll know it with just 10 people
• If it’s RIGHT, you’ll see clear signals even with 10 people
• It’s fast (weeks, not months)
• It’s cheap (minimal cost to test)

My rule: If you can’t validate your leap-of-faith assumption with 10-50 people, your assumption is probably wrong!

Example – E-commerce for Handmade Jewelry:

My client wanted to sell handmade jewelry online. Her leap-of-faith assumption: “People will buy handmade jewelry without seeing it in person.”

Our test:

• Posted 15 pieces on Instagram
• Offered free shipping for first 10 buyers
• Tracked: How many people bought? Did they return items?

Result: 8 people bought, zero returns! Assumption validated with just 8 sales!

Lesson: You don’t need 1,000 customers to validate a leap-of-faith assumption. Start with 10!

---

Common Mistakes When Identifying Leap-of-Faith Assumptions

Mistake 1: Testing Too Many Assumptions at Once

The problem: You can’t learn which assumption was wrong if you test them all together.

Solution: Test ONE leap-of-faith assumption at a time. Once validated, move to the next.

Mistake 2: Confusing “Nice to Have” with “Must Have”

The problem: Not all assumptions are equally critical.

Solution: Focus ONLY on assumptions that, if wrong, would kill your business.

Example: “Customers want blue buttons instead of green buttons” is NOT a leap-of-faith assumption. “Customers will pay for this solution” IS.

Mistake 3: Testing With the Wrong People

The problem: Asking friends and family for feedback leads to false positives.

Solution: Test with REAL potential customers who don’t know you and have no reason to be polite.

Mistake 4: Building Before Testing

The problem: Many founders build a full product FIRST, then try to validate assumptions.

Solution: Test your leap-of-faith assumptions BEFORE writing a single line of code!

---

Five Key Takeaways from Chapter 5

Takeaway 1: Identify Your Leap-of-Faith Assumptions Early

Every startup has assumptions that, if wrong, will cause the business to fail. Identify these FIRST before investing time and money.

Takeaway 2: Focus on the Value Hypothesis and Growth Hypothesis

These two assumptions are almost always the most critical: Does your product deliver value? Will it grow?

Takeaway 3: Test with Early Adopters, Not Average Customers

Early adopters feel the problem most acutely and are more forgiving of imperfect solutions. They’re your best source of honest feedback.

Takeaway 4: Use Analogs and Antilogs to Learn Faster

Study similar successes (analogs) and failures (antilogs) to understand what works and what doesn’t.

Takeaway 5: Test Assumptions Before Building

Don’t build a full product until you’ve validated your riskiest assumptions. Start small, test fast, learn quickly.

---

Action Plan: What To Do Right Now

Your Next Steps

Step 1: Write down all your business assumptions
Spend 30 minutes listing EVERY assumption your business depends on.

Step 2: Identify your top 3 leap-of-faith assumptions
Use the question: “If this assumption is wrong, does my business fail?”

Step 3: Research analogs and antilogs
Find 3 companies that succeeded with similar ideas and 3 that failed. Learn from both.

Step 4: Design a test for your riskiest assumption
Create the simplest possible experiment to validate or invalidate this assumption in the next 2 weeks.

Step 5: Find 10-20 early adopters
Identify where your early adopters hang out online and start engaging with them today.

“The lesson of the MVP is that any additional work beyond what was required to start learning is waste, no matter how important it might have seemed at the time.”

---

End of Chapter 5: Leap

Next up: Chapter 6: Test
We’ll dive into how to design and run effective MVP tests, measure what matters, and make data-driven decisions about your startup’s future.