Senior leaders push an unpopular directive down to a mid-level manager with no senior name attached, so the manager either alienates the team by carrying it out or gets called insubordinate.
An example
A regional bank decided to close its branches on Saturdays and cut lunch-hour staffing, a change customers and tellers were both going to hate. The directive reached district managers as an email from an operations analyst, with a rollout template and no senior name on it. The district manager for the eastern branches, whose tellers had been told for years that Saturday service was the bank's advantage, called the regional executive to ask who owned the decision. The answer was that it was standard operating policy and that district managers who could not implement policy would be discussed at the talent review. Carrying it out meant announcing it to eight branch teams as if it were the district manager's own call. Refusing meant the insubordinate label. In the first month, customer complaints were routed to the district manager's inbox.
Why it works
Refusal is made to look worse, because the directive is framed so that saying no cannot read as principled dissent, only as insubordination. The framing makes refusal costlier too, because that label travels in reviews, references, and informal networks far beyond this one decision. Compliance carries no upside, so the manager absorbs a cost the senior actor declines to carry. Four conditions make it bite: the senior actor clearly has authority to issue the directive, the manager has no lateral sponsors or ready exit, the directive looks like routine policy, and the team is cohesive enough to resent it.
The thinking behind it
Stanley Milgram In Obedience to Authority: An Experimental View (1974), Milgram argued that people acting under a legitimate authority come to see themselves as carrying out its wishes and no longer as responsible for their own acts, and his variations showed obedience falling when authority was divided or its legitimacy questioned. A directive with no senior name attached asks the manager to obey without the authority being visible. Surfacing it to a peer with parallel authority divides the authority and reopens the question.
Niccolò Machiavelli The Prince (1532) advises that princes leave affairs of reproach to others and keep affairs of grace in their own hands. Routing an unpopular branch closure through an analyst's email, with no senior name on it, keeps the reproach away from the people who decided. The defense asks the decision's owner to put their name on the announcement, so the reproach lands where the decision was made.
Warning signs
No senior sponsor is named on the rollout of an unpopular directive that arrives one level down. Accountability is not shared, and the compliance branch carries no career upside. Refusal is framed in advance as insubordination. Questions about who owns the decision are answered with references to policy. Complaints about the change are routed to the manager carrying it out.
How to defend yourself
Take neither branch as offered. Surface the dilemma to a third party before you choose.
- Ask in writing who owns the decision and whether that person will put their name on the announcement.
- Bring the question to a peer with parallel authority, a senior sponsor, HR, or the board, depending on what you can reach.
- Propose a rollout in which the owner announces the decision and you implement it.
- Tell your team honestly what you can: that the decision came from above and what you are doing about its effects.
If the directive crosses a legal or ethical line, say so explicitly. That changes both your options and your protection.
How a leader shuts it down
Requiring every contentious directive to carry its owner's name on the announcement removes the dilemma at its source. Give mid-level managers an explicit right to escalate without it counting as refusal, and a neutral referee for disputes across levels. Notice who receives the complaints, and make sure they reach the person who made the decision.