Ask whoever ran the training day how it went, and the answer is almost always the same: it went well. The facilitator was engaging and the feedback forms came back positive. The debrief was pleasant, too. Ask what has changed on the floor a fortnight later, and the answer gets quieter fast. It gets quieter still when the question is what changed in the metric the budget was meant to move.
That gap between a good day and a moved number is the most common outcome of training Oliver has seen in 25 years spent running it, commissioning it and cleaning up when it didn't land. It isn't a motivation problem, and it usually isn't the facilitator's fault either. Most training days are designed for enjoyment rather than application, and on a feedback form those two things look identical.
The size of that mistake scales with the size of the sign-off. A team leader booking a single workshop is committing an afternoon and a modest invoice; a CFO approving a leadership program, a COO resetting standards after an acquisition, or an operating partner reviewing a portfolio company's training spend is signing off a decision that either compounds for years or gets quietly rebooked next year because it taught the room nothing new. What separates those two outcomes is the design around the day, and a buyer can specify and check for that before signing.
The fortnight test
Most workshops pass in the room and fail outside it. Energy is high on the day, and the feedback is glowing. Come back two weeks later and ask what has changed about how people work, and the answers blur into "I've been meaning to" or the old habit wearing a new label.
That isn't a discipline problem, and it isn't the group being dishonest on the feedback form. What fades, fades because nothing in the fortnight afterward asked anyone to use it: no manager mentioned it in a one-to-one, no follow-up session returned to the part that was hardest to apply, and the job didn't change shape around the new skill.
Run the numbers on that outcome and the cost is not just the invoice. It is the day rate, plus the wages of everyone who was out of the business for the day, plus whatever cover or delay that caused, plus the near-certainty that the same gap gets a very similar line item in next year's plan. A workshop that doesn't hold costs twice: once as the wasted day, and again when the same gap gets rebooked next year.
Treat this as a motivation problem and the fix looks like a better speaker or a punchier slide deck. Treat it as a design problem, because that's what it is, and the fix looks completely different: less about the day itself, more about what surrounds it before and after.
What makes training stick
Four things separate sessions that change behaviour from sessions that simply get a good rating. None of them are exotic, and none of them cost significantly more to build in. They just have to be specified in the brief, because a provider who isn't asked for them by name will not offer them as a matter of course.
Practice in the room
Listening to someone explain a skill teaches a group what the skill sounds like, not how to do it under pressure, in their own words, with their own team. Sessions that hold up are built around rehearsal: the real difficult conversation, the real coaching moment, the real objection, all run out loud more than once, with feedback while it's still cheap to get wrong. That's the thinking behind frontline leadership training built this way: less time spent describing the skill, more time spent practising it badly in a safe room before doing it for real on the floor.
Application between sessions
A single day assumes a skill is either taught or not. Skills that stick are usually built across a few shorter sessions with a specific task set in between: try this one thing on three calls this week, then bring back what happened. The gap between sessions does more of the real work than the sessions themselves, because that is where the skill meets an actual customer instead of a role-play partner.
Manager reinforcement
This is the piece that gets skipped most often, and it decides whether anything survives past week three. A team's daily standard is set by what their manager notices, mentions and follows up on, far more than by what a facilitator said once before leaving the building. If the direct manager wasn't in the room, doesn't know what was covered, and never references it again, the training has nothing to anchor to once everyone is back at their desks. Building that reinforcement skill into managers themselves, rather than assuming it turns up on its own, is a large part of what train the trainer work is for.
Follow-up clinics
One injection of content rarely holds by itself. A short return session four to six weeks later, working through what has gone wrong since rather than repeating the original material, tends to do more for retention than adding another hour to the original day. It is also the most honest feedback a provider ever gets, because the room will say plainly what stuck and what didn't.
Build, buy or blend: choosing how you close the gap
Once those four mechanisms are accepted, a real decision follows: who designs and delivers this, and how much of that capability should live inside the business permanently. That decision sits with whoever owns the budget rather than with the provider being asked to quote for it. A provider will rarely recommend building the capability away from them.
A handful of questions decide it more reliably than habit:
- How often will this skill be needed? A one-off gap usually closes faster and cheaper bought in from outside; a skill every new hire will need for years starts to justify building delivery capability internally.
- How close does the skill sit to revenue or reputational risk? Frontline leadership, sales conversion and complaint handling sit close enough to the business model that keeping design control in-house, even with external delivery, is usually worth the extra coordination.
- Is there anyone credible to own it internally? Internal delivery only survives if someone senior enough is accountable for it after the first cohort, or "we'll build this ourselves" quietly becomes next year's abandoned initiative.
- How much time exists before the gap has to close? Standing up internal capability properly takes months; a well-designed bought-in program can be running within weeks.
Most organisations end up blending the two: a bought-in design for the harder or less frequent skills, delivered by people who do it every week, alongside an internal reinforcement structure of line managers and supervisors trained specifically to keep it alive after the provider leaves the building. Design without reinforcement fades by the fortnight test above. Reinforcement without a well-designed program behind it has nothing worth repeating.
Why the one-day workshop still gets bought
None of this is a secret. Most people responsible for buying training already suspect a single day rarely changes behaviour by itself. It keeps getting bought anyway, because a single day is easy to schedule, easy to cost as one line, and easy to report upward as complete. A closed item in a board pack beats an open one, even when the open one would have done more good.
A plan spread across two months is harder to fit around shift patterns, harder to reduce to one number, and harder to point to as a finished, ticked-off deliverable at the next leadership meeting. That's a real constraint on the person buying it, not a failure of judgement, and it's worth naming rather than treating the single day as the ideal format that just happens to be convenient.
If budget or rostering genuinely only allow for one day, say so to the provider before anything is signed. A provider who knows the real constraint can still design a single day to hold better than most do: shorter content, more practice, a lighter-touch follow-up built around a call or an email chain rather than a second workshop. What a provider cannot do is make a single day behave like a properly spaced program if nobody tells them the constraint exists.
Briefing a provider for behaviour change
The brief shapes the outcome more than the day itself does. "Run a half-day on communication skills for supervisors" gives a provider almost nothing to design against, and what comes back will look like a nice day out, because that description cannot produce anything else.
A brief built for behaviour change answers three things a vague brief skips. First, what is happening now: the specific conversations supervisors are avoiding, the specific gap in how feedback lands, instead of a general skill category. Second, what should look different in ninety days, and who would notice: a number on a dashboard, a comment in a one-to-one, a drop in a specific kind of complaint. Third, what capacity genuinely exists for follow-up, even when the honest answer is very little, so the design works around that constraint instead of pretending it doesn't exist.
It also has to name the direct managers: whether they will be in the room or briefed separately, and what they are expected to do afterward. A provider designing without that information is designing blind, and will fill the gap with a generic assumption that rarely matches the team in front of them.
This is the conversation worth having before any training consultancy work gets designed, because a day built against a vague brief gets designed to be liked, and being liked is a much lower bar than changing anything afterward. It takes longer than emailing over a request for a workshop proposal. It also produces a genuinely different result, and the half hour it costs is cheap against the price of the day it shapes.
Failure modes that quietly waste the budget
A handful of patterns show up again and again in training spend that doesn't hold, often visible well before the day itself goes wrong.
- There was no day-ninety marker. If nobody can say, before signing, what should look different in ninety days and who would notice, there is no way to know afterward whether the spend worked or merely felt good.
- The facilitator was chosen for rapport rather than fit. A likeable facilitator makes for a well-rated day; a facilitator who has diagnosed the specific gap is what makes it change anything. These are not always the same person.
- Managers were absent from the design conversation. Training a manager doesn't know about is training that manager cannot reinforce, however good the day itself was.
- The workshop gets bought mainly as cover. Training commissioned to be seen responding to an incident or an audit finding rarely gets designed for retention, because retention was never really the goal.
- The same gap gets the same booking again a year later. Rebuying the identical workshop for a problem it didn't solve the first time is the clearest sign the issue was never the day itself.
Any one of these is recoverable. Two or three together are usually a sign the budget is being spent to be seen spending it, rather than to move a number the business tracks.
Questions to ask before you sign
If a training line is already sitting in next quarter's plan, the questions below decide whether it becomes another well-rated day that fades by the fortnight test, or an investment that moves the number it was approved to move. They take an hour with a provider before a contract is signed, well before any invoice has landed.
- What happens on day fifteen? If the honest answer is nothing until the next booking, the design has a gap.
- How much of the day is practice versus listening? Content delivered with a short exercise bolted on at the end is not built for retention.
- Are managers involved before, during or after the session, or not at all? Training a manager doesn't know about is hard for that manager to reinforce.
- Is a follow-up mechanism included, or is it something to negotiate separately once the invoice has already landed?
- What does the provider do differently for a team that has tried this before and watched it fade? A provider with no real answer has probably not been asked the question very often.
Training will not fix everything a business brings to it. If the real issue is a process that punishes the behaviour just taught, or a supervisor with no time left in the week to coach anyone, the workshop can be excellent and still not hold, because the environment around it hasn't changed. Where it's genuinely unclear whether training, structure or something else is the right starting point, raise it directly before the budget is committed rather than after: start that conversation.
Frequently asked questions
Does a longer or more expensive program retain better than a single day?
Not automatically. Length matters less than what surrounds it: a well-designed half-day with real practice and a follow-up session tends to outperform a full day with neither, because retention comes from reinforcement more than from hours spent in the room. Spend more only where it buys more practice or more follow-up. More content alone rarely earns the extra budget.
How do we know if training is the right fix, rather than a process or resourcing problem in disguise?
If the same mistake keeps happening despite people clearly knowing what to do differently, the gap is rarely a skills gap. Training closes a genuine skills or confidence gap; it will not hold against a process that punishes the new behaviour or a manager with no time left in the week to coach anyone.
What should a training brief include beyond the topic and the headcount?
A good brief states what is happening now, specifically, and what should look different in ninety days, including who would notice the change. It also names the direct managers, what they are expected to do afterward, and what capacity genuinely exists for a follow-up session once the day ends.
About the author
Oliver Catt is the founder of The Cattalyst. He has spent 25 years inside contact centres, customer service, sales and training operations, and now helps organisations develop their leaders and build outsourced teams through a global partner network.
Start a conversation with Oliver
