Product Thinking · Published March 25, 2026
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.
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.
Four things that genuinely matter
Translating the business problem a client describes into rules and boundaries developers can build, reducing rework.
Controlling scope: finding the minimum viable path within budget and telling the client clearly what is not included.
Guarding experience, because clients do not specify interaction detail, and the end user needs an advocate.
Preparing acceptance: a checklist and demo script in advance, so mismatched expectations surface before launch.
What is not needed
A complete product roadmap document, which in project work often expires as it is written.
Winning arguments with the client. The goal is shared expectation, not being right.
In a project business, the product manager is the translator between client and engineers. Good translation makes projects smooth; bad translation exhausts both sides.
← Previous post
Cross-Service Consistency: Compensation Beats Distributed Transactions
Next post →
Retrospective: Translation Is Not Copy-Paste
Want to apply these ideas to your project?
We are happy to go deeper into implementation details, or to discuss the specific questions you are facing.
Start a conversation →