Article
The Absorption Lens

Team failure: the real capacity problem

Raymond Honings 11 February 2026
Team failure: the difference between having skills and being able to use them together.
Summary

Give two teams the same training with the same facilitator and six months later the outcomes look entirely different. One team still needs direction and waits for answers, the other handles pressure internally and learns in real time. Talent is a tempting explanation, but then the outcomes would diverge within the first months. They only diverge after three to six months, which points to something the team builds collectively.

Key Insights
  • Two teams can get the same training and have completely different outcomes six months later. The difference isn't talent. It is whether the team learned how it thinks and moves together.
  • Teams that outgrow coaching share three patterns: they surface experience instead of referring to hierarchy, they talk about how work gets done, and they turn individual wins into shared playbooks.
  • The strongest leaders don't ask 'can you fix my team'. They ask 'can you help us build something you are no longer needed for'.
Visual: cheatsheet on solving problems that stay solved, a set of rituals for teams that learn to think for themselves.
Strong teams aren't built by adding more input. They are built by connecting what is already there.

Most teams don't fail because they lack skills. They fail because they never learned how to use what they already have together.

Same training, different outcome six months later

You can give the same training to two teams. Same content. Same facilitator. Same time investment.

Six months later the outcomes look completely different.

One team still needs direction. Still escalates tension. Still waits for answers.

The other team handles pressure internally. Learns from mistakes in real time. Adapts without external input.

The difference isn't talent. It is whether the team learned how it thinks and moves together.

I have seen this more times than I can count. Two teams in the same organisation, same manager, same investment. One team grows on, the other stagnates. When I look deeper, I almost always find the same cause: one team built an internal practice to immediately connect what it learns, the other didn't.

The real difference isn't talent

Talent is tempting as an explanation. When a team performs better, we credit the people. When a team performs less well, we think it has the wrong people.

But if talent were the deciding factor, outcomes would diverge already after the first months. That isn't what I see. The outcomes only significantly diverge after three to six months, and then keep diverging. That pattern tells me it isn't about individual talent, but about something the team builds collectively or doesn't.

That 'something' is a capacity for self-reflection and self-adjustment. It is a habit of the team to keep examining itself without anyone imposing it. Talent is static. Capacity is dynamic. And dynamics win over time.

Three patterns of teams that outgrow coaching

The teams that outgrow coaching share a few patterns.

They surface experience instead of referring to hierarchy. They talk about how work gets done, not only what gets done. They turn individual wins into shared playbooks.

That is when development stops being 'training' and starts being movement.

Three patterns, not three hacks. They reinforce each other, and they rarely emerge in isolation. A team that develops one without the other two slides back over time. A team that develops all three keeps growing even without external support.

Experience surfaced, not referred upward

The first pattern. Surfacing experience instead of referring to hierarchy.

In most teams it works differently. When there is a hard situation, people look up. To the manager. To the senior. To whoever has 'experience'. The implicit assumption is that experience sits above and execution below.

In teams that outgrow, the opposite works. The question becomes: who among us has been through something similar before? The answer comes more often from the middle or bottom of the team than from the top. Not because the manager has no experience, but because the relevant experience often sits on the executing side.

That pattern breaks a hidden efficiency loss. In hierarchical referral much time is spent re-explaining context to someone who wasn't there. In horizontal referral someone who was there picks up the thread directly.

Talking about how, not only what

The second pattern. Talking about how work gets done, not only what gets done.

Most team meetings are about what. What is finished, what is in progress, what is still open. That is useful and necessary. It is not sufficient.

What is missing is the how. How was this finished, and could someone else do that too? How is this in progress, and what has the team learned along the way? How is this still open, and what have we encountered about that situation so far?

The how is where learning gain sits. The what is where performance sits. Both are needed, but the how is often skipped because it costs more time and is less directly measurable.

Fifteen minutes per week on the how, in a team of seven, produces more learning gain after three months than a two-day offsite. Not because the offsite is waste, but because the how-conversation captures the offsite's learning gain and anchors it in daily practice.

From individual win to shared playbook

The third pattern. Turning individual wins into shared playbooks.

In most teams an individual win stays with the individual. Someone solves something cleverly, the project moves on, and nobody asks 'what did you do exactly'. The knowledge disappears the moment the person moves on to the next task.

In teams that outgrow, something different happens. When someone does something unusually well, what worked is made explicit. Not as an interview, not as documentation, but as a brief share. 'How did you approach that?' And the answer doesn't only get noted, it becomes part of how the team approaches a similar situation next time.

A shared playbook isn't a document. It is a collective memory built up through hundreds of small shares. The difference shows most strongly when someone leaves the team. In a team without a shared playbook, their knowledge goes with them. In a team with a shared playbook, much of what they knew stays behind, because it was already absorbed by the group.

Better rooms instead of more answers

That is why the strongest leaders I work with don't ask 'can you fix my team'.

They ask: 'Can you help us build something you are no longer needed for?'

That question changes everything. It shifts the goal of a coaching or training engagement. Not 'improve this team' but 'help this team build the capacity to improve itself'. It is a fundamentally different mandate, with fundamentally different outcomes.

Strong teams aren't built by adding more input. They are built by connecting what is already there.

Most teams don't need more answers. They need better rooms. A room where experience surfaces, a room where the how is discussed, a room where individual wins are absorbed by the collective. Three properties, activatable in every meeting. Not through extra content, but through better questions.

A Take-Home Message

Strong teams aren't built by adding more input. They are built by connecting what is already there.

Most teams don't need more answers. They need better rooms. Don't ask 'can you fix my team'. Ask 'can you help us build something you are no longer needed for'.

Frequently Asked Questions

How do you know if your team really lacks skills or the capacity to use them together? +
Ask a few team members separately: 'Which skill is our team short on?' When everyone names something different, the problem usually isn't skills, it's collaboration. The individual baggage is enough, only it doesn't get made visible or connected. Another signal: at every workshop or training people complain that they 'didn't have time to apply it'. That isn't always accurate; often it is a lack of rhythm to use what they learned together.
What are 'better rooms' concretely? +
Three properties. One: there is room to share what worked without it becoming bragging. Two: how something worked is explicitly asked, not just what happened. Three: the team extracts patterns from individual experiences and turns them into shared habits. A better room isn't a beautiful space with whiteboards, it is a ritual where the team systematically makes its own learning gain visible. Fifteen minutes a week is enough, provided it is consistent.
What is the difference between outgrowing training and ignoring training? +
Ignoring training means the team thinks it already knows everything and shuts itself off from new input. Outgrowing training means the team has developed the capacity to integrate input independently into its working practice. With ignoring, learning stagnates. With outgrowing, it accelerates, even though from outside it looks like the team needs less external support. You see the difference in how the team responds to something new: outgrown teams are curious without becoming dependent.
Does this approach work in newly formed teams? +
Not immediately, but quickly. A new team first needs a phase where individual experiences are shared to build a common base. After that, the pattern of 'surfacing experience' can begin. In my experience the start-up phase lasts about three months in well-supported teams. Then the team can start building its own playbook, long before a traditional training would solidify into routine.
What do you do when the leader keeps wanting to 'add more input'? +
Don't shift the entire work model at once. Start with one moment a week where the rule is: no new input, only connection of what is already there. That is feasible for a leader still focused on input. When that moment starts to show returns, the room appears to expand the pattern. Moving from a 'more input' leader to a 'better room' leader rarely happens through one conversation. It happens through evidence that piles up.
Raymond Honings
About the author

Raymond Honings

Raymond is the founder of Seemotion. He works with managers and leadership teams across cultures, helping them build self-reliant teams that perform under pressure. Over the past years he has worked with more than 1,000 managers worldwide. Today most of his work takes place in Asia, mainly in Korea, Taiwan, China and Japan.