Organisation

Origin & evolution

The idea that a firm is the deliberate alternative to coordinating everything through the open market goes back to Ronald Coase's 1937 paper The Nature of the Firm, which argued that organisations exist because internal coordination is sometimes cheaper than transacting in the market. That framing explains why a single organisation chooses to own and manage a portfolio of products rather than spin each one out.

As firms grew into multiple product lines, the question became how to structure them. Alfred Chandler's Strategy and Structure (1962) traced the rise of the multidivisional form, where a corporate centre oversees semi-autonomous units organised around products or markets. The modern product organisation, with its split between a corporate parent and product-aligned areas, is a direct descendant of that shift.

The practical lesson is that "organisation" carries several meanings that need🫀NeedUserA user need, pain, desire, or constraintView reference → separating. The operating company that builds and runs products is distinct from the legal entity🏢Legal EntityLegalA legal entity (company, subsidiary)View reference → that signs contracts and files accounts, and both differ from the department or product area🪀Product AreaPortfolioA grouping of products by organisational axisView reference → that does a slice of the work. A holding company might own three legal entities running five products across a dozen areas. Collapsing those layers into one node makes capital allocation and ownership impossible to model cleanly.

How it works in practice

A 400-person company runs three products: a mature analytics tool that funds the business, a younger collaboration app growing fast, and an early experiment🧫ExperimentValidationA test designed to validate a hypothesisView reference → in AI tooling. As an organisation it allocates engineering headcount and budget across all three, and that allocation is a single contested decision⚖️DecisionStrategyA recorded decision with context, rationale, and consequencesView reference → rather than three independent ones. Funding the AI experiment👾AI ExperimentAI & Machine LearningAn AI-focused experimentView reference → means the analytics tool waits a quarter for its replatforming.

The organisation is also organised internally into product areas, so the collaboration app's growth team and the analytics tool's platform team report up through the same structure. Naming the organisation as the explicit top of the hierarchy makes the trade-off legible: every product and every area traces back to one entity that decides where the money goes.

Organization vs. its neighbours

• Legal entity is the incorporated body that holds contracts, liabilities, and accounts. An organisation is the operating company as people experience it. One organisation can span several legal entities (a parent plus regional subsidiaries), and the two diverge whenever structure is driven by tax or jurisdiction rather than how work is run.
• Product area is a sub-unit inside the organisation, scoped to a domain or product line. The organisation owns areas; an area is a part of the whole. Areas come and go through reorganisation while the organisation persists.
• Portfolio is the managed set of products and investments the organisation holds. The organisation is the owner; the portfolio is what it owns and balances. One organisation runs one or more portfolios, and the portfolio is where allocation decisions are expressed.

In the graph

In the Unified Product Graph, an organisation anchors the portfolio region as the top of the ownership hierarchy. The organization_invests_via_portfolioOrganizationinvests viaPortfoliohierarchy edge connects it to the portfolio through which it allocates capital, and organization_organised_into_product_areaOrganizationorganised intoProduct Areahierarchy connects it down to the internal units that do the work. Keeping the organisation distinct from its legal entities and its product areas means capital allocation, legal structure, and operating structure can each be modelled and queried on their own terms, instead of being flattened into a single ambiguous "company" node.