[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-onboarding-design-zh-CN":3,"blog-adjacent-onboarding-design-zh-CN":30,"blog-related-onboarding-design-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},68,"onboarding-design","新用户引导：让第一次使用就成功","引导的目标不是介绍所有功能，而是让用户完成一件有结果的事。","\u003Cp>后台系统的引导通常是三步弹窗加一段视频。用户点完“下一步”，依然不知道从哪里开始。真正有效的引导，是带用户完成第一个真实任务。\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>\n\u003Cp>引导的成败标准只有一个：新用户能否在十分钟内独立完成一件有价值的事。\u003C\u002Fp>","","teal","佳益方圆团队","2026-03-13T11:54: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":48},{"id":32,"slug":33,"title":34,"excerpt":35,"content":9,"cover":9,"tone":36,"author":11,"publishedAt":37,"updatedAt":37,"readingMinutes":13,"featured":14,"tags":38,"category":42},48,"miniapp-performance","小程序性能：首屏一秒内的取舍","小程序有包体积限制和启动开销，首屏优化更多是取舍而不是技巧。","cyan","2026-03-15T11:54:00+08:00",[39,40,41],"小程序","性能","前端",{"id":13,"parentId":21,"slug":43,"name":44,"description":45,"icon":46,"cover":9,"tone":26,"kind":27,"sortOrder":47,"count":21},"engineering","技术专栏","架构设计、性能优化、AI 集成与跨端方案等一线技术实践，由研发团队持续分享。","cpu",60,{"id":49,"slug":50,"title":51,"excerpt":52,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":53,"updatedAt":53,"readingMinutes":13,"featured":14,"tags":54,"category":58},88,"legacy-replacement-parallel-run","老系统替换复盘：并行运行的两个月","新旧系统同时运行两个月，多花了成本，却避免了一次可能致命的切换事故。","2026-03-11T11:54: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}]