lean-startup

name	lean-startup
description	Design MVPs, validated learning experiments, and pivot-or-persevere decisions using Build-Measure-Learn. Use when the user mentions "MVP scope", "validated learning", "pivot or persevere", "vanity metrics", or "test assumptions". Covers innovation accounting and actionable metrics. For 5-day prototype testing, see design-sprint. For customer motivation analysis, see jobs-to-be-done. Trigger with 'lean', 'startup'.
allowed-tools	Read, Glob, Grep
license	MIT
author	Wondelai <[e-mail]>
version	1.0.1
compatible-with	claude-code, codex, openclaw
tags	["productivity","testing","lean-startup"]

Lean Startup Methodology

A systematic approach to building startups and launching new products that shortens development cycles and rapidly discovers if 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.

The foundation: Most startups fail not because they couldn't build what they planned, but because they built the wrong thing. The Lean Startup methodology applies scientific experimentation to eliminate waste and accelerate validated learning.

Scoring

Goal: 10/10. When reviewing or creating product development plans, experiments, or metrics, rate them 0-10 based on adherence to Lean Startup principles. A 10/10 means full application of Build-Measure-Learn, validated learning, and evidence-based decisions; lower scores indicate waterfall thinking or waste. Always provide the current score and specific improvements needed to reach 10/10.

The Build-Measure-Learn Loop

The fundamental cycle of Lean Startup:

     IDEAS
       ↓
    BUILD → Product
       ↓
    MEASURE → Data
       ↓
    LEARN → Knowledge
       ↓
    (back to IDEAS)

Critical insight: The loop is actually backward. Start with what you want to learn, determine metrics that will inform that learning, then build the minimum product to collect those metrics.

Reverse planning:

1. What do we want to learn? (hypothesis to test)
2. How will we know if we learned it? (metrics)
3. What's the minimum we can build? (MVP)

Goal: Minimize total time through the loop.

See: references/build-measure-learn.md for detailed loop execution.

Validated Learning

Definition: Learning what customers really want through validated experiments, not opinion or anecdotes.

Validated learning is not:

• Building features customers request (they don't know what they want)
• Achieving vanity metrics (downloads, signups without engagement)
• Doing surveys or focus groups (people lie/mispredict behavior)

Validated learning is:

• Testing hypotheses with real behavior
• Measuring what customers do, not what they say