[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-admin-panel-experience-en":3,"blog-adjacent-admin-panel-experience-en":30,"blog-related-admin-panel-experience-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},53,"admin-panel-experience","Admin Systems Are Products Too","Back-office users spend eight hours a day there. One inefficient click becomes a long-term cost.","\u003Cp>Many teams pour effort into customer-facing visuals and treat the admin side as merely functional. But admin users are high-frequency users, and their efficiency converts directly into labour cost. Clients notice when the backend is well designed.\u003C\u002Fp>\n\u003Ch2>Four high-return improvements\u003C\u002Fh2>\n\u003Cp>Batch operations: if a hundred rows can be selected, do not require a hundred clicks. Bulk approval and export are basic needs.\u003C\u002Fp>\n\u003Cp>Remember the last context: filters, page position and sort order should still be there on return.\u003C\u002Fp>\n\u003Cp>Fewer navigations: open detail in a drawer or modal and return to the list without losing context.\u003C\u002Fp>\n\u003Cp>Keyboard friendliness: Enter to search, Tab through forms, shortcuts for repetitive work.\u003C\u002Fp>\n\u003Ch2>Details often missed\u003C\u002Fh2>\n\u003Cp>Explicit loading states; any wait over a second needs feedback.\u003C\u002Fp>\n\u003Cp>Confirm destructive actions and describe the consequence instead of asking 'are you sure'.\u003C\u002Fp>\n\u003Cp>Empty states should suggest the next step, such as creating an item or explaining why nothing appears.\u003C\u002Fp>\n\u003Cp>The admin side is not an internal tool; it is the client's daily workbench. Treat it as a product and clients vote with renewals.\u003C\u002Fp>","","cyan","佳益方圆团队","2026-09-09T12:39:00+08:00",1,false,[16,17,18],"Admin","UX","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,{},{"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},33,"slow-query-first-steps","Taming Slow Queries: Read the Plan Before Optimising","Adding an index is not a universal cure. Without an execution plan, tuning is guesswork.","teal","2026-09-11T12:39:00+08:00",[39,40,41],"Database","Performance","SQL",{"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":26,"author":11,"publishedAt":53,"updatedAt":53,"readingMinutes":13,"featured":14,"tags":54,"category":58},73,"miniapp-launch-retro","Retrospective: Launch Day Is Not the Finish Line","Users arrived on launch day and so did the problems. We now include post-launch operations in scope.","2026-09-07T12:39:00+08:00",[55,56,57],"Retrospective","Mini Program","Operations",{"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,77,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":76},"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,74,75],"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":78,"title":79,"excerpt":80,"content":9,"cover":9,"tone":70,"author":11,"publishedAt":81,"updatedAt":82,"readingMinutes":13,"featured":14,"tags":83,"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",[84,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":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,74,73],"MVP",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21}]