[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-mvp-boundary-en":3,"blog-adjacent-mvp-boundary-en":29,"blog-related-mvp-boundary-en":64},{"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":28},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.","\u003Cp>MVPs are often read as a rough first version. The result demos well but cannot be used, so no value is validated and the effort is wasted. The mistake is treating an MVP as feature trimming instead of loop design.\u003C\u002Fp>\n\u003Ch2>What a loop contains\u003C\u002Fh2>\n\u003Cp>One complete flow from start to finish, even if it covers only a single business type.\u003C\u002Fp>\n\u003Cp>Essential support: accounts, permissions and data retention are not extras; without them the product cannot be used.\u003C\u002Fp>\n\u003Cp>A measurable outcome: how many people used it, how often, and where they got stuck.\u003C\u002Fp>\n\u003Ch2>Three trimming rules\u003C\u002Fh2>\n\u003Cp>Cut scenarios, not steps: support one business type, but every step of that type.\u003C\u002Fp>\n\u003Cp>Cut automation, not manual work: reports can be exported by hand, but the numbers must be right.\u003C\u002Fp>\n\u003Cp>Cut edges, not the core: support one approval level, make it reliable.\u003C\u002Fp>\n\u003Cp>An MVP exists to get real feedback quickly. A version that cannot complete the loop produces fake feedback.\u003C\u002Fp>","","blue","佳益方圆团队","2026-10-03T10:13:00+08:00",1,false,[16,17,18],"MVP","Product","Requirements",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"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","article",50,{},{"previous":30,"next":46},{"id":31,"slug":32,"title":33,"excerpt":34,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":35,"updatedAt":35,"readingMinutes":13,"featured":14,"tags":36,"category":40},31,"idempotent-design-basics","Idempotency: Duplicate Submissions Are Not Just Double Clicks","Retries, redelivery and impatient users all send the same request more than once. Idempotency belongs in the API design.","2026-10-05T10:13:00+08:00",[37,38,39],"API Design","Idempotency","Reliability",{"id":13,"parentId":21,"slug":41,"name":42,"description":43,"icon":44,"cover":9,"tone":10,"kind":26,"sortOrder":45,"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":47,"slug":48,"title":49,"excerpt":50,"content":9,"cover":9,"tone":51,"author":11,"publishedAt":52,"updatedAt":52,"readingMinutes":13,"featured":14,"tags":53,"category":57},71,"mes-integration-retro","Retrospective: Integrating ERP With MES","The hard part of integration is not the interface, but getting two departments to agree on what a field means.","cyan","2026-10-01T10:13:00+08:00",[54,55,56],"Retrospective","Manufacturing","Integration",{"id":58,"parentId":21,"slug":59,"name":60,"description":61,"icon":62,"cover":9,"tone":10,"kind":26,"sortOrder":63,"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,[65,74,84],{"id":27,"slug":66,"title":67,"excerpt":68,"content":9,"cover":9,"tone":69,"author":11,"publishedAt":70,"updatedAt":70,"readingMinutes":13,"featured":14,"tags":71,"category":73},"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",[18,17,72],"Risk",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21},{"id":20,"slug":75,"title":76,"excerpt":77,"content":9,"cover":9,"tone":69,"author":11,"publishedAt":78,"updatedAt":79,"readingMinutes":13,"featured":14,"tags":80,"category":83},"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",[81,82],"Industry Products","Product Design",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21},{"id":85,"slug":86,"title":87,"excerpt":88,"content":9,"cover":9,"tone":89,"author":11,"publishedAt":90,"updatedAt":90,"readingMinutes":13,"featured":14,"tags":91,"category":94},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.","teal","2026-09-21T11:26:00+08:00",[92,93,17],"Research","Interviews",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21}]