Diagnose Whether a Requested Workshop Addresses a Real Behavior Gap

A workshop request usually points at something real, but the label the sponsor gives it rarely matches the actual gap. "We need a workshop on communication" or "our managers need accountability training" describes a feeling, not a behavior. Before you commit a design team and a training slot to it, you need to know what people are supposed to do differently, what they do instead, and what is stopping them. Skip that step and you risk building a polished session that never touches the real problem, because the problem was never a skills problem to begin with.

Why This Conversation Goes Wrong

Sponsors come to you with a solution already named. They say workshop because that is the tool they know you have. Underneath the request is usually a manager who is frustrated, a metric that slipped, or an executive who wants visible action. None of those things tell you whether the fix is training, a process change, a staffing decision, or a shift in who has authority to decide something.

The trap is agreeing to build before you understand the behavior. You say yes to the topic, you schedule the design work, and three months later the pilot lands and nothing changes on the floor. Now you own a training program that did not work, and the sponsor still has the original problem. Worse, you have spent credibility you needed for the next request. The conversation goes wrong when you treat the request as a brief instead of a hypothesis that needs testing.

How to Prepare

Before you sit down with the sponsor, decide what evidence would tell you this is a genuine behavior gap rather than a structural one. You want two or three concrete work examples, not a general impression. Ask yourself what you would need to see or hear to know that people understand what to do, have the authority to do it, and still do not do it. That is the signature of a real capability gap. If people do not have the authority, or the process actively works against the behavior, training will not move it.

Read whatever documentation already exists on the process in question, meeting notes, ticket data, performance reviews, anything that shows the pattern in its natural setting rather than as a summary someone gave you secondhand. Bring a short list of questions rather than a fixed opinion. Your job in this meeting is not to defend a design, it is to find out whether a design is even the right response.

What to Say

Sponsor Priya opened with the request. "Our team leads need a workshop on giving feedback. They are too soft on performance issues." Learning leader Devon asked her to make it concrete. "What would I actually see a team lead doing differently if this were fixed?" Priya thought about it and said, "They would name the specific behavior that is a problem instead of talking around it in the one on one."

Devon pushed one step further. "Can you send me two examples, maybe a summary of a recent one on one or a case where a performance issue got raised late? I want to see whether the team lead avoided naming the behavior, or whether something else was going on, like not having the performance data in front of them, or not being sure they had backing from HR to have that conversation." Priya agreed to send two examples from different teams.

A week later they reviewed the examples together. In both cases the team lead had the observation but stopped short of stating it directly. Devon asked, "Do they have access to the performance data before the conversation, and do they know HR will back them up if the employee pushes back?" Priya checked and found that one team had no advance access to attendance records, so the lead was flying without evidence. Devon said, "That changes the design. We can build practice around naming a specific behavior and setting a clear next step, but we also need someone to fix the data access problem, or the practice will not transfer." Priya agreed to raise the data access issue with the operations lead separately.

That exchange did the real work of intake. Devon did not refuse the request or slow walk it. He tested it, found a genuine behavior component and a genuine structural component, and separated them so the workshop only carries what it can actually fix.

Mistakes to Avoid

Do not accept a topic label as a specification. "Communication," "accountability," and "ownership" are not behaviors, they are categories that hide several different behaviors underneath. Ask the sponsor to point at a specific moment and describe what happened.

Do not skip the question about authority and reinforcement. A manager can practice a new behavior perfectly in a session and abandon it within a week if their own manager does not expect or reward it. If nobody above the group is going to reinforce the change, the workshop will not stick, no matter how well it is designed.

Do not let the sponsor's urgency substitute for evidence. A sponsor under pressure wants a date on the calendar more than they want a correct diagnosis. It is fine to hold two conversations, one to acknowledge the pressure and give a timeline, and a second one once you have looked at real examples. Rushing the diagnosis to protect the schedule usually costs you more time later when the pilot fails to land.

Do not treat this as a one time filter you apply and then forget. Keep the evidence you gathered. When the pilot runs, you will want to check it against the original examples, not against your memory of the meeting.

How to Practice and Score This Conversation

This is a conversation worth rehearsing before you have to run it live, because the sponsor in the room will resist your questions in ways that are hard to predict from a script. A practice partner playing the sponsor should push back at least once with something like "I do not have time to pull examples, just build the workshop," so you have to hold your ground without sounding dismissive of their urgency.

Score yourself on a few things. Did you get the sponsor to describe an observable behavior instead of a label. Did you ask for actual work examples rather than accepting a general impression. Did you ask about authority and manager reinforcement before agreeing to design anything. Did you leave the conversation with a next step that is not automatically a workshop, such as reviewing documents, checking a process, or coaching a manager directly. If you found yourself agreeing to a build before any of that was answered, mark it as a miss and try the conversation again.

DealSpeak is built for exactly this kind of rehearsal. You can run the sponsor conversation against an AI counterpart that argues back the way a real sponsor does, and get scored on whether you actually diagnosed the behavior or just took the request at face value. If your team also handles onboarding, look at Plan Accessible Learning Participation Through the Approved Support Route for a related intake conversation, and if you work adjacent to employee relations cases, Receive Additional Documents After an Employee Relations Intake covers a similar discipline of separating fact from assumption before you act.

Closing the Loop

Build a short evidence sheet for every workshop request, with the topic as stated, the work examples, the desired behavior, the barriers you found, and whether managers will reinforce it. Ask the sponsor to mark which parts of that sheet are known facts and which are still assumptions. More HR and Leadership practice conversations are available if you want to rehearse this kind of intake before your next request lands on your desk.