One team owns the official data pipelines and metric definitions, and every strategic number runs through it, so the team's analysis frames each major decision before anyone argues about it.
Borderline: whether this move is justified depends on the situation, and only the person in it can judge.
An example
Three years of watching business units argue from incompatible spreadsheets had convinced the head of planning and analysis at a diversified chemicals company that the numbers needed one owner. With the chief financial officer's backing, her group of six built a single data warehouse, wrote and published the metric definitions, and took over the weekly executive pack. Every strategic number, from freight cost to unit margin, now ran through them. She set a monthly session where any unit could challenge a definition, and opened the raw data behind the pack to every unit's analysts. When the water-treatment president argued that freight allocation understated her margins, the group reran the numbers with her team, agreed a revised method, and restated two quarters. Within a year the executive committee asked the group to frame every major capital decision, which gave its head a seat where those decisions were made.
Why it works
Synthesized and reconciled, a single view is easier to use than anything else, so relying on it costs executives nothing, and one trusted version of the numbers looks better than competing spreadsheets. Rival analyses look weaker by comparison and cost more to produce, because the official definitions and data set the standard they must meet. The team that owns the pipeline sets the starting point of every argument. It depends on control of three layers, the data plumbing, the definitions, and the executive presentation, and it stays legitimate while others can see the data and challenge the definitions.
The thinking behind it
Jeffrey Pfeffer Pfeffer's Power in Organizations (1981) argues that power comes largely from structural position: control of resources, information, and the decision process, and centrality in networks of dependence. A team that owns the data pipeline, the definitions, and the executive pack holds all of these. That is why the role brings influence, and why publishing definitions and opening the raw data keep that influence earned and contestable.
Herbert A. Simon Simon's Administrative Behavior (1947) holds that decisions are shaped by premises the organization supplies, and that whoever controls those premises influences the decisions made from them. Metric definitions and the executive pack are premises for every capital decision. The team that writes them frames choices before the argument starts, so a forum for challenging definitions is what keeps the framing fair.
When it fits
Finance, planning, or analytics teams in organizations where decisions stall on competing numbers are natural owners of it. They need a sponsor with authority over reporting, enough analytic capacity to build and run the pipeline, and a willingness to publish definitions and open the raw data. It suits a team that wants influence earned by being the most useful source.
How to use it well
Build the pipeline end to end: one warehouse, one set of definitions, one executive pack. Publish the definitions and their lineage, and give units' analysts read access to the raw data so they can check you. Hold a regular forum to challenge definitions, change them when a challenge is right, and restate past figures when you do. Work disputed numbers through with the unit that raised them. Keep the people who build the plumbing close to the people who present, so errors surface early. Over time, offer to frame major decisions, and be the team that shows the uncomfortable number first.
What it costs and where it backfires
Owning the numbers makes you the target when they are wrong: one bad allocation and every unit's grievance lands on your team. The role also attracts suspicion, so every dispute needs to be resolved where others can see it. Trouble starts when the team uses its position to correct rivals on definitional grounds without engaging the substance, keeps raw data behind gates it administers, or bends a definition to favor one side. Then the pipeline has become a chokepoint, and the organization will eventually pay for a second one.
When it is used on you
Bring your own analysis with your definitions and sources written beside it, and ask the team to reconcile it line by line. Ask for read access to the raw data and the published definitions. If the team will neither reconcile nor share the data, find an ally with standing, a finance leader or internal audit, to rebuild one disputed number.