[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-dashboard-that-gets-used-zh-CN":3,"blog-adjacent-dashboard-that-gets-used-zh-CN":29,"blog-related-dashboard-that-gets-used-zh-CN":58},{"id":4,"slug":5,"title":6,"excerpt":7,"content":8,"cover":9,"tone":10,"author":11,"publishedAt":12,"updatedAt":13,"readingMinutes":14,"featured":15,"tags":16,"category":19,"seoSettings":28},7,"dashboard-that-gets-used","让经营看板真正被使用：三个设计原则","看板失败通常不是数据不准，而是它只回答了“发生了什么”，没有回答“现在该做什么”。","\u003Cp>几乎每个管理系统都有看板，但真正被日常使用的并不多。原因通常不是数据不准，而是看板回答了“发生了什么”，却没有回答“我现在该做什么”。\u003C\u002Fp>\n\u003Ch2>原则一：一屏只回答一个问题\u003C\u002Fh2>\n\u003Cp>把销售额、库存、客流、满意度全部塞进一屏，结果是谁都看不清重点。更好的做法是按角色拆分：店长看当日经营与异常，区域经理看门店对比，老板看趋势与结构。\u003C\u002Fp>\n\u003Ch2>原则二：把对比放在同一视线\u003C\u002Fh2>\n\u003Cp>单独一个数字没有意义。同比、环比、目标完成率、同类门店对比，能帮助使用者快速判断“这个数字是好还是坏”。对比维度要稳定，避免每次打开口径都不一样。\u003C\u002Fp>\n\u003Ch2>原则三：给出下一步动作\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>库存低于安全线时，直接给出补货入口；\u003C\u002Fli>\n\u003Cli>转化率异常时，能下钻到具体渠道与页面；\u003C\u002Fli>\n\u003Cli>客诉集中时，能查看相关订单与处理进度。\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cblockquote>看板的价值，不在于展示多少数据，而在于帮助使用者更快做出一个正确的决定。\u003C\u002Fblockquote>\n\u003Cp>在项目里，我们通常先和一线使用者一起看一周的旧报表，找出他们真正反复查看的几项，再开始设计。这样做出的看板，使用率往往更高。\u003C\u002Fp>","","blue","佳益方圆团队","2026-08-15T09:00:00+08:00","2026-10-18T15:58:14.731+08:00",1,false,[17,18],"数据产品","经营分析",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21},2,0,"product-thinking","产品思维","需求分析、用户体验与产品设计方法论，以及从业务问题到产品方案的思考过程。","lightbulb","article",50,{},{"previous":30,"next":41},{"id":31,"slug":32,"title":33,"excerpt":34,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":35,"updatedAt":35,"readingMinutes":14,"featured":15,"tags":36,"category":40},55,"empty-states-in-b2b","B 端产品的空状态","用户第一次进入系统时看到的不是功能，而是一片空白。空状态决定了他们能否开始。","2026-08-16T14:05:00+08:00",[37,38,39],"B 端","体验","空状态",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21},{"id":42,"slug":43,"title":44,"excerpt":45,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":46,"updatedAt":46,"readingMinutes":14,"featured":15,"tags":47,"category":51},75,"dashboard-adoption-retro","数据看板复盘：上线三个月没人看","看板做得漂亮，领导也点赞，但三个月后打开率接近于零。","2026-08-14T14:05:00+08:00",[48,49,50],"复盘","数据看板","零售",{"id":52,"parentId":21,"slug":53,"name":54,"description":55,"icon":56,"cover":9,"tone":10,"kind":26,"sortOrder":57,"count":21},3,"project-retrospective","项目复盘","从 0 到 1 的真实项目记录，完整呈现问题、方案、踩坑经验与最终结果。","clipboard-check",40,[59,70,80],{"id":27,"slug":60,"title":61,"excerpt":62,"content":9,"cover":9,"tone":63,"author":11,"publishedAt":64,"updatedAt":64,"readingMinutes":14,"featured":15,"tags":65,"category":69},"grading-requirement-confidence","需求的真实度分级","把需求当成事实来做，是项目延期最常见的原因。需求其实有可信度高低之分。","indigo","2026-10-15T09:00:00+08:00",[66,67,68],"需求","产品方法","风险管理",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21},{"id":20,"slug":71,"title":72,"excerpt":73,"content":9,"cover":9,"tone":63,"author":11,"publishedAt":74,"updatedAt":75,"readingMinutes":20,"featured":15,"tags":76,"category":79},"vertical-product-rules","垂直行业产品的分水岭：把行业默认规则写进系统","垂直不是换一个行业名字。真正的门槛，是能否理解并承接那些从业者习以为常的默认规则。","2026-10-09T10:00:00+08:00","2026-10-18T15:58:14.661+08:00",[77,78],"行业产品","产品设计",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21},{"id":81,"slug":82,"title":83,"excerpt":84,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":85,"updatedAt":85,"readingMinutes":14,"featured":15,"tags":86,"category":88},51,"mvp-boundary","MVP 的边界怎么划","最小可用不是功能最少，而是能完整跑通一条业务闭环。","2026-10-03T10:13:00+08:00",[87,67,66],"MVP",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21}]