[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-cheap-usability-testing-zh-CN":3,"blog-adjacent-cheap-usability-testing-zh-CN":30,"blog-related-cheap-usability-testing-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},62,"cheap-usability-testing","可用性测试的廉价做法","不需要实验室和眼动仪，五个人、一台电脑、一小时，就能发现大部分问题。","\u003Cp>很多团队觉得可用性测试是大公司的流程，需要预算和专业设备。实际上，最早发现问题的方式非常朴素：找五个真实用户，看他们用一遍。\u003C\u002Fp>\n\u003Ch2>具体怎么做\u003C\u002Fh2>\n\u003Cp>准备三个真实任务，比如“新建一条订单并提交审批”，不要给操作提示。\u003C\u002Fp>\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-05-24T13:36: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},42,"offline-deployment-notes","局域网离线部署的注意事项","工厂、政务和大企业内部网络常常不能访问互联网，部署方式要为此重新设计。","slate","2026-05-26T13:36: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":10,"author":11,"publishedAt":53,"updatedAt":53,"readingMinutes":13,"featured":14,"tags":54,"category":58},82,"migration-three-runs","数据迁移复盘：十万条数据的三次重跑","第一次跑出错，第二次跑对不上数，第三次才通过。每次失败都暴露了不同的问题。","2026-05-22T13:36: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,76,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":75},"grading-requirement-confidence","需求的真实度分级","把需求当成事实来做，是项目延期最常见的原因。需求其实有可信度高低之分。","indigo","2026-10-15T09:00:00+08:00",[73,18,74],"需求","风险管理",{"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":70,"author":11,"publishedAt":80,"updatedAt":81,"readingMinutes":20,"featured":14,"tags":82,"category":85},"vertical-product-rules","垂直行业产品的分水岭：把行业默认规则写进系统","垂直不是换一个行业名字。真正的门槛，是能否理解并承接那些从业者习以为常的默认规则。","2026-10-09T10:00:00+08:00","2026-10-18T15:58:14.661+08:00",[83,84],"行业产品","产品设计",{"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,18,73],"MVP",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21}]