[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-dashboard-metric-definition-en":3,"blog-adjacent-dashboard-metric-definition-en":30,"blog-related-dashboard-metric-definition-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},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.","\u003Cp>We built a sales dashboard and three departments each reported wrong numbers. Sales counted signed customers, finance counted collected payments, operations counted registrations. All three were right, with different definitions.\u003C\u002Fp>\n\u003Ch2>Define metrics down to the field\u003C\u002Fh2>\n\u003Cp>Name, definition, time range and exclusion rules, all four. 'New customers' must state whether trials count and whether the date is signing or payment.\u003C\u002Fp>\n\u003Cp>Store definitions in a metric dictionary inside the product, viewable from the page, instead of relying on verbal explanation.\u003C\u002Fp>\n\u003Ch2>Three dashboard habits\u003C\u002Fh2>\n\u003Cp>One screen answers one question. Too many metrics and nobody knows where to look.\u003C\u002Fp>\n\u003Cp>Numbers must drill down. Being able to open the detail behind an anomaly beats ten more charts.\u003C\u002Fp>\n\u003Cp>State the refresh time. A two-hour delay and real-time updates lead to completely different decisions.\u003C\u002Fp>\n\u003Cp>A dashboard is not about beautiful charts. It is about everyone reading the same number the same way.\u003C\u002Fp>","","teal","佳益方圆团队","2026-07-11T09:44:00+08:00",1,false,[16,17,18],"Dashboards","Metrics","Product Design",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},2,0,"product-thinking","Product Thinking","Requirement analysis, user experience and product design methods, plus the thinking from business problems to product solutions.","lightbulb","blue","article",50,{},{"previous":31,"next":46},{"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":41},38,"message-queue-tradeoffs","Message Queues Are Not a Cure-All","A queue decouples and absorbs spikes, and also introduces duplicates, ordering and observability problems.","2026-07-13T09:44:00+08:00",[38,39,40],"Architecture","Queues","Engineering",{"id":13,"parentId":21,"slug":42,"name":40,"description":43,"icon":44,"cover":9,"tone":26,"kind":27,"sortOrder":45,"count":21},"engineering","Hands-on engineering practices in architecture, performance optimization, AI integration and cross-platform delivery from our R and D team.","cpu",60,{"id":47,"slug":48,"title":49,"excerpt":50,"content":9,"cover":9,"tone":51,"author":11,"publishedAt":52,"updatedAt":52,"readingMinutes":13,"featured":14,"tags":53,"category":57},78,"change-request-cascade","Retrospective: The Cascade Behind One Change","Splitting 'customer' into enterprise and individual looked like one field. It touched six modules.","cyan","2026-07-09T09:44:00+08:00",[54,55,56],"Retrospective","Change","Delivery",{"id":58,"parentId":21,"slug":59,"name":60,"description":61,"icon":62,"cover":9,"tone":26,"kind":27,"sortOrder":63,"count":21},3,"project-retrospective","Project Retrospectives","Real project records from zero to one, covering problems, solutions, lessons learned and final outcomes.","clipboard-check",40,[65,76,85],{"id":28,"slug":66,"title":67,"excerpt":68,"content":9,"cover":9,"tone":69,"author":11,"publishedAt":70,"updatedAt":70,"readingMinutes":13,"featured":14,"tags":71,"category":75},"grading-requirement-confidence","Grading the Confidence Behind Requirements","Treating requirements as facts is the most common cause of delay. Requirements differ in how reliable they are.","indigo","2026-10-15T09:00:00+08:00",[72,73,74],"Requirements","Product","Risk",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":20,"slug":77,"title":78,"excerpt":79,"content":9,"cover":9,"tone":69,"author":11,"publishedAt":80,"updatedAt":81,"readingMinutes":13,"featured":14,"tags":82,"category":84},"vertical-product-rules","The Watershed for Vertical Products: Writing Industry Defaults into the System","Vertical is not a new industry label on a generic product. The real barrier is understanding and carrying the default rules that practitioners take for granted.","2026-10-09T10:00:00+08:00","2026-10-18T15:58:14.661+08:00",[83,18],"Industry Products",{"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":26,"author":11,"publishedAt":90,"updatedAt":90,"readingMinutes":13,"featured":14,"tags":91,"category":93},51,"mvp-boundary","Drawing the Boundary of an MVP","Minimum viable is not the fewest features; it is one complete business loop running end to end.","2026-10-03T10:13:00+08:00",[92,73,72],"MVP",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21}]