[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-pm-in-project-business-en":3,"blog-adjacent-pm-in-project-business-en":30,"blog-related-pm-in-project-business-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},67,"pm-in-project-business","What a Product Manager Does in a Project Business","Without an owned product line, the value is not in drawing prototypes but in thinking the client's problem through.","\u003Cp>Product managers in project businesses often feel awkward: the client brings requirements, sales sets the schedule, and little is theirs to decide. After a few years some wonder whether the role is needed. We think it is, with a different definition.\u003C\u002Fp>\n\u003Ch2>Four things that genuinely matter\u003C\u002Fh2>\n\u003Cp>Translating the business problem a client describes into rules and boundaries developers can build, reducing rework.\u003C\u002Fp>\n\u003Cp>Controlling scope: finding the minimum viable path within budget and telling the client clearly what is not included.\u003C\u002Fp>\n\u003Cp>Guarding experience, because clients do not specify interaction detail, and the end user needs an advocate.\u003C\u002Fp>\n\u003Cp>Preparing acceptance: a checklist and demo script in advance, so mismatched expectations surface before launch.\u003C\u002Fp>\n\u003Ch2>What is not needed\u003C\u002Fh2>\n\u003Cp>A complete product roadmap document, which in project work often expires as it is written.\u003C\u002Fp>\n\u003Cp>Winning arguments with the client. The goal is shared expectation, not being right.\u003C\u002Fp>\n\u003Cp>In a project business, the product manager is the translator between client and engineers. Good translation makes projects smooth; bad translation exhausts both sides.\u003C\u002Fp>","","cyan","佳益方圆团队","2026-03-25T10:41:00+08:00",1,false,[16,17,18],"Product Management","Projects","Roles",{"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},47,"cross-service-consistency","Cross-Service Consistency: Compensation Beats Distributed Transactions","Distributed transactions sound complete, but real projects rely more on compensable business flows.","indigo","2026-03-27T10:41:00+08:00",[39,40,41],"Distributed","Consistency","Architecture",{"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":36,"author":11,"publishedAt":53,"updatedAt":53,"readingMinutes":13,"featured":14,"tags":54,"category":58},87,"multilingual-site-retro","Retrospective: Translation Is Not Copy-Paste","After the English site launched, overseas visitors said they did not understand it. The problem was the content, not the language.","2026-03-23T10:41:00+08:00",[55,56,57],"Retrospective","Multilingual","Export",{"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,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","Grading the Confidence Behind Requirements","Treating requirements as facts is the most common cause of delay. Requirements differ in how reliable they are.","2026-10-15T09:00:00+08:00",[72,73,74],"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":77,"title":78,"excerpt":79,"content":9,"cover":9,"tone":36,"author":11,"publishedAt":80,"updatedAt":81,"readingMinutes":13,"featured":14,"tags":82,"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",[83,84],"Industry Products","Product Design",{"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,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}]