By Marty Cagan · svpg.com · LinkedIn
Cagan describes a role that appears in large matrixed companies: the business owner, who represents a business unit (by geography, device, or function) that a central product organization serves. He argues this role can either empower product work or obstruct it, depending on how it is defined relative to the product manager. When the business owner becomes a requirements gatherer or hands the product manager mockups, product management effectively disappears. When roles are clear, the business owner handles business-side duties like revenue model, partners, and stakeholders, freeing the product manager to focus on discovery. Unclear boundaries can push business units to build their own products, creating fragmented and hard-to-maintain systems.
01Key takeaways
- Define the business owner and product manager roles explicitly, with clear boundaries, before the matrix model starts.
- Have the business owner write the opportunity assessment that sets the problem and success measures, not the solution.
- Let business owners own revenue model, pricing, partners, and stakeholder management so product managers can focus on discovery.
- Treat a business owner who designs product solutions as a warning sign of role confusion or a product manager gap.
- Monitor the model so business units don't build shadow product teams, which fragment the software and burden support.
02Key sections
- What the business owner role is
- Business owners emerge in matrix organizations where a shared product team serves several business units. The title is inconsistent, and the role often arises as general managers seek direct control over the people driving their revenue.
- Two ways the model can go
- Done well, the pairing of business owner and product manager drives the business aggressively. Done poorly, the product manager becomes a requirements scribe, which Cagan says means product management is absent.
- Five business owner responsibilities
- Business owners define the opportunity and success measures, own the revenue model, manage stakeholders and key partners, and track business analytics. Each duty otherwise lands on the product manager and diverts time from core work.
- What stays with the product manager
- Product discovery, finding innovative solutions that are valuable, usable, feasible, and deliverable, belongs to the product manager and not the business owner. Business owners who hand over mockups signal a role-clarity problem.
- Risks of unclear roles
- When business units lose confidence in the central organization, they hire their own teams or outsource development. The result is incompatible, poorly supported software that frustrates users and the company.
03From the post
“A partnership dedicated to teaching best practices to product teams and product leaders”
04Frameworks mentioned
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.