Every year, organizations spend more on developing individuals: functional skills, technical skills, leadership programs, executive coaching. And every year, the teams those individuals sit in perform about the same as they did before.
That isn’t because the training is bad. It’s because it is aimed at the wrong unit.
The pyramid nobody looks at
Picture individual learning as a pyramid. Functional skills at the base, technical above it, then leadership, then the conceptual, strategic thinking we reserve for the most senior people. Companies invest up and down that pyramid.
Underneath the whole thing, almost always unexamined, is a foundation: how the people who hold those skills actually work together. How they decide. How they disagree. What they do when a commitment slips. Whether anyone has ever said out loud what winning looks like for this team, this quarter.
In our diagnostic data, fewer than one team in a hundred has explicitly agreed how it will work. That is the foundation, and it is missing under almost every pyramid we see.
Why individual learning stalls
A newly trained individual goes back to a team that hasn’t changed. The new capability gets applied to that person’s own work, which is the only place they control. The team’s ways of working absorb the individual, not the other way round.
So the organization gets a slightly better individual contributor and exactly the same team. Multiply that by every course, every certification, every offsite, and you have the modern training budget: large, well intentioned, and mostly spent on optimizing parts of a machine that nobody has tuned as a whole.
Learning is a team sport
The shift is not to stop developing individuals. It is to add a second, foundational layer: the team learning together how it will work, and holding itself to it.
That layer is smaller and cheaper than it sounds. In about two hours a team can write down how it will decide, how it will surface disagreement, who owns what, and what happens when something slips. The hard part isn’t the writing. It’s the follow-through, which is why we measure at day 0 and day 90 rather than handing over a document and hoping.
Once the foundation is in place, individual development starts paying out at the team level, because there is finally a team for it to pay out into. The finance leader who learned to run a tighter close now has a team that has agreed what “done” means. The engineering director who learned to delegate now has a team that has agreed how decisions get made without her in the room.
Three questions for your next budget cycle
Before approving the next round of individual development, ask:
- Has this team ever explicitly agreed how it works together? Not values on a wall. Working agreements, written down, that people can be held to.
- If a person comes back from this course with a new capability, what in the team’s current ways of working will let it show up in results?
- What are we measuring at the team level, before and after?
If the answers are no, nothing, and nothing, the individual spend is not wasted, but most of it will leak. Fix the foundation first. It’s the cheapest line in the budget and the only one that makes the rest of it work.
Only around one team in twenty reports operating near its full potential. The other nineteen aren’t short of talented individuals. They’re short of a team.