In the first three articles in this series, we explored how organisations typically approach capability development, why traditional learning interventions often fail to deliver sustained performance improvement, and how capability is shaped by a broader system of factors beyond training alone. If you haven’t read them yet, it’s worth starting there to understand the foundations of this perspective.
In this article, we build on that thinking by examining what happens when capability is treated not as a fixed outcome, but as something that evolves through continuous feedback and learning within the organisation.
Introduction
When organisations want to improve quality, they rarely focus only on the products they produce. They look at the production system itself. When they want to improve sales performance, they go beyond individual deals and refine the sales system. The same pattern shows up in customer service, software development and operations. Sustainable improvement comes from strengthening the system that produces the outcome, not just repeating the activity that created it.
Capability is often treated differently.
Learning and Development has become increasingly effective at designing programmes, building learning pathways and developing skills. Progress is usually measured by asking whether people have become more capable through learning, application and experience. That matters, because organisational performance depends on capable people. But it may not be the question that determines whether capability continues to improve over time.
A more fundamental question sits underneath it: is the organisational system responsible for developing capability getting better at doing so?
This shifts the conversation. Instead of evaluating individual learning interventions, it asks us to look at the system that produces them. Rather than focusing only on whether people learned, it asks what the organisation learned about how capability is actually created in its own context.
Every capability system is built on assumptions about how capable people are developed. Organisations that improve consistently tend to test these assumptions against operational reality, rather than simply repeating them. Over time, this leads to a clearer understanding of what genuinely drives capability, and what does not.
Why Do Businesses Improve While Capability Systems Often Repeat Themselves?
Mature business systems are not defined by how efficiently they execute a process. They are defined by how well they improve it. Producing another product, closing another sale or releasing another software update may create value today, but lasting improvement comes from understanding why those outcomes occurred and using that insight to strengthen the system behind them.
This pattern appears across disciplines. Manufacturers investigate production defects not just to fix today’s issue, but to improve tomorrow’s process. Sales organisations analyse both successful and unsuccessful opportunities to refine how future deals are qualified, managed and won. Software teams use customer feedback, operational data and usage patterns to improve future releases rather than simply shipping new versions. In each case, operational outcomes become evidence that challenges assumptions about how the system creates value.
This highlights the difference between execution and adaptation. An organisation can become very efficient at repeating the same activities without getting any better at producing the outcomes those activities are meant to deliver. Continuous improvement begins when evidence is used to question existing assumptions, uncover patterns that were not visible before, and adjust how the system operates. The aim is to improve the organisation’s ability to create success, not just repeat it.
This is not a separate step that happens after the work is done. It is built into the system itself. Every production cycle, customer interaction, software release or sales opportunity becomes a chance for the system to learn. Over time, that learning builds, helping the organisation develop a more accurate understanding of what consistently creates value in its own environment.
This leads to an important question for Learning and Development. If mature business systems improve by testing their assumptions against operational evidence, should capability development be treated any differently? Or should it also be seen as a business system, responsible not only for delivering development activities but for continually improving the organisation’s ability to develop capability?
If We Already Understand How Capability Creates Value, What Are We Still Missing?
In a previous article, we explored capability as a value chain. Learning develops knowledge and skills, those skills become capability through application, capability influences performance, and sustained performance contributes to business outcomes. This perspective remains useful because it shows how learning creates organisational value, rather than just generating activity.
But value creation is only part of the picture.
A value chain explains how inputs become outcomes. It does not explain what the organisation does with those outcomes once they exist. This is where an adaptive business system comes into play. The outcome is no longer treated as the end of the process. It becomes the starting point for improving the system that will produce the next outcome.
You can see this across mature business disciplines. A successful product launch is not just celebrated; it is examined to understand which decisions should be repeated and which should change. A successful sales campaign is not only measured by revenue; it informs future sales strategy. In each case, the outcome matters. What the organisation learns from it matters just as much, because it shapes what happens next.
Capability should be viewed in the same way.
If a development initiative improves workplace performance, that is a meaningful result. But the more useful question is what the organisation learned about how that capability was created. Which assumptions about development held up, and which did not? Which behaviours consistently led to stronger performance, and which attracted attention without delivering real operational value? These questions shift the focus away from outcomes alone and toward the mechanisms behind them.
At this point, the focus moves beyond evaluating programmes and toward examining the organisation’s underlying view of capability. Every capability model is built on assumptions: what people need to know, which behaviours matter most, how capability develops, and what drives performance. These assumptions are never fixed. They become more reliable only when they are tested against real conditions and adjusted over time.
This is where adaptation begins. It starts when operational evidence is no longer treated simply as proof that an initiative worked, but as input for refining how the organisation understands capability. Used this way, evidence can improve the system itself. That raises a further question: what exactly is the organisation learning, and how does that learning happen?
Why Doesn’t Producing Capable People Automatically Produce a Better Capability System?
Most organisations do not set out to build a static capability system. Many invest heavily in continuous improvement. Learning programmes are updated, pathways are refined, new technologies are introduced, and participant feedback shapes future delivery. These changes often improve the learning experience and can enhance individual outcomes. Even so, they do not always strengthen the system that produces capability.
The reason sits beneath the programme.
Every capability system rests on a view of how capability is created. Sometimes this view is made explicit through competency frameworks or development models. More often, it shows up in everyday decisions: what is taught, what is assessed, what managers reinforce, and what the organisation chooses to measure. Whether acknowledged or not, these choices reflect assumptions about which capabilities matter, how they develop, and why they influence performance.
The difficulty is that assumptions can become more convincing simply through repetition. A capability model that once matched operational reality may drift as customer expectations, technology, workforce composition, and business priorities change. If the system continues to deliver learning based on those same assumptions without testing them, it becomes increasingly effective at reinforcing an outdated view of capability.
This is why improving programmes and improving the capability-producing system are different activities. Improving a programme asks whether the intervention can be made more effective. Improving the system asks whether the organisation’s understanding of capability is becoming more accurate. The questions are related, but they lead in different directions.
In practice, operational evidence is often available across the organisation. Managers observe behaviour, performance conversations highlight recurring strengths and development needs, and business results reveal capability gaps that were not anticipated in the learning design. Yet this evidence often stays within individual functions instead of shaping the capability model itself. As a result, the organisation improves what it delivers while learning relatively little about how capability is actually created.
This is the central challenge. A capability system becomes more capable only when it treats its own assumptions as something to be tested, not simply repeated.
Can an Organisation Learn While Its People Learn?
The previous section leaves an important question unanswered. If a capability system continually tests its assumptions against operational reality, who is actually doing the learning?
The obvious answer is the individual. People develop capability through learning, application, experience and feedback. As they encounter new situations, refine their judgement and improve their performance, they become more capable in the context of their work. This learning cycle is familiar because it sits at the centre of most capability initiatives.
At the same time, a second learning cycle is unfolding.
As individuals apply capability across different roles, teams and operational environments, the organisation gathers evidence about how capability actually develops. No single learner provides the full picture; patterns only emerge when many learning experiences are viewed together. Over time, the organisation starts to see which assumptions consistently hold, which need adjustment, and which no longer reflect operational reality. In this way, the capability-producing system builds a clearer understanding of how capability is created within its own context.
This helps explain why two organisations can invest similar resources in Learning and Development yet mature at very different rates. Both may produce capable people. Only one consistently learns from those experiences and uses that insight to improve how capability is developed across the organisation.
Capability development therefore operates through two connected learning cycles. Individuals learn how to perform more effectively. The organisation learns how to develop capability more effectively. The first produces capable people; the second strengthens the capability-producing system itself. Sustainable improvement depends on both.
What Is the Real Purpose of a Capability System?
Seen this way, evidence is no longer just a way to evaluate past performance. Its real value lies in improving future capability. Every observation, manager conversation, operational outcome and performance pattern becomes a chance to test the organisation’s assumptions about how capability is developed and sustained. Some assumptions are confirmed. Others need to change. Over time, the capability-producing system becomes better at understanding what consistently drives performance within its own context.
This shift changes the purpose of the system.
The objective extends beyond producing capable people, important as that remains. It includes continually improving the organisation’s ability to produce capable people. Capability becomes more than the result of learning activities. It reflects an organisational system that learns from its own performance and keeps refining how capability is developed.
The true measure of a mature capability system is not how many programmes it delivers, or even how well those programmes perform. It is whether each development cycle leaves the organisation with a clearer understanding of how capability is actually created than it had before.
Adaptation is not an additional feature of the capability system. It is its defining purpose.
The Next Evolution of Capability Management
Developing capable people will always remain the central objective of Learning and Development. The opportunity is to broaden that objective by designing capability systems that learn alongside the people they develop. When operational evidence is used to test assumptions, refine capability models and guide future development decisions, capability becomes more than the outcome of learning activities. It reflects an organisation that continually improves how it develops capability.
The next evolution of capability management is not simply developing capable people. It is developing an organisation that continually improves its ability to do so.
About the perspective of this article: This article draws on ideas from systems thinking, organisational learning and continuous improvement. Rather than presenting capability development as a series of isolated learning interventions, it explores what happens when capability is viewed as an adaptive organisational system that continually learns from operational evidence. The perspective offered here is intended as a synthesis of these disciplines, applied specifically to Learning and Development.
