Middle-manager leadership development should prepare managers to translate senior priorities into workable team decisions, coordinate dependencies with peers and coach the supervisors or teams they lead. It is not simply a more advanced version of a new-supervisor course. The role often requires working across boundaries where the manager does not control every resource or decision.
Start the development plan with a real assignment that requires those capabilities. A list of desirable traits is less useful than a specific decision the manager must learn to handle, the authority available and the support their sponsor will provide.
Choose an assignment that exposes the real interface
Select a priority that crosses at least one meaningful boundary: departments, locations, management levels or shifts. Identify the result, the contributing teams and the decision that repeatedly becomes unclear. Choose work where practice is appropriate and risks can be managed under existing procedures—not an unbounded assignment described as a growth opportunity.
For example, a hypothetical operations manager might coordinate a change in the way two departments accept work from each other. The development challenge is not to write a more persuasive announcement. It is to agree acceptance conditions, decision ownership and the trade-off to make when local priorities conflict. The example is illustrative, not a reported client engagement.
Capability one: translate the priority into a working agreement
Ask the manager to explain the intended outcome, the first observable change, what should remain unchanged and the trade-off that takes precedence. Have the receiving supervisor explain the same priority back using an actual work example. Differences should be resolved before the manager issues more reminders.
Our guide to why good organizations struggle to execute describes the gap between senior direction and frontline action. A development assignment can make that gap visible: review the original intent, the manager's translation and the team's next decision together.
Capability two: negotiate dependencies without becoming the messenger
Have the manager identify which inputs they need from peers and which inputs they owe others. The agreement should specify what is usable, when it is needed, who accepts it and how an unresolved disagreement is escalated. Being accountable for coordination does not give the manager authority over every contributing department.
Practice a peer conversation using evidence from the work. Instead of 'your department never supports us,' state which input was missing, what happened and what agreement needs clarification. Record the decision and the owner. If the two departments are receiving conflicting priorities from senior leaders, the sponsor must resolve that conflict rather than making the manager negotiate an impossible compromise.
Capability three: coach leaders rather than reclaim their work
When a supervisor raises a routine issue, ask what outcome is required, what they have observed, which options they considered and where their authority ends. Provide a decision when the situation requires one; otherwise agree what the supervisor will try and when it will be reviewed. Development should not become a ritual of withholding help in the name of empowerment.
Review the manager's coaching on a specific conversation. Did they clarify the standard? Did the supervisor leave with ownership? Was the needed support available? Our discussion of accountability versus control provides context for the difference between supporting an outcome and becoming the answer to every problem.
Give the sponsor concrete responsibilities
The sponsor should clarify authority, protect practice time and address constraints the middle manager cannot fix. They should also model the same operating expectations. Asking a manager to develop cross-functional collaboration while rewarding only local results creates a conflict that a course cannot resolve by itself.
Use the guide to leadership consistency beyond coaching when similar problems appear across departments. Development may be appropriate, but it must be accompanied by changes to the management conditions that are undermining application.
An adaptable 30/60/90-day review
At the first review, examine the assignment brief, authority and agreements with partners. At the second, review actual priority translations, peer decisions and coaching conversations. At the third, ask whether the routine continues without the manager or sponsor personally chasing every step. These checkpoints are an example, not a promised engagement duration or universal development timeline.
Keep the evidence modest and useful: an agreed decision, an accepted handoff, a coaching example and a relevant operating measure. A completed competency form is not sufficient evidence that the work changed. Choose the next development priority from what the assignment revealed rather than adding another generic course.
Can a development assignment support succession without promising a promotion?
A supported assignment can provide evidence about a leadership capability without becoming a promise of promotion. State the learning purpose, assigned authority and review method openly, and distinguish these from the organization's separate appointment process. The succession-planning guide separates continuity arrangements from longer-term readiness. One successful assignment is useful evidence to examine, not a validated forecast of performance in a different role.
For an illustrative assignment, a manager coordinates one authorized cross-team decision while their sponsor observes the reasoning and the effect on receiving teams. The coaching conversation guide supports feedback on that work rather than on a general impression of potential. Record what was practiced, what support made it possible and what remains untested. Use the same transparent development standards and required organizational processes for comparable participants.
If the recurring issue spans the leadership system, book a conversation with Shannon about the real assignment and its constraints. Clarifying the level of the problem comes before selecting outside support.
About this resource: Prepared with AI-assisted drafting. Examples and the review sequence are illustrative, not a validated assessment or a new service offer. Cover illustration: AI-generated.