Before pushing a plan, a manager lists every approval, budget, system, and team it depends on and who controls each, so effort goes to the dependencies that could stop it.
An example
Twelve sites in nine months was the brief a program manager at a third-party logistics company got for rolling out a new warehouse scanning system. Before the kickoff, she listed everything the rollout needed and who controlled each item: capital approval from the chief financial officer, network upgrades from the infrastructure team, labor scheduling from each site manager, training hours under the labor agreement, the vendor's installation crews, and the client contracts that required notice before system changes at their sites. Thirty-one dependencies, eleven owners. She ranked them by how likely each was to stall the work and how hard it would be to replace. The client notice requirement, which no one had flagged, came out on top: four clients needed ninety days' notice. She sent the notices in the first week and gave the infrastructure team, second on the list, its own planning session. The rollout finished one week late.
Why it works
Managerial work runs on things other people control: approvals, money, systems, staff. Plans fail less often from bad ideas than from a dependency nobody noticed until it stalled them. Listing every input with its owner, and ranking them by risk, shows where to spend persuasion and where a backup is needed, which makes the plan easier to carry out. It depends on being thorough and on checking the list with people who know where the hidden requirements sit.
The thinking behind it
John P. Kotter Power and Influence: Beyond Formal Authority (1985) argues that managerial work is shaped by dependence on many people over whom the manager has little or no formal authority, so managers must build influence beyond their authority to get things done. Listing every approval, system, and team a rollout needs makes those dependencies visible before any of them can stall it.
Jeffrey Pfeffer Managing with Power: Politics and Influence in Organizations (1992) argues that getting things done starts with diagnosis: who has power, where it comes from, and whose support is needed. A ranked map of dependencies and their owners is that diagnosis applied to one plan, and it points effort at the few owners who could stop it.
Gerald R. Salancik Pfeffer and Salancik's The External Control of Organizations: A Resource Dependence Perspective (1978) holds that whoever controls a critical, scarce resource gains power over those who depend on it. The ranking on this page asks exactly that of each input: how critical it is, and how hard it would be to replace. The client notice requirement topped the list because nothing could substitute for it.
When it fits
Plans that cross units or need resources you do not control are the setting: rollouts, launches, reorganizations, cross-functional programs. You need time to map before you start, access to people who know the hidden requirements, and the discipline to act on what the map shows.
How to use it well
Write down every input the plan needs before the kickoff: approvals, money, systems, people, data, outside parties.
- Name the owner of each, and what they would need before saying yes.
- Rank each by how likely it is to stall you and how hard it is to replace.
- Check the list with someone experienced in the area, looking for what is missing.
- Plan specific actions for the top few: early asks, backups, a meeting.
Update the map as the plan moves, because owners change and new dependencies appear.
What it costs and where it backfires
Mapping takes time before any visible progress, and a long list can look like an excuse. A map shared too widely can read as a list of obstacles, or of people in the way. Treating owners as obstacles to get around, and skipping approvals they are entitled to give, turns a planning tool into an end run.
When it is used on you
Expect an early conversation when someone maps your unit as a dependency of their plan, and use it. State honestly what you need to say yes, and your lead times. Early requests are easier to accommodate than late ones, and telling people so brings them to you sooner.