idea-validation

在投入时间或金钱之前验证商业想法。每当个体企业家有一个原始想法并需要一个结构化流程来根据现实对其进行压力测试时，就可以使用它——涵盖问题定义、需求证据、竞争环境、客户发现、风险最大的假设测试以及评分的通过/不通过决策。触发诸如“验证我的想法”、“这个想法是否值得构建”、“我应该追求这个”、“测试我的商业想法”、“这个想法有效吗”等短语。

## 概述（中文）

在投入时间或金钱之前验证商业想法。每当个体企业家有一个原始想法并需要一个结构化流程来根据现实对其进行压力测试时，就可以使用它——涵盖问题定义、需求证据、竞争环境、客户发现、风险最大的假设测试以及评分的通过/不通过决策。触发诸如“验证我的想法”、“这个想法是否值得构建”、“我应该追求这个”、“测试我的商业想法”、“这个想法有效吗”等短语。

## 原文

# Idea Validation

## Overview
Kill bad ideas fast, confirm good ones cheaply. Walk through every phase in order. Each phase has a kill-check — if the idea fails, document why and stop before wasting further time.

---

## Phase 1: Problem Definition

Everything starts here. A vague problem = a vague business.

**Answer these four questions precisely:**

1. **Who** — The exact person. Not "small businesses." Something like "freelance graphic designers juggling 3-8 client projects at once."
2. **What** — The specific painful moment. "They spend 4+ hours/week manually exporting deliverables and coordinating revision feedback via email chains."
3. **Why it hurts** — The real cost: time lost, revenue lost, stress, missed deadlines, damaged relationships. Quantify where possible.
4. **What they do now** — Their current workaround. This IS your real competition — not just competitor apps, but the status quo itself.

**Kill check:** Cannot answer all four concretely → problem is not well-defined. Do more discovery first.

---

## Phase 2: Demand Signal Gathering

Prove real people care. Do not rely on assumptions or polite friends.

**Check 3+ of these signal sources:**

| Signal | Where | Positive Signal |
|---|---|---|
| Search volume | Google Trends, Ubersuggest free | Stable or growing volume on core problem keywords |
| Forum pain | Reddit, HN, Slack/Discord | Threads with 10+ comments describing this exact pain |
| Existing tool gaps | G2, App Store reviews | Tools solving adjacent problems with reviews citing the gap you'd fill |
| Job postings | LinkedIn, Indeed | Roles that exist only because this problem is expensive to solve manually |
| Social venting | Twitter/X search, LinkedIn | People publicly complaining about this unprompted |

**Kill check:** Fewer than 3 positive signals → problem may not be painful enough. Pivot or kill.

---

## Phase 3: Solution Fit Check

Pressure-test whether your proposed solution actually solves the problem well enough to build a business on.

1. **10x rule:** Is your solution 10x better (not 10%) than the current workaround in speed, cost, ease, or quality? Marginally better won't make people switch.
2. **Workflow change audit:** Map exactly what the user must change in their current routine. High friction = low adoption.
3. **Solo-build feasibility:** Can a working MVP be built by one person in weeks-to-a-few-months? If it needs a 10-person engineering team, that's a different company.
4. **Unfair advantage:** Why you specifically? Skills, industry access, data, network, credibility — something competitors can't easily replicate.

**Kill check:** Fail the 10x rule or have zero unfair advantage → move on.

---

## Phase 4: Customer Discovery (Talk to Humans)

10-15 conversations with real potential customers. Non-negotiable. No amount of desk research replaces this.

**Finding people:**
- Post in 2-3 relevant communities asking for 15-min feedback chats.
- DM matching personas on LinkedIn or Twitter.
- Offer a small incentive if needed (gift card, free future access).

**Conversation flow (15-20 min):**

```
1. CONTEXT (2 min)
   "Tell me about your work. Walk me through a typical week
    around [problem area]."
   → Listen only. Do NOT pitch or explain your idea.

2. PAIN EXPLORATION (5 min)
   "What's the most frustrating part of [workflow]?"
   "How often does that come up?"
   "What have you already tried to fix it?"
   "What's still missing?"
   → Ask "why" and "what happens when" repeatedly. Dig.

3. OUTCOME PROBING (3 min)
   "If a tool could [describe the outcome, not your feature set],
    how would that change things?"
   "What would that be worth — in time, money, stress?"
   → Let them quantify. Never suggest a number first.

4. WILLINGNESS TO PAY (2 min)
   "Would you pay for something like that? What range feels fair?"
   → Discount stated numbers by ~50% when planning.

5. WARM REFERRAL (1 min)
   "Know anyone else who hits this same wall? Mind if I reach out?"
```

**Track across all conversations:**
- % who described the problem without prompting (pain signal)
- % currently spending real money or time on workarounds (revenue signal)
- % with clear willingness to pay (demand signal)
- Features multiple people independently requested (product signal)
- Assumptions you held that conversations proved wrong (kill features early)

**Kill check:** Fewer than 60% confirm pain + willingness to pay → rework or kill.

---

## Phase 5: Riskiest Assumption Test (RAT)

One assumption, if wrong, kills everything. Find it. Test it in under 2 weeks and $200.

**Common riskiest assumptions and cheap tests:**

| Assumption | Minimum Test | Pass Threshold |
|---|---|---|
| People will pay | Landing page + "pre-order" button. Drive 200 targeted visitors. | 3-5% convert to payment/deposit |
| CAC is affordable | Run $100 targeted ad campaign. Measure cost-per-lead. | CPL < 20% of planned customer lifetime value |
| People will change workflow | Offer a manual version of the service to 5 people for free. See if they actually use it. | 3+ out of 5 use it consistently |
| I can build it solo | Build the single hardest technical feature as a prototype first. | Working prototype in ≤ 2 weeks |

**Process:**
1. State the assumption.
2. Define what "confirmed" looks like (a concrete, measurable number).
3. Design the cheapest possible test.
4. Set a hard deadline (max 2 weeks).
5. Run it. Record results with zero spin.

**Kill check:** RAT fails → idea in current form is not viable. Pivot the solution, the customer, or the model — or kill entirely.

---

## Phase 6: Go / No-Go Scorecard

| Dimension | Score (1-5) | Weight |
|---|---|---|
| Problem severity & clarity | __ | 20% |
| Demand evidence gathered | __ | 15% |
| Customer discovery confirmation | __ | 20% |
| Solution fit (10x + feasibility) | __ | 15% |
| RAT result | __ | 20% |
| Your unfair advantage | __ | 10% |

**Weighted score = Σ (score × weight)**

- **4.0–5.0 → GO.** Move to MVP planning + business model canvas.
- **3.0–3.9 → CONDITIONAL GO.** Resolve the weakest dimension with one more test round first.
- **< 3.0 → NO-GO.** Kill or fundamentally pivot. Write down lessons.

---

## Meta-Rules
- Document everything in one "Idea Validation" doc — it becomes raw material for your business plan.
- Time-box the whole process: 2-3 weeks max. Validation paralysis is a real trap.
- Run 2-3 ideas in parallel when possible. Comparing sharpens judgment.

---

## 中文说明

# 想法验证

## 概述
快速扼杀糟糕的想法，廉价地确认好的想法。按顺序走完每个阶段。每个阶段都有一个“扼杀检查”——如果想法失败，记录原因并停下，以免进一步浪费时间。

---

## 阶段 1：问题定义

一切从这里开始。模糊的问题 = 模糊的业务。

**精确地回答这四个问题：**

1. **谁** — 确切的那个人。不是“小企业”。而是类似“同时兼顾 3-8 个客户项目的自由职业平面设计师”。
2. **什么** — 具体的痛点时刻。“他们每周花 4 个多小时手动导出交付物，并通过邮件往来协调修改反馈。”
3. **为什么痛** — 真实的代价：损失的时间、损失的收入、压力、错过的截止日期、受损的关系。尽可能量化。
4. **他们现在怎么做** — 他们目前的变通办法。这才是你真正的竞争对手——不只是竞品应用，而是现状本身。

**扼杀检查：** 无法具体回答全部四个问题 → 问题定义不清。先做更多发现工作。

---

## 阶段 2：需求信号收集

证明真实的人在乎。不要依赖假设或客气的朋友。

**检查这些信号来源中的 3 个以上：**

| 信号 | 在哪里 | 正面信号 |
|---|---|---|
| 搜索量 | Google Trends、Ubersuggest 免费版 | 核心问题关键词的搜索量稳定或在增长 |
| 论坛痛点 | Reddit、HN、Slack/Discord | 有 10 条以上评论描述这一确切痛点的帖子 |
| 现有工具的空缺 | G2、App Store 评论 | 解决相邻问题的工具，其评论提及你将填补的空缺 |
| 招聘启事 | LinkedIn、Indeed | 仅因为手动解决此问题代价高昂才存在的岗位 |
| 社交吐槽 | Twitter/X 搜索、LinkedIn | 人们在无人提示下公开抱怨此事 |

**扼杀检查：** 正面信号少于 3 个 → 问题可能不够痛。转向或扼杀。

---

## 阶段 3：解决方案契合度检查

压力测试你提出的解决方案是否真的把问题解决得足够好，足以以此建立一项业务。

1. **10 倍法则：** 在速度、成本、易用性或质量上，你的解决方案是否比当前的变通办法好 10 倍（而非 10%）？仅仅略好不会让人们切换。
2. **工作流程变更审计：** 准确地梳理出用户必须在其当前惯例中改变什么。高摩擦 = 低采用。
3. **单人构建可行性：** 一个可用的 MVP 能否由一个人在几周到几个月内构建出来？如果它需要一个 10 人的工程团队，那是另一家公司。
4. **不公平优势：** 为什么偏偏是你？技能、行业渠道、数据、人脉、信誉——某种竞争对手不易复制的东西。

**扼杀检查：** 未通过 10 倍法则，或毫无不公平优势 → 放弃，去做别的。

---

## 阶段 4：客户发现（与真人交谈）

与 10-15 位真实的潜在客户交谈。没有商量余地。再多的案头研究都无法替代它。

**找人：**
- 在 2-3 个相关社区发帖，征求 15 分钟的反馈交流。
- 在 LinkedIn 或 Twitter 上私信匹配的人物画像。
- 如有需