[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-change-request-cascade-en":3,"blog-adjacent-change-request-cascade-en":30,"blog-related-change-request-cascade-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},78,"change-request-cascade","Retrospective: The Cascade Behind One Change","Splitting 'customer' into enterprise and individual looked like one field. It touched six modules.","\u003Cp>In week seven the client asked for this change. We estimated three days; it affected six modules and took two extra weeks. We had assessed development but not data and process.\u003C\u002Fp>\n\u003Ch2>Cascading impacts we missed\u003C\u002Fh2>\n\u003Cp>Historical data migration, with three thousand of twenty thousand records impossible to classify automatically.\u003C\u002Fp>\n\u003Cp>Approval routing by customer type, which required adjusting three existing flows.\u003C\u002Fp>\n\u003Cp>Every report and export template changed, and the client had already submitted those templates upward.\u003C\u002Fp>\n\u003Ch2>Our checklist now\u003C\u002Fh2>\n\u003Cp>Every change is assessed across five dimensions: development, data migration, process impact, reporting impact and training.\u003C\u002Fp>\n\u003Cp>The assessment goes into the change request with schedule and cost, signed before work starts.\u003C\u002Fp>\n\u003Cp>Any change touching historical data structure is estimated on the worst case.\u003C\u002Fp>\n\u003Cp>Change is not the problem; underestimating it is. Counting the cascade also helps clients understand why time is needed.\u003C\u002Fp>","","cyan","佳益方圆团队","2026-07-09T09:44:00+08:00",1,false,[16,17,18],"Retrospective","Change","Delivery",{"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},58,"dashboard-metric-definition","Dashboards: Define the Metric Before Showing the Number","The same 'customer count' can mean three different things to sales, finance and operations.","teal","2026-07-11T09:44:00+08:00",[39,40,41],"Dashboards","Metrics","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},97,"overtime-tracking","Recording and Compensating Overtime","Neither glamorise nor ignore overtime. Treat it as a cost that must be visible.","indigo","2026-07-07T09:44:00+08:00",[57,58,59],"Team Culture","Overtime","Management",{"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,88],{"id":69,"slug":70,"title":71,"excerpt":72,"content":9,"cover":9,"tone":54,"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":10,"author":11,"publishedAt":83,"updatedAt":83,"readingMinutes":13,"featured":14,"tags":84,"category":87},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,85,86],"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":89,"slug":90,"title":91,"excerpt":92,"content":9,"cover":9,"tone":36,"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.","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}]