Open the page in your HRIS that everyone calls "the org chart" and look at it for thirty seconds. You will see a tree. One person at the top, branches going down, each box reporting to exactly one parent. It's a beautiful artefact in its way — clean, finite, easy to print. It is also, for the purposes of running strategy, dangerously incomplete.
The org chart describes who reports to whom. That's a hierarchy. The goals that actually matter to the company — net revenue retention, time-to-market for a new product, the cost-to-serve of a key segment, the multi-quarter platform migration — move through several boxes on that tree simultaneously. That's a network. When the only structural artefact the company maintains and updates is the tree, every networked outcome has to be re-negotiated by hand, every time, in a meeting, by people whose authority comes from the tree and whose accountability spans the network.
This is exhausting, and it is the single largest reason cross-functional work is harder than it should be.
What gets lost without an explicit goal graph
Three specific things go missing when the tree is the only map. The first is cross-functional dependencies. They exist — they always exist — but they're invisible until somebody slips. The platform team didn't know that the data team's roadmap depended on their migration finishing in March. The data team didn't know that the analytics rebuild was sequenced behind that. The CRO didn't know that the customer-facing dashboard they promised in their kickoff was downstream of all of it. Each team, looking at their own branch of the tree, was being entirely rational. Nobody owned the seam.
The second is ownership defaulting to whichever box is biggest. When a goal touches four functions, the question of who "owns" it tends to resolve in favour of whoever has the most headcount in the room, because the tree has trained everyone to read structural weight as authority. That isn't always — or even usually — the function closest to the outcome. The result is goals owned by the wrong function, with the people who actually move the needle relegated to a contributor role on someone else's plan.
The third is reorgs being treated as strategy interventions. If the only lever you have for changing how work moves through the company is the reporting line, then every time the strategy changes, the company reaches for a reorg. New strategic priority on customer experience? Move the support function under the chief product officer. Reorgs are expensive — months of distraction, real human cost, dropped momentum — and they don't actually solve the underlying problem, which is that strategy moves through a network the tree can't represent.
What a goal graph adds
A goal graph is the second structure. It is not a replacement for the org chart; it is the missing companion to it. Nodes are objectives — the things the company is trying to move. Edges are the work that moves them, and the teams that do that work. A given objective can be connected to multiple teams, and a given team can be connected to multiple objectives, because that's how the world actually is.
The org chart still exists. Reporting lines still matter. Performance management still flows through them. But the tree stops being the only map of how the company works. A leader can ask "who is moving retention?" and get a network answer — three teams, two objectives, this much capacity allocated, this much being absorbed by BAU — instead of a "well, technically Customer Success owns it" answer that everyone in the room knows is partial.
Once the goal graph exists as a live artefact rather than a slide deck, a different set of conversations becomes possible. Capacity trade-offs can be seen directly: when two strategic objectives are pulling on the same team, the conflict is visible before the slip happens. Cross-functional dependencies can be mapped before they become incidents. The portfolio review can ask "should this objective still exist, given the rest of the graph" instead of just "is each team on track within its own column."
Why most companies don't have one
The goal graph isn't missing because nobody has thought of it. It's missing because building it requires more discipline than most operating models impose. Somebody has to maintain the link between objectives and the work that moves them. Somebody has to keep the team-to-initiative mapping honest as people rotate. Somebody has to enforce that new initiatives can't enter the graph without an owner, a capacity commitment, and a parent objective. The tree updates itself every time HR processes a transfer. The graph only updates if the operating model insists on it.
So the graph lives, in most companies, as a series of partial views: a strategy deck refreshed twice a year, an OKR tool that captures objectives but not capacity, a project portfolio that captures work but not the goal it serves, a roadmap that captures sequence but not ownership. Each view is true. None of them compose. And the company runs on the tree by default, because the tree is the only thing that's always current.
The Vindaris view
If you can draw your entire strategy on the org chart, your strategy is too small — you've trimmed your ambitions to fit the only structural artefact you trust. The goal graph is the second structure every leadership team past a certain size needs. It shouldn't live in a deck, refreshed twice a year by a chief of staff. It should be the live spine the operating model runs on, sitting alongside the tree, updating as the company updates, visible to everyone whose work depends on it.
The org chart tells you who reports to whom. The goal graph tells you who is moving what. Both are needed. Only one of them is usually built.