[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-dashboard-adoption-retro-en":3,"blog-adjacent-dashboard-adoption-retro-en":29,"blog-related-dashboard-adoption-retro-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":28},75,"dashboard-adoption-retro","Retrospective: A Dashboard Nobody Opened","The dashboard looked great and leadership applauded. Three months later its open rate was close to zero.","\u003Cp>We built an operations dashboard for a retail client. The launch demo went well. A follow-up three months later showed fewer than ten visits a day, half of them our own tests.\u003C\u002Fp>\n\u003Ch2>Why nobody used it\u003C\u002Fh2>\n\u003Cp>The metrics were not decision inputs. The numbers looked good but did not imply an action, so store managers kept ordering on instinct.\u003C\u002Fp>\n\u003Cp>Reaching it took a login and three menu levels, and the mobile experience was worse.\u003C\u002Fp>\n\u003Cp>Data refreshed a day late, which is useless for daily ordering.\u003C\u002Fp>\n\u003Ch2>What version two changed\u003C\u002Fh2>\n\u003Cp>Metrics became action-oriented: instead of total sales, the dashboard shows SKUs that need replenishment and suggested quantities.\u003C\u002Fp>\n\u003Cp>A summary card is pushed through the company chat every morning, linking straight to the detail.\u003C\u002Fp>\n\u003Cp>Extraction runs hourly, making key metrics near real time.\u003C\u002Fp>\n\u003Cp>A dashboard earns its place by driving decisions, not by showing data. If it cannot answer what to do next, nobody opens it.\u003C\u002Fp>","","blue","佳益方圆团队","2026-08-14T14:05:00+08:00",1,false,[16,17,18],"Retrospective","Dashboard","Retail",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"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","article",40,{},{"previous":30,"next":47},{"id":31,"slug":32,"title":33,"excerpt":34,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":35,"updatedAt":36,"readingMinutes":13,"featured":14,"tags":37,"category":40},7,"dashboard-that-gets-used","Making Dashboards Actually Used: Three Design Principles","Dashboards usually fail not because the data is wrong, but because they only answer what happened and never answer what should I do now.","2026-08-15T09:00:00+08:00","2026-10-18T15:58:14.731+08:00",[38,39],"Data Products","Business Analysis",{"id":41,"parentId":21,"slug":42,"name":43,"description":44,"icon":45,"cover":9,"tone":10,"kind":26,"sortOrder":46,"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":48,"slug":49,"title":50,"excerpt":51,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":52,"updatedAt":52,"readingMinutes":13,"featured":14,"tags":53,"category":57},94,"tech-sharing-day","A Quarterly Tech Sharing Day","Thirty minutes a week is not always enough, so we take half a day, mute notifications and talk shop properly.","2026-08-12T14:05:00+08:00",[54,55,56],"Team Culture","Knowledge Sharing","Organisation",{"id":58,"parentId":21,"slug":59,"name":60,"description":61,"icon":62,"cover":9,"tone":10,"kind":26,"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},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.","indigo","2026-10-13T09:00:00+08:00",[16,73,74],"Government","Acceptance",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"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},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,84,85],"Manufacturing","Integration",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21},{"id":88,"slug":89,"title":90,"excerpt":91,"content":9,"cover":9,"tone":92,"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.","teal","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":10,"kind":26,"sortOrder":27,"count":21}]