[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-multi-vendor-integration-en":3,"blog-adjacent-multi-vendor-integration-en":30,"blog-related-multi-vendor-integration-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},74,"multi-vendor-integration","Retrospective: Three Vendors, One Project","In multi-party projects the most expensive cost is waiting and arguing, not development.","\u003Cp>We owned the middle platform, another vendor supplied hardware and a third provided industry software. Three contracts, one schedule. The project slipped two months and blame was hard to assign, but the lessons were clear.\u003C\u002Fp>\n\u003Ch2>Three collaboration problems\u003C\u002Fh2>\n\u003Cp>Unclear interface ownership. The hardware vendor expected us to adapt their format; we expected them to provide a standard output.\u003C\u002Fp>\n\u003Cp>Separate test environments. Each vendor built its own, versions diverged, and issues could not be reproduced.\u003C\u002Fp>\n\u003Cp>Meetings without conclusions. Every three-way call was thorough, but nobody recorded who would do what and when.\u003C\u002Fp>\n\u003Ch2>What we do now\u003C\u002Fh2>\n\u003Cp>At kickoff, an interface agreement lists fields, formats and owners, signed by all three parties.\u003C\u002Fp>\n\u003Cp>One shared test environment, maintained by the integrator, with vendors connecting only through agreed channels.\u003C\u002Fp>\n\u003Cp>Every meeting produces an action list with owners and deadlines; the next meeting reviews it first.\u003C\u002Fp>\n\u003Cp>Multi-party projects demand coordination more than coding. Writing responsibilities clearly protects the schedule better than writing elegant code.\u003C\u002Fp>","","slate","佳益方圆团队","2026-08-26T13:52:00+08:00",1,false,[16,17,18],"Retrospective","Integration","Collaboration",{"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":48},{"id":32,"slug":33,"title":34,"excerpt":35,"content":9,"cover":9,"tone":36,"author":11,"publishedAt":37,"updatedAt":38,"readingMinutes":13,"featured":14,"tags":39,"category":42},6,"design-handoff-contract","From Design File to Design System: Three Agreements with Engineering","Inconsistent spacing, missing states and duplicated components are rarely attitude problems. They usually mean the team never wrote down shared agreements before handoff.","indigo","2026-08-28T10:00:00+08:00","2026-10-18T15:58:14.717+08:00",[40,41],"Design Systems","Team Collaboration",{"id":13,"parentId":21,"slug":43,"name":44,"description":45,"icon":46,"cover":9,"tone":26,"kind":27,"sortOrder":47,"count":21},"engineering","Engineering","Hands-on engineering practices in architecture, performance optimization, AI integration and cross-platform delivery from our R and D team.","cpu",60,{"id":49,"slug":50,"title":51,"excerpt":52,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":53,"updatedAt":53,"readingMinutes":13,"featured":14,"tags":54,"category":57},93,"remote-work-boundaries","Boundaries in Remote Work","The hard part of remote work is not the tools; it is turning always-online into defined hours.","2026-08-24T13:52:00+08:00",[55,56,18],"Team Culture","Remote Work",{"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,75,85],{"id":66,"slug":67,"title":68,"excerpt":69,"content":9,"cover":9,"tone":36,"author":11,"publishedAt":70,"updatedAt":70,"readingMinutes":13,"featured":14,"tags":71,"category":74},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,72,73],"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":76,"slug":77,"title":78,"excerpt":79,"content":9,"cover":9,"tone":80,"author":11,"publishedAt":81,"updatedAt":81,"readingMinutes":13,"featured":14,"tags":82,"category":84},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,83,17],"Manufacturing",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":86,"slug":87,"title":88,"excerpt":89,"content":9,"cover":9,"tone":90,"author":11,"publishedAt":91,"updatedAt":91,"readingMinutes":13,"featured":14,"tags":92,"category":95},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,93,94],"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}]