The Art of Leaving Things Out: A Practical Case for Pruning Your Training Plan
Photo: Alvin kipchumba, CC BY-SA 4.0, via Wikimedia Commons
Most training plans I see have a growth problem. Not in ambition — in content. Every review meeting adds something. A new module here, an extra handout there, a half-day bolted on because someone raised a concern in a team meeting. Very few plans have a mechanism for taking things away.
That's a shame, because the best training plans I've worked with aren't the fullest ones. They're the ones that have been edited. They have a delete column.
The plan that only grows
A training plan is a bit like a cupboard. You keep putting things in because they seem useful at the time. Six months later you can't find the thing you actually need, and half the contents are duplicates or dead batteries.
In our work with UK teams, this usually shows up as a calendar packed with sessions that people attend politely and then forget by Thursday. The plan looks thorough. It isn't. It's just busy.
A delete column is not about cutting training for the sake of it. It's a formal place in the plan where you ask, every time: what are we taking out? What has stopped earning its place?
Why deletion feels risky — and why it usually isn't
The instinct to keep everything comes from a reasonable place. You don't want to drop something that might matter. You don't want to be the person who removed the safeguarding refresher or the manual handling module.
But here's the thing: a plan that tries to cover everything rarely covers anything deeply. Attention is finite. If a session is on the calendar, someone has to prepare it, deliver it, and then — crucially — your team has to remember it. That's a lot of cost for content that might not be changing behaviour.
Deletion isn't the same as neglect. It's prioritisation with a paper trail.
The Tuesday-after test
If you want a simple way to spot content that looks useful but doesn't change behaviour, try this. For any module or session, ask: what will people do differently on the Tuesday after the course?
Not what will they know. Not what will they have discussed. What will they do — at their desk, in a team meeting, on a call — that they wouldn't have done otherwise?
If the honest answer is 'nothing much', you've found a candidate for the delete column.
This test is deliberately unglamorous. It doesn't care how interesting the content is or how well it was received. It only cares about the gap between the training room and the day job.
What to cut first
You don't need to start with the big stuff. In my experience, three types of content are usually safe to reconsider.
1. The stuff people already do every day
If your team already uses a tool, follows a process, or has a habit that works, a training module explaining it from scratch may be adding little. A quick refresher or a one-page prompt might do the same job. Better still, ask the team what they'd actually find useful. You'll often find the gap is somewhere else entirely.
2. The stuff that exists because it's interesting to the trainer
This is a gentle one, because trainers are enthusiasts. We like the subject. We like the detail. But a session that exists mainly because someone enjoys delivering it is not the same as a session that earns its place in the plan.
The test: would you still include it if you had to justify the time away from the desk to a sceptical line manager? If the answer is 'probably not', it belongs in the delete column — or at least in a 'revisit later' pile.
3. The one-off request that became permanent
A team member asked for a session on a specific topic two years ago. It ran once, went fine, and has been on the plan ever since. Nobody has asked for it again. That's not a training need; that's a habit.
Cut it, or replace it with something the team is asking for now.
Cutting without losing what matters
The delete column isn't a purge. It's a filtering process. Some things must stay, even if they're not exciting: statutory training, safety-critical procedures, the skills that keep the team running when someone is off sick.
Keep a short 'essential' list. Anything that isn't on it should be able to answer the Tuesday-after question clearly. If it can't, it's a candidate for deletion — or for a different format. Sometimes the answer isn't 'cut it' but 'make it shorter, more practical, or closer to the desk'.
Make it a habit, not a clear-out
The best time to use a delete column is every time you add something. If a new module goes in, something else comes out. That might sound brutal, but it keeps the plan honest. It also makes the plan easier to defend when someone asks why a particular session is there.
A leaner plan is easier to deliver, easier to remember, and easier to improve. It respects people's time. And it sends a clear message: we're not just filling the calendar. We're choosing what actually helps.
So next time you review your training plan, add a column. Not for new ideas — for the ones you're ready to let go.