Back to Details

worst-idea

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Worst Possible Idea

Worst Possible Idea

What this technique does

该方法的作用

Ask for the worst solution to the problem, not the best. Design solutions that would reliably make things terrible, then dissect each one to find the exact mechanism that makes it bad. Invert that mechanism, and you have a feature. The move works because "what's the best design?" routes through everyone's inhibitions and lands on the safe, obvious answer, whereas "how would we guarantee failure?" removes the fear of being wrong and lets people say things out loud — and every named failure mode is a design principle wearing its opposite.
Source: reverse brainstorming, attributed to Hotpoint's product development practice in the 1950s, and standard in the d.school/IDEO facilitation toolkit as "Worst Possible Idea."
要求大家提出最糟糕的问题解决方案，而非最优方案。设计能切实让情况恶化的方案，然后剖析每个方案，找出其糟糕的核心机制。将该机制反转，就能得到一个优质特性。这种方法之所以有效，是因为「什么是最佳设计？」这类问题会让所有人受限于思维定式，最终得出保守、显而易见的答案；而「如何确保失败？」则能消除犯错的恐惧，让人们畅所欲言——每一个明确的失败模式，都是反向呈现的设计原则。
来源：反向头脑风暴（reverse brainstorming），可追溯至20世纪50年代Hotpoint的产品开发实践，也是d.school/IDEO引导工具包中的标准方法，名为「Worst Possible Idea」。

Workflow

工作流程

Step 1: Confirm the target

步骤1：明确目标

A valid target is a concrete creative problem stated as something to design or reinvent: an onboarding flow, a pricing page, a landing page, a naming direction, a ritual the team runs. If the target is unclear, ask one focused question — "What are we designing, and what would 'good' look like?"
Refuse requests to perform analytical work — debugging, reviewing code, implementing a change — and suggest an analytical approach instead. Redesigning or ideating about such a process is a valid creative target: "reinvent our code-review ritual" is in scope; "review this PR" is not.
有效的目标是具体的创意问题，表述为需要设计或重塑的内容：比如用户引导流程、定价页面、着陆页、命名方向、团队执行的仪式等。如果目标不清晰，可提出一个聚焦问题——「我们要设计什么，以及『好』的标准是什么？」
拒绝执行分析类工作的请求——如调试、代码评审、落地某项变更——并建议采用分析类方法替代。对这类流程进行重塑或构思属于有效的创意目标：「重塑我们的代码评审仪式」在适用范围内；「评审这个PR」则不在。

Step 2: Generate genuinely terrible solutions

步骤2：生成真正糟糕的解决方案

Produce 5–8 solutions that would make the problem worse. The bar is high: each one must be plausible enough that someone, somewhere, has actually shipped it. Cartoon evil ("delete the user's files!") is too easy and teaches nothing. The useful terrible ideas are the ones a real team rationalized its way into — the ones that sound almost defensible in a meeting.
Show them plainly. Do not soften them, and do not pre-apologize for them.
产出5-8个会让问题恶化的方案。标准要高：每个方案必须足够合理，以至于现实中确实有团队推出过这类方案。卡通式的恶意（比如「删除用户文件！」）太简单，毫无借鉴价值。有价值的糟糕想法是那些真实团队自圆其说后落地的方案——在会议上听起来甚至几乎站得住脚的方案。
直白地展示这些想法，不要弱化，也不要提前道歉。

Step 3: Isolate the mechanism of badness

步骤3：定位糟糕的核心机制

For each bad idea, state in one sentence why it is bad — the mechanism, not the symptom. Not "it's annoying" but the structural reason it fails.
Example: "it's bad because it makes the user prove value to the product, not the reverse."
The mechanism is the whole technique. A bad idea with no articulated mechanism is just a bad idea.
针对每个糟糕想法，用一句话说明其为何糟糕——要讲核心机制，而非表面症状。不是「它很烦人」，而是它失败的结构性原因。
示例：「它之所以糟糕，是因为它让用户向产品证明价值，而非产品向用户证明价值。」
核心机制是整个方法的关键。没有明确机制的糟糕想法，只是单纯的坏点子。

Step 4: Invert the mechanism, not the idea

步骤4：反转机制，而非想法本身

Flip the mechanism into its opposite. This is not "don't do the bad thing" — that only gets you back to neutral. Inverting the mechanism produces a positive design principle.
Bad idea's mechanism: "it makes the user prove value to the product." Inversion: "make the product prove value before asking anything of the user."
Inverting the surface ("so, don't make users prove value") is the common failure. Invert the underlying force.
将核心机制反转成其对立面。这不是「不要做糟糕的事」——那样只会回到中性状态。反转机制能产生积极的设计原则。
糟糕想法的机制：「它让用户向产品证明价值。」 反转后的原则：「在向用户索取任何东西之前，先让产品向用户证明价值。」
只反转表面行为（比如「那就不要让用户证明价值」）是常见的错误做法。要反转背后的核心逻辑。

Step 5: Develop the inversions

步骤5：深化反转后的原则

Take the 2–4 strongest inversions and push each into a concrete direction — an actual feature, layout, flow, or line of copy. An inverted mechanism is a principle; a direction is something you could build on Monday.
选取2-4个最有力的反转原则，将每个原则推进到具体方向——比如一个可落地的特性、布局、流程或文案。反转后的机制是原则，而具体方向是周一就能着手开发的内容。

Step 6: Meta-pattern scan

步骤6：元模式扫描

The mechanisms of badness cluster. Read them side by side and name the cluster out loud: it is a map of what this thing must never do. Often three or four separate terrible ideas turn out to be the same underlying sin in different costumes. State that sin explicitly — it is usually the sharpest output of the whole session.
糟糕的核心机制会呈现聚类特征。将这些机制放在一起阅读，明确说出聚类的共性：这是一份该事物绝对不能做的行为清单。通常三四个不同的糟糕想法，本质上是同一核心问题的不同表现形式。明确指出这个核心问题——这往往是整个环节最有价值的输出。

Step 7: Honest ranking, no closure pressure

步骤7：如实排序，不施加决策压力

Rank the surviving directions. Say which are strong, which are thin, and why. Offer next moves — develop one further, generate a fresh batch of terrible ideas, switch technique, or stop. Never push the user to commit.
对筛选后的方向进行排序，说明哪些方向有力、哪些薄弱，以及原因。提出后续行动建议——进一步深化某个方向、生成新的糟糕想法、切换方法，或停止工作。绝不强迫用户做出承诺。

Honesty mechanics

有效性保障机制

The secretly-clever disqualification. Sometimes a "worst idea" turns out to be quietly good — a real business model or a legitimate feature in disguise. When that happens, the idea has failed as a worst idea and must be disqualified and replaced with a genuinely terrible one. Say so out loud:
"charge per bug report" is actually a support-tier pricing model in disguise — too good, replacing.
This keeps the batch honest. If nothing in the batch makes you wince, the batch is fake.
Dead mechanisms. Not every mechanism inverts into something useful. Some flip into the blandly obvious, or into a principle you already follow, or into nothing at all. Show at least one dead — invert it, look at the result, and declare it dead rather than dressing it up. A batch where every mechanism yields treasure is a tell that the output was reverse-engineered from the answers.
When the batch itself fails. If most mechanisms invert into principles you already follow, the technique has told you something real: this thing is not failing for lack of imagination, and more terrible ideas will not help. Name the diagnosis, suggest the technique that fits it as the user's next move, and stop there — do not run it yourself:
  • The inversions are all things you already do → the design is sound and the question is elsewhere. Suggest 
    concept-fan
    to check you are solving the right problem.
  • You cannot generate a terrible idea that anyone would actually ship → the target is too small or too abstract to have failure modes. Suggest 
    random-stimulus
    for generative range.
**暗藏巧思的不合格项。**有时「最差想法」实际是隐性的好想法——伪装成糟糕方案的真实商业模式或合理特性。遇到这种情况，该想法就不符合「最差想法」的要求，必须被淘汰，替换成真正糟糕的想法。要明确说明：
「按Bug报告收费」实际上是一种支持层级定价模式的伪装——不够糟糕，需要替换。
这能确保所有想法的真实性。如果所有想法都不会让你皱眉，那这些想法就是虚假的。
**无效机制。**并非所有机制反转后都有价值。有些反转后会变成平淡无奇的常识，或是你已经在遵循的原则，或是毫无意义的内容。至少要展示一个无效机制——将其反转，查看结果，然后直接判定无效，而非强行包装。如果所有机制都能产出有价值的内容，说明这些输出是从预设答案反向推导出来的。
**当整个环节失效时。**如果大多数机制反转后都是你已经在遵循的原则，那这个方法其实告诉你一个事实：这件事的问题不在于缺乏创意，更多的糟糕想法也无济于事。明确给出诊断结果，建议用户采用适合的方法作为下一步行动，然后停止当前流程——不要强行继续：
  • 反转后的原则都是你已经在做的事→设计本身是合理的，问题出在别处。建议使用
    concept-fan
    方法，确认你是否在解决正确的问题。
  • 你无法生成任何真实团队会落地的糟糕想法→目标太小或太抽象，没有明确的失败模式。建议使用
    random-stimulus
    方法拓展创意范围。

What NOT to do

禁忌事项

  • Don't sanitize the terrible ideas. The wince is the signal. If a bad idea is genuinely uncomfortable, keep it uncomfortable — the softened version teaches nothing.
  • Don't invert the surface. "Don't do X" is not an inversion of X; it is the absence of X. Invert the mechanism underneath X into a positive force.
  • Don't skip the mechanism step. Jumping straight from bad idea to good idea skips the only part that does work. The mechanism IS the technique; without it you are just guessing at features.
  • Don't force every mechanism to pay off. Show the dead ones dead.
  • Don't push the user toward a decision. The technique is divergent; convergence belongs to the user.
  • **不要弱化糟糕想法。**皱眉是信号。如果一个糟糕想法真的让你不适，就保留这种不适感——弱化后的版本毫无借鉴价值。
  • 不要只反转表面行为。「不要做X」不是对X的反转；它只是X的缺失。要反转X背后的核心机制，转化为积极的驱动力。
  • **不要跳过机制定位步骤。**直接从糟糕想法跳到好想法，跳过了整个方法中唯一真正起作用的环节。核心机制就是方法本身；没有它，你只是在盲目猜测特性。
  • **不要强迫所有机制产出价值。**直接展示无效的机制即可。
  • **不要强迫用户做出决策。**该方法用于发散思维；收敛决策应由用户主导。

References

参考资料

  • ./references/worked-example.md
     — a real session showing the full shape, including a dead mechanism and a disqualified idea
  • ./references/worked-example.md
     — 完整展示该方法流程的真实案例，包含一个无效机制和一个被淘汰的想法