故事 · Alan Cooper 与一个叫 Kathy 的人
Origin Story · Alan Cooper and a Woman Named Kathy
1980 年代,软件设计师 Alan Cooper(后被称为「Visual Basic 之父」)在做一款项目管理软件时,
发现团队一谈「用户」就吵成一团 —— 因为每个人脑子里的「用户」都不一样。他索性虚构了一个真人:
一位叫 Kathy 的项目经理,给她设定了具体的工作、习惯和烦恼。神奇的事发生了:从此争论不再是「用户想要 X」,
而是「Kathy 在那种情况下会怎么做」—— 抽象的需求一下子有了血肉,决策快且不跑偏。
这就是 Persona 的诞生。它的洞见是:人类对一个具体的人能产生共情,对一个统计平均值不能。
把「25–45 岁、中等收入的女性用户」换成「35 岁、每天接送孩子、怕给孩子吃添加剂的小李」,
整个团队的设计直觉,就被悄悄校准到了同一个人身上。
In the 1980s, software designer Alan Cooper — later called "the father of Visual Basic" —
was building a project-management tool when he noticed that the moment his team said the word "the user," they started arguing,
because every person in the room pictured someone different. So he invented a single, specific human:
Kathy, a project manager, with a concrete job, daily habits, and her own annoyances. Something quietly magical happened:
the debates stopped being "users want X" and became "what would Kathy do in that situation?"
Abstract requirements grew flesh and bone, and decisions got faster and straighter. That was the birth of the persona.
The insight: humans can feel empathy for a specific person; we cannot feel empathy for a statistical average.
Replace "women aged 25–45 with mid-tier income" with "Mei, 35, drops the kids off every morning, terrified of artificial additives,"
and the team's design intuition is quietly calibrated to the very same human.
1 人物画像卡 The Persona Card
点左侧维度高亮2 拿画像当裁判:这个功能该做吗 The Persona as Referee: Should We Ship This?
待检验的设计决策Design decision on trial
点「用这张卡检验一个决策」。
Tap "Stress-test a decision with this card."
小李会怎么说
让画像替你回答「她会用吗」。
Let the persona answer "would she actually use it?" for you.
3 现实里的人物画像 Personas in the Real World
用户画像:给抽象用户一个名字、照片、故事,团队对一个具体的人才能产生共情与一致认知。
User archetype: give the abstract user a name, a face, a story — only then can the whole team feel empathy and share a single mental model of who they're building for.
目标用户聚焦:一个产品聚焦一到三个核心 Persona,宁可服务好一类人,也别讨好所有人。
Focus the target: pick one to three primary personas per product. Better to serve one group brilliantly than to flatter everyone.
避免大众化:「为所有人」会稀释每个决策;锁定具体人,产品才有锋利的个性与卖点。
Avoid the mass-market trap: "for everyone" dilutes every decision. Lock onto a specific person and the product gains a sharp personality and a real reason to exist.
决策检验:争论功能时问「Persona 会用吗」,把口味之争变成可裁决的事实之问。
Stress-test decisions: when a feature debate stalls, ask "would the persona actually use this?" That turns a taste fight into a question that can be answered.
一句话In One Line
团队设计时最隐蔽的灾难,是每个人脑子里的「用户」都不一样:产品经理想的是年轻白领,
工程师默认是技术达人,老板惦记着付费大客户 —— 嘴上说着同一个词,做出的决定却各拉各的方向。
Persona 的本质,是给所有人发一张同一张脸:从此「用户」不再是抽象名词,而是那个有名有姓的小李。
它最大的价值不在「描述用户」,而在充当一个可被反复追问的裁判 —— 任何功能、文案、流程,
都得过一遍「小李会不会用、看不看得懂、用得爽不爽」。
但记住:Persona 必须来自真实的用户研究,不能是团队一拍脑袋编出来的人 —— 否则你只是在为一个幻觉精心设计。
The most invisible disaster on a design team is that every person has a different "user" in their head:
the PM pictures young urban professionals, engineering defaults to power users, the CEO is thinking about the big paying account.
Everyone says the same word; everyone is pulling in a different direction.
A persona quietly hands everyone the same face — "the user" is no longer an abstract noun, it's Mei, with a name and a story.
Its biggest value isn't "describing the user" but acting as a referee you can interrogate again and again —
every feature, every line of copy, every flow has to pass "would Mei use it, understand it, enjoy it?"
But remember: a persona must come from real user research, not from a group brainstorm — otherwise you're just lovingly designing for a hallucination.
常见误用Common Mistakes
拍脑袋编 Persona,没有任何用户研究支撑。必须基于真实访谈与数据,否则是在为幻觉设计。
Inventing a persona off the top of your head, with zero user research behind it. Ground it in real interviews and data — otherwise you're just designing for a hallucination.
一口气做十几个 Persona,等于又回到「为所有人」。聚焦一到三个主画像,其余作次要参考。
Cranking out a dozen personas at once — that's just "designing for everyone" with extra steps. Focus on one to three primary personas, treat the rest as secondary references.
画完卡片就锁进文件夹吃灰。让它进每一次评审,真拿来检验决策才有意义。
Finishing the card and filing it away forever. Bring it into every review and actually use it to stress-test decisions — that's the only place its value lives.