[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-handover-without-docs-en":3,"blog-adjacent-handover-without-docs-en":30,"blog-related-handover-without-docs-en":66},{"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},83,"handover-without-docs","Retrospective: A Month Lost to Missing Documentation","The core developer left and the successor spent a month before daring to change a line.","\u003Cp>The system had run stable for two years when the core developer resigned. Handover lasted two weeks, and the successor spent the first month reading code and guessing intent. A small client request took ten days to reach production.\u003C\u002Fp>\n\u003Ch2>What was missing\u003C\u002Fh2>\n\u003Cp>Why things were built that way. Several odd behaviours existed for a specific client requirement years earlier.\u003C\u002Fp>\n\u003Cp>Which data must not be touched. Some tables are written by external systems, and manual edits break synchronisation.\u003C\u002Fp>\n\u003Cp>The deployment procedure lived in one head: which servers, which scheduled jobs, which environment variables.\u003C\u002Fp>\n\u003Ch2>Our handover checklist now\u003C\u002Fh2>\n\u003Cp>Each core member maintains a system note with architecture diagrams, key decisions and common incident playbooks.\u003C\u002Fp>\n\u003Cp>Deployment and rollback are scripts, so anyone can follow the document and release.\u003C\u002Fp>\n\u003Cp>Handover starts at least a month before departure, and the successor performs one release alone.\u003C\u002Fp>\n\u003Cp>People move on. Whether a system keeps running after anyone leaves is the real measure of team maturity.\u003C\u002Fp>","","indigo","佳益方圆团队","2026-05-10T14:49:00+08:00",1,false,[16,17,18],"Retrospective","Handover","Team",{"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,{},{"previous":31,"next":49},{"id":32,"slug":33,"title":34,"excerpt":35,"content":9,"cover":9,"tone":36,"author":11,"publishedAt":37,"updatedAt":37,"readingMinutes":13,"featured":14,"tags":38,"category":42},63,"error-message-audience","Who Is the Error Message Written For?","'Operation failed, please retry' is the least useful message there is. Users need to know what happened and what they can do.","cyan","2026-05-12T14:49:00+08:00",[39,40,41],"Errors","UX","Product Design",{"id":43,"parentId":21,"slug":44,"name":45,"description":46,"icon":47,"cover":9,"tone":26,"kind":27,"sortOrder":48,"count":21},2,"product-thinking","Product Thinking","Requirement analysis, user experience and product design methods, plus the thinking from business problems to product solutions.","lightbulb",50,{"id":50,"slug":51,"title":52,"excerpt":53,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":54,"updatedAt":54,"readingMinutes":13,"featured":14,"tags":55,"category":59},102,"internal-training-design","Designing Internal Training That Works","Training that ends in forgetting is a ritual, not training. We send people in with a problem and out with an artefact.","2026-05-08T14:49:00+08:00",[56,57,58],"Team Culture","Training","Growth",{"id":60,"parentId":21,"slug":61,"name":62,"description":63,"icon":64,"cover":9,"tone":26,"kind":27,"sortOrder":65,"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,[67,77,87],{"id":68,"slug":69,"title":70,"excerpt":71,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":72,"updatedAt":72,"readingMinutes":13,"featured":14,"tags":73,"category":76},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.","2026-10-13T09:00:00+08:00",[16,74,75],"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":78,"slug":79,"title":80,"excerpt":81,"content":9,"cover":9,"tone":36,"author":11,"publishedAt":82,"updatedAt":82,"readingMinutes":13,"featured":14,"tags":83,"category":86},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.","2026-10-01T10:13:00+08:00",[16,84,85],"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":88,"slug":89,"title":90,"excerpt":91,"content":9,"cover":9,"tone":92,"author":11,"publishedAt":93,"updatedAt":93,"readingMinutes":13,"featured":14,"tags":94,"category":97},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",[16,95,96],"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}]