Roles that sit where many teams' work passes through, such as program integration or production planning, let their holders see problems first and have their judgment sought on decisions all along the flow.
An example
At a mid-size maker of infusion pumps, the program integration job had sat empty for eight months because nobody wanted it. It owned no budget and no staff, only the weekly schedule that tied firmware, mechanical design, regulatory filings, and the contract manufacturer together. A senior engineer took it anyway. Every slip in any of the four streams now crossed her desk before it reached a vice president, and within a quarter she was the person who could say which delay would move the submission date and which would not. When the leadership team debated adding a second pump variant to the launch, the chief executive asked her to walk them through the dependency chart first. She showed that the variant shared a test fixture with the main product and would cost six weeks; the plan had assumed two. The variant was moved to the following year, on her numbers.
Why it works
Seeing every handoff makes the holder's view look better because it is better informed: they know which problems are real before the people upstream do, so their reading of a proposal carries weight. Consulting them is also easy, since they are already in every thread and their answer arrives fast. Nothing about the alternatives changes. Three things have to hold: the flow is genuinely central (work many teams need, with few routes around it), the holder reports what they see accurately, and they stay in the seat long enough for others to learn to ask.
The thinking behind it
Daniel J. Brass In Being in the Right Place: A Structural Analysis of Individual Influence in an Organization (1984), Brass studied 140 nonsupervisory employees of a newspaper publisher and found that their positions in the workflow, communication, and friendship networks, including centrality and access to and control over others, were related to how influential colleagues judged them and to later promotions. An integration or planning seat is a central workflow position of exactly that kind, which is why its holder's judgment gets sought.
Jeffrey Pfeffer Pfeffer's Power in Organizations (1981) treats organizations as political systems where power comes largely from position in the structure: control of resources, information, and the decision process, and centrality in networks of dependence. A coordinating role controls little money but sits on the information every team depends on. That centrality is the source of the holder's standing, and it explains why the standing disappears if the flow is rerouted.
When it fits
It suits a manager who wants a say in decisions that cross many teams and will take a coordinating job others find unglamorous: program integration, production or demand planning, a release train, the intake desk of a shared service. The role needs no large budget. It needs real traffic, the patience to earn a name for accurate reporting over several quarters, and a boss who lets you speak to senior people about what you see.
How to use it well
Choose the seat for the traffic that runs through it; the title matters less.
- Ask which desk every escalation, schedule change, or handoff already passes through, and whether the work has other routes around it.
- Make the flow visible: one dependency map or schedule that everyone uses, kept current, with your name on it.
- Report what you see before you are asked, plainly and without spin, to the people both upstream and downstream.
- Offer judgment only where the flow gives you knowledge others lack; outside that, say you do not know.
Accuracy is what earns the standing. Once leaders learn that your read of a slip holds up, they start asking you before they decide, and proposals that run through the flow begin to carry your view.
What it costs and where it backfires
Coordinating roles eat time and rarely get credit for what goes right, so the standing builds slowly and can vanish if the flow is rerouted or automated. Teams that feel watched may start working around you, which shrinks the very traffic the role depends on. The line sits at accurate reporting. Once you slow, filter, or color what passes through your desk to steer an outcome, you are distorting information other people rely on, and the first time it shows, nobody asks for your judgment again.
When it is used on you
If someone in a central role keeps shaping decisions you care about, find out what their view rests on and go to the source data yourself. Build your own relationships with the teams upstream so their reading of your work is not the only one leadership hears. Should the role start to delay or edit information, raise it as a process question and ask for direct reporting on the facts.