Kacam.net

Product design

新手引导该怎么做

一个新用户做了什么之后,你就基本确定他会留下来?

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.

答「让用户熟悉产品」会被追问「熟悉到什么程度算够、拿什么衡量」。引导的目的不是介绍功能,是让人尽快拿到第一次价值。

所以第一步是定义那个具体的、可测量的行为,然后量它:从注册到那一步要几步、中位数多久、每一步掉多少人。这三个数没测过,就不知道引导要优化什么。

还有一问它不会放过:能不能不做引导,靠界面本身让人会用? 引导常常是在给糟糕的信息架构打补丁。

★★★☆☆ · about 35 min · Tests: aha moment、到价值的时间、每一步掉多少人、引导不是教程

What this one tests

Funnels and retention Metric design 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.