[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-form-design-tradeoffs-en":3,"blog-related-form-design-tradeoffs-en":30,"blog-adjacent-form-design-tradeoffs-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},56,"form-design-tradeoffs","Form Design: One Field Fewer, One Step More Completion","Every field has a cost. Designing a form means deciding which information is truly needed now.","\u003Cp>The most common state of an admin form is that it keeps growing. Every new business request adds a field, and after a few years a create page has forty inputs and takes ten minutes to fill.\u003C\u002Fp>\n\u003Ch2>Three costs of a field\u003C\u002Fh2>\n\u003Cp>Entry cost: users type it every time, and drop-off rises with field count.\u003C\u002Fp>\n\u003Cp>Maintenance cost: validation, permissions, exports and reports. One change touches several modules.\u003C\u002Fp>\n\u003Cp>Data quality cost: optional fields accumulate blanks and inconsistent formats over time.\u003C\u002Fp>\n\u003Ch2>How we handle it\u003C\u002Fh2>\n\u003Cp>Separate required from optional and collapse the optional group so it does not interrupt the main flow.\u003C\u002Fp>\n\u003Cp>Anything that can be defaulted, inherited or filled later stays off the first screen.\u003C\u002Fp>\n\u003Cp>Remove fields that have held no data for a long time, but check usage logs before deciding.\u003C\u002Fp>\n\u003Cp>Form design is not about collecting everything. It is about collecting what is necessary at the right moment.\u003C\u002Fp>","","cyan","佳益方圆团队","2026-08-04T15:18:00+08:00",1,false,[16,17,18],"Forms","Product Design","B2B",{"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,17],"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":76},{"id":62,"slug":63,"title":64,"excerpt":65,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":66,"updatedAt":66,"readingMinutes":13,"featured":14,"tags":67,"category":70},36,"gray-release-for-smb","Gray Releases for Small and Mid-Sized Projects","Without heavy infrastructure, simple techniques still keep release risk under control.","2026-08-06T15:18:00+08:00",[68,69,40],"Releases","Operations",{"id":13,"parentId":21,"slug":71,"name":72,"description":73,"icon":74,"cover":9,"tone":26,"kind":27,"sortOrder":75,"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":77,"slug":78,"title":79,"excerpt":80,"content":9,"cover":9,"tone":81,"author":11,"publishedAt":82,"updatedAt":82,"readingMinutes":13,"featured":14,"tags":83,"category":87},76,"low-budget-project-retro","Retrospective: Where to Save Money on a Tight Budget","At half the usual budget, the way to protect quality is to cut scope rather than foundations.","teal","2026-08-02T15:18:00+08:00",[84,85,86],"Retrospective","Budget","Scope",{"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]