Activity is not the same as capability
By Deana Nannskog
Most organisations have plenty of activity, programmes, tools, workshops, initiatives. What they often lack is the capability to translate that activity into repeatable, sustainable performance. The distinction matters because organisations keep investing in activity while wondering why results don't compound.
"Sweden had the ball. Kosovo had the result."
In two FIFA World Cup qualifying matches in 2025, Sweden outpossessed Kosovo by more than two to one. And lost both games. Possession is activity. The scoreline is capability. Most organisations are Sweden.
Most organisations have plenty of activity: programmes, tools, workshops, initiatives. What they often lack is the capability to translate that activity into repeatable, sustainable performance. The distinction matters because organisations keep investing in activity while wondering why results don't compound.
What does the pattern look like?
Organisations struggling with capability gaps typically have more activity, not less. They have transformation programmes running in parallel, skills initiatives underway, AI pilots launching, learning platforms in use. The problem is not effort. The problem is that none of it connects well enough to create compounding capability.
Why does activity not compound into capability?
- Activity is episodic. Capability is structural. A workshop develops individual understanding; capability requires that understanding to be embedded in how work actually happens, in decisions, processes, and everyday practice.
- Activity consumes energy. Capability releases it. When people have to figure out the same problems repeatedly, they burn capacity rather than building it.
- Activity is visible. Capability is quiet. Leaders reward the launch of initiatives because it is visible. The hard work of designing conditions, so that what was learned actually changes how the organisation operates, rarely gets the same attention.
What builds capability instead of just activity?
- Shared language: when people across the organisation use the same concepts to describe work, strategy, and value, decisions get faster and alignment becomes real rather than assumed.
- Conditions for agency: people need clear enough direction, enough decision-making authority, and enough psychological safety to act rather than wait for permission.
- Feedback loops: mechanisms that show whether what people are doing is actually moving toward the capability the organisation needs, not just metrics that measure activity itself.
"The question is not: are we doing enough? It is: is what we are doing building something that lasts?"
The question worth asking
When your transformation programme or learning initiative ends, what will the organisation be permanently able to do that it could not do before? If that question is hard to answer, the programme is probably investing in activity rather than building capability.
Activity answers the question: are we doing something? Capability answers the question: are we becoming something? Both matter, but only one of them compounds.
Related reading
- What is Capability Architecture? The full discipline for moving from activity to value
- From intent to value: why capability design is not the same as capability investment
- Capability Architecture in practice: the four components that close the gap
- Enquire about a keynote or executive session on Capability Architecture with Deana Nannskog
References
- Argyris, C., & Schön, D. A. (1978). Organizational learning: A theory of action perspective. Addison-Wesley.
- Kirkpatrick, D. L., & Kirkpatrick, J. D. (2006). Evaluating training programs: The four levels (3rd ed.). Berrett-Koehler.
- Senge, P. M. (1990). The fifth discipline: The art and practice of the learning organization. Doubleday.
- Wenger, E. (1998). Communities of practice: Learning, meaning, and identity. Cambridge University Press.