故事 · 神户造船厂的「质量表」
Origin Story · The "Quality Table" at the Kobe Shipyard
1960 年代末，日本三菱重工神户造船厂面对一个难题：客户对船的要求又多又抽象，到了车间却没人知道该怎么落地。
学者赤尾洋二(Yoji Akao)与水野滋(Shigeru Mizuno)提出了一个朴素却强大的想法 ——
做一张「质量表」，把「客户要什么」一栏栏对应到「我们怎么造」。
后来它发展成 QFD（Quality Function Deployment，质量功能展开）：
用四个串联的矩阵，把客户之声从需求一路展开到产品特性、零件、工艺，最终到车间的每一项生产要求。
1980 年代丰田用它把新车开发周期和返工成本大幅压低，QFD 由此名声大噪，传遍全球制造业。
In the late 1960s, the Mitsubishi Heavy Industries shipyard in Kobe faced a familiar headache: customer requirements for a ship were many and abstract, yet by the time they reached the shop floor, nobody knew how to act on them.
Scholars Yoji Akao and Shigeru Mizuno proposed a humble but powerful idea —
build a "quality table" that lined up "what the customer wants" against "how we will build it," column by column.
That table grew into Quality Function Deployment (QFD):
four chained matrices that deploy the voice of the customer from needs through product characteristics, parts, and processes, all the way to every single production requirement on the floor.
In the 1980s Toyota used QFD to slash new-vehicle development time and rework cost, and the method spread through global manufacturing.
1 四级接力：上一棒的「怎么做」= 下一棒的「做什么」 Four-Leg Relay: The Previous HOW = The Next WHAT
点阶段查看click a phase2 这一阶段：输入 → 矩阵 → 输出 This Phase: Input → Matrix → Output
输入（WHAT · 做什么）
Input (WHAT)
—
输出（HOW · 怎么做）
Output (HOW)
—
3 现实里的 QFD 传递 QFD Handoff in the Real World
需求传递：客户之声不靠口耳相传，而是被结构化矩阵一棒棒接力，可追溯、可核对。
Requirement handoff: The voice of the customer doesn't ride on hearsay — it travels through structured matrices, baton by baton, traceable and auditable.
QFD 四矩阵：质量屋、零件展开、工艺规划、生产规划 —— 四张表把抽象需求落到车间动作。
QFD's four matrices: House of Quality, Parts Deployment, Process Planning, Production Planning — four tables that drive abstract needs all the way down to shop-floor actions.
防止需求走样：每一棒都对照上一棒的输出，确保翻译没跑偏、没私自加戏或漏项。
Guarding against drift: Each leg checks back against the previous leg's output, so the translation never wanders, no one ad-libs new items, and nothing gets quietly dropped.
端到端展开：从一句模糊的客户期望，一直追到某台机床的某个公差，全程闭环可回溯。
End-to-end deployment: From a fuzzy customer wish all the way to a specific tolerance on a specific machine — fully closed-loop and traceable.
一句话In One Line
产品开发最怕的，是客户的声音在层层交接里悄悄走样、慢慢丢失 ——
市场部听到的、设计师理解的、工程师实现的、车间执行的，常常是四个不同版本的「客户需求」。
QFD 的本质，就是用一根可追溯的链条把这四棒焊在一起：
每一棒的「怎么做」必须明确成下一棒的「做什么」，谁也别想私自加戏或偷偷漏项。
于是当车间问「这个公差为什么定 0.1 毫米」，你能一路反查回那句最初的客户之声。
但它也不是万能咒语：第一棒（质量屋）若把客户需求理解错了，后面三棒翻译得再精准，也只是把错误高效地放大到车间。
The biggest fear in product development is that the voice of the customer quietly drifts and slowly leaks away across the handoffs —
what marketing hears, what designers interpret, what engineers implement, and what the shop floor executes are often four different versions of "the customer requirement."
QFD's whole point is to weld those four legs together with a single traceable chain:
every leg's HOW must crystallize into the next leg's WHAT — no ad-libbing, no silent omissions.
So when the shop floor asks, "Why is this tolerance set to 0.1 mm?" you can trace it all the way back to the original sentence from the customer.
But QFD is no magic spell: if the first leg (the House of Quality) misreads the customer's need, the three downstream legs will only amplify that mistake more efficiently to the shop floor.
常见误用Common Mistakes
四阶段全做，把矩阵填到天荒地老。多数项目只需做透第一屋（质量屋），按需向下展开。
Insisting on filling all four matrices to the bitter end. Most projects only need to do the first house (House of Quality) thoroughly, then deploy downstream on demand.
交接时各填各的，不对照上一棒输出。本屋的 WHAT 必须严格继承上一屋的 HOW，链条不断。
Each house filling its own table without checking the previous leg's output. The current house's WHAT must strictly inherit the previous house's HOW — keep the chain unbroken.
把 QFD 当一次性填表交差。它是活的追溯链，需求变了要回头更新整条链。
Treating QFD as a one-shot paperwork exercise. It's a living traceability chain — when needs change, walk back up the chain and update every link.