故事 · 那个「更大的杯架」
Origin Story · That "Bigger Cup Holder"
语义学家 S. I. Hayakawa 提出了「抽象阶梯」：从一头具体的母牛「Bessie」，到「牛」，到「牲畜」，到「资产」 —— 同一对象可以站在不同抽象高度去说。
做需求时同理：客户说「把杯架做大一点」是阶梯最底层的方案，不是需求本身。
往上爬一格问「为什么要大？」 —— 「要放我的超大水壶」；再爬一格 —— 「我希望开车路上随时有水喝」。
到了这一层，方案一下子打开了：加大杯架、车门储物格、磁吸水壶座……全都行。会上下爬梯，就不会被客户随口给的方案锁死。
The semanticist S. I. Hayakawa sketched the original ladder: start with one concrete cow named "Bessie," step up to "cow," to "livestock," to "farm asset." The same thing, described at very different heights.
Requirements work the same way. "Make the cup holder bigger" is the lowest rung — it's a solution, not a need.
Climb one rung up by asking "why bigger?" — "I need to fit my giant water bottle." Climb one more: "I want easy access to water whenever I'm driving."
At that height, the design space cracks open: bigger cup holder, door pocket, magnetic bottle dock — all on the table. Knowing how to climb keeps you from getting trapped by the first solution a customer hands you.
1 抽象阶梯：同一需求的五个高度 The Abstraction Ladder: One Need at Five Heights
点击任意一格2 这一层：能做什么 × 风险在哪 This Rung: What You Can Do × Where It Bites
这一层的好处
What this rung gives you
点上方阶梯查看。
Tap a rung above.
这一层的风险
Where this rung bites
点上方阶梯查看。
Tap a rung above.
3 现实里的抽象阶梯 The Ladder in the Wild
需求层级：客户给的常是「方案」，不是「需求」。往上爬一格问「为什么」，才能摸到真实需要。
Customer need vs solution: customers usually hand you a solution, not a need. Climb one rung and ask "why" — that's where the real need lives.
跳出方案锁定：被「更大杯架」锁死的设计师只会做杯架；爬到「随时有水喝」的人能想出十种解法。
Escape solution lock-in: a designer stuck on "bigger cup holder" only makes cup holders; one who climbed to "water on the road" thinks of ten different fixes.
打孔 vs 挂画：客户要的不是「墙上一个洞」，是「把画挂起来」 —— 抽象一层，无痕挂钩也成了解。
Drilling a hole vs hanging the picture: the customer doesn't want a hole in the wall — they want the picture up. Climb one rung and adhesive hooks become a valid option.
创新空间：中间层级既不锁死方案、又能落地 —— 创新通常发生在这里，不在顶也不在底。
Where innovation happens: the middle rungs leave room to redesign yet stay shippable — that's where innovation actually lives, not at the top, not at the bottom.
一句话
In One Line
抽象阶梯不是叫你「永远往高处爬」 —— 顶层太抽象（「让生活更美好」）等于没说，无法落地；
底层太具体（「杯架直径加 2 厘米」）又把创新锁死在一个方案里。
真正的功夫是会上下移动：拿到客户的方案就往上爬，问「为什么、要解决什么」，把需求提到既能保留创新空间、又能动手落地的中间层级。
然后再向下展开，生成多个可比较的具体方案。同一句话，站对了高度，解空间就完全不一样。
The ladder isn't a command to "always climb higher." The top rung ("make life better") is so abstract it says nothing and ships nothing;
the bottom rung ("add 2 cm to the cup-holder diameter") locks innovation into a single solution.
The real skill is moving up and down deliberately: when a customer hands you a solution, climb up — ask "why" and "what are we really solving" — until the need sits at a middle rung that keeps design room open and stays shippable.
Then climb back down to generate several concrete options you can actually compare. Same sentence, different rung, completely different solution space.
常见误用
Common Mistakes
把客户随口给的方案当成需求直接做（真去加大杯架）。先往上爬一格，问清「为什么、要达成什么」。
Treating the customer's off-the-cuff solution as the requirement (actually shipping the bigger cup holder). Climb one rung first — pin down "why" and "what outcome."
一味往最高层抽象，停在「让用户更幸福」。太抽象无法落地，要再向下展开到可设计的中间层。
Climbing all the way to "make users happier" and stopping there. Too abstract to design against — drop back down to a middle rung you can actually build.
整个团队都卡在同一高度上讨论。有意识地上下移动，才能既不锁死方案、又不空谈。
The whole team stuck arguing at one fixed height. Move up and down on purpose — that's how you avoid both solution lock-in and hot air.