我常犯错
I am often wrong

原始链接: https://borischerny.com/management,/product/2026/09/19/I-am-often-wrong.html

作者概述了一套用于产品开发的一贯性、迭代式问题解决方法:搜集信息、界定问题、确立简易方案、设定目标以及采取紧急行动。由于该过程依赖于在获取新数据时更新个人的“先验知识”,作者认为由此产生的“反复折腾”或波动是寻找正确解决方案中健康且必要的组成部分。 最常见的失败模式发生在问题或方案定义不清时,这会导致不必要的复杂化。为了缓解这一问题,作者强调了持续反馈循环和实时协作的重要性。最终,作者拥抱错误,将其视为完善认知、加速学习并实现更清晰、更有效成果的宝贵催化剂。

这篇 Hacker News 讨论聚焦于 Boris Cherny 的一篇博文,文中他概述了一个六步问题解决框架:理解问题、过度构建解决方案、推销方案、与他人迭代以简化方案、推卸责任、说服专家解决问题,最后居功自傲。 社区反应极为负面,许多用户认为该框架是“硅谷陈词滥调”或“企业心理变态”的体现。主要争议点包括: * **管理风格:** 批评者认为,强迫员工遵循个人的、僵化的框架属于微观管理,并且在强调“紧迫感”的同时,会营造出一种有毒的工作环境。 * **虚伪:** 许多用户认为标题“我经常犯错”是一种表演性的“假谦虚”,或者是掩盖缺乏真正反思的肤浅亲和尝试。 * **产品质量:** 一些评论者借此机会发泄对“Claude Code”质量的不满,提到了持续存在的漏洞、迟缓的性能,以及该团队在处理社区反馈时表现出的傲慢态度。 * **回音室效应:** 讨论表明,“AI 炒作”文化往往导致领导者优先考虑肤浅的思想领导力,而非构建可靠的、以用户为中心的软件。
相关文章

原文

September 19, 2026

[I shared this note with my team earlier this week, and am posting it here as well. I hope it is interesting or helpful for others working on building product in the age of AI.]

Something that people learn quickly when they work with me is that my approach to pretty much every problem is:

  1. Understand the available information
  2. Gather missing information
  3. Define the problem
  4. Define a clear and simple approach to solve the problem
  5. Define a goal
  6. Act with urgency to achieve the goal

Along the way, I will often learn new information. That means going back and redefining #3-5, and repeating. This process is iterative and for complicated problems, it can take many tries to get right. This can feel thrashy, but if you are aware that it’s all part of the process, and that the only way to really solve a problem is to adjust when there is new data, then the churn is healthy. When there’s new data, you have to update your priors.

I apply something like these six steps for pretty much every problem, and pretty much every product (a product solves a problem for users). I apply this rough framework many times on most days.

Sometimes I will give feedback to people when they are missing steps in the framework, or are poorly executing some of the steps. I expect the same feedback in return. I try hard to give the feedback in real time, so the person/team can learn more quickly. Most often, the failure mode I see is (3) failure to clearly define the problem, and (4) failure to define an approach that is clear and simple. When one of these is missing, it leads to complex plans and unclear success criteria. For complicated problems, lack of clarity can be hard to spot if you’re the one making the plan, making it even more important to get feedback from people.

If part of this meta-process is meta-wrong, I am open to changing it.

All this to say, I love being wrong. It is my favorite, because it helps me more clearly define the problem, find the right solution, learn more quickly, and solve the problem.

联系我们 contact @ memedata.com