Discuss a Learning Pilot With Different Results Across Locations

A learning pilot rarely produces the same result in every location, and that is exactly when the conversation gets hard. One site shows real change, another falls flat, and a sponsor in the room wants a single verdict about the whole program. As a talent development leader, your job is not to defend the pilot or apologize for it. Your job is to explain what the data actually supports, name what is still unknown, and give sponsors a decision they can act on without overreaching.

Why this conversation goes wrong

Sponsors want speed. A quarter has already passed, budget is on the line, and one strong number from one site feels like enough to move. The leader in the room who reports the results often gets pulled toward one of two bad instincts. The first is to agree that the good site proves the program works and let the sponsor launch everywhere. The second is to get defensive about the weak site and start explaining away the result instead of examining it. Both instincts skip the actual question, which is why the two locations produced different outcomes. Workload, staffing, manager habits, and measurement all vary from site to site, and any one of them can explain a gap that has nothing to do with the design of the learning itself.

There is also a plain anchoring problem. Once a sponsor hears one good number, that number becomes the story, and every later fact gets measured against it instead of examined on its own. A talent development leader who does not interrupt that pattern early ends up defending a launch decision that was made before the real evidence was on the table.

This is also where scheduling differences quietly distort a pilot. A site with shift workers or rotating coverage can show lower completion simply because employees could not get into a room at the scheduled time, not because the content missed the mark. If that describes one of your locations, it is worth reading Adapt a Learning Schedule for Shift Employees before you present results, because a scheduling problem and a program problem look identical on a dashboard.

How to prepare

Before you sit down with sponsors, build a plain comparison of what actually happened at each site. Note attendance and completion at each location, whether a manager reinforced the practice in team meetings, what else was happening operationally during the pilot window, such as a system change or a busy season, and how the outcome was measured at each site. If one location logged behavior change through direct observation and another relied on a survey, that difference alone can produce a gap that has nothing to do with the learning.

Check attendance patterns before you assume disengagement. A location with unusually low participation sometimes has an access problem rather than a motivation problem. Employees skip a session because they cannot reach it, not because they do not value it. The post on Investigate Access Barriers When Learning Enrollment Is Low walks through how to tell the two apart, and running that check before your sponsor meeting saves you from defending a design flaw that is really a logistics flaw.

Walk in with a specific recommendation, not just a list of open questions. Sponsors respect a leader who says what should happen next even while acknowledging the evidence is incomplete. Decide in advance whether you want to test a single change in a second site, extend the pilot window, or hold the design steady and only fix a known logistics issue. Write that recommendation down before the meeting starts, so pressure in the room does not talk you out of it.

What to say

Priya, a talent development leader, presents pilot results to two regional sponsors. In Eastfield, employees completed the practice and supervisors discussed it in weekly team huddles. In Lakeside, attendance was lower and the huddle got dropped during a busy stretch.

One sponsor leans forward and says, "Eastfield improved. That is the proof we needed. Let's launch this everywhere next month."

Priya nods before answering. "Eastfield gives us a real signal, and I do not want to lose that. But before we scale, I want to understand what made Eastfield different. Supervisors there ran a weekly huddle to reinforce the practice. Lakeside did not, and attendance dropped during the pilot window. I want to know whether the result came from the content or from that huddle routine."

The sponsor pushes back. "We cannot wait through another quarter just to compare huddle schedules. Every month we delay costs us."

Priya holds her ground without dismissing the urgency. "I am not proposing a full quarter. I am proposing one more site running the same huddle routine as Eastfield, over four weeks, so we know whether that routine is the reason it worked. If the second site also improves, we scale with confidence and we know exactly what has to travel with the training. If it does not, we just saved ourselves from rolling out something that only worked because one manager happened to reinforce it well."

The second sponsor asks the practical question. "What do you need from us to make that happen?"

"Confirmation that the third site can run the same huddle cadence for four weeks, and forty minutes with both site leads and our learning analyst to map out what we track," Priya says. "I will bring you a recommendation right after that."

Mistakes to avoid

1. Treating one strong site as proof for the whole population. A single location can outperform because of a specific manager, a specific team, or a quiet quarter. It says nothing on its own about a site with different workload or staffing.

2. Answering urgency with more caution and nothing else. Telling a sponsor to wait without offering a bounded next step reads as stalling, even when your instinct is correct.

3. Comparing outcomes without checking how each site measured them. A completion rate from one system and a manager rated by a checklist are not the same evidence, and averaging them hides more than it reveals.

4. Presenting the gap as a mystery instead of a set of named, checkable factors. Sponsors lose confidence in a leader who shrugs at a puzzle. They gain confidence in one who names three specific factors and proposes a way to test them.

5. Letting the low performing site disappear from the story once the good site gets attention. The weaker location still has employees who need the skill, and it still holds clues about what a wider rollout will need to succeed there.

How to practice and score it

This conversation is hard to get right live because the pressure to say yes shows up fast and the sponsor's frustration is real. Rehearse it before you walk into the room. Have a manager or colleague play the impatient sponsor and push you the way a busy regional leader would, including the moment where they ask you to commit to a launch date on the spot.

Score your own performance on three things. Did you name the specific differences between sites instead of speaking about the gap in general terms. Did you propose a bounded next step with a timeline, rather than an open ended request for more time. Did you keep the sponsor's urgency in the room instead of brushing past it. A manager listening in can also check whether you gave a recommendation at all, since a leader who only raises questions in this meeting has not actually done the job.

A practice tool like DealSpeak lets you run this exact exchange with an AI counterpart that argues back the way a real sponsor would, and scores how well you held the line on evidence while still respecting the deadline pressure. You can find this scenario and others built for talent leaders among the HR and Leadership practice conversations.

Different results across locations are not a verdict on your program, they are a set of clues. Name the conditions that differ, propose a specific test, and give sponsors a real decision instead of a guess dressed up as certainty.