lean-product

# Lean Product Validation (独立开发方法论) ## Overview A methodology for solopreneur product development centered on validation speed, scene verification, and minimum action units. The core insight: in the AI era, the bottleneck shifts from "can I execute" to "do I want this" — execution friction disappears, so purpose becomes the real constraint. ## Core Model ### MVP: Art vs Way (术与道) **The Art (术) — How to do it right:** - Use minimum cost to verify maximum uncertainty - Identify the most important part AND the most uncertain part - Structured validation: funnel analysis, event tracking, user behavior data - Tools like PostHog for tracking conversion funnels (signup → create → share) **The Way (道) — How to do the right thing:** 1. **Reverse thinking**: Start from the end goal, work backwards 2. **Hit the core spark**: Not the derivation steps, but the thing that makes users "glimpse the future" and go crazy 3. **Top creators lead with intuition**: Jobs' "people don't know what they want until you show them" — product aesthetic sense over pure user feedback ### Scene Verification (场景验证) - **Must test in daily use context**, not as hypothetical discussion - Talk-testing (口嗨) is worthless — only embedded daily usage reveals truth - Run the basic link, verify the minimum action unit repeatedly ### Minimum Action Unit (最小行动单元) - Obsession with the smallest repeatable validation loop - Get feedback early, iterate fast - Perfectionism is fear of feedback in disguise ### Front-end Primacy in AI Era - Backend simplified by AI models and SaaS/PaaS - Frontend is closest to user, best for MVP closure - Stack: Next.js / Tailwind / Firebase / Vercel for full-stack delivery ## When to Apply - Starting a new product or feature - Validating whether a problem is worth solving - Deciding between building more vs. shipping faster - Choosing between user feedback and creator intuition - Estimating when to add i18n, analytics, or other non-core features ## Key Principles 1. **Minimum cost, maximum uncertainty reduction** — every action should reduce the biggest unknown 2. **Scene verification over talk-testing** — embed in daily use, not hypothetical discussion 3. **Iterate fast** — one week of three experiments beats six months polishing one idea 4. **Perfectionism = fear disguised** — ship and learn 5. **Creator's intuition matters** — over-relying on user feedback traps you in incremental iteration 6. **"Why build this" > "How to build this"** — purpose increasingly dominates method ## Cognitive Evolution - **2025-03**: Emphasis on MVP, validation speed, tech stack choices — tactical methodology - **2026-02**: Product development understood as meaning production and self-shaping, not just business action The key shift: from "how to build good products" to "why build this product" — the question of purpose intersects with life meaning. ## Related Skills - `ai_native_workflow`: AI is the execution layer rewriting indie dev methodology - `meaning_architecture`: Building products is also producing meaning and shaping the self - `systematization_experience`: Beware of turning product development into pure system optimization