Capability frameworks are a defining tool in modern organisations. They clarify expectations, guide development and align people with strategy.
We map out capability levels. We define behaviours. We build skill matrices, career pathways, pay bands and KPIs. We tell people, “This is what good looks like,” and then we measure them against it.
Yet one dimension of this equation is often overlooked.
What does “good” look like for the organisation that’s demanding those capabilities?
In theory, capability frameworks are holistic. They describe the knowledge, skills and behaviours that help an organisation deliver its strategy. They should sit alongside organisational design, leadership, culture and systems.
In practice, however, they’re often experienced as something much narrower: a carefully constructed set of expectations for individuals.
- Here’s what you must be able to do.
- Here’s how we’ll assess you.
- Here’s how your progression depends on those assessments.
The accountability is largely one-way. The burden sits with the individual rather than the system.
Perhaps that’s because we’ve come to think of capability as something individuals possess. If someone isn’t performing, we assume the answer lies in developing their skills, behaviours or mindset.
Research from organisational psychology, human factors and systems thinking consistently suggests otherwise. Thinkers such as W. Edwards Deming, Amy Edmondson and Sidney Dekker have all argued, from different perspectives, that outcomes emerge from systems as much as from individuals. Capability, viewed through that lens, is not simply a trait people possess but something organisations help create – or constrain.
As Demming said, “A bad system will beat a good person every time.”
In other words, capability doesn’t exist in isolation. It emerges through the interaction between people and the environment in which they’re expected to perform. A capable person working in a poorly designed system may appear incapable. Equally, an ordinary performer working within a well-designed system can achieve extraordinary results.
Capability is contextual and relational. And this an important distinction.
Capability asks: Can this person do the work?
Capacity asks: Can this organisation realistically enable them to do the work consistently, sustainably and well?
That second question is rarely asked with the same rigour as the first.
We rarely see a corresponding framework that defines what the organisation commits to providing so that capability is realistic, sustainable and humanly possible.
Yet capacity isn’t a nice-to-have. It’s the precondition for capability.
You can be highly skilled and deeply motivated, but if you’re permanently overloaded, under-resourced, unclear on priorities and working in a culture where it’s risky to tell the truth, your capability exists mostly on paper.
Think about some of the expectations that regularly appear in capability frameworks.
- Strategic thinking – but there’s no protected time to think and no meaningful access to organisational data.
- Stakeholder influence – but decision rights are unclear and politics often outweigh evidence.
- Continuous learning – but workloads leave no room for learning during work hours, so development becomes something people are expected to do in their own time.
- Psychological safety – but speaking up carries unpredictable consequences and escalation pathways are informal or inconsistent.
The framework says, “Be capable.” The environment winks and says, “Good luck.”
If capability frameworks are to live up to their promise, perhaps they need a partner: an explicit framework describing the organisational conditions required for capability to flourish. Imagine if every capability expectation had a corresponding organisational commitment.
- Time – protected time for thinking, learning and collaboration.
- Resources – appropriate systems, information and tools.
- Workload – realistic expectations about volume and complexity.
- Decision rights – genuine clarity about authority, influence and escalation.
- Leadership and culture – observable behaviours that create trust and psychological safety, rather than aspirational values written on posters.
That’s a better conversation. HR and L&D aren’t simply designing frameworks that describe employee performance. They’re also defining the organisational obligations that make high performance possible. Senior leaders aren’t just approving what they expect people to become. They’re also committing to the conditions they will create.
It’s also a very different kind of accountability. One that leads to more honest conversations about performance. Instead of assuming every gap is a development issue, we might ask:
- Is this genuinely a capability gap?
- Or is it a capacity gap involving time, resources, clarity or safety?
- Or is it a design problem where the role itself makes the expected capability almost impossible to demonstrate?
For organisations that genuinely care about sustainable performance, engagement and psychological safety, this isn’t another layer of bureaucracy.
It’s organisational integrity.
If we’re prepared to codify what we expect from our people, we should be equally prepared to codify what they can expect from us. Organisations are becoming increasingly sophisticated at defining what employees owe the organisation. Perhaps it’s time we became equally sophisticated at defining what organisations owe their people.
Because capability doesn’t exist in a vacuum.
Capability needs capacity.
References:
Bakker, A. B., & Demerouti, E. (2007). The Job Demands–Resources model: State of the art. Journal of Managerial Psychology, 22(3), 309–328.
Dekker, S. (2014). The Field Guide to Understanding Human Error.
Deming, W. E. (1993). The New Economics for Industry, Government, Education.
Edmondson, A. C. (2019). The Fearless Organization: Creating Psychological Safety in the Workplace for Learning, Innovation, and Growth.
Senge, P. M. (2006). The Fifth Discipline: The Art and Practice of the Learning Organization.