In the early 1900s, as the Industrial Revolution scaled, organizations faced a paradox: the bigger they got, the slower they moved. Managers assumed the solution was rigid hierarchy — clear chains of command and centralized decision-making. For manufacturing, it worked.
For modern multidivisional organizations building hardware-software ecosystems, that same structure has created a new form of friction. I saw it last month when a VP of Product at a connected device company described his frustration: “My Pms (Product Managers) are talented. But they spend more time in alignment meetings than building products. They’re treated like consultants from corporate, not members of the team.”
His company wasn’t failing because of talent. It was failing because of structure. They were paying what I call The Integration Tax: the invisible cost of separating product authority from market accountability.
The Myth of the “Clean” Org Chart
Most struggling organizations make one critical mistake: they treat all product managers the same. Whether you are building lighting systems or the shared IoT platform that powers the whole fleet, you report to the same centralized CPO.
On an org chart, this looks clean. In practice, it creates chaos.
When Market PMs report outside their divisions, they lose the tight feedback loop with the leaders who live and breathe their markets. Decisions slow down. Context gets lost. The PM becomes a liaison rather than a leader —attending meetings about the market rather than being in the market.
When Platform PMs report into that same structure, they face a different problem: they are treated as a service organization. Roadmaps become reactive wish lists. Long-term architectural thinking is sacrificed for short-term divisional firefighting.
The Solution: Specialized Systems, Common Nervous System
The best multidivisional organizations I’ve studied build their product function like the human body: specialized systems connected by a common nervous system. The principle is simple: align reporting with accountability.
- Market PMs: The Agile Patrol Boats
Market-facing Pms — those responsible for specific customer segments — must report to a Director of Product within their division, who reports directly to the Division President.
This is a fundamental rewiring. When a PM reports to the leader who owns the P&L, the Integration Tax disappears. I’ve observed the same pattern across the connected device sector: companies that embed market PMs into divisions see a radical collapse in lead times. When the ‘Integration Tax’ is removed, a planning cycle that typically takes 12 weeks of cross-functional ‘alignment’ can be condensed into 3 weeks of focused execution. The reason is simple: the PM could walk down the hall and make a decision with the division president in five minutes instead of scheduling a cross-functional alignment meeting three weeks out. - Platform PMs: The Aircraft Carrier
Platform PMs own the underlying shared technologies. These PMs report to a Director of Platform Product, reporting to a VP of Engineering or COO.
They aren’t measured on divisional revenue; they are measured on leverage. They build the systems that allow market teams to move faster. Because they report outside the divisions, they can make trade-offs that serve the enterprise, not just the loudest stakeholder. - Product Operations: The Common Nervous System
Product Ops (also reporting to a Director of Platform Product) ensures every PM follows the same development process and uses the same artifacts. It isn’t bureaucracy; it’s lubrication. When everyone speaks the same language, executives stop asking “What does this slide mean?” and start asking “Is this the right bet?”
What Greatness Looks Like
Think of a naval battle group. The Market PMs are agile patrol boats—fast, maneuverable, pivoting at the first sign of a threat. The Platform PMs are the aircraft carrier—slower, but providing the fuel and technology that makes the patrol boats effective. Product Operations is the navigation system, ensuring no one crashes.
The 4 Rules (For Multi-divisional Organizations)
- Integrate the Market: Market-facing roles report to the Division President.
- Separate the Platform: Horizontal/Enabling roles report to Engineering or Ops.
- Protect the Platform: Never let platform teams report to a market division (prevents short-termism).
- Empower the Market: Never let market PMs report centrally (prevents “contractor culture” and severs the feedback loop).
When you get the structure right, the noise disappears. Teams stop fighting the organization and start fighting the competition. You stop paying the Integration Tax and start collecting the Integration Dividend.
Does your structure align accountability with reporting, or are your best people fighting the org chart?