故事 · 那匹「更快的马」 Story · That "Faster Horse"
有句流传很广的话(常被安到福特头上):「如果我去问客户想要什么,他们会说想要一匹更快的马。」 这句话常被误读成「别听客户的」 —— 大错特错。它真正的意思是:客户给的是「字面方案」,不是「真实需求」。 「更快的马」背后的需求,是更快、更省力地到达目的地。读懂了这层,你才会去造汽车。 VOC 的全部功夫,就在于既要认真听客户的原话,又不能停在原话上 —— 要把它一层层提纯,翻译成可设计的真实需求。听话,得听音。 There is a widely quoted line (often pinned on Henry Ford): "If I had asked people what they wanted, they would have said a faster horse." It gets misread as "ignore the customer" — wrong. The real point is this: customers hand you a literal solution, not the underlying need. Behind "a faster horse" is the need to get there faster and with less effort. Read that layer and you build a car. All the craft of VOC sits exactly there: listen seriously to the literal words, but do not stop at the words — refine them layer by layer into a need you can actually design against. Hear the meaning, not just the words.

1 VOC 五步漏斗:从一堆原话到几条真需求 The VOC Five-Step Funnel: From a Pile of Quotes to a Few Real Needs

点击任意步骤click any step

漏斗从上到下越来越窄 —— 大量杂乱的客户原话,经过收集、整理、转译、排序、验证,被逐层提纯成少数几条经过确认的真实需求。点击任意一步,看它具体怎么做、容易栽在哪。 The funnel narrows top to bottom — a flood of raw customer quotes goes through collect, sort, translate, prioritize, and verify, and gets refined into a handful of confirmed real needs. Click any step for what to do and where teams trip.

2 这一步:怎么做 × 别踩坑 This Step: How to Do It × Where Teams Trip

怎么做How to do it
点上方步骤查看。Click a step above to see.
常见陷阱Common pitfalls
点上方步骤查看。Click a step above to see.

3 现实里的 VOC VOC in the Real World

需求采集:访谈、观察、客诉、评论 —— 多渠道收集第一手原话,越原始越好,先别急着加工。 Need collection: interviews, observation, complaints, reviews — pull first-hand quotes from many channels. The rawer the better; do not polish them yet.
原话转译:把「要更快的马」翻成「更快到达」 —— 抓住背后的真实需求,而非字面方案。 Quote translation: turn "I want a faster horse" into "I want to get there faster" — grab the underlying need, not the literal solution.
Kano 排序:用 Kano、重要度对需求排优先级,分清「必备、期望、兴奋」,把资源压在刀刃上。 Kano prioritization: rank needs with the Kano model and importance scores — separate must-be, performance, and delighter. Spend resources where they bite.
避免闭门造车:所有设计决策都能追溯到一条真实客户之声,而不是团队的「我觉得」。 No designing in the dark: every design decision should trace back to a real customer voice, not to the team's gut.
一句话In One Line
VOC 最容易走向两个极端:要么完全不听客户,凭团队直觉拍脑袋;要么完全照搬客户的话,客户说什么就做什么。 两个都会翻车。真正的功夫在中间那条窄路:认真听原话,但不停在原话上 —— 原话是线索,真实需求才是目标。客户是「需求」的专家,但你才是「方案」的专家。 五步流水线的意义,就是让每一条设计需求,都能追溯回一句真实的客户之声,又都经过了提纯与验证。 这样造出来的产品,才既不脱离客户、又超越客户的想象。 VOC fails toward two opposite extremes: either ignore the customer entirely and design on team gut, or copy the customer's words verbatim and ship whatever they said. Both crash. The real craft lives on the narrow path between them: listen seriously to the words, but do not stop at the words — the quote is a clue; the real need is the target. The customer is the expert on the need; you are the expert on the solution. The five-step pipeline exists to make every design requirement traceable back to a real customer quote, and every quote refined and verified along the way. That is how you build a product that stays close to the customer yet goes beyond what they could ask for.
常见误用Common Mistakes
把客户原话直接当需求做(真去养更快的马)。必须经转译,抓住原话背后的真实需求。 Treating literal quotes as the requirement (actually going to breed a faster horse). Always translate — capture the underlying need behind the words.
只发问卷、不去现场观察。客户说的和做的常常不一致,观察比问卷更接近真相。 Sending surveys and skipping field observation. What customers say and what they do often disagree — observation gets you closer to the truth than a survey.
收集完就开干,跳过排序与验证。需求要排优先级、要回客户确认,没验证的需求只是假设。 Collect and run — skipping prioritize and verify. Needs must be prioritized and confirmed with customers. An unverified need is only an assumption.

VOC 五步