Separate Participation Data From Demonstrated Capability

A sponsor waves a completion report and calls it proof that people can do the job. Ninety percent showed up, so ninety percent must be ready. That leap feels natural to a sponsor who wants a clean number for a steering committee, but it collapses two different things into one. Attendance tells you who reached the learning event. It tells you nothing about whether that person can open a hard conversation, build a forecast, or run a negotiation the way the program intended. As a talent development leader, your job in this moment is not to argue that the completion number is wrong. It is to keep that number honest while building the evidence that actually answers the sponsor's question.

Why This Conversation Goes Sideways

People conflate access with skill because access is easy to measure and skill is not. A learning management system logs who clicked through a course in a few seconds. Judging whether someone applies a new behavior on the job takes observation, time, and a bit of design work. Sponsors under pressure to report progress will reach for the number that already exists. Once that number gets used in a slide deck as evidence of readiness, walking it back becomes a credibility problem for everyone in the room, not just for you. If you wait until the review meeting to raise this, you are contradicting a claim the sponsor already made public. If you raise it early, before the numbers get repeated to anyone above the sponsor, you are simply shaping how the data gets used. Timing decides whether this feels like a partnership or a correction, so raise it early. This is the same dynamic covered in Align People Process Timing With an Operational Deadlinewhere the cost of a people process rises sharply once it collides with a deadline nobody planned around.

How to Prepare Before You Meet

Before you sit down with the sponsor, name the specific behavior the program is meant to produce. Not communication skills in general, but something you could watch for, like opening a difficult conversation with a specific observed fact instead of a general complaint. Write down what an observer would see or hear if a manager did this well, and what they would see if a manager did it poorly. This single step turns a vague debate about readiness into a concrete, checkable thing.

Next, pick a measurement that fits the stakes. A full skills assessment for every participant usually costs more than it is worth. A sample of work products, a short roleplay, or a manager review of a real plan tells you almost as much for a fraction of the effort. Decide on the sample size and the review questions before you propose anything, so you walk into the conversation with a plan instead of an abstract objection. Set a review date that gives people enough time to actually try the new behavior at work. A review scheduled the week after the workshop shows you nothing except who remembers the slides.

Finally, decide what you will do with weak results before you see them. If the sample shows managers are not opening conversations well, is the next step more coaching, a revised job aid, or a second practice session. Deciding this in advance keeps the review meeting focused on action instead of blame.

What to Say in the Room

Open by affirming the number the sponsor already has, then draw the line between what it shows and what it does not.

Sponsor Mei said, "Ninety percent of managers completed the workshop, so we can report that they are ready for difficult conversations." Learning leader Arturo replied, "That ninety percent is real and it matters. It tells us access is not the problem, people are showing up and getting through the material. Readiness is a separate question, and completion alone cannot answer it. In the workshop, managers practiced opening a conversation with a specific fact rather than a general impression. Could we ask each manager to write a short plan for one upcoming conversation, then have their own leader check whether the opening names the actual issue and a clear next step." Mei asked, "Will that turn into a large reporting exercise for every manager in the program." Arturo said, "No. We pull a sample of twenty plans, use a three question review guide, and report the pattern, not a grade for each person."

Notice what Arturo did not do. He did not tell Mei the ninety percent figure was meaningless or that she had misled anyone. He kept the number and gave it a name, an access measure, then offered a second measure sized to the actual decision Mei needs to make. When Mei pushed on effort, he answered with a specific limit on scope rather than a vague reassurance.

Mistakes That Undermine Your Credibility

Do not attack the completion number itself. It is a legitimate measure of one thing, reach, and dismissing it makes you sound like you are protecting your own turf rather than improving the data. Do not propose a measurement plan so heavy that the sponsor has a reason to ignore it. A request to assess every single participant in depth will die in committee and take your credibility with it. Do not run the new assessment quietly and spring the results on the sponsor later. Agree on what a sample can and cannot prove before anyone sees a result, or every number you bring back will look like it was chosen to fit a conclusion. And do not let the review sit unused. A dashboard that separates access, practice, and observed use only helps if someone in the room commits to an action tied to each section, whether that is removing a barrier to attendance, revising a practice activity, or asking managers to coach a specific behavior.

How to Practice and Score This Conversation

Rehearse this exchange before you have it live, because the moment a sponsor pushes back on effort or cost, an unprepared answer sounds defensive even when the substance is right. Run the conversation with an AI counterpart on DealSpeak that plays a sponsor focused on a clean number for a steering committee, and push through at least one round where the sponsor questions the added workload. Score yourself on three things. Did you affirm the existing number instead of dismissing it. Did you name a specific, observable behavior instead of a general skill. Did you offer a scoped measurement plan with a sample size and a review method rather than an open ended promise to look into it. If your first attempt turns into a debate about whether completion data is useful at all, you have lost the frame. Reset and come back to the distinction between access and capability. Practicing this on HR and Leadership practice conversations gives you a repeatable way to test your opening line and your response to pushback before the real meeting, and a similar pattern for handling a challenge to your evidence shows up in Respond When an Employee Disagrees With a Performance Example.

Where This Leaves You

Attendance and capability answer different questions, and your job is to keep them labeled correctly even when a sponsor wants one number to do both jobs. Name the behavior, size the measurement to the decision, and agree on what the result can prove before anyone sees it. Do that consistently and your data stays trustworthy long after this one report is filed away.