[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-facilitating-retrospectives-zh-CN":3,"blog-adjacent-facilitating-retrospectives-zh-CN":30,"blog-related-facilitating-retrospectives-zh-CN":63},{"id":4,"slug":5,"title":6,"excerpt":7,"content":8,"cover":9,"tone":10,"author":11,"publishedAt":12,"updatedAt":12,"readingMinutes":13,"featured":14,"tags":15,"category":19,"seoSettings":29},100,"facilitating-retrospectives","复盘会的主持技巧","一次好的复盘会，主持人说得少，问题问得准。","\u003Cp>复盘会开不好很常见：要么变成追责现场，要么变成吐槽大会，最后没有结论。我们在几十次复盘里总结出几个主持上的做法，会议质量稳定了很多。\u003C\u002Fp>\n\u003Ch2>会议节奏\u003C\u002Fh2>\n\u003Cp>先花五分钟还原时间线，只讲事实，不做评价。事实对齐了，后面的讨论才有基础。\u003C\u002Fp>\n\u003Cp>讨论原因时区分"直接原因"和"根本原因"。很多复盘停在直接原因，改进项治标不治本。\u003C\u002Fp>\n\u003Cp>最后二十分钟只做一件事：确定改进项、责任人和日期。没有这三项的复盘不算结束。\u003C\u002Fp>\n\u003Ch2>主持人的几个动作\u003C\u002Fh2>\n\u003Cp>把"谁犯错"的问题改成"哪个环节缺失"。前者让人防御，后者让人思考。\u003C\u002Fp>\n\u003Cp>有人沉默超过两轮讨论时点名提问。沉默的人往往有不同视角，只是不愿打断。\u003C\u002Fp>\n\u003Cp>如果有人情绪激动，先认可其感受再引导回到事实。复盘不是发泄场。\u003C\u002Fp>\n\u003Cp>复盘的质量取决于主持人的克制：少下结论，多问问题，把结论留给团队自己说出口。\u003C\u002Fp>","","cyan","佳益方圆团队","2026-06-01T12:23:00+08:00",1,false,[16,17,18],"团队文化","复盘","会议",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},4,0,"team-culture","团队动态","公司活动、技术分享、团建与招聘文化，了解佳益方圆团队的日常。","users","blue","article",30,{},{"previous":31,"next":47},{"id":32,"slug":33,"title":34,"excerpt":35,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":36,"updatedAt":36,"readingMinutes":13,"featured":14,"tags":37,"category":40},81,"third-party-api-change","第三方接口复盘：对方改了字段没通知","合作方升级接口版本，返回结构悄然变化，系统在两周后才出现异常。","2026-06-03T12:23:00+08:00",[17,38,39],"第三方接口","稳定性",{"id":41,"parentId":21,"slug":42,"name":43,"description":44,"icon":45,"cover":9,"tone":26,"kind":27,"sortOrder":46,"count":21},3,"project-retrospective","项目复盘","从 0 到 1 的真实项目记录，完整呈现问题、方案、踩坑经验与最终结果。","clipboard-check",40,{"id":48,"slug":49,"title":50,"excerpt":51,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":52,"updatedAt":52,"readingMinutes":13,"featured":14,"tags":53,"category":57},119,"open-source-license-risk","开源协议风险：企业在用，但并不了解","几乎每个项目都会用到开源组件，但很少有人说得清它们的协议义务。","2026-05-30T12:23:00+08:00",[54,55,56],"行业观察","开源","合规",{"id":58,"parentId":21,"slug":59,"name":54,"description":60,"icon":61,"cover":9,"tone":26,"kind":27,"sortOrder":62,"count":21},5,"industry-watch","对互联网、软件与数字化行业趋势的深度分析，输出团队自己的判断。","globe",20,[64,74,84],{"id":65,"slug":66,"title":67,"excerpt":68,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":69,"updatedAt":69,"readingMinutes":13,"featured":14,"tags":70,"category":73},89,"thirty-minute-weekly","每周三十分钟的技术分享会","不讲新技术，不讲行业趋势，只讲这周踩过的坑和解决方式。","2026-10-11T09:00:00+08:00",[16,71,72],"技术分享","成长",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":75,"slug":76,"title":77,"excerpt":78,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":79,"updatedAt":79,"readingMinutes":13,"featured":14,"tags":80,"category":83},90,"what-code-review-is-for","代码评审是为了什么","评审不是找错，是让另一个人的脑子过一遍你的代码。","2026-09-29T10:13:00+08:00",[16,81,82],"代码评审","工程实践",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":85,"slug":86,"title":87,"excerpt":88,"content":9,"cover":9,"tone":89,"author":11,"publishedAt":90,"updatedAt":90,"readingMinutes":13,"featured":14,"tags":91,"category":94},91,"docs-start-with-templates","文档从模板开始","没人愿意写文档，多半是因为不知道从哪写起。一张模板能解决大半问题。","teal","2026-09-17T11:26:00+08:00",[16,92,93],"文档","知识管理",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21}]