故事 · 「太重了」三个字
Origin Story · The Words "Too Heavy"
一个工程团队收到客户反馈:「这破玩意太重了,根本拿不动!」有人当场就想:那就减重呗。
可「太重」到底多重才算?是单手拿不动,还是装进背包压肩?是整机重,还是某个部件重?
直接照搬「减重」,做完客户照样可能不满意。需求转化逼你追问:去掉情绪「破玩意/太」,
去掉隐含方案,留下真实需要 —— 「用户能单手长时间握持而不疲劳」,再量化成「整机重量 < 1.5 kg」。
这才是能写进规格、能验收、能驱动设计的需求陈述。客户之声是线索,需求陈述才是目标。
An engineering team gets a customer report: "This thing is way too heavy — I can barely lift it!" Someone immediately thinks, "Fine, we'll cut weight."
But how heavy is "too heavy," really? Too heavy to lift one-handed? Too heavy on the shoulder when stuffed in a backpack? Is it the whole product, or one specific part?
Run with "cut weight" verbatim and the customer can still end up unhappy. Need transformation forces the harder questions: strip the emotion ("this thing," "way too…"),
strip the implied solution, keep the real need — "the user can comfortably hold the device one-handed for an extended period" — then quantify it as "total weight < 1.5 kg".
That is something you can put in a spec, verify, and design against. The voice of the customer is a clue; the need statement is the target.
1 原话 → 转化器 → 需求陈述 Raw Quote → Transformer → Need Statement
点原话 / 转化2 这一句:去掉了什么 × 留下了什么 For This Quote: What Got Stripped × What Was Kept
去掉(情绪 / 方案)
Stripped (emotion / proposed solution)
留下(真实需要 · 可衡量)
Kept (real need · measurable)
3 现实里的需求转化 Need Transformation in the Real World
需求陈述:把客户之声改写成「谁,在什么场景,需要什么」的中性句式,去掉情绪与抱怨。
Need statement: rewrite the voice of the customer into a neutral "who, in what situation, needs what" form — emotion and complaint stripped out.
去方案化:客户给的「加个按钮」是方案,要还原成它想解决的需求,别让方案锁死设计空间。
De-solutioning: "add a button" is the customer's solution. Roll it back to the underlying need so you don't lock the design space prematurely.
可衡量需求:「快一点」无法验收,「响应 < 200ms」才能。需求必须能被测量与确认。
Measurable needs: "make it faster" can't be verified; "response < 200 ms" can. A requirement has to be measurable — otherwise no one can sign off on it.
CTQ 转化:转化后的需求继续往下落,就变成关键质量特性(CTQ)与可量化的设计指标。
Down to CTQ: the transformed need keeps cascading down into Critical-to-Quality characteristics and quantitative design targets.
一句话In One Line
客户原话里混着三样东西:情绪(破玩意、烦死了)、方案(加个按钮、做大一点)、
和真正值钱的真实需要。需求转化就是一道提纯:滤掉情绪(它只告诉你痛点有多痛),
还原方案(别被客户的解法绑架),把真实需要写成中性、无方案、可衡量的陈述。
可衡量尤其关键 —— 不能验收的需求等于没需求,会在评审、测试、量产时反复扯皮。
记住:你是在「翻译」客户,不是在「照抄」客户。译得准,后面整条设计链才不会跑偏。
Any raw customer quote is three things mixed together: emotion ("this thing," "I'm so done"), a proposed solution ("add a button," "make it bigger"),
and the actually valuable part — the underlying need. Need transformation is a purification step: filter out the emotion (it only tells you how much the pain hurts),
roll back the solution (don't let the customer's fix hijack your design space), and rewrite the real need as a statement that is neutral, solution-free, and measurable.
That last word matters most — a requirement no one can verify is no requirement at all; it just sparks endless arguments in review, in test, and in production.
Remember: you are translating the customer, not transcribing them. Translate well and the rest of the design chain stays on track.
常见误用Common Mistakes
把客户的抱怨原话直接写进规格(「太重了」)。去情绪、量化成可验收的指标(重量 < 1.5 kg)。
Pasting the raw complaint into the spec ("too heavy"). Strip the emotion and quantify into a verifiable target (weight < 1.5 kg).
照搬客户给的方案当需求(「加个按钮」)。还原它要解决的真实需要,再开放方案空间。
Adopting the customer's proposed solution as the requirement ("add a button"). Roll it back to the underlying need, then reopen the solution space.
需求写得模糊、无法衡量(「更好用」)。加上可测量的标准,否则验收时各执一词。
Writing the requirement in vague, unmeasurable terms ("easier to use"). Attach a measurable criterion — otherwise everyone interprets it differently at acceptance.