The Training Request Is Not the Problem: What to Ask Before You Say Yes

A training request arrives as a topic. “We need a session on communication.” “Can you do something on conflict?” “The team needs to be more accountable.” Each one is a sentence someone wrote after a bad week, and each one hides a decision the requester already made without saying so: that the gap is a skill, that the skill is the same for everyone, and that a few hours in a room will close it.

Any of those three can be wrong. The gap may be a rule nobody enforces. The skill may be missing for two people, not twelve. A few hours may be too short, or the wrong shape entirely. When I say yes to the topic, I inherit all three assumptions. That is why I treat the request as the start of a conversation, not the scope of work.

This is not a quibble about wording. A session built on the wrong diagnosis still gets delivered, still gets a decent satisfaction score, and still leaves the original problem standing. Then the same person asks for the next session, and the cycle repeats with a bigger bill.

I do not open with a proposal. I open with questions, and I keep the meeting to about forty minutes so the requester can see the method is not a stall. This is training request intake, and the questions are the same every time because they are the ones that separate a training problem from everything else.

1. What did you see or hear that made you ask? I want one specific moment, not a summary.
2. What should people be doing instead, in terms I could watch happen?
3. Who is doing it well today, and what do they do differently?
4. What has already been tried, and what happened?
5. What would stop someone from doing it even if they knew exactly how?
6. Who has to support this the week after, and do they know they are involved?
7. How will you know in sixty days that it worked?

The fifth question does most of the work. If the honest answer is a broken form, a manager who rewards the opposite behavior, or a tool that makes the right step slower, then information will not move anything. I lay out that test, with a worksheet, in how to run a training needs analysis for a small team. This post is about the conversation that comes before the worksheet.

Three of those questions regularly turn the request into something else.

“What did you see?” People who ask for communication training usually have one scene in mind: a handoff that went wrong, a meeting where two people talked over each other, an email that landed badly. One scene points at a behavior I can design for. Vague frustration points at a topic, and topics produce slide decks.

“Who is doing it well?” If three people on the team already handle it fine, the gap is not a missing skill. Something is different about their conditions, their manager, or their workload. I would rather learn from them than teach around them.

“What would stop them?” This is where requests collapse most often, and where I am most useful. Sometimes the answer is that nobody has told people what good looks like. That is a clarity problem, and a one-page expectation doc costs less than a workshop.

I say no to a session, or to the session as requested, in four situations. These are the signals I look for, and they come up often enough that I raise them early.

• The behavior is already known and nobody is held to it. People can do the thing. The system does not ask them to.
• The problem is one or two people. A group session is a polite way to avoid a direct conversation, and the rest of the room knows it.
• The conditions block the behavior. If the tool, the staffing level or the deadline makes the right action impossible, teaching it adds frustration.
• Nobody will reinforce it afterward. If the managers are not involved before and after, the session ends and so does the change.

Saying no sounds like bad business, and in the short term it is. Over a longer view it is the reason a requester trusts the next recommendation. A facilitator who can say “this is not a training problem” is a facilitator whose yes means something.

When the questions point at a real skill gap, scoping a facilitation engagement becomes much easier, because the questions already produced the pieces. The observable behavior becomes the objective. The people who do it well become the examples. The conditions that block it become the thing the session names honestly, or the thing the sponsor agrees to fix in parallel.

Then the shape follows. A gap held by one team is a small live session with practice. A gap that needs repetition is two short blocks with work in between, a pattern I cover in how long a training session should be. A gap that is mostly information may be a document and a short Q&A, which is cheaper, and I will say so. The cost conversation gets simpler too, since the price reflects a defined scope; see what a corporate facilitator costs.

I also write down, in the first meeting, what I will watch for afterward. If you have not already planned it, how to measure training covers the options a small team can actually run.

“We do not have time for a discovery phase.” The first meeting is forty minutes. A session that misses costs the session, the preparation and the credibility of the next one.

“Leadership already decided we need this.” Then the forty minutes is where we make that decision stronger, by naming what the session is meant to change. If leadership is right, the answers show it quickly.

“Just give us the session; we will sort the rest out.” I can run a session on request. I will tell you first what I think it will and will not fix, in writing, so we both know what we are measuring.

If you are the person asking, write down one specific scene that prompted the request, and write down what you would want to see instead. Two sentences each is enough. Then answer the fifth question honestly: if people knew exactly what to do, what would still stop them?

If the answer is nothing, you have a training problem and we can design a good session. If the answer is something, you have found the lever before spending a budget on the wrong one. Either way the request improves, and the next conversation starts further along. If you want a second pair of eyes on a request you are weighing, the free consult is built for it.

Want a second look at a training request?

Bring the request and the scene behind it. In a free consult we work out whether it needs a session, a smaller fix, or something else.