Product Is Not a Function. It Is the Heart of the Organisation.

Most technology companies say that product is central to their organisation. Very few actually operate that way. In practice, product management tends to be positioned as a coordination function — the team that takes requirements from business stakeholders and translates them into specifications for engineering. This is a narrow conception of the role, and it produces a narrow outcome: products that are technically correct and strategically incoherent.

The alternative conception of product — as the connective tissue that holds the organisation together and gives it direction — is rarer and more demanding. It requires product leaders who can operate at the level of strategy as well as execution, and it requires organisational structures that give product the authority to make meaningful decisions. But when it works, it produces something that the coordination model cannot: a company that builds the right things, not just builds things well.

What "Product as the Heart" Actually Means

When I describe product as the heart of the organisation, I mean something specific. The heart circulates. It takes inputs from the entire body and distributes what is needed where it is needed. A product team that functions as the heart of an organisation is doing something similar: taking inputs from users, from the market, from sales conversations, from support cases, from engineering constraints, and from business strategy — and synthesising those inputs into a coherent direction that the rest of the organisation can execute on.

This is categorically different from product as a coordination function. A coordination function receives requirements and passes them along. A connective tissue function absorbs signals from everywhere and makes decisions. The difference is the locus of synthesis. In the coordination model, synthesis happens at the top of the organisation — by leadership, or by whoever has the most authority in the room. In the connective tissue model, synthesis happens in product, by people who are close enough to the details to make informed decisions and senior enough to make them stick.

The Functions That Product Must Connect

To function as the heart of the organisation, product must maintain active, substantive relationships with several functions that are often treated as peripheral to the product process.

Engineering is the obvious one. The product/engineering relationship is where most of the operational work of product management happens, and it needs to be a genuine partnership. But engineering alone is not enough.

Sales and business development feed the product team information about what the market needs and what is being promised to customers. If product is not in genuine dialogue with sales, it will be building a product that diverges from what is being sold — a problem that compounds over time until it becomes a crisis.

Customer support surfaces the friction in the user experience that the product team did not design and may not be aware of. A product team that does not have a systematic feedback loop from support is flying partially blind.

Marketing shapes how the product is understood by potential users. If product and marketing are not aligned on what the product is and what problems it solves, the external story will diverge from the internal reality — which damages both acquisition and retention.

Finance sets the constraints within which the product must operate. A product team that does not understand the unit economics of its product cannot make intelligent prioritisation decisions.

The Authority That Product Requires

For product to function as the heart of the organisation, it needs commensurate authority. This does not mean product gets to make every decision — that would be as dysfunctional as product having no authority at all. It means product must have clear authority to make prioritisation decisions within a strategic framework that leadership sets, and leadership must respect those decisions rather than overriding them at every turn.

The most common failure mode I have seen is product teams that have the appearance of authority — they own the roadmap, they run the planning process — but not the substance of it. Every significant prioritisation decision is escalated to leadership or overridden by sales. The product team learns, gradually, that its authority is nominal, and it stops making decisions with conviction. The organisation loses the benefit of having a product function at all.

What Happens When Product Is Treated as a Function

When product is treated as one department among many, the symptoms are predictable. Roadmaps become wish lists — a collection of things that various stakeholders want, with no coherent narrative connecting them. Features are built for the loudest voice rather than the most important problem. Engineering cycles are consumed by low-value work that happened to be at the top of the backlog when a sprint started. Users receive a product that is full of features and short on coherence.

The root cause in each case is the same: no one is doing the synthesis. No one is looking across all the inputs — user needs, market dynamics, technical constraints, business priorities — and making coherent decisions about what matters most. When product is positioned as a coordination function, this synthesis either happens ad hoc, by whoever has the most authority in any given meeting, or it does not happen at all.

Building a Product-Led Organisation

The shift from product as a function to product as the heart of the organisation is not primarily a structural change. It is a cultural one. It requires leadership that genuinely trusts product to make meaningful decisions, and product leadership that has earned that trust by making good ones.

It also requires product managers who are capable of the synthesis role — who can hold technical, commercial, and user perspectives simultaneously and make decisions that are coherent across all three. This is a rare skill set, and it is one of the reasons that senior product leadership is so hard to hire.

The companies that build products that matter — products that users love, that generate sustainable revenue, that define categories — are almost invariably companies where product is genuinely central. Not as an organisational chart description, but as an operating reality. The product team is where the organisation's understanding of the world is synthesised into decisions about what to build. Everything else follows from that.