知识卡片
失败复盘形成共同改进
设计者对方案负责,失败后先弄清发生了什么,再共同回答如何避免重演,并跟进决定。领导者自己的判断失败也采用同一流程。接近明显疏忽的行为可私下教练式讨论,聚焦可控制的过程,避免公开过激反应。承认所有架构都有失败方式,才能兼顾高标准和愿意主动报告风险的学习环境。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 构建与演进系统 · 查看原书依据
When something fails, probe until you understand in detail what happened and always end with a second-order question such as “What can we (notice it is we, not you) do to avoid this from happening in the future?” Then, make sure those decisions are followed.
参考来源
- 位置:《Software Architecture and Decision-Making》第13章《Building and Evolving the Systems》(来源项目:book-sources;源文件:extracted/Software Architecture and Decision-Making Leveraging Leadership, Technology, and Product Management to Build Great Products… (Srinath Perera)/_epub-src/ch13.xhtml)
- 结论依据:摘录说明设计者对方案负责,失败后先弄清发生了什么,再共同回答如何避免重演,并跟进决定。其余条件结合本章相邻例子与取舍说明,数字示例不作当前性能承诺。
- 原始内容:When something fails, probe until you understand in detail what happened and always end with a second-order question such as “What can we (notice it is we, not you) do to avoid this from happening in the future?” Then, make sure those decisions are followed.