故事 · 为什么屋顶要做成三角形
Story · Why the roof is a triangle
房间矩阵很好懂:行是客户需求,列是工程特性,每格回答「关系有多强」。难懂的是屋顶。
为什么它非得是个奇怪的三角形?因为它要表达的,不是「需求 × 特性」,而是「特性 × 特性」 ——
任意两个工程特性之间,是协同(改善一个顺带改善另一个)还是冲突(改善一个反而拖累另一个)。
把这种两两关系画成方阵会上下对称、浪费一半,于是工程师把它斜过来切一半,正好架在天花板之上,
像一个三角屋顶。绿色「＋」是协同,红色「－」是冲突。
那些红格,就是设计里逃不掉的权衡:更轻 vs 更结实、更快 vs 更省、更安静 vs 更便宜 ——
屋顶逼着你提前看见它们,而不是等样机做出来才发现「顾此失彼」。
The room is easy to read: rows are customer needs, columns are engineering features, every cell answers "how strong is the link?". The roof is the harder part.
Why does it have to be that odd triangle? Because it isn't tracking "needs × features" — it's tracking "feature × feature" —
between any two engineering characteristics, are they in synergy (improve one and the other rides along) or in conflict (improve one and the other suffers)?
A full square matrix would be symmetric and waste half the cells, so engineers tilted it on its side, sliced off the redundant half, and parked it on top of the ceiling
like a triangular roof. A green "+" is synergy, a red "−" is conflict.
Those red cells are the unavoidable trade-offs in every design — lighter vs. stiffer, faster vs. cheaper, quieter vs. cheaper still —
the roof forces you to see them on paper, not after the prototype shows up and one spec robs another.
1 可交互:房间打分 + 屋顶认冲突 Interactive: score the room, spot conflicts on the roof
点格子试试Click a cell2 两个部件,各管一件事 Two parts, two jobs
房间 · 关系矩阵:需求 × 特性。回答「谁影响谁」。空列＝无主特性,空行＝没人管的需求。
Room · Relationship matrix: needs × features. Answers "who drives what". A blank column is an orphan feature; a blank row is a need no one owns.
屋顶 · 相关矩阵:特性 × 特性。回答「谁拖累谁」。红格＝设计冲突,绿格＝可顺手共赢。
Roof · Correlation matrix: features × features. Answers "who drags who down". Red cells are design conflicts, green cells are free wins.
◎9 ○3 △1:关系强度不是连续打分,而是离散三档,逼你判断「强 / 中 / 弱」,避免假精确。
◎9 ○3 △1: relationship strength is deliberately discrete — three buckets force you to commit to "strong / medium / weak" instead of faking precision with decimals.
－负相关:最值钱的信息。它提前暴露你以后一定会撞上的取舍,让团队现在就拍板,而非返工时才发现。
− Negative correlation: the most valuable information on the entire chart. It flags the trade-off you will hit anyway, so the team decides now instead of during rework.
3 现实里的关系矩阵与屋顶 The matrix and roof in the wild
需求-特性映射:每条客户需求都能指向具体可调的工程特性,没有「悬空」的承诺。
Need-to-feature mapping: every customer need lands on a concrete, tunable engineering feature — no marketing promise floats with nothing behind it.
设计权衡:手机要更薄又要电池更大,屋顶的红格把这种结构性矛盾摆上台面。
Design trade-off: a phone has to be thinner and have a larger battery — the red cells on the roof put that structural conflict on the table early.
屋顶相关性:航空发动机推力与油耗强负相关,先认下冲突,才能谈在哪个点折中。
Roof correlation: in a jet engine, thrust and fuel burn are sharply negatively correlated. Admit the conflict first, then argue about where to land the compromise.
矛盾识别:识别出冲突后,可交给 TRIZ 等创新方法去「双赢破局」,而不是简单各退一步。
Contradiction spotting: once a conflict is named, hand it to TRIZ or another inventive-problem method to look for a win-win break — instead of reflexively splitting the difference.
一句话In One Line
房间和屋顶,回答的是两个截然不同的问题。房间问「这个工程特性,能帮上哪条客户需求」 ——
它把客户语言翻译成工程语言,确保每个技术指标都「事出有因」。屋顶问的却是「这些工程特性之间,会不会互相打架」 ——
这是工程世界自己的物理现实,和客户无关。协同(绿＋)是免费的午餐:调一个,白赚一个;
冲突(红－)则是必须付出的代价:想要这个,就得舍一点那个。
质量屋最被低估的智慧,就是逼你在画图纸的阶段、而不是在样机翻车之后,
把这些权衡一个个看清、摆明、拍板。看见冲突不可怕,假装冲突不存在才致命。
The room and the roof answer two completely different questions. The room asks "which customer need does this engineering feature actually serve?" —
it translates customer language into engineering language, so every spec on the sheet has a reason to exist. The roof asks "do these engineering features fight each other?" —
a pure piece of engineering physics, nothing to do with the customer. Synergy (green +) is a free lunch: tune one, you get the other.
Conflict (red −) is the bill: get one, and you pay a little of the other.
The most underrated wisdom of the House of Quality is that it forces you to see, name and decide those trade-offs on paper, not after a prototype implodes.
Naming a conflict is fine; pretending it doesn't exist is what kills the program.
常见误用Common Mistakes
关系强度随手乱打,凑满格。◎○△ 要有工程依据,没关系就留空,矩阵才有判断价值。
Filling cells just to fill them. Every ◎ / ○ / △ needs an engineering reason. If there's no link, leave it blank — that's what makes the matrix a decision tool instead of decoration.
只填房间,懒得画屋顶。屋顶的负相关才是最该团队拍板的设计冲突,缺它质量屋就废了一半。
Filling the room, skipping the roof. The negative correlations on the roof are exactly the design conflicts the team must rule on — skip them and you've thrown away half the House.
看见红色冲突就各退一步和稀泥。先认下冲突,再用 TRIZ 等方法找双赢解,而非草率折中。
Splitting the difference the moment you see red. Acknowledge the conflict first, then reach for TRIZ or other inventive methods to look for a win-win — instead of reflexively compromising both specs.