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.
A fill-in development-plan brief
Illustrative planning prompt: The assignment is [specific cross-team decision or handoff]. The manager may decide [authorized scope] and must escalate [boundary] to [approved owner]. The capability to practice is [priority translation, peer coordination or coaching]. The sponsor will provide [time, access and support]. Partners will agree [usable input and acceptance condition]. At [checkpoint], we will review [one work record and relevant measure] to decide [continue, adapt or stop the practice]. Use the actual assignment and approved authority; leave unresolved fields open rather than inventing agreement.
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.
Practice managing up: bring a decision brief, not just an update
Practice note (AI-assisted editorial): A middle manager may need a decision from their own manager before peer coordination can proceed. Harvard DCE’s guidance on managing up recommends raising issues early, connecting communication to business priorities and bringing options. This is practitioner guidance, not evidence that a particular course improves results or earns a promotion.
Fictional practice example: two initiatives both need the same analyst’s review by Thursday, but only one review fits the available time. Instead of sending another status update, the manager prepares a short brief: the decision needed, the two affected commitments, feasible options, a recommended order and its reason, the information still missing, and when a decision is needed. The senior manager retains the priority decision. If authority or an essential fact is unresolved, the brief says so rather than inventing agreement. This is an editorial illustration, not a reported client case.
When comparing development support, ask whether participants will practice that upward conversation using an appropriate work decision, not merely polish a presentation. Have the participant explain what they need their manager to decide and what they can decide themselves. Review whether the brief makes the trade-off understandable, gives usable options and leaves room for the senior manager to challenge the recommendation. Use feedback on that work to choose the next practice task; an impressive-looking update is not proof of sound judgment.
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
Planning note (AI-assisted editorial): If an AI-assisted assignment adds drafting or review work, separate a learning need from an operating-capacity problem. Name who prepares, checks and accepts each output, and what existing work will be reduced or rescheduled to make the assignment feasible. Faster drafting does not demonstrate that the manager has time to verify more decisions. Use the AI workflow pilot scorecard to compare preparation, review, corrections and waiting before expanding the assignment. Keep required approvals and approved data-use controls in place.
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.
If HR is comparing outside support for middle managers, ask each provider to explain how they would review one cross-team assignment—not just which topics their course covers. The response should name the decisions participants will practice, how the provider will observe or review that practice, and what the internal sponsor must do between sessions. Ask what working agreement or coaching routine the managers should be able to continue after support ends. Use the leadership development RFP template to put those requirements into the same brief for every respondent. Compare the proposed work and internal time, not a supervisor course and a cross-functional development engagement as if the labels make them equivalent. This is an editorial planning aid, not a new service promise.
Individual development plan example: coach without taking over
Illustrative plan (AI-assisted editorial): In a fictional department, a middle manager routinely supplies the answer when a supervisor brings a normal scheduling conflict. The individual development goal is to help that supervisor reason through an authorized decision—not to make the manager refuse support. The sponsor first confirms which scheduling decisions the supervisor may make and which require escalation. This is a practice example, not a client result or promotion assessment.
The manager and supervisor agree to use three suitable, non-confidential work conversations before their next review. The manager asks what outcome is required, what information is available, which options are feasible and where authority ends. The supervisor explains the proposed next action; the manager checks the reasoning, supplies any necessary decision and agrees a review point. Required safety, quality and staffing approvals remain in force. If no suitable case occurs, they record that limit rather than invent evidence.
At review, the sponsor and manager examine the agreed action and the supervisor’s explanation for each case. Did the supervisor leave with a usable decision and the support needed to act? Where did the manager appropriately decide or escalate? Contrast this evidence with the activity goal attend a coaching course: attendance does not show that the coaching response changed. Do not infer a business return or general competence from three conversations. Agree whether to continue the practice, adjust the authority or support, or choose a different development need. The individual plan belongs with the role’s work, not a generic list of courses.
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. Use the coaching, consulting and training comparison before commissioning a program.
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.