Handle Conflicting Development Priorities From Two Sponsors

Two executive sponsors rarely coordinate before they call you. Jordan wants managers to practice staffing conversations this quarter. Elena wants the same managers focused on customer recovery instead. Both requests sound urgent, and both sponsors sign off on your budget and your team's credibility. Neither one knows the other made a competing ask, and neither one is wrong to want what they want. If you try to build one program that quietly serves both agendas, you end up with a diluted curriculum that satisfies no one, and you carry the blame when the results fall short. The stronger move is to make the conflict visible early and let the sponsors decide together which need comes first, with you guiding the decision rather than making it alone.

Why This Conversation Goes Wrong

This situation goes wrong because each sponsor sees a different slice of the business. Jordan watches staffing gaps close in real time, on his own dashboard, with his own metrics. Elena watches complaint volume climb on a completely different report. Each person is reacting to real pressure, and each assumes their priority is obviously the right one, because from where they sit, it is. Neither sponsor has visibility into the other's request, and neither one thinks of your program as a shared resource with limited capacity and a hard deadline.

The learning leader often makes the situation worse by trying to avoid conflict rather than surface it. You build a hybrid session that touches staffing and customer recovery in the same four weeks, hoping both sponsors leave the room satisfied. Instead you end up with a shallow agenda that does not build real skill in either area, and both sponsors notice within the first session. Or you pick one priority privately, without telling the other sponsor why, and that sponsor finds out later that their request got quietly dropped. Either path damages trust, and it puts the same unresolved decision back on your desk next quarter, except now with less goodwill to work with.

Prepare Before You Bring Sponsors Together

Before you talk to either sponsor, build a short comparison of the two requests. Write down the target audience for each ask, the specific behavior the sponsor wants to see, the timing pressure behind it, and the evidence the sponsor is using to justify urgency. Note what current work already demonstrates the gap, and note the business consequence each sponsor is trying to prevent.

Put these details side by side on one page. You need this because most sponsor conflicts are not really disagreements about direction. They are two separate, valid problems competing for the same four weeks of manager time. Once you separate the business question, which problem matters more right now, from the design question, what a single learning activity can actually support, the conversation gets much easier to run.

If you support multiple leaders competing for the same coaching slots or the same stretch assignment, the same comparison habit applies. See Prepare a Consistent Process for Employees Seeking the Same Opportunity for how to build that kind of process before a request turns into a standing complaint.

Bring both sponsors into the same conversation whenever you can manage it. A joint conversation prevents each sponsor from negotiating with you separately and then comparing notes afterward, which almost always ends with someone feeling shortchanged.

What To Say When Priorities Collide

Open by naming both requests out loud, in front of both sponsors, before you propose a solution.

Farah, a learning leader, put it this way. "Jordan, you have asked for managers to practice staffing conversations this quarter. Elena, you have asked the same managers to focus on customer recovery. I am looking at two different behaviors and a four week window to work with. Before I design anything, I want us to agree on which situation creates the more immediate need."

Jordan answered first. "Staffing decisions are happening right now. I cannot wait until next quarter."

Elena pushed back. "Complaints are climbing every week. My team needs help sooner, not later."

Farah did not pick a side. She asked a question that moved the conversation from opinion to evidence. "Which group of managers will actually use each skill in the next month, and what evidence supports that? We could choose one priority for this pilot and schedule a separate discovery session for the other, so neither request gets dropped."

Elena thought about it and answered first. "The service leaders probably do need help sooner. I can bring our complaint themes to a discovery session instead of asking for a full program right now."

Notice what Farah did not do. She did not evaluate whose business problem mattered more. She is not equipped to make that call, and pretending otherwise would put her in the middle of a fight that belongs to two executives, not to the learning team. That last line from Elena is the turn that makes the conversation work. Elena did not lose her request, she agreed to a sequence. Farah got a decision, a reason for the decision, and a next step for the deferred priority, all in one meeting.

Mistakes That Make The Conflict Worse

A few habits turn a manageable disagreement into a lasting problem.

1. Designing a blended program before the sponsors agree on priority. A session that tries to cover staffing and customer recovery in four weeks usually teaches neither skill well.

2. Picking a winner without recording the reason. If Jordan later asks why his request got pushed back, you need a documented answer, not a memory of a hallway conversation.

3. Promising a business outcome you cannot support. Do not tell a sponsor that a workshop will reduce complaints or close staffing gaps without evidence and without the leader's own follow through afterward. A learning activity builds a skill. It does not guarantee a business result on its own.

4. Letting the deferred sponsor feel dismissed. Elena's request does not disappear because Jordan's need is more urgent this month. Schedule the discovery session, put a date on it, and follow through, or you will face the same standoff again next quarter.

5. Carrying the decision alone. If you choose a priority without sponsor agreement, you own the outcome by yourself, and you own the blame if the other sponsor complains later.

Practice The Conversation Before It Happens

This conversation is hard to run well the first time you try it live, with two executives watching how you handle pressure. Rehearse it before the real meeting.

Run through the exchange with a practice partner or with an AI counterpart that plays both sponsors and pushes back the way Jordan and Elena did. Score yourself on specific behaviors, not just how the conversation felt. Did you name both requests before offering a solution? Did you ask for evidence instead of accepting urgency at face value? Did you avoid promising a business outcome you cannot control? Did you leave the meeting with a documented decision, a reason, and an owner for the deferred topic?

DealSpeak's HR and Leadership practice conversations let a talent development leader run this exact scenario, get pushback from two simulated sponsors, and get scored on whether the decision was clear and evidence based by the end of the exchange. The same practice habit helps with other high stakes exchanges you own, including correcting a mistake in a sensitive record, covered in Correct an Error in an Employee Relations Intake Note. Practicing the hard version of the conversation, the one where a sponsor pushes back twice, prepares you far better than practicing the easy version where everyone agrees right away.

A conflict between two sponsors is not a problem you solve by pleasing both of them at once. It is a business decision, and your job is to make that decision visible, evidence based, and documented, then design a program that actually fits the choice the sponsors made. Handle it this way and you keep the trust of both sponsors, including the one who has to wait, because they watched you treat their request as real instead of letting it quietly disappear.