[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-onboarding-design-en":3,"blog-related-onboarding-design-en":30,"blog-adjacent-onboarding-design-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},68,"onboarding-design","Onboarding: Make the First Use Successful","The goal is not to introduce every feature, but to get the user through one task with a real outcome.","\u003Cp>Admin onboarding is usually a three-step modal plus a video. Users click next and still do not know where to start. Onboarding that works walks the user through their first real task.\u003C\u002Fp>\n\u003Ch2>Three layers\u003C\u002Fh2>\n\u003Cp>First sign-in: explain what problem the system solves and where to begin.\u003C\u002Fp>\n\u003Cp>First task: complete one flow with real data, such as creating a record and submitting it.\u003C\u002Fp>\n\u003Cp>First result: show the outcome, whether a generated report or a sent notification, to close the loop.\u003C\u002Fp>\n\u003Ch2>Design details\u003C\u002Fh2>\n\u003Cp>Provide sample data so users can try things before deciding to clear it, which beats an empty page.\u003C\u002Fp>\n\u003Cp>Place help next to the action, not only in a help centre in the top corner.\u003C\u002Fp>\n\u003Cp>Record where users get stuck and use it to prioritise the next release.\u003C\u002Fp>\n\u003Cp>Onboarding has one success criterion: a new user independently completes something valuable within ten minutes.\u003C\u002Fp>","","teal","佳益方圆团队","2026-03-13T11:54:00+08:00",1,false,[16,17,18],"Onboarding","New Users","Product Design",{"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,42,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":41},"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,39,40],"Requirements","Product","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":43,"title":44,"excerpt":45,"content":9,"cover":9,"tone":35,"author":11,"publishedAt":46,"updatedAt":47,"readingMinutes":13,"featured":14,"tags":48,"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",[49,18],"Industry Products",{"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,39,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":78},{"id":62,"slug":63,"title":64,"excerpt":65,"content":9,"cover":9,"tone":66,"author":11,"publishedAt":67,"updatedAt":67,"readingMinutes":13,"featured":14,"tags":68,"category":72},48,"miniapp-performance","Mini Program Performance: Trade-offs for a One-Second First Screen","Mini programs have bundle limits and platform startup costs, so first-screen work is about trade-offs, not tricks.","cyan","2026-03-15T11:54:00+08:00",[69,70,71],"Mini Program","Performance","Frontend",{"id":13,"parentId":21,"slug":73,"name":74,"description":75,"icon":76,"cover":9,"tone":26,"kind":27,"sortOrder":77,"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":79,"slug":80,"title":81,"excerpt":82,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":83,"updatedAt":83,"readingMinutes":13,"featured":14,"tags":84,"category":88},88,"legacy-replacement-parallel-run","Retrospective: Two Months of Parallel Running","Running old and new systems together cost extra, and prevented a potentially fatal cutover.","2026-03-11T11:54:00+08:00",[85,86,87],"Retrospective","Legacy","Cutover",{"id":89,"parentId":21,"slug":90,"name":91,"description":92,"icon":93,"cover":9,"tone":26,"kind":27,"sortOrder":94,"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]