[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-compressed-schedule-cost-en":3,"blog-adjacent-compressed-schedule-cost-en":30,"blog-related-compressed-schedule-cost-en":67},{"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},77,"compressed-schedule-cost","Retrospective: The Cost of Compressed Testing","To hit a client's opening date we cut testing from three weeks to one, then spent six weeks fixing production.","\u003Cp>The client had a public commitment date and required launch that day. We agreed to compress testing from three weeks to one. The system was available on launch day, and we spent the next two months patching.\u003C\u002Fp>\n\u003Ch2>What surfaced after launch\u003C\u002Fh2>\n\u003Cp>Concurrent orders drove inventory negative, a gap that concurrency testing would have caught.\u003C\u002Fp>\n\u003Cp>The nightly settlement job mishandled time zones, so two days of reports did not reconcile.\u003C\u002Fp>\n\u003Cp>Some mobile pages showed blank screens on older browsers; compatibility testing was skipped entirely.\u003C\u002Fp>\n\u003Ch2>Lessons\u003C\u002Fh2>\n\u003Cp>If something must be compressed, compress scope and visuals, never testing of core flows.\u003C\u002Fp>\n\u003Cp>Assign two people to on-call during the first week so issues are closed the same day.\u003C\u002Fp>\n\u003Cp>Build buffer into quotes and schedules instead of discovering there is none when the client pushes.\u003C\u002Fp>\n\u003Cp>Schedules are negotiable; quality is not. The two weeks saved on testing were repaid with six weeks of fixes and a loss of trust.\u003C\u002Fp>","","slate","佳益方圆团队","2026-07-21T16:31:00+08:00",1,false,[16,17,18],"Retrospective","Schedule","Quality",{"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},57,"approval-flow-design","Approval Flows: Do Not Turn Organisational Problems Into Software Problems","Overlong approval chains usually reflect unclear authority, not poor workflow design.","indigo","2026-07-23T16:31:00+08:00",[39,40,41],"Approvals","Workflow","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":54,"author":11,"publishedAt":55,"updatedAt":55,"readingMinutes":13,"featured":14,"tags":56,"category":60},96,"continuous-feedback","Feedback Should Not Wait for Year-End","Criticism first heard in a year-end review is already six months late.","teal","2026-07-19T16:31:00+08:00",[57,58,59],"Team Culture","Feedback","Communication",{"id":61,"parentId":21,"slug":62,"name":63,"description":64,"icon":65,"cover":9,"tone":26,"kind":27,"sortOrder":66,"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,[68,78,89],{"id":69,"slug":70,"title":71,"excerpt":72,"content":9,"cover":9,"tone":36,"author":11,"publishedAt":73,"updatedAt":73,"readingMinutes":13,"featured":14,"tags":74,"category":77},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,75,76],"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":79,"slug":80,"title":81,"excerpt":82,"content":9,"cover":9,"tone":83,"author":11,"publishedAt":84,"updatedAt":84,"readingMinutes":13,"featured":14,"tags":85,"category":88},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,86,87],"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":90,"slug":91,"title":92,"excerpt":93,"content":9,"cover":9,"tone":54,"author":11,"publishedAt":94,"updatedAt":94,"readingMinutes":13,"featured":14,"tags":95,"category":98},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.","2026-09-19T11:26:00+08:00",[16,96,97],"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}]