[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-acceptance-dispute-retro-en":3,"blog-related-acceptance-dispute-retro-en":30,"blog-adjacent-acceptance-dispute-retro-en":62},{"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},79,"acceptance-dispute-retro","Retrospective: The Cost of Vague Acceptance Criteria","The system was finished and the client said it was not what they wanted. Every argument returned to one line: it was never specified.","\u003Cp>Development went smoothly and every listed feature was delivered. At acceptance the client said the workflow did not match their habits and asked for major changes. The dispute ran three weeks and ended in compromise, with the relationship damaged.\u003C\u002Fp>\n\u003Ch2>Where the dispute came from\u003C\u002Fh2>\n\u003Cp>The requirement document listed features but not flows, such as who clicks what in which state.\u003C\u002Fp>\n\u003Cp>In prototype review the client looked at layout, not process.\u003C\u002Fp>\n\u003Cp>Acceptance criteria had no usability clause, blurring the line between working and workable.\u003C\u002Fp>\n\u003Ch2>What we do now\u003C\u002Fh2>\n\u003Cp>Requirement sign-off includes flow diagrams and role descriptions, confirmed item by item.\u003C\u002Fp>\n\u003Cp>Prototype review requires the client to click through the main flow, not look at screenshots.\u003C\u002Fp>\n\u003Cp>Acceptance checklists include usability items, such as a maximum number of steps for a typical task.\u003C\u002Fp>\n\u003Cp>Acceptance disputes are rarely bad faith; they are insufficient confirmation earlier. Confirming flows beats writing ten more pages.\u003C\u002Fp>","","indigo","佳益方圆团队","2026-06-27T10:57:00+08:00",1,false,[16,17,18],"Retrospective","Acceptance","Requirements",{"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,40,51],{"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":39},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,38,17],"Government",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":41,"slug":42,"title":43,"excerpt":44,"content":9,"cover":9,"tone":45,"author":11,"publishedAt":46,"updatedAt":46,"readingMinutes":13,"featured":14,"tags":47,"category":50},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,48,49],"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":52,"slug":53,"title":54,"excerpt":55,"content":9,"cover":9,"tone":56,"author":11,"publishedAt":57,"updatedAt":57,"readingMinutes":13,"featured":14,"tags":58,"category":61},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,59,60],"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":63,"next":81},{"id":64,"slug":65,"title":66,"excerpt":67,"content":9,"cover":9,"tone":68,"author":11,"publishedAt":69,"updatedAt":69,"readingMinutes":13,"featured":14,"tags":70,"category":74},59,"ai-feature-positioning","Positioning an AI Feature","Treating a large model as a universal assistant usually produces features nobody uses. Start from a specific task.","slate","2026-06-29T10:57:00+08:00",[71,72,73],"AI","Positioning","Adoption",{"id":75,"parentId":21,"slug":76,"name":77,"description":78,"icon":79,"cover":9,"tone":26,"kind":27,"sortOrder":80,"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":82,"slug":83,"title":84,"excerpt":85,"content":9,"cover":9,"tone":68,"author":11,"publishedAt":86,"updatedAt":86,"readingMinutes":13,"featured":14,"tags":87,"category":91},98,"knowledge-base-habit","A Knowledge Base Is a Habit","A knowledge base does not get used because it exists. It exists when every problem starts there.","2026-06-25T10:57:00+08:00",[88,89,90],"Team Culture","Knowledge Management","Documentation",{"id":92,"parentId":21,"slug":93,"name":94,"description":95,"icon":96,"cover":9,"tone":26,"kind":27,"sortOrder":97,"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]