ROLES

Product Manager

The person who owns what gets built and why, then defends those decisions against everyone who wants something else built instead.

Last reviewed: 2026-06-02 byKevin Riedl wiki β†—

A Product Manager owns the what and the why, not the how. They decide which problem the team solves next, why it matters, and what “done” means for the customer. They do not write the code, they do not run the sprint as a manager, and they do not design the architecture. Their job is to make sure the team is building the right thing before anyone argues about how to build it well.

The role is mostly judgment and communication under conflicting pressure. Sales wants the deal-closing feature. Support wants the bug fixed. The founder wants the bold bet. A good PM holds all of that, says no to most of it out loud, and ships the one thing that moves the business. They are accountable for the outcome, which means they own the roadmap and the prioritisation calls, not just the backlog grooming.

Product Manager versus Product Owner is where most teams get confused. Product Owner is a specific Scrum role: it owns and orders the backlog so the development team has a clear next thing to build. Product Manager is the broader business role: market, strategy, pricing input, stakeholder alignment, and the why behind the roadmap. On a small team one person wears both hats. On a larger one the PM sets direction and the PO turns it into ordered, ready-to-build work.

The common mis-hire is a PM with no authority. If the roadmap is really set by the loudest stakeholder and the PM just writes tickets, you have hired a project coordinator and called it product. We slot product ownership into founding teams as part of a fractional co-founder engagement when the founder is too deep in the build to own it.

// FAQ

FAQs

FAQs

They own what the team builds and why. They pick the next problem to solve, justify why it matters more than the alternatives, define what success looks like, and say no to everything that does not move the business. They do not own the how, that is engineering.
Product Owner is a Scrum role that owns and orders the backlog. Product Manager is the broader business role covering strategy, market, and the why behind the roadmap. On a small team it is one person. On a larger one the PM sets direction and the PO turns it into ready-to-build work.
When prioritisation is being decided by whoever shouts loudest, when engineers do not know why they are building something, or when the founder can no longer own product and the build at the same time. Until then a focused founder is the cheapest PM you will ever have.