Before You Book the Course: A 20-Minute Diagnosis for Managers

When a deadline slips or a handover goes sideways, the first suggestion in many team meetings is a course. It is an understandable reflex. A course is visible, budgetable and easy to put in a calendar. It also feels like action.

But a course only fixes one kind of problem: a gap in knowledge or skill. Plenty of workplace wobbles are not that. They are process gaps, tooling gaps, memory gaps or feedback gaps wearing a training-shaped coat. If you book the course before you diagnose, you pay twice — once for the training and again for the disruption when nothing changes.

Here is a practical way to run the diagnosis before you spend the money.

Look at the task, not the complaint

Start with a recent example. Not the broad statement that the team are rubbish at admin, but the specific thing that happened on Thursday. Ask three questions: what was supposed to happen, what happened instead, and where exactly did it break down?

That last question matters most. If the answer is that nobody knew the correct process, you may have a training need. If the answer is that the form timed out, the approval sat with someone on leave, or the system would not let them save the record, a course will not help. You need a process or tooling fix.

Managers often skip this step because the complaint sounds like a capability issue. It rarely is once you get into the detail. Sit with someone for ten minutes and watch them do the task. You will learn more than you would from a whole survey.

Four gaps that often get mislabelled as training

Process gap. The steps are unclear, there are too many handoffs, or nobody owns the final check. People may know what good looks like but the workflow makes it hard to deliver. Training can explain the process, but it cannot remove three unnecessary approvals.

Tooling gap. The system is slow, the permissions are wrong, or the fields do not match the real work. A course can make people fluent in a bad process. It will not make the process less annoying.

Memory gap. They knew it once, but not at the moment they needed it. This is normal. People forget five-step routines when they are busy. A job aid, a checklist or a short refresher at the point of need will do more than a day away from the desk.

Feedback gap. Nobody notices when the task is done well or badly. There is no review, no consequence and no regular conversation about it. Training can raise awareness for a week. It cannot replace the manager's attention.

There is a fifth gap worth naming too: confidence. Someone can do the task in theory but freezes when a customer is waiting. That is not usually solved by more information. A short practice drill, a shadowing session or a gentle first attempt with backup is often the better answer.

The 20-minute triage

Before you approve a course, run this short set of questions with the person who wants it.

Can anyone on the team do this reliably? If yes, you do not have a whole-team knowledge gap. You have a know-how transfer problem. Capture what the capable person does and turn it into a simple guide or a peer session.

Can the person do it when the job aid is open? If yes, it is recall, not knowledge. Build the job aid properly and make it easy to find. That is not cheating. It is good design.

Is the sticking point a decision, a system or a step? Decisions may need training or coaching. Systems and steps usually need fixing, not teaching.

What would we see change after the course? If you cannot describe the observable difference in the first fortnight, do not book yet. A course without a follow-up plan is just a day out.

Who will follow up in week two? If the answer is nobody, the training is likely to die by Friday. Someone has to check whether the new skill is being used, and help when it is not.

When a course is the sensible move

This is not an argument against training. Far from it. A course is often exactly right when people are new to a role, when a new system or regulation is landing, when the knowledge is complex and needs practice with feedback, or when the team needs a shared language for a difficult part of the work.

Good training gives people time to try, fail safely and ask questions. It builds capability, not just awareness. But even then, the course is only one part of the fix. The manager still has to make space for practice afterwards, and the team still needs the tools and processes that let the new skill survive.

Small fixes that beat a course — sometimes

A one-page job aid stuck near the desk can outperform a half-day workshop. A ten-minute huddle demonstration can sort out a recurring error. A two-column table showing what to do and what not to do can be enough. So can a short shadowing swap, a checklist at the point of use, or simply giving one person clear ownership of a messy process.

None of this is glamorous. It does not come with a certificate or a lunch. But it often works faster, costs less and sticks because it lives where the work happens.

Make the request prove itself

If someone asks for a course, do not say no immediately. Ask what they will do differently at their desk afterwards, and what is stopping them doing it now. The answer will usually tell you which gap you are dealing with.

If they say they do not know how, training may be the answer. If they say the system will not let them, you have just saved the training budget. If they say they did not know it mattered, you have a feedback problem, not a course problem.

A course is a tool, not a cure-all. The manager's job is to diagnose first, then choose the intervention that fits. Book the course when it is the right answer — not when it is simply the most comfortable one.