thedixitjain Lean Startup Methodology
A systematic approach to building startups and launching new products that shortens development cycles and rapidly discovers whether a business model is viable.
Core Principle
Entrepreneurship is a form of management. Success doesn't require a perfect plan or brilliant insight—it requires a systematic process for testing assumptions, learning from customers, and iterating rapidly. Most startups fail not because they couldn't build what they planned, but because they built the wrong thing: treat every plan as a set of hypotheses to falsify, and spend effort to eliminate waste and accelerate validated learning, not to execute a fixed roadmap.
Scoring
Goal: 10/10. Score a plan, experiment, or metric set by the five Quick Diagnostic rows—1 point each when the answer is yes, 2 points when it is also backed by evidence on the Validation Ladder (Level 3+):
- 9-10: every leap-of-faith assumption named and ranked by risk, the riskiest tested by a real MVP, actionable metrics defined, and explicit pivot criteria set before building.
- 5-6: a hypothesis and some MVP exist, but metrics are vanity or pivot criteria are undefined—decisions can't be made from the data.
- ≤3: waterfall thinking—building the full product first, asking customers what they want, or scaling before product/market fit.
State the current score and the lowest-scoring diagnostic row to fix next.
The Build-Measure-Learn Loop
The fundamental cycle: IDEAS → BUILD (product) → MEASURE (data) → LEARN (knowledge) → back to IDEAS.
Critical insight: Plan the loop backward:
- What do we want to learn? (hypothesis to test)
- How will we know if we learned it? (metrics)
- What's the minimum we can build? (MVP)
Goal: Minimize total time through the loop.
See references/build-measure-learn.md when planning an experiment—reverse-planning sequence, an experiment-design template, per-product-type loop examples, and the build/vanity-metric loop traps.
Validated Learning
Learning what customers really want through experiments on real behavior—not feature requests, surveys, or focus groups (people mispredict their own behavior). Measure what customers do, not what they say, and run experiments that could falsify your assumptions. Vanity wins (downloads, signups without engagement) are not learning.
The Validation Ladder:
| Level | Evidence | Strength |
|---|---|---|
| 1 | "I think customers want this" | Weakest (opinion) |
| 2 | "Customers said they want this" | Weak (stated preference) |
| 3 | "Customers signed up for early access" | Medium (low commitment) |
| 4 | "Customers paid a deposit" | Strong (real commitment) |
| 5 | "Customers are actively using it" | Strongest (revealed preference) |
Target: Level 4-5 before building at scale.
Minimum Viable Product (MVP)
The version of a new product that allows maximum validated learning with the least effort. Not a prototype (technical feasibility), not a beta (quality), not a minimum marketable product—a learning vehicle, often embarrassingly small and low quality, and usually much smaller than you think.
MVP Types:
| Type | What It Is | When to Use | Example |
|---|---|---|---|
| Concierge | Manual service pretending to be automated | Test if solution is valuable | Food on the Table (manual meal planning) |
| Wizard of Oz | Fake automation, manual backend | Test if automation is needed | Zappos (no inventory, bought shoes retail) |
| Smoke test | Landing page + signup, no product | Test demand before building | Dropbox video (explained concept, measured signups) |
| Single feature | One core feature only | Test which feature is most valuable | Twitter (just status updates) |
| Piecemeal | Combine existing tools | Test workflow before custom build | Groupon (WordPress + email) |
Design questions: What's the riskiest assumption? What's the minimum that tests it? How do we measure whether it was validated?
See references/mvp-design.md when choosing and sizing an MVP—seven types in depth, a type-selection decision matrix, lower/upper sizing bounds, and the MVP Design Canvas.
Leap-of-Faith Assumptions
The assumptions that, if wrong, will cause your business to fail. Identify them, prioritize by risk (which failure would be fatal?), and test the riskiest first—never in order of ease.
| Assumption Type | Question | Test Method |
|---|---|---|
| Value hypothesis | Do customers care about this problem? | Smoke test, concierge MVP |
| Growth hypothesis | How will customers discover us? | Channel tests, referral experiments |
| Retention hypothesis | Will customers come back? | Cohort analysis, engagement metrics |
| Monetization hypothesis | Will customers pay? | Pre-orders, pricing tests |
Example—Dropbox: Leap of faith: "people will download and use a file sync tool." Test: explainer video before building scale infrastructure. Result: beta list grew from 5,000 to 75,000 overnight—demand validated.
See references/assumptions.md when mapping and ranking assumptions—the Impact-Uncertainty matrix, a prioritization scoring template, test methods per assumption type, and industry-specific assumption lists.
Innovation Accounting
Measuring progress when traditional metrics fail: revenue and customers start at zero, and vanity metrics look good without driving decisions.
1. Establish the Baseline
Measure current reality precisely, even if it's zero or embarrassing: conversion funnel (signup → active → retained → paying), engagement (DAU/MAU, session length, features used), economics (CAC, LTV, churn).
2. Tune the Engine
Run experiments to improve baseline metrics: A/B test pricing ($9 vs. $19/mo), onboarding completion rates, acquisition channels (SEO vs. paid vs. referral). Each experiment targets a measurable improvement through validated learning.
3. Pivot or Persevere
When tuning stalls, make the evidence-based call (criteria and pivot types below in Pivot or Persevere).
See references/innovation-accounting.md when building the baseline dashboard—funnel, cohort, and economics metric frameworks.
Actionable vs. Vanity Metrics
Vanity metrics make you feel good but don't change behavior; actionable metrics drive decisions and clarify cause and effect.
| Vanity | Why It's Bad | Actionable Alternative |
|---|---|---|
| Total signups | Always goes up, no context | % signup → active (conversion rate) |
| Page views | Doesn't indicate value | Time on page, bounce rate |
| Total users | Includes inactive/churned | Active users (DAU, WAU, MAU) |
| Downloads | Doesn't mean usage | DAU/downloads (activation rate) |
| Revenue | Without context | Revenue per cohort, LTV/CAC |
Three characteristics of actionable metrics: actionable (clear cause-and-effect, reproducible), accessible (simple, understood by everyone), auditable (underlying data can be checked).
Example: Vanity: "We have 100,000 users!" Actionable: "Channel X users retain 2x better than channel Y—double down on X."
Cohort analysis: Group users by signup date and track behavior over time—the only way to see whether the product is actually improving.
See references/metrics.md when building a cohort table or choosing what to track—a five-step cohort walkthrough and AARRR (Pirate Metrics) aligned with Lean Startup stages.
Pivot or Persevere
A pivot is a structured course correction designed to test a new hypothesis about the product, strategy, or engine of growth.
Pivot when: experiments repeatedly fail to validate hypotheses, metrics stay flat despite iterations, customer feedback contradicts the vision, or progress is too slow for the runway. Persevere when: metrics are improving (even slowly), clear learning is happening, and adjustments move the right direction.
Pivot Types:
| Pivot Type | What Changes | Example |
|---|---|---|
| Zoom-in | Single feature becomes the whole product | Instagram (photo filters from Burbn) |
| Zoom-out | Product becomes a single feature | Flickr (photo-sharing from Game Neverending) |
| Customer segment | Same problem, different customer | Groupon (activism platform → local deals) |
| Customer need | Same customer, different problem | Potbelly (antique store → sandwiches) |
| Platform | App ↔ Platform | YouTube (dating site → video platform) |
| Business architecture | High margin/low volume ↔ low margin/high volume | Salesforce (software → SaaS) |
| Value capture | Monetization model change | Android (paid → free + app revenue) |
| Engine of growth | Viral, sticky, or paid model | Facebook (viral in colleges → paid advertising) |
| Channel | How you reach customers | Salesforce (direct sales → self-service) |
| Technology | Different technology, same solution | Apple (Intel → ARM chips) |
Cadence: Successful startups commonly pivot 1-5 times before product-market fit. Anti-pattern: "pivoting" without validating that the new direction solves the core problem.
See references/pivots.md when the data suggests a pivot—the data-driven pivot signals, a structured pivot-meeting agenda, leading indicators, and the Instagram/Slack/YouTube pivot stories.
The Three Engines of Growth
How a startup acquires and retains customers sustainably. Pick one engine, optimize it, then consider adding others—running multiple engines simultaneously dilutes focus and learning.
1. Sticky Engine of Growth
Retention-driven: growth rate = new customer acquisition rate − churn rate. Track churn rate, retention cohorts (30/60/90 days), and DAU/MAU. Fits SaaS, subscriptions, social networks. Strategy: improve the product until natural growth exceeds churn.
2. Viral Engine of Growth
Customers bring customers: viral coefficient = (% who invite) × (invites sent) × (% who join); above 1.0 means exponential, self-sustaining growth. Track the coefficient, viral cycle time, and referral attribution. Fits Dropbox, Hotmail, WhatsApp. Strategy: build virality into the product itself.
3. Paid Engine of Growth
Spend to acquire: requires LTV > CAC (target LTV/CAC > 3x). Track CAC, LTV, and payback period. Fits e-commerce and traditional businesses. Strategy: optimize until each customer's profit funds acquiring more.
See references/growth-engines.md when picking or tuning an engine—churn-reduction tactics, the K-factor and viral-loop design, LTV/CAC optimization, a channel-economics table, and the product-to-engine matching framework.
The Five Whys
Root cause analysis: when a problem occurs, ask "why?" five times, then invest proportionally at every level—not just the symptom.
Example—website went down:
- Why? Server ran out of memory
- Why? Memory leak in a new feature
- Why? Code wasn't reviewed for memory management
- Why? No code review process for infrastructure changes
- Why? Team is moving too fast to create processes
Proportional investments: fix the bug (1), add memory monitoring (2), implement code review (3-4), slow down to build quality processes (5). Anti-pattern: stopping at level 1.
See references/five-whys.md when facilitating a session—three worked examples (outage, churn spike, launch failure) and how to handle diverging chains, blame creep, and root causes outside your control.
Small Batches
Work in small batches for faster feedback loops, easier pivots, less waste when you're wrong, and faster time to market.
| Large Batch | Small Batch |
|---|---|
| Build entire product, then launch | Launch landing page, then build |
| Release quarterly | Release weekly or daily |
| Plan 12-month roadmap | Plan 6-week cycles |
| Big bang rewrite | Incremental refactoring |
Continuous deployment is the ultimate small batch: deploy every commit, catch bugs immediately, learn continuously, reduce risk per release.
See references/small-batches.md when setting up faster release cadence—the continuous-deployment pipeline and prerequisites, feature-flag types, a progressive-rollout checklist, and work-decomposition techniques.
Lean Startup Applied: From Idea to Scale
Phase 1—Problem/Solution Fit: validate that the problem exists and customers care, via customer discovery, smoke tests, and concierge MVPs. Metric: customers willing to pay or commit.
Phase 2—Product/Market Fit: build the MVP and iterate on usage data. Metric: high retention, organic growth, strong engagement.
Phase 3—Scale: optimize the growth engine and unit economics. Metric: sustainable, profitable growth. Anti-pattern: skipping Phases 1-2 and jumping straight to scale.
By context:
- SaaS startup: smoke test (landing page + email list) → concierge MVP with 10 customers → single-feature MVP → measure retention, NPS, feature usage → pivot or scale on cohort data
- Corporate innovation: separate innovation accounting from core-business metrics, shield teams from quarterly revenue pressure, unlock metered funding on validated-learning milestones
- Product features: deploy behind a feature flag → A/B test against core metrics → kill, iterate, or scale based on data
See references/applications.md for context-specific playbooks (SaaS, corporate innovation, features), and references/case-studies.md for the full Dropbox, IMVU, Zappos, and Groupon stories—including failures—when you want a worked precedent for the bet in front of you.
Common Mistakes
| Mistake | Why It Fails | Fix |
|---|---|---|
| Building too much | Waste before validation | Test with smoke test or concierge first |
| Asking customers | People don't know/mispredict | Observe behavior, not opinions |
| Vanity metrics | Feel-good numbers, no decisions | Track cohorts, conversion, retention |
| No hypothesis | Can't learn if you don't predict | Write hypothesis before each experiment |
| Pivot too slow | Waste runway | Set clear pivot criteria upfront |
| Skip innovation accounting | Can't tell if you're improving | Establish baseline, measure tuning efforts |
| Premature scale optimization | Polishing before product-market fit | Validate learning first; quality follows evidence |
Quick Diagnostic
Audit any product development plan:
| Question | If No | Action |
|---|---|---|
| What's the riskiest assumption? | Building on shaky ground | Map leap-of-faith assumptions |
| How will you test it? | You're guessing | Design MVP to test the assumption |
| What metric will validate/invalidate? | You won't learn | Define actionable metrics |
| Can you test with less than this? | Over-building | Shrink the MVP further |
| What will you do if the experiment fails? | No pivot criteria | Define pivot triggers upfront |
Further Reading
For the complete framework, research, and case studies:
- "The Lean Startup" by Eric Ries
- "The Startup Way" by Eric Ries (applying Lean Startup to established companies)
About the Author
Eric Ries is an entrepreneur and author who developed the Lean Startup methodology as co-founder and CTO of IMVU, where he pioneered the continuous deployment and customer development practices behind it. The Lean Startup has been translated into over 30 languages and shaped startup culture worldwide. He later created the Long-Term Stock Exchange (LTSE).
Source: jeremylongshore/claude-code-plugins-plus-skills → plugins/productivity/wondelai-lean-startup/SKILL.md