[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-dashboard-metric-definition-zh-CN":3,"blog-adjacent-dashboard-metric-definition-zh-CN":30,"blog-related-dashboard-metric-definition-zh-CN":65},{"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","看板指标：先定义再看数","同一个“客户数”，销售、财务和运营的理解可能完全不同。","\u003Cp>做过一个销售看板，上线后三个部门各自反馈数字不对。排查发现：销售算的是签约客户，财务算的是回款客户，运营算的是注册客户。三个数字都对，只是口径不同。\u003C\u002Fp>\n\u003Ch2>指标定义要写到字段级\u003C\u002Fh2>\n\u003Cp>名称、口径、时间范围、排除规则，四项缺一不可。比如“新增客户数”要说明是否包含试用、是否按签约时间统计。\u003C\u002Fp>\n\u003Cp>定义写进系统的指标字典，页面上可以点开查看，避免靠口头解释。\u003C\u002Fp>\n\u003Ch2>看板设计的三条经验\u003C\u002Fh2>\n\u003Cp>一屏只回答一个问题。指标太多，用户反而不知道该看什么。\u003C\u002Fp>\n\u003Cp>数字要可下钻。看到异常能点进去看明细，比再多加十个图表有用。\u003C\u002Fp>\n\u003Cp>更新时间写清楚。数据延迟两小时和实时更新，用户的决策方式完全不同。\u003C\u002Fp>\n\u003Cp>看板的价值不在于图表精美，而在于所有人对同一个数字有一致的理解。\u003C\u002Fp>","","teal","佳益方圆团队","2026-07-11T09:44:00+08:00",1,false,[16,17,18],"数据看板","指标","产品设计",{"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","产品思维","需求分析、用户体验与产品设计方法论，以及从业务问题到产品方案的思考过程。","lightbulb","blue","article",50,{},{"previous":31,"next":47},{"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","消息队列不是万能药","引入队列能解决耦合和削峰，也会带来重复、顺序和可观测性三类新问题。","2026-07-13T09:44:00+08:00",[38,39,40],"架构","消息队列","工程实践",{"id":13,"parentId":21,"slug":42,"name":43,"description":44,"icon":45,"cover":9,"tone":26,"kind":27,"sortOrder":46,"count":21},"engineering","技术专栏","架构设计、性能优化、AI 集成与跨端方案等一线技术实践，由研发团队持续分享。","cpu",60,{"id":48,"slug":49,"title":50,"excerpt":51,"content":9,"cover":9,"tone":52,"author":11,"publishedAt":53,"updatedAt":53,"readingMinutes":13,"featured":14,"tags":54,"category":58},78,"change-request-cascade","需求变更复盘：一次改动的连锁反应","客户要求把“客户”拆成“企业客户”和“个人客户”，看起来只是加一个字段。","cyan","2026-07-09T09:44:00+08:00",[55,56,57],"复盘","需求变更","项目管理",{"id":59,"parentId":21,"slug":60,"name":61,"description":62,"icon":63,"cover":9,"tone":26,"kind":27,"sortOrder":64,"count":21},3,"project-retrospective","项目复盘","从 0 到 1 的真实项目记录，完整呈现问题、方案、踩坑经验与最终结果。","clipboard-check",40,[66,77,86],{"id":28,"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":76},"grading-requirement-confidence","需求的真实度分级","把需求当成事实来做，是项目延期最常见的原因。需求其实有可信度高低之分。","indigo","2026-10-15T09:00:00+08:00",[73,74,75],"需求","产品方法","风险管理",{"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":78,"title":79,"excerpt":80,"content":9,"cover":9,"tone":70,"author":11,"publishedAt":81,"updatedAt":82,"readingMinutes":20,"featured":14,"tags":83,"category":85},"vertical-product-rules","垂直行业产品的分水岭：把行业默认规则写进系统","垂直不是换一个行业名字。真正的门槛，是能否理解并承接那些从业者习以为常的默认规则。","2026-10-09T10:00:00+08:00","2026-10-18T15:58:14.661+08:00",[84,18],"行业产品",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":87,"slug":88,"title":89,"excerpt":90,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":91,"updatedAt":91,"readingMinutes":13,"featured":14,"tags":92,"category":94},51,"mvp-boundary","MVP 的边界怎么划","最小可用不是功能最少，而是能完整跑通一条业务闭环。","2026-10-03T10:13:00+08:00",[93,74,73],"MVP",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21}]