[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-project-retrospective-practice-en":3,"blog-related-project-retrospective-practice-en":30,"blog-adjacent-project-retrospective-practice-en":65},{"id":4,"slug":5,"title":6,"excerpt":7,"content":8,"cover":9,"tone":10,"author":11,"publishedAt":12,"updatedAt":13,"readingMinutes":14,"featured":15,"tags":16,"category":19,"seoSettings":29},8,"project-retrospective-practice","How to Run a Retrospective That Works: A Real Session from Our Team","A retrospective is not a blame meeting and should not be a process performance. It only needs to solve one problem: how to do a little better next time.","\u003Cp>Retrospectives tend to turn into two kinds of meetings: one where the process is completed and everyone says a few polite words, and one that becomes indirect blame until nobody is willing to tell the truth. We prefer a retrospective that solves one concrete problem: next time a similar situation appears, the team does a little better.\u003C\u002Fp>\u003Ch2>Before the meeting: facts only, no conclusions\u003C\u002Fh2>\u003Cp>Collect the timeline, change records, defect list and key decisions in advance so everyone discusses based on the same facts. Avoid conclusion-style descriptions such as poor communication or weak execution. They sound right but cannot guide action.\u003C\u002Fp>\u003Ch2>During the meeting: separate decisions from execution\u003C\u002Fh2>\u003Cul>\u003Cli>Which problems were decision errors caused by insufficient information at the time;\u003C\u002Fli>\u003Cli>Which problems came from a correct decision that was poorly executed;\u003C\u002Fli>\u003Cli>Which problems are external constraints that cannot change in the short term.\u003C\u002Fli>\u003C\u002Ful>\u003Cp>Separating these three categories keeps the discussion away from whose fault it is and moves it toward how to judge and collaborate next time.\u003C\u002Fp>\u003Ch2>After the meeting: keep only three actionable items\u003C\u002Fh2>\u003Cp>The output does not need to be long, but every action needs an owner, a due date and a way to verify it. We usually keep only the three items that most affect future projects, and check at the next retrospective whether the previous actions were truly completed.\u003C\u002Fp>\u003Cblockquote>A retrospective is not an explanation for the past. It is a better starting point for next time.\u003C\u002Fblockquote>\u003Cp>When the team sees that retrospectives really change how work is done instead of just following a process, more people become willing to speak honestly.\u003C\u002Fp>","","slate","佳益方圆团队","2026-08-01T17:00:00+08:00","2026-10-18T15:58:14.744+08:00",1,false,[17,18],"Retrospectives","Team Culture",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},3,0,"project-retrospective","Project Retrospectives","Real project records from zero to one, covering problems, solutions, lessons learned and final outcomes.","clipboard-check","blue","article",40,{},[31,43,54],{"id":32,"slug":33,"title":34,"excerpt":35,"content":9,"cover":9,"tone":36,"author":11,"publishedAt":37,"updatedAt":37,"readingMinutes":14,"featured":15,"tags":38,"category":42},70,"gov-project-acceptance","Retrospective: Why Acceptance Took Half a Year","The system was live for months while acceptance stalled. The causes were documents, process and communication, not software.","indigo","2026-10-13T09:00:00+08:00",[39,40,41],"Retrospective","Government","Acceptance",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":44,"slug":45,"title":46,"excerpt":47,"content":9,"cover":9,"tone":48,"author":11,"publishedAt":49,"updatedAt":49,"readingMinutes":14,"featured":15,"tags":50,"category":53},71,"mes-integration-retro","Retrospective: Integrating ERP With MES","The hard part of integration is not the interface, but getting two departments to agree on what a field means.","cyan","2026-10-01T10:13:00+08:00",[39,51,52],"Manufacturing","Integration",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":55,"slug":56,"title":57,"excerpt":58,"content":9,"cover":9,"tone":59,"author":11,"publishedAt":60,"updatedAt":60,"readingMinutes":14,"featured":15,"tags":61,"category":64},72,"cross-border-site-retro","Retrospective: Traffic Arrived, Enquiries Did Not","Ads ran normally after launch but enquiries stayed low. The review found trust and form friction were the blockers.","teal","2026-09-19T11:26:00+08:00",[39,62,63],"Cross-border","Conversion",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"previous":66,"next":76},{"id":67,"slug":68,"title":69,"excerpt":70,"content":9,"cover":9,"tone":59,"author":11,"publishedAt":71,"updatedAt":71,"readingMinutes":14,"featured":15,"tags":72,"category":75},76,"low-budget-project-retro","Retrospective: Where to Save Money on a Tight Budget","At half the usual budget, the way to protect quality is to cut scope rather than foundations.","2026-08-02T15:18:00+08:00",[39,73,74],"Budget","Scope",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":77,"slug":78,"title":79,"excerpt":80,"content":9,"cover":9,"tone":48,"author":11,"publishedAt":81,"updatedAt":81,"readingMinutes":14,"featured":15,"tags":82,"category":85},95,"hiring-criteria","How We Hire","Not puzzle counts, not buzzwords on a CV. Three things matter.","2026-07-31T15:18:00+08:00",[18,83,84],"Hiring","Interviews",{"id":86,"parentId":21,"slug":87,"name":88,"description":89,"icon":90,"cover":9,"tone":26,"kind":27,"sortOrder":91,"count":21},4,"team-culture","Team and Culture","Company events, tech sharing, team building and hiring culture that show the daily life of the Jiayifangyuan team.","users",30]