Kacam.net

Product design

下线一个功能

还有 1200 人在用,你怎么下线它?

Copy the prompt, then pick a model. It plays the interviewer and asks you through it scene by scene instead of handing you the answer.

On a phone with the app installed, the system opens the app directly. Links cannot open external apps inside WeChat — open it in a browser first.

The copied text ends with the answer key the model grades you against. Don't read it yourself first — working it out on your own is the point.

做减法比做加法更需要设计,但几乎没人练过。

「才 1200 人,直接下」是最常见的答案,而它跳过了这一份最重要的一问:有没有一群人,这个功能就是他们留在这儿的唯一理由? 找出这批人的办法也要说得出来。

它还会逼一个很多人没想过的对比:「留着不维护」这个选项的代价,通常比下线更贵。

★★★☆☆ · about 35 min · Tests: 谁在用、迁移路径、沟通时间线、哪几步不可逆

What this one tests

Trade-offs and costs Persuading people Evidence and numbers

Have you done this one?

Sign in to mark this one as practised — next time you come back you'll see when you did it.

Notes from people who did this one

Nobody has written yet. After you run it, say what came out of the conversation — which scene stumped you, which conclusion you changed afterwards.

Sign in to write a note.

How to use this

There is no model answer here — but there are definite wrong answers. Only three things make a case hold up, and every prompt's answer key carries a "common wrong answers" section that is more useful than the checklist itself.

The three things that make it hold up

  1. You can say whose problem this is and what it is — **with evidence** (not "I think users would want it")
  2. You can say what success looks like — **and what that number is today** (no baseline, no acceptance criteria)
  3. You can name the cost and what you gave up — **the hardest one to fake**, which is why every prompt hunts for it

How to start

  1. Pick a question, open it, copy the prompt.
  2. Paste it into a brand-new conversation — not one where you already discussed it.
  3. Say nothing. Wait for its first question.

Four commands you can call out at any time

  • 跳过 move to the next scene now
  • 提示 give a direction, not the answer
  • 直说吧 spell this point out in full, then keep pressing on the trade-offs
  • 复盘 jump to the wrap-up and print the review card

Three traps

  • Don't rush to a solution. More than half the lost points here come from designing before asking — especially describing features before defining what success means.
  • Expect to be pushed for numbers. "It'll perform better", "users will like it" get cut off: which metric, what is it today, and when do you look?
  • When it starts praising you, point it back to rule five — feeling validated crowds out noticing what you missed.

Start with the north star metric; it underpins everything else. Then pick by what's on your plate: a backlog you can't order → prioritisation; nobody using it or retention sliding → retention and onboarding; need to price something → pricing. Save the experiment review for later, and keep redoing the one about turning a one-line request into a spec — it's the closest to daily work.