[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-mvp-boundary-zh-CN":3,"blog-related-mvp-boundary-zh-CN":29,"blog-adjacent-mvp-boundary-zh-CN":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":28},51,"mvp-boundary","MVP 的边界怎么划","最小可用不是功能最少，而是能完整跑通一条业务闭环。","\u003Cp>MVP 常被理解成“先做个简陋版本”。结果做出来的东西能演示，却不能真正使用，最后既没验证价值，也浪费了开发时间。问题出在把 MVP 当成功能裁剪，而不是闭环设计。\u003C\u002Fp>\n\u003Ch2>一条闭环包含什么\u003C\u002Fh2>\n\u003Cp>一个完整流程：从发起到结束，哪怕只覆盖一种业务类型，也要能走通。\u003C\u002Fp>\n\u003Cp>必要的支撑能力：账号、权限、数据留存，这些不是锦上添花，缺了就无法真实使用。\u003C\u002Fp>\n\u003Cp>可衡量的结果：能统计有多少人用、用了多少次、卡在哪一步。\u003C\u002Fp>\n\u003Ch2>三条裁剪原则\u003C\u002Fh2>\n\u003Cp>砍场景不砍环节：只支持一种业务类型，但这类业务的全部环节都要有。\u003C\u002Fp>\n\u003Cp>砍自动化不砍人工：报表可以先人工导出，但数据必须准确。\u003C\u002Fp>\n\u003Cp>砍边缘不砍核心：审批只支持一级，但一级审批要稳定可靠。\u003C\u002Fp>\n\u003Cp>MVP 的目标是尽快得到真实反馈。跑不通闭环的版本，得到的反馈也是假的。\u003C\u002Fp>","","blue","佳益方圆团队","2026-10-03T10:13:00+08:00",1,false,[16,17,18],"MVP","产品方法","需求",{"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","产品思维","需求分析、用户体验与产品设计方法论，以及从业务问题到产品方案的思考过程。","lightbulb","article",50,{},[30,39,49],{"id":27,"slug":31,"title":32,"excerpt":33,"content":9,"cover":9,"tone":34,"author":11,"publishedAt":35,"updatedAt":35,"readingMinutes":13,"featured":14,"tags":36,"category":38},"grading-requirement-confidence","需求的真实度分级","把需求当成事实来做，是项目延期最常见的原因。需求其实有可信度高低之分。","indigo","2026-10-15T09:00:00+08:00",[18,17,37],"风险管理",{"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":40,"title":41,"excerpt":42,"content":9,"cover":9,"tone":34,"author":11,"publishedAt":43,"updatedAt":44,"readingMinutes":20,"featured":14,"tags":45,"category":48},"vertical-product-rules","垂直行业产品的分水岭：把行业默认规则写进系统","垂直不是换一个行业名字。真正的门槛，是能否理解并承接那些从业者习以为常的默认规则。","2026-10-09T10:00:00+08:00","2026-10-18T15:58:14.661+08:00",[46,47],"行业产品","产品设计",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21},{"id":50,"slug":51,"title":52,"excerpt":53,"content":9,"cover":9,"tone":54,"author":11,"publishedAt":55,"updatedAt":55,"readingMinutes":13,"featured":14,"tags":56,"category":59},52,"user-interview-questions","用户访谈里最该问的三个问题","问“你想要什么”得到的是想象，问“你上次怎么做”得到的才是事实。","teal","2026-09-21T11:26:00+08:00",[57,58,17],"用户研究","访谈",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21},{"previous":61,"next":77},{"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":71},31,"idempotent-design-basics","幂等设计：重复提交不只是用户手抖","网络重试、消息重投、用户连点，都会让同一个请求到达多次。幂等应该设计在接口里。","2026-10-05T10:13:00+08:00",[68,69,70],"接口设计","幂等","可靠性",{"id":13,"parentId":21,"slug":72,"name":73,"description":74,"icon":75,"cover":9,"tone":10,"kind":26,"sortOrder":76,"count":21},"engineering","技术专栏","架构设计、性能优化、AI 集成与跨端方案等一线技术实践，由研发团队持续分享。","cpu",60,{"id":78,"slug":79,"title":80,"excerpt":81,"content":9,"cover":9,"tone":82,"author":11,"publishedAt":83,"updatedAt":83,"readingMinutes":13,"featured":14,"tags":84,"category":88},71,"mes-integration-retro","制造企业 MES 对接复盘","系统对接最难的部分不是接口，而是让两个部门对同一个字段达成一致。","cyan","2026-10-01T10:13:00+08:00",[85,86,87],"复盘","制造业","系统集成",{"id":89,"parentId":21,"slug":90,"name":91,"description":92,"icon":93,"cover":9,"tone":10,"kind":26,"sortOrder":94,"count":21},3,"project-retrospective","项目复盘","从 0 到 1 的真实项目记录，完整呈现问题、方案、踩坑经验与最终结果。","clipboard-check",40]