[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-user-interview-questions-zh-CN":3,"blog-adjacent-user-interview-questions-zh-CN":30,"blog-related-user-interview-questions-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},52,"user-interview-questions","用户访谈里最该问的三个问题","问“你想要什么”得到的是想象，问“你上次怎么做”得到的才是事实。","\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>","","teal","佳益方圆团队","2026-09-21T11:26: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},32,"rbac-to-data-permissions","权限模型：从角色控制到数据权限","多数后台的权限停在菜单和按钮层面，真正难的是让不同的人只看到自己该看的数据。","indigo","2026-09-23T11:26: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},72,"cross-border-site-retro","跨境独立站复盘：流量到了，转化没到","网站上线后广告投放正常，询盘却很少。复盘发现，问题集中在信任和填写成本上。","2026-09-19T11:26: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,75,85],{"id":28,"slug":67,"title":68,"excerpt":69,"content":9,"cover":9,"tone":36,"author":11,"publishedAt":70,"updatedAt":70,"readingMinutes":13,"featured":14,"tags":71,"category":74},"grading-requirement-confidence","需求的真实度分级","把需求当成事实来做，是项目延期最常见的原因。需求其实有可信度高低之分。","2026-10-15T09:00:00+08:00",[72,18,73],"需求","风险管理",{"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":76,"title":77,"excerpt":78,"content":9,"cover":9,"tone":36,"author":11,"publishedAt":79,"updatedAt":80,"readingMinutes":20,"featured":14,"tags":81,"category":84},"vertical-product-rules","垂直行业产品的分水岭：把行业默认规则写进系统","垂直不是换一个行业名字。真正的门槛，是能否理解并承接那些从业者习以为常的默认规则。","2026-10-09T10:00:00+08:00","2026-10-18T15:58:14.661+08:00",[82,83],"行业产品","产品设计",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":86,"slug":87,"title":88,"excerpt":89,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":90,"updatedAt":90,"readingMinutes":13,"featured":14,"tags":91,"category":93},51,"mvp-boundary","MVP 的边界怎么划","最小可用不是功能最少，而是能完整跑通一条业务闭环。","2026-10-03T10:13:00+08:00",[92,18,72],"MVP",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21}]