Backlog and Priority
The point of prioritizing isn't to produce an absolutely correct order — it's to make every cut in line require a reason.
What you will run into
- 谁的声音大就先做谁的
- 池子里躺着几十条，越攒越不敢动
- 做完一版，发现基础的东西还缺着，花哨的先上了
Bucket with KANO First
Five categories — bucket first, then rank. Bucketing answers "should we do it at all"; ranking answers "which one first."
| 类型 | 有和没有的差别 | 例子与处理 |
|---|---|---|
| 必备型 | 有了不加分，没有会掉分 | 支付要安全、内容不能丢。缺一个就是事故，优先补齐 |
| 期望型 | 做得越好，满意度越高 | 导航的实时路况。资源允许就往上加，是竞争力所在 |
| 魅力型 | 有了惊喜，没有也不失望 | 播放器的歌词同步。每个版本挑一个，不要贪多 |
| 无差异 | 有没有都没人在意 | 阅读器的朗读功能。直接砍，别犹豫 |
| 逆向型 | 做了反而招人烦 | 自动把邮件标为已读。做了要挨骂 |
Then Apply the Scoring Formula
After bucketing, you still have to rank within each bucket. The value of this formula isn't the precise number — it's that it puts every relevant factor on the table.
Maintaining the Pool
- Every entry needs a source and the original context. Without these two columns, three months later you can't judge whether it should still be done, so it just stays forever.
- When the same item comes up a second time, add a counter. Count says more than the wording of a single mention, and it also blocks the illusion created by "one person keeps bringing up the same thing."
- Prune regularly, don't let it only grow. Once a month, archive entries nobody has mentioned in three months and that have no data behind them. The backlog's value is that it can be finished.
- What you cut, keep a record of. Write down clearly why you cut it at the time. Half a year later when someone brings up the same item, you can pull up last time's call instead of re-arguing from scratch.
When you're building solo, this table can shrink to five columns: need, source, scenario, bucket, status. Use whatever tool you like — the point is that every new entry fills these five cells, and anything that can't be filled isn't thought through yet, so don't queue it.