[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-empty-states-in-b2b-zh-CN":3,"blog-adjacent-empty-states-in-b2b-zh-CN":29,"blog-related-empty-states-in-b2b-zh-CN":58},{"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},55,"empty-states-in-b2b","B 端产品的空状态","用户第一次进入系统时看到的不是功能，而是一片空白。空状态决定了他们能否开始。","\u003Cp>做 C 端产品时，空状态通常是一个插画加一句引导语。B 端不一样：用户打开列表页看到空白，第一反应往往是“系统坏了”或者“我是不是没有权限”。\u003C\u002Fp>\n\u003Ch2>空状态要回答三个问题\u003C\u002Fh2>\n\u003Cp>为什么是空的？是没有数据、没有权限，还是筛选条件太严？三种原因必须区分。\u003C\u002Fp>\n\u003Cp>我怎么开始？给出明确动作，比如新建第一条记录、导入模板或申请权限。\u003C\u002Fp>\n\u003Cp>空白是否正常？有些页面在业务初期确实没有数据，需要说明这是预期状态。\u003C\u002Fp>\n\u003Ch2>一个常见错误\u003C\u002Fh2>\n\u003Cp>把“暂无数据”当成万能文案。用户看到这五个字，既不知道原因，也不知道下一步。\u003C\u002Fp>\n\u003Cp>我们的做法是按场景准备三套文案：筛选无结果、暂未创建、无访问权限，并分别给出操作入口。\u003C\u002Fp>\n\u003Cp>空状态是用户与系统的第一次对话。把它写清楚，比多加两个按钮更有价值。\u003C\u002Fp>","","blue","佳益方圆团队","2026-08-16T14:05:00+08:00",1,false,[16,17,18],"B 端","体验","空状态",{"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":47},{"id":31,"slug":32,"title":33,"excerpt":34,"content":9,"cover":9,"tone":35,"author":11,"publishedAt":36,"updatedAt":36,"readingMinutes":13,"featured":14,"tags":37,"category":41},35,"frontend-monitoring-basics","前端监控：等白屏了才知道","用户不会告诉你页面打不开，他们只会离开。前端监控应该在上线前就位。","slate","2026-08-18T14:05:00+08:00",[38,39,40],"前端","监控","运维",{"id":13,"parentId":21,"slug":42,"name":43,"description":44,"icon":45,"cover":9,"tone":10,"kind":26,"sortOrder":46,"count":21},"engineering","技术专栏","架构设计、性能优化、AI 集成与跨端方案等一线技术实践，由研发团队持续分享。","cpu",60,{"id":48,"slug":49,"title":50,"excerpt":51,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":52,"updatedAt":53,"readingMinutes":13,"featured":14,"tags":54,"category":57},7,"dashboard-that-gets-used","让经营看板真正被使用：三个设计原则","看板失败通常不是数据不准，而是它只回答了“发生了什么”，没有回答“现在该做什么”。","2026-08-15T09:00:00+08:00","2026-10-18T15:58:14.731+08:00",[55,56],"数据产品","经营分析",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21},[59,70,80],{"id":27,"slug":60,"title":61,"excerpt":62,"content":9,"cover":9,"tone":63,"author":11,"publishedAt":64,"updatedAt":64,"readingMinutes":13,"featured":14,"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":14,"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":13,"featured":14,"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}]