How mapping knowledge prepares your enterprise for change

When Australia overhauled its aged care funding system last year, it put providers in the industry to a real test.

The new model swapped a relatively flexible arrangement with one that demanded precise, activity-level claiming. Every service delivered to every person had to be tracked, categorised and submitted correctly.

Get any of it wrong and the claim was rejected automatically. The wrong service, the wrong category, the wrong funding source, any of it could delay payment or stop the claim going through at all.

For a lot of providers, that was a real shock. Not because their staff weren't good at their jobs, and not because the technology let them down.

But because the knowledge required to claim accurately, including which categories applied to which services, how to handle unusual situations, what the system would and wouldn't accept,  had never actually been written down anywhere. 

It lived in the heads of a handful experienced people who had figured it out over time, mostly through trial and error.

Under the old system, those people could quietly catch a mistake and fix it before anyone noticed. Under the new one, the claim had to be right the first time, before it was submitted. 

Suddenly, knowledge that had only ever lived in a few experienced heads had to be consistent and reliable across a whole team. In most organisations, it wasn't. Administrative costs under the new model can outweigh revenue where process gaps go unresolved.

The knowledge gap had always been there. The regulation just changed what it cost.

This isn't just an aged care story

Australia's experience makes a good case study, but it’s not unusual. 

Regulators everywhere are starting to ask a different kind of question. Less "do you have the right processes documented?" and more "can you show me exactly how this decision got made?"

If you're in financial services, that might mean showing the reasoning behind an advice decision, not just proof a process was followed. In healthcare, it's evidence of clinical judgement, not just what's in the treatment record. In social care, it's being able to show how someone's individual circumstances actually shaped the decision made for them.

Whatever the sector, the pattern's the same. Eventually someone asks how a decision was really made, and the answer's nowhere to be found. That's usually the moment organisations discover the knowledge regulators want to see was never captured in the first place.

And it’s not a small gap. Up to 80% of what people know about their work is tacit, meaning unwritten, built from experience and held in someone’s head, rather than any system. 

Formal documentation tells you what's supposed to happen. It doesn't capture the judgment, the exceptions or the reasoning that make things work day to day. That's the gap regulation keeps exposing.

Getting ahead of it

The businesses that handle these moments best usually aren't the biggest or best resourced. They're just the ones who'd already made the effort to get their people's knowledge out of their heads and onto paper, before anyone came asking for proof.

That means capturing how work actually happens: the decisions, the exceptions, the reasoning, not just how it's supposed to happen. 

It means sitting down with your most experienced people and asking what they actually know, including the judgement calls, workarounds and patterns they've learned to spot without even thinking about it.

And it means turning all of that into something your organisation actually owns: documentation that reflects reality, decision logic new starters can genuinely follow, processes that don't fall apart the moment one person's out of the room.

Do that, and the next regulation change won't expose a gap. Because by then, it's already closed.

Australia's aged care providers are living this right now. Most industries will face their own version of this sooner or later. 

The real question is whether you get ahead of it, or wait until a regulation change makes the cost of the gap impossible to ignore.

Next
Next

Better by design: the efficiency gains hiding inside your operations