[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-pm-in-project-business-zh-CN":3,"blog-adjacent-pm-in-project-business-zh-CN":30,"blog-related-pm-in-project-business-zh-CN":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},67,"pm-in-project-business","产品经理在项目制公司里做什么","没有独立产品线时，产品经理的价值不在画原型，而在替客户把问题想清楚。","\u003Cp>项目制公司的产品经理常常处境尴尬：需求由客户提，排期由销售定，自己能决定的很少。做了几年之后，有人会怀疑这个岗位是否必要。我们的答案是必要，但职责要重新定义。\u003C\u002Fp>\n\u003Ch2>四件真正有价值的事\u003C\u002Fh2>\n\u003Cp>需求翻译：把客户描述的业务问题，翻译成可开发的规则和边界，减少返工。\u003C\u002Fp>\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>","","cyan","佳益方圆团队","2026-03-25T10:41:00+08:00",1,false,[16,17,18],"产品经理","项目制","角色",{"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","产品思维","需求分析、用户体验与产品设计方法论，以及从业务问题到产品方案的思考过程。","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},47,"cross-service-consistency","跨服务一致性：补偿比事务更现实","分布式事务听起来完备，实际项目中更常用的是可补偿的业务流程。","indigo","2026-03-27T10:41:00+08:00",[39,40,41],"分布式","一致性","架构",{"id":13,"parentId":21,"slug":43,"name":44,"description":45,"icon":46,"cover":9,"tone":26,"kind":27,"sortOrder":47,"count":21},"engineering","技术专栏","架构设计、性能优化、AI 集成与跨端方案等一线技术实践，由研发团队持续分享。","cpu",60,{"id":49,"slug":50,"title":51,"excerpt":52,"content":9,"cover":9,"tone":36,"author":11,"publishedAt":53,"updatedAt":53,"readingMinutes":13,"featured":14,"tags":54,"category":58},87,"multilingual-site-retro","多语言站点复盘：翻译不是复制粘贴","英文站上线后，海外客户反馈看不懂，问题不在语言，而在内容直接照搬。","2026-03-23T10:41:00+08:00",[55,56,57],"复盘","多语言","外贸",{"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","项目复盘","从 0 到 1 的真实项目记录，完整呈现问题、方案、踩坑经验与最终结果。","clipboard-check",40,[66,76,86],{"id":28,"slug":67,"title":68,"excerpt":69,"content":9,"cover":9,"tone":36,"author":11,"publishedAt":70,"updatedAt":70,"readingMinutes":13,"featured":14,"tags":71,"category":75},"grading-requirement-confidence","需求的真实度分级","把需求当成事实来做，是项目延期最常见的原因。需求其实有可信度高低之分。","2026-10-15T09:00:00+08:00",[72,73,74],"需求","产品方法","风险管理",{"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":77,"title":78,"excerpt":79,"content":9,"cover":9,"tone":36,"author":11,"publishedAt":80,"updatedAt":81,"readingMinutes":20,"featured":14,"tags":82,"category":85},"vertical-product-rules","垂直行业产品的分水岭：把行业默认规则写进系统","垂直不是换一个行业名字。真正的门槛，是能否理解并承接那些从业者习以为常的默认规则。","2026-10-09T10:00:00+08:00","2026-10-18T15:58:14.661+08:00",[83,84],"行业产品","产品设计",{"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","MVP 的边界怎么划","最小可用不是功能最少，而是能完整跑通一条业务闭环。","2026-10-03T10:13:00+08:00",[93,73,72],"MVP",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21}]