Organizational Learning as a System Problem

A principal I was coaching recently walked me through his improvement plan. New instructional strategies, a rollout calendar, a training schedule for the fall. He was proud of the plan, and it was a good one on paper.

Halfway through the conversation, I noticed something the plan didn’t account for. He understood the problem. He’d done the work of naming it, sizing it, deciding training was a viable piece of the answer. His teachers and his other administrators hadn’t done that work. They were being handed a training calendar built on questions they’d never been asked.

I told him I didn’t think his team needed more training. I thought they needed the foundational conversation he’d already had with himself, and then support implementing what came after it.

What Training Assumes, and What It Doesn’t

Training assumes the problem is capability. Someone doesn’t know how to do the thing, so you teach them the thing. That’s a real problem sometimes, and training is the right answer for it.

But most of the time, in schools and in companies, the gap isn’t between what people know and what they don’t know. It’s between what leadership understands about the problem and what everyone else has been told about it, and between what’s expected of people and what actually shows up in practice once the day gets hard.

Neither gap closes with a workshop. In practice, closing the first one means one working session before the training gets built, not after. Not a kickoff, not a slide explaining the decision. A session where the team looks at the actual evidence, the observation data, the numbers, the specific pattern that convinced leadership something needed to change, and names the problem in their own words before anyone proposes a fix. If the room can’t get to roughly the same diagnosis leadership already reached, that’s not a training problem waiting to happen. It’s the understanding gap, right there, and it’s cheaper to close it now than to discover it three months into a rollout that isn’t sticking.

The second gap closes with problem solving support while the work is happening, someone helping a team hold focus on the improvement effort when three other priorities are competing for the same hour.

Training builds capability. It doesn’t build shared understanding, and it doesn’t build follow-through. Most organizations only budget for the one thing training actually does.

The Training Calendar Is Not a Learning System

Here’s the pattern I see constantly, in K-12 and in corporate learning functions alike. Leadership identifies a gap, understands its shape, and decides on a response. Then the response gets scheduled and rolled out to everyone else, on the assumption that everyone else already sees the gap the same way leadership does. Usually they don’t. Nobody asked them to.

The training happens, gets good marks, and the org moves on to the next initiative. Three months later, the gap is still there, and the response is more training.

That’s not a learning system. That’s a training calendar mistaking itself for one, skipping the step where people get oriented to why any of this matters before being told how to do it.

None of this is faster, and that’s worth naming plainly. A working session before the rollout costs time the training calendar doesn’t ask for, and that’s precisely why most organizations skip it. The calendar looks like momentum. A room full of people getting oriented to a problem looks, for an afternoon, like nothing is happening yet. That trade-off is real. The cost of the working session is upfront and visible. The cost of skipping it is deferred and usually invisible, until the third round of retraining makes it obvious.

A learning system does something a calendar can’t. It starts by checking whether the people expected to change their behavior understand the problem the same way the people who designed the response do. If they don’t, no amount of training closes that distance, because training answers how and the real gap is still sitting at why. And once that foundation exists, a real learning system keeps going. It puts people in position to practice the new behavior under real conditions, with real competing priorities, and it puts someone in the room, virtually or literally, who can catch the moment a team starts drifting back to the old default and name it before it hardens into habit.

The principal’s team didn’t just need someone checking in when the strategy got hard to hold onto. They needed the conversation that would have made the strategy feel necessary in the first place, the one their principal had already had with himself and never fully brought them into.

What This Looks Like in Practice

The corporate version of this is nearly identical. A sales team gets trained on a new discovery framework. Leadership rolled it out because they’d seen the close rates and understood exactly why the old pitch wasn’t working anymore. The reps in the room mostly hadn’t seen those numbers. They just got told the pitch was changing.

The training lands well. Three weeks later, half the team has quietly reverted to their old pitch, not because the framework didn’t work, but because nobody ever made the case to them for why it mattered, and nobody built in the structure to notice the drift and correct it while it was still small.

A learning system in that context starts before the training does, with reps actually seeing the problem their leadership saw. It continues with scheduled practice reps on real deals, not just role play in the training room. It looks like a manager who reviews calls specifically for the new framework and flags the gap between what was taught and what actually happened on the call. It looks like naming, explicitly, that the first month after training is when the system either holds people to the new standard or quietly lets them drift back to the old one.

None of that requires more training. It requires designing for both gaps, the understanding gap and the implementation gap, instead of assuming the first one doesn’t exist and hoping the second one closes on its own.

The Real Question to Ask

Most organizations, when they see a performance gap, ask the same question. What training do we need. It’s the wrong first question. The better one is whether the people expected to change actually understand the problem the way leadership does, and whether the gap that’s left after that is a knowledge problem or an implementation problem. Each of those requires a different response.

Here’s a rough way to tell which one you’re facing. If people can describe the problem back to you in their own words, unprompted, and it roughly matches how you’d describe it, that’s not an understanding gap. If what comes back is a paraphrase of the training announcement, or a shrug, that’s your answer. The understanding gap doesn’t usually announce itself. It hides behind polite compliance, people nodding along in the room and then doing something else entirely once the day gets hard, because the thing they were asked to do never became their problem to solve.

If people don’t understand the problem, no training fixes that. That takes the working session, the one the principal had already effectively had with himself. If it’s a knowledge problem after that, train it. If it’s an implementation problem, and it usually is, no amount of additional training will close it. What closes it is a system that expects the gap between knowing and doing to show up, and has a mechanism ready for when it does.

The principal didn’t need a better training calendar. He needed his team standing where he was already standing, and then a system that helped them act on it when the day made it hard.

That’s the harder thing to build. It’s also the only thing that actually moves the needle.