[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-facilitating-retrospectives-en":3,"blog-adjacent-facilitating-retrospectives-en":30,"blog-related-facilitating-retrospectives-en":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","Facilitating a Retrospective","A good facilitator talks little and asks precisely.","\u003Cp>Bad retrospectives are common: either a blame session or a complaint club, ending in nothing. Across dozens of retrospectives we settled on a few facilitation habits that lifted the quality steadily.\u003C\u002Fp>\n\u003Ch2>Pacing the meeting\u003C\u002Fh2>\n\u003Cp>Reconstruct the timeline for five minutes with facts only, no judgement. Shared facts are the basis for everything after.\u003C\u002Fp>\n\u003Cp>Separate direct causes from root causes during discussion. Many reviews stop at the former and fix symptoms.\u003C\u002Fp>\n\u003Cp>The last twenty minutes take one item only: improvements, owners, dates. Without all three, the review is unfinished.\u003C\u002Fp>\n\u003Ch2>Facilitator moves\u003C\u002Fh2>\n\u003Cp>Turn who erred into what was missing. The first invites defence, the second invites thought.\u003C\u002Fp>\n\u003Cp>Ask the quiet ones directly after two rounds. Silence often hides a different perspective that nobody invited.\u003C\u002Fp>\n\u003Cp>When feelings rise, acknowledge them before returning to facts. A retrospective is not a venting room.\u003C\u002Fp>\n\u003Cp>Retrospective quality is the facilitator's restraint: fewer conclusions, more questions, let the team say it.\u003C\u002Fp>","","cyan","佳益方圆团队","2026-06-01T12:23:00+08:00",1,false,[16,17,18],"Team Culture","Retrospective","Meetings",{"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","Team and Culture","Company events, tech sharing, team building and hiring culture that show the daily life of the Jiayifangyuan team.","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","Retrospective: A Third Party Changed a Field Silently","A partner upgraded their API, the response shape shifted quietly, and our system broke two weeks later.","2026-06-03T12:23:00+08:00",[17,38,39],"Third Party","Stability",{"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","Project Retrospectives","Real project records from zero to one, covering problems, solutions, lessons learned and final outcomes.","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","Open Source Licence Risk: Used, Not Understood","Nearly every project uses open source, yet few can explain its obligations.","2026-05-30T12:23:00+08:00",[54,55,56],"Industry Watch","Open Source","Compliance",{"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","In-depth analysis of internet, software and digital industry trends with our own point of view.","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","The Thirty-Minute Weekly Share","No new technology, no industry trends. Just the pitfalls of the week and how they were solved.","2026-10-11T09:00:00+08:00",[16,71,72],"Knowledge Sharing","Growth",{"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","What Code Review Is Really For","Review is not fault-finding. It is letting another mind walk through your code.","2026-09-29T10:13:00+08:00",[16,81,82],"Code Review","Engineering Practice",{"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","Documents Start With Templates","People avoid writing docs mostly because they do not know where to start. A template solves most of it.","teal","2026-09-17T11:26:00+08:00",[16,92,93],"Documentation","Knowledge Management",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21}]