[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-cheap-usability-testing-en":3,"blog-adjacent-cheap-usability-testing-en":30,"blog-related-cheap-usability-testing-en":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","Cheap Ways to Run Usability Tests","No lab and no eye tracker needed. Five people, one laptop and an hour reveal most problems.","\u003Cp>Many teams assume usability testing requires budget and equipment. The earliest way to find problems is plain: put five real users in front of the product and watch.\u003C\u002Fp>\n\u003Ch2>How to run it\u003C\u002Fh2>\n\u003Cp>Prepare three real tasks, such as creating an order and submitting it for approval, with no instructions.\u003C\u002Fp>\n\u003Cp>Ask users to think aloud; the observer takes notes without guiding and does not help when they get stuck.\u003C\u002Fp>\n\u003Cp>Record three things: completed or not, how long, and exactly where they stalled.\u003C\u002Fp>\n\u003Cp>Five users surface more than eighty percent of serious issues. A larger sample is unnecessary.\u003C\u002Fp>\n\u003Ch2>Common mistakes\u003C\u002Fh2>\n\u003Cp>Testing with colleagues. They already know the system and cannot reproduce a newcomer's confusion.\u003C\u002Fp>\n\u003Cp>Explaining while testing. The moment you explain, the problem disappears.\u003C\u002Fp>\n\u003Cp>Testing only happy paths. Real users' mistakes are the most valuable data.\u003C\u002Fp>\n\u003Cp>Usability testing costs far less than rework. Two hours before launch saves two months of patching after it.\u003C\u002Fp>","","teal","佳益方圆团队","2026-05-24T13:36:00+08:00",1,false,[16,17,18],"Usability","Research","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,{},{"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","Notes on Offline, Air-Gapped Deployment","Factory, government and large enterprise networks often cannot reach the internet, so deployment must be designed for it.","slate","2026-05-26T13:36:00+08:00",[39,40,41],"Deployment","Offline","Delivery",{"id":13,"parentId":21,"slug":43,"name":44,"description":45,"icon":46,"cover":9,"tone":26,"kind":27,"sortOrder":47,"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":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","Retrospective: Three Reruns for a Hundred Thousand Rows","The first run errored, the second disagreed on totals, the third passed. Each failure exposed a different problem.","2026-05-22T13:36:00+08:00",[55,56,57],"Retrospective","Migration","Legacy",{"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","Project Retrospectives","Real project records from zero to one, covering problems, solutions, lessons learned and final outcomes.","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","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",[73,18,74],"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":77,"title":78,"excerpt":79,"content":9,"cover":9,"tone":70,"author":11,"publishedAt":80,"updatedAt":81,"readingMinutes":13,"featured":14,"tags":82,"category":85},"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",[83,84],"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":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","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",[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}]