[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-gov-project-acceptance-en":3,"blog-adjacent-gov-project-acceptance-en":30,"blog-related-gov-project-acceptance-en":64},{"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},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.","\u003Cp>This project finished development in 2023, ran in production for half a year, and only then completed acceptance. Looking back, almost none of the delay was technical: incomplete documents, unclear process and a change of counterpart.\u003C\u002Fp>\n\u003Ch2>Three direct causes\u003C\u002Fh2>\n\u003Cp>Acceptance material was prepared late. Government projects need test reports, security scans and manuals, and we started assembling them after launch, which took over a month.\u003C\u002Fp>\n\u003Cp>The client's owner changed mid-project. The new owner did not know earlier agreements, so many points were reopened.\u003C\u002Fp>\n\u003Cp>The security assessment queue. The third-party assessor had no slot for six weeks.\u003C\u002Fp>\n\u003Ch2>What we changed\u003C\u002Fh2>\n\u003Cp>Acceptance documents are now planned as deliverables produced during development, not after launch.\u003C\u002Fp>\n\u003Cp>Key meetings produce written minutes confirmed by both sides, so a change of personnel can be handed over cleanly.\u003C\u002Fp>\n\u003Cp>Third-party assessment windows are identified early and placed on the critical path.\u003C\u002Fp>\n\u003Cp>Government acceptance is an exam in documents and process. Good engineering is only a pass; prepared paperwork is what finishes it.\u003C\u002Fp>","","indigo","佳益方圆团队","2026-10-13T09:00:00+08:00",1,false,[16,17,18],"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},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":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":41},50,"grading-requirement-confidence","Grading the Confidence Behind Requirements","Treating requirements as facts is the most common cause of delay. Requirements differ in how reliable they are.","2026-10-15T09:00:00+08:00",[38,39,40],"Requirements","Product","Risk",{"id":42,"parentId":21,"slug":43,"name":44,"description":45,"icon":46,"cover":9,"tone":26,"kind":27,"sortOrder":32,"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",{"id":48,"slug":49,"title":50,"excerpt":51,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":52,"updatedAt":52,"readingMinutes":13,"featured":14,"tags":53,"category":57},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",[54,55,56],"Team Culture","Knowledge Sharing","Growth",{"id":58,"parentId":21,"slug":59,"name":60,"description":61,"icon":62,"cover":9,"tone":26,"kind":27,"sortOrder":63,"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,[65,76,87],{"id":66,"slug":67,"title":68,"excerpt":69,"content":9,"cover":9,"tone":70,"author":11,"publishedAt":71,"updatedAt":71,"readingMinutes":13,"featured":14,"tags":72,"category":75},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",[16,73,74],"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":77,"slug":78,"title":79,"excerpt":80,"content":9,"cover":9,"tone":81,"author":11,"publishedAt":82,"updatedAt":82,"readingMinutes":13,"featured":14,"tags":83,"category":86},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,84,85],"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},{"id":88,"slug":89,"title":90,"excerpt":91,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":92,"updatedAt":92,"readingMinutes":13,"featured":14,"tags":93,"category":96},73,"miniapp-launch-retro","Retrospective: Launch Day Is Not the Finish Line","Users arrived on launch day and so did the problems. We now include post-launch operations in scope.","2026-09-07T12:39:00+08:00",[16,94,95],"Mini Program","Operations",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21}]