Ownership mapping: a single source of truth for accounts and infrastructure
Ownership mapping turns implicit knowledge — who owns what, who pays for what, who has access to what — into a queryable graph. Here is how to build one that survives reorgs.
In most companies, ownership lives in three places: people's heads, a Slack channel, and a stale wiki. That works until someone leaves, a tool gets renewed by accident, or a security review asks who can access what. Ownership mapping makes that knowledge explicit and queryable.
What ownership actually means
Ownership is not a single relationship. A given account has a financial owner (whose budget it sits on), a technical owner (who maintains it), and an access set (who can use it). Useful ownership maps capture all three separately, because they change at different rates and for different reasons.
Build the map in layers
Start with the most stable layer — entities and brands. Then add accounts and subscriptions. Then identities. Each layer narrows the search space for the next. By the time you get to access mapping, most of the structure is already in place and the work becomes mechanical.
- Layer 1: entities and brands. The legal and product structure of the business.
- Layer 2: accounts, subscriptions, and infrastructure. What the business runs on.
- Layer 3: identities and roles. Who has access and at what level.
- Layer 4: financial relationships. Which payment methods and addresses pay for what.
Survive reorgs by design
Ownership maps fail when they are tied too tightly to the current org chart. Model ownership as relationships between durable nodes — entities, accounts, identities — rather than as fields on a single record. When the org changes, you re-point a few edges instead of rewriting the whole document.
From map to control plane
Once the graph is honest, it becomes a control plane. Cost allocation, access reviews, vendor consolidation, and risk detection all become queries against the same structure. That is the moment ownership stops being tribal knowledge and starts being infrastructure.