Works, Usable, Used
Validation comes in three layers. Each layer answers a different question and uses different methods. Mix them together and you validate nothing clearly.
What you'll run into
- 上线了，但不知道该看哪个数，只能看每天有多少人打开
- 数据不好，说不清是功能有 bug、体验太绕，还是根本没人需要
- 验收全靠自己点几下，点的还都是自己熟悉的那条路
What to look at in each layer
| 层 | 要回答 | 怎么验 | 不通过的表现 |
|---|---|---|---|
| 能用 | 功能对不对，异常情况会不会崩 | 走查清单、真实数据压测、安全检查 | 白屏、报错、数据丢失 |
| 好用 | 陌生人能不能自己走完 | 五秒测试、找三五个人试用并观察 | 他卡在某一步、需要你在旁边解释 |
| 有人用 | 他们会不会回来、愿不愿意付钱 | 埋点、留存曲线、转化漏斗 | 用了一次再也不来 |
The order can't be shuffled
The three layers are dependent. If the lower layer doesn't hold, the upper layer's conclusion is meaningless.
- If it doesn't pass "works," don't look at retention. If it crashes mid-flow, low retention is guaranteed — it has nothing to do with whether the need is real.
- If it doesn't pass "usable," don't rush to drive traffic. Pulling people in only to lose them at step two is paying for churn.
- If "someone uses it" doesn't hold, the first two layers being polished is wasted effort. Something nobody needs, no matter how smooth, won't bring anyone back.
- But the order you discover things is often reversed. Bad numbers → find someone to try it → a step doesn't work → dig into the code and find a bug. So you need to be able to work all three layers.
How to do it solo
| 时机 | 做什么 |
|---|---|
| 写完一个功能 | 对着状态清单逐条过；用零条数据和超长内容各跑一遍 |
| 上线前 | 走查清单全过一遍，含安全那几条；用全新账号完整走一次 |
| 上线时 | 埋点必须已经在了。没埋点的功能，上线等于没上 |
| 上线后第一周 | 找三五个真实用户看他们怎么用，别在旁边指导 |
| 上线后一个月 | 看留存曲线走不走平，这决定了要不要继续投入 |