[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-user-interview-questions-en":3,"blog-related-user-interview-questions-en":30,"blog-adjacent-user-interview-questions-en":60},{"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","Three Questions Worth Asking in User Interviews","Asking what people want yields imagination; asking what they did last time yields facts.","\u003Cp>The most common research mistake is mistaking imagination for requirement. Users happily describe an ideal system but rarely recall precisely what they did last month. Our interview outline is built around past behaviour.\u003C\u002Fp>\n\u003Ch2>The three questions\u003C\u002Fh2>\n\u003Cp>When did you last hit this problem, and what exactly happened? It pulls the conversation from abstraction into fact.\u003C\u002Fp>\n\u003Cp>How did you solve it? Which tools, which people, how long? The real pain usually hides in this answer.\u003C\u002Fp>\n\u003Cp>What would you do if the system broke tomorrow? It reveals how much the business actually depends on it.\u003C\u002Fp>\n\u003Ch2>Two rules while interviewing\u003C\u002Fh2>\n\u003Cp>Do not interrupt and do not pitch a solution. Useful information appears while users describe details.\u003C\u002Fp>\n\u003Cp>Record their words, not your summary. Summaries quietly absorb your own assumptions.\u003C\u002Fp>\n\u003Cp>A good interview leaves you with a record of concrete behaviour, not a wish list of features.\u003C\u002Fp>","","teal","佳益方圆团队","2026-09-21T11:26:00+08:00",1,false,[16,17,18],"Research","Interviews","Product",{"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","Product Thinking","Requirement analysis, user experience and product design methods, plus the thinking from business problems to product solutions.","lightbulb","blue","article",50,{},[31,41,51],{"id":28,"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":40},"grading-requirement-confidence","Grading the Confidence Behind Requirements","Treating requirements as facts is the most common cause of delay. Requirements differ in how reliable they are.","indigo","2026-10-15T09:00:00+08:00",[38,18,39],"Requirements","Risk",{"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":42,"title":43,"excerpt":44,"content":9,"cover":9,"tone":35,"author":11,"publishedAt":45,"updatedAt":46,"readingMinutes":13,"featured":14,"tags":47,"category":50},"vertical-product-rules","The Watershed for Vertical Products: Writing Industry Defaults into the System","Vertical is not a new industry label on a generic product. The real barrier is understanding and carrying the default rules that practitioners take for granted.","2026-10-09T10:00:00+08:00","2026-10-18T15:58:14.661+08:00",[48,49],"Industry Products","Product Design",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":52,"slug":53,"title":54,"excerpt":55,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":56,"updatedAt":56,"readingMinutes":13,"featured":14,"tags":57,"category":59},51,"mvp-boundary","Drawing the Boundary of an MVP","Minimum viable is not the fewest features; it is one complete business loop running end to end.","2026-10-03T10:13:00+08:00",[58,18,38],"MVP",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"previous":61,"next":77},{"id":62,"slug":63,"title":64,"excerpt":65,"content":9,"cover":9,"tone":35,"author":11,"publishedAt":66,"updatedAt":66,"readingMinutes":13,"featured":14,"tags":67,"category":71},32,"rbac-to-data-permissions","Permissions: From Roles to Data Scope","Most admin systems stop at menus and buttons. The hard part is showing each person only the data they should see.","2026-09-23T11:26:00+08:00",[68,69,70],"Permissions","Admin","Architecture",{"id":13,"parentId":21,"slug":72,"name":73,"description":74,"icon":75,"cover":9,"tone":26,"kind":27,"sortOrder":76,"count":21},"engineering","Engineering","Hands-on engineering practices in architecture, performance optimization, AI integration and cross-platform delivery from our R and D team.","cpu",60,{"id":78,"slug":79,"title":80,"excerpt":81,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":82,"updatedAt":82,"readingMinutes":13,"featured":14,"tags":83,"category":87},72,"cross-border-site-retro","Retrospective: Traffic Arrived, Enquiries Did Not","Ads ran normally after launch but enquiries stayed low. The review found trust and form friction were the blockers.","2026-09-19T11:26:00+08:00",[84,85,86],"Retrospective","Cross-border","Conversion",{"id":88,"parentId":21,"slug":89,"name":90,"description":91,"icon":92,"cover":9,"tone":26,"kind":27,"sortOrder":93,"count":21},3,"project-retrospective","Project Retrospectives","Real project records from zero to one, covering problems, solutions, lessons learned and final outcomes.","clipboard-check",40]