The single main thread
A product can do only one thing outstandingly well. Pick it, and demote everything else to "good enough."
What you'll run into
- 功能不少，但用户说不出你比别人强在哪
- 每个模块都做了一半，哪个都不够好
- 做新功能时不知道该投多少精力，全凭当时的心情
Resources are fixed, and so is attention. Spread your effort across five directions and you get five things that just barely pass — and nobody recommends a product that just passes. The point of a main thread is to give you a legitimate reason to do "good enough" on the other four.
How to find the main thread
| 从这里找 | 具体怎么问 |
|---|---|
| 用户重复最多的动作 | 他一天里在你这儿做得最频繁的那一步是什么 |
| 他会跟人提起的那句 | 如果他向朋友推荐，他会说这个东西「能怎么怎么」 |
| 砍掉之后产品就死了的 | 逐个假设砍掉某功能，哪一个砍了整个产品就不成立 |
| 你能做到最好的那件 | 在众多方向里，哪一件是你比同类做得明显好的 |
How to split the resources
A rough but useful ratio: the main thread takes 70%; the other four directions split the remaining 30%.
主线打磨到出彩
配角
配角
配角
配角
How to hold the line
- Every new feature has to answer one question: does it strengthen the main thread, or dilute it? The diluting ones aren't off-limits, but they go to the back of the line.
- The homepage serves only the main thread. What you put on the homepage is your public statement of what the main thread is (see one screen, one job).
- The main thread experience has to be clearly better than peers, not slightly better. A little better doesn't move anyone; it usually has to be better enough that the user feels it at a glance.
- The main thread can be swapped, but only one at a time. If you picked wrong, switch wholesale — don't end up defending two at once.