Over the past few months, I’ve had a string of conversations that all start the same way.
Someone, usually in HR or operations, leans in and says:
“Our training is… kind of all over the place.”
They’re not wrong. I hear about folders scattered across SharePoint and Google Drive. A few PDFs that haven’t been updated since 2018. Spreadsheets tracking completions (if they’re tracked at all). And almost always, there’s one person who “kind of knows where everything is” – the unofficial keeper of the training kingdom.
On the surface, this patchwork can feel like flexibility. Each team builds what they need, when they need it. No waiting on approvals, no central bottleneck.
But here’s what I’ve learned after more than a decade of watching these setups in action: decentralised training feels agile… right up until you try to scale it or audit it.
The Hidden Cost of Decentralised Training No One Is Counting
The biggest trap with decentralised training is that the costs don’t show up as a neat line item in the budget. They’re invisible, but very real. And they tend to show up all at once when something breaks – a compliance breach, an audit, or a critical onboarding failure.
One cost is time. Without a central approach, every department recreates the wheel. Onboarding checklists get rebuilt five different ways. Policies are rewritten instead of reused. I’ve seen teams spend weeks creating content that already exists in another corner of the organisation – simply because no one knew it was there.
Quality takes a hit too. When training lives in silos, it ages at different speeds. One manager updates a safety process. Another forgets. Two people in the same role can be taught conflicting information, both thinking they’re right because “that’s how I was trained.” Over time, these variations create a fractured learning culture.
Risk is the most dangerous cost. In a decentralised model, compliance records are scattered, sign-offs are buried in email threads, and there’s no single source of truth. When an audit lands, teams scramble to piece together evidence. If they can’t, the consequences range from fines to reputational damage.
Then there’s the cost to engagement. Learners notice inconsistency far quicker than leaders expect. If every course looks, feels, and functions differently – new templates, different tone, varying quality – they start to tune out. Training becomes something to get through, not something to learn from.

Why This Happens in Mid-Sized Organisations
In most mid-sized organisations, L&D isn’t a dedicated department. It’s a “side-of-desk” job. HR might oversee training, but they’re also juggling compliance, recruitment, onboarding, employee engagement, and a dozen other priorities. Training gets built reactively, in the cracks between other tasks.
Without a central framework, local leaders step in to fill the gap. They create content for their teams, often doing a great job, but without alignment to what other parts of the organisation are doing. It’s well-intentioned, but without coordination, it produces a patchwork. And patchworks don’t scale.
This isn’t about blaming individuals. It’s about recognising the structural reality. If no one is empowered – and resourced – to own training across the organisation, decentralisation will happen by default. It will work for a while. But it can’t keep up with growth, change, or scrutiny.

Moving from Patchwork to Playbook
The solution isn’t to centralise everything. That just creates bottlenecks and slows down decision-making. The real opportunity is to identify what absolutely must be consistent organisation-wide – and lock that in – while giving local teams the flexibility to adapt everything else.
I call this laybook thinking. The idea is simple: decide on your non-negotiables, build them once, keep them updated in one place, and give local teams the tools and guardrails to customise the rest.
For most organisations, the non-negotiables are three to five processes that protect compliance, culture, and critical skills. These might include onboarding, WHS compliance, key policy training, and role-specific skills that can’t vary between sites. Everything else – local onboarding extras, department-specific SOPs, role-based skills – can and should be tailored by local teams.
This approach ensures consistency where it matters, while preserving flexibility where it’s valuable.

What Playbook Thinking Looks Like in Practice
One organisation I worked with had wildly different onboarding experiences across departments. Some ran a three-day program. Others had a three-hour slideshow. A few handed over a checklist and called it done.
We started by standardising only the essentials: a welcome from leadership, an overview of values and organisational structure, core compliance modules, and key operational policies. Everything else was left to departments to tailor.
Six months later, the results were hard to ignore. Time to productivity dropped because new hires got the essentials faster. Compliance reporting became a single-click process instead of a multi-day chase. Local leaders spent less time building from scratch and more time refining training that mattered to them.
This is the power of the playbook: a shared foundation that still leaves room for context and creativity.
Why the Playbook Approach Works
Playbook thinking works because it addresses three major challenges at once.
First, it creates consistency where it matters most. Compliance, culture, and critical skills are protected from drift. You can be confident that no matter where someone is in the organisation, they’ve had the same baseline training.
Second, it preserves flexibility where it’s genuinely useful. Teams can adapt training to local conditions, roles, or challenges without undermining the core. This flexibility is especially valuable in industries with varied operations across sites.
Third, it creates clear ownership. Central teams own the playbook. Local teams own the application. Everyone knows their role, which reduces duplication, improves accountability, and builds trust in the system.
The Mindset Shift Leaders Need
The hardest part of this shift isn’t the technology. It’s breaking the “everyone does their own thing” habit and replacing it with “we share a common playbook.”
This requires being deliberate about what gets centralised and committing to keeping those assets current. Outdated core content is worse than no core content at all – it erodes trust and encourages workarounds. It also means equipping local leaders with the skills, templates, and support they need to make the content their own without drifting into chaos.
It’s a cultural change as much as a process change. Leaders need to model the playbook mindset and reinforce that the goal is not to control local teams, but to free them from reinventing the wheel so they can focus on what’s unique to their work.
Starting Small and Building Momentum
If this sounds like your organisation, the key is not to try to centralise everything at once. That’s the fastest way to overwhelm your team and stall the project.
Instead, start with one process – onboarding is usually the easiest win – and standardise it. Test it. Get feedback. Iterate. Once the benefits are clear, add the next piece to your playbook. Over time, you’ll replace the hidden costs of decentralisation with the compounding benefits of consistency.
This gradual approach not only makes the workload manageable, it also gives your teams time to adjust to the new way of working and see the benefits for themselves.
The Payoff of Moving from Patchwork to Playbook
The shift from patchwork to playbook delivers benefits well beyond efficiency and compliance.
It builds confidence in the organisation’s training. Leaders can trust the essentials are covered. Employees know they’re getting the right information. Audit prep becomes a matter of running a report, not a week-long fire drill.
It strengthens culture. When everyone shares the same foundation, it’s easier to feel like part of one organisation – even across sites, regions, or roles. This shared understanding creates cohesion and alignment.
And it frees up resources. The time saved on duplication can be redirected into improving training quality, adding new programs, or supporting managers to coach and develop their teams.

Final thoughts
Decentralised training often grows out of necessity. But if you want to scale, stay compliant, and build a cohesive culture, it’s not enough to “make do” with what each team creates. Playbook thinking protects what’s essential, empowers your people, and sets you up for training that works today – and still works when you’re twice the size.
Further Reading
- When Training Starts Falling Through the Cracks
- What LMS Reporting Should Actually Look Like
- LMS Integration Isn’t a Nice-to-Have, It’s What Keeps Your Data Clean
- Going Beyond Spreadsheets in Training Compliance
- 7 Steps to Quickly Implement Online Compliance Training
- The Silent Killer of LMS Rollouts: Inconsistent Branding and Customisation