Royal Army College

Lesson Overview

A capability built to meet today's needs, with today's methods and against today's circumstances, will not remain fit forever, because the world it was built for changes. New kinds of crisis emerge, the threats and needs a force must meet shift, technology advances and changes what is possible and what is expected, and methods that were sound become outdated. A force that builds a capability and then holds it unchanged, however well it sustains it against decay, will find over time that it has sustained a capability that no longer fits the world, kept in good order but increasingly beside the point. This lesson is about preventing that: adapting capability to keep pace with change, so that the force's capabilities stay relevant and effective as the world moves, rather than becoming well-maintained answers to questions no longer being asked. It is distinct from sustaining, which keeps a capability working as it is; adaptation changes the capability itself to keep it fit as circumstances change. For a small state, adaptation is both harder, with fewer means to renew capability, and more vital, because a small force cannot afford to hold capabilities that have quietly become irrelevant.

The lesson takes adapting capability in three parts. First, why adaptation is necessary: that the world a capability was built for changes, in the threats and needs, in technology, and in methods, so that capability must change with it or fall out of relevance, and that this is different from and additional to the decay that sustainment addresses. Second, how a force keeps pace: by watching for the changes that matter, learning from experience and from others, and being willing to change capabilities, including to give up those that have become irrelevant, which is often the hardest part. Third, adaptation in a small state: how a small force adapts within tight means, by being clever rather than lavish, adapting and repurposing what it has, learning quickly, and using the same affordability and cooperation that build capability to renew it, while avoiding both the failure to adapt and the opposite error of chasing every change fashionably. Throughout, the lesson holds that a force's capability must be a living thing that changes with the world, and that the officer's part includes not only building and sustaining capability but keeping it fit for a world that will not stand still.

This is the knowledge layer. Reasoning about adaptation and keeping pace with change, by a capability-planning exercise, is assessed in person. By the end you will be able to explain why capability must be adapted to keep pace with change, and how this differs from sustainment; identify the kinds of change that make adaptation necessary, in threats and needs, technology, and methods; explain how a force keeps pace, by watching, learning, and being willing to change and to give up the irrelevant; adapt capability in a small state by being clever, repurposing, and learning quickly within tight means; and avoid both failing to adapt and chasing every change fashionably.

Key Terms

Adaptation: the changing of a capability itself to keep it fit and relevant as the world it serves changes, distinct from sustaining a capability unchanged against decay.
Keeping pace with change: the continuous work of adapting the force's capabilities so they remain relevant and effective as threats, needs, technology, and methods change.
Relevance: the fitness of a capability to the world as it now is, which erodes as the world changes even if the capability is well sustained.
Change in threats and needs: the shifting over time of the tasks a force must meet, the crises it faces, and what the nation needs of it, which can make an old capability less needed and create a need for a new one.
Technological change: the advance of technology, which changes what is possible, what is expected, and what an effective capability looks like, often quickly.
Change in methods: the evolution of how tasks are best done, so that methods once sound become outdated and capability built on them falls behind.
Obsolescence (irrelevance): the state of a capability that no longer fits the world, well-maintained perhaps but beside the point, which adaptation exists to prevent.
Giving up the irrelevant: the discipline of discarding or repurposing a capability that has become irrelevant, often the hardest part of adaptation, to free means for what is now needed.
Learning: the drawing of lessons from the force's own experience and from others, which tells a force what needs to change and how, the engine of adaptation.
Fashionable change-chasing: the opposite error to failing to adapt, changing capability to follow every novelty or fashion regardless of the force's real needs, which a small state can least afford.

Why capability must be adapted

The need for adaptation follows from a simple truth: a capability is built for a particular world, and that world changes. When a force builds a capability, it builds it to meet particular needs, using particular methods, against particular circumstances, all of which belong to the world as it is at the time of building. But the world does not stand still. Over the years a capability serves, the threats and needs shift, technology advances, and methods evolve, and a capability built for the world of its making becomes, by degrees, less fit for the world as it has become. This is not because the capability has decayed; it may be perfectly sustained, the equipment serviceable, the people trained, the whole in good order. It is because the world has moved while the capability stood still, so that what was a good answer to the needs of its time is a poorer answer to the needs of the present.

This is why adaptation is distinct from, and additional to, the sustaining the capstone teaches, and an officer must hold both. Sustainment keeps a capability working as it is, against the decay of its components; adaptation changes the capability itself to keep it fit as the world changes. A force can sustain perfectly and still fall behind, because sustainment fights decay but not irrelevance: it keeps the old capability in good order while the world makes that capability less and less the right one. A force that sustains without adapting ends with well-maintained capabilities that no longer fit the world, kept in excellent condition and increasingly beside the point, which is a particular and wasteful failure, because the means spent sustaining an irrelevant capability are means not spent on the relevant one the changed world now needs. The two disciplines are therefore both necessary and different: sustain a capability against decay so it stays able to do what it does, and adapt it against change so that what it does stays what the world needs. For a small state both matter acutely, but adaptation has a particular edge, because a small force has no spare capacity to carry capabilities that have quietly become irrelevant, and every capability it holds must earn its place against the world as it now is. The officer responsible for capability must therefore watch not only whether a capability is being kept in good order but whether it still fits the world, because a capability can pass the first test and fail the second, and a force can be well-sustained and yet falling behind.

   WHY ADAPT  (sustainment vs adaptation: both needed, different)

   a capability is built for a PARTICULAR WORLD (needs, methods,
   circumstances of its time) -- and the world CHANGES:
        threats + needs shift · technology advances · methods evolve
        -> the capability becomes less fit for the world as it now is
           (NOT because it decayed -- it may be perfectly sustained)

   SUSTAINMENT (capstone) keeps a capability WORKING AS IT IS, against
        the decay of its components
   ADAPTATION (this lesson) CHANGES the capability itself to keep it
        FIT as the world changes

   a force can SUSTAIN PERFECTLY and still FALL BEHIND: sustainment
   fights decay, not IRRELEVANCE.
   -> well-maintained capabilities that no longer fit the world =
      excellent condition, beside the point (means wasted).
   small state: no spare capacity to carry the irrelevant; every
   capability must earn its place against the world as it NOW is.

How a force keeps pace

If capability must change as the world changes, a force needs a way to keep pace, and it rests on three things: watching for the changes that matter, learning what to change and how, and being willing to change, including to give up the irrelevant. The first is watching. A force keeps pace only if it notices the changes that bear on its capabilities, the new kinds of crisis emerging, the shifts in what the nation needs of it, the advances in technology that change what is possible or expected, the evolution of methods. A force that does not watch for change is overtaken by it unawares, discovering only in a crisis that the world has moved and its capabilities have not. Watching is not passive; it is the deliberate attention to the changing world that gives the force the warning it needs to adapt in time rather than being caught out.

The second is learning, which is the engine of adaptation, because it tells the force both what needs to change and how. A force learns from its own experience, drawing lessons from the crises it meets and the tasks it performs about where its capabilities fell short or where the world had changed, and it learns from others, from the experience of other forces and from the wider world, about changes it has not yet met itself. A force that learns honestly from its experience, facing what went wrong and what the world is teaching it rather than explaining it away, knows what it must adapt; a force that does not learn repeats its shortfalls and is taught the same lesson again, more expensively, each time. The third, and often the hardest, is the willingness to change, including the willingness to give up the irrelevant. Adapting a capability may mean changing how it is done, adopting a new method or technology, or it may mean discarding or repurposing a capability that the changed world no longer needs, to free the means for one it does. Giving up a capability is hard: there is attachment to it, means already invested in it, advocates for it, and a natural reluctance to admit that what was once right is right no longer. But a force unwilling to give up the irrelevant carries dead weight, spending means to sustain capabilities the world has passed by, and a small state can least afford to do so. The willingness to change what should change, and to let go of what should be let go, is therefore essential to keeping pace, and it is as much a matter of honesty and discipline as of foresight, because the obstacle is usually not failing to see that change is needed but being unwilling to act on it.

Adapting capability in a small state

A small state adapts under the same tight constraint that governs all its capability work, and the disciplines are the small-state disciplines applied to renewal: being clever rather than lavish, repurposing what it has, learning quickly, and using affordability and cooperation to adapt as well as to build. A wealthy power can adapt by buying new capability to replace the outdated; a small state usually cannot, so it must adapt cleverly. Often this means adapting and repurposing what it already has, changing how an existing capability is used, applying it to a new need, or modifying it to meet a changed circumstance, rather than replacing it wholesale, which gets renewed relevance from means already spent. It means learning quickly, because a small force that learns fast can adapt ahead of being caught out, getting more from its limited means by changing in good time rather than late and expensively. And it means using the same affordability and cooperation that Lesson 05 taught for building: adapting affordably, getting the most renewed capability per unit of means, and cooperating with others to access changes, technologies, or methods the small state could not develop alone. Adaptation, like building, is something a small state does by cleverness and cooperation rather than by spending, and the same creativity that lets it build real capability from limited means lets it keep that capability relevant.

The small state must also avoid two opposite errors, and holding between them is the discipline of adapting well. The first is the failure to adapt, treated above: holding capabilities unchanged as the world moves, sustaining the irrelevant, and falling behind, which leaves the force well-maintained but beside the point. The second is the opposite error, fashionable change-chasing: changing capability to follow every novelty, every new technology, every fashion, regardless of whether it serves the force's real needs. A small state can least afford this, because chasing fashion scatters its scarce means on changes that do not serve its actual tasks, and a force that adopts every novelty for its own sake ends as poorly served as one that adopts nothing, having spent its means on relevance to others' circumstances rather than its own. The discipline is to adapt by need, not by novelty: to change capability when and because the changing world has made the change genuinely necessary for the force's real tasks, grounded as always in what the force must actually be able to do, and to resist changing merely because something is new or because others are changing. This is the same task-grounded honesty that Lesson 03 demanded of goal-setting, applied to adaptation: adapt to keep the force fit for its real, changing needs, neither clinging to the outdated nor chasing the merely new. Held this way, adaptation keeps a small force's capabilities a living thing, renewed by cleverness and cooperation, grounded in real and changing needs, fit for the world as it becomes rather than as it was, which is what lets a small state's modest capabilities stay genuinely useful across the years and the changes they must serve through. The officer's part in capability thus includes this keeping-fit alongside the building and sustaining, because a capability that is built, sustained, and never adapted will, however well kept, end as an answer to a world that has moved on.

   ADAPTING IN A SMALL STATE  (clever, not lavish; by need, not novelty)

   HOW (small-state disciplines applied to renewal):
     REPURPOSE what you have (new use / modify) -> renewed relevance
        from means already spent
     LEARN QUICKLY -> adapt ahead of being caught out, in good time
     AFFORDABILITY + COOPERATION (as in Lesson 05) -> adapt cheaply;
        access via others changes you couldn't develop alone

   AVOID TWO OPPOSITE ERRORS:
     FAIL TO ADAPT ......... hold unchanged, sustain the irrelevant,
        fall behind -> well-maintained but beside the point
     CHASE FASHION ......... change for every novelty regardless of
        real need -> scatter scarce means on others' relevance
        (a small state can LEAST afford this)

   THE DISCIPLINE: adapt BY NEED, not by novelty -- change when the
   world has made it genuinely necessary for the force's REAL tasks
   (task-grounded honesty of Lesson 03, applied to renewal).

In Practice: The capability kept fit for a changing world

An officer of the Royal Kaharagian Army is responsible, over years, for a capability the force relies on, and the test of their stewardship is not only whether they keep it working but whether they keep it fit for a world that changes. A less thoughtful officer would sustain the capability diligently, keeping its equipment serviceable and its people trained, and consider the job done, and for a time the capability would remain both well-maintained and relevant. But the world moves: the kinds of crisis the force meets shift, a new technology changes what an effective response looks like, and the methods the capability was built on begin to fall behind better ones. The diligent-but-static officer, sustaining faithfully, would end with a capability in excellent order that no longer quite fits the world, kept beside the point.

This officer does more than sustain. They watch the changing world, noticing the shift in the crises the force faces, the new technology, the evolving methods, so they are not overtaken unawares. They learn, drawing honest lessons from the force's own experience about where the capability has begun to fall short and from others about changes they have not yet met, so they know what needs to adapt and how. And they are willing to change: they adapt the capability to keep it fit, and where part of it has become genuinely irrelevant, they have the discipline to give that part up or repurpose it rather than clinging to it, freeing means for what the changed world now needs. They adapt as a small state must, cleverly rather than lavishly, repurposing what the force already has, learning quickly to change in good time, and using affordability and cooperation to access changes the force could not develop alone. And they hold between the two errors: they neither cling to the outdated nor chase every novelty, adapting by genuine need grounded in the force's real tasks rather than by fashion, so the scarce means go to changes that actually serve.

The value, across the years, is a capability that stays genuinely useful rather than becoming a well-kept relic. Because the officer watched, learned, and was willing to change, the capability is adapted as the world moves and remains fit for the crises the force actually faces, not the ones it faced when the capability was built. Another officer who sustained faithfully but never adapted would have a capability in excellent condition and declining relevance, having kept it working while the world made it beside the point, and a small state would have spent its scarce means maintaining an answer to a question no longer being asked. This officer kept the capability a living thing, adapted by cleverness and cooperation and grounded in real and changing needs, which is the keeping-fit that completes the officer's part alongside building and sustaining, and what lets a small force's capabilities serve through a world that will not stand still.

Check Your Understanding

Explain why a capability built for today's world becomes less fit over time even if it is perfectly sustained. How does adaptation differ from sustainment, and why can a force "sustain perfectly and still fall behind"?
Describe the three things on which keeping pace rests: watching for change, learning, and the willingness to change including to give up the irrelevant. Why is giving up an irrelevant capability often the hardest part, and why is it as much a matter of honesty and discipline as of foresight?
Explain how a small state adapts within tight means, by repurposing, learning quickly, and using affordability and cooperation. Then explain the two opposite errors, failing to adapt and fashionable change-chasing, and the discipline of adapting by need rather than novelty.

Reflection (write a short paragraph): This lesson argues that a capability can be kept in excellent condition and still quietly become beside the point, because sustainment fights decay but not irrelevance, and that keeping pace requires the willingness to change and even to give up what was once right but is right no longer. Think about how strong the pull is to keep faithfully maintaining what you have built rather than facing that the world has moved and it must change, and why giving up an old capability, with its invested means and its advocates, is so hard. Why does keeping a force fit for a changing world depend as much on the honesty and discipline to let go and to change as on the foresight to see change coming, and what would it take to be the officer who keeps a capability a living thing rather than a well-kept relic?

Summary

A capability is built for a particular world, and that world changes: threats and needs shift, technology advances, methods evolve, so a capability becomes less fit for the world as it now is, even if it has not decayed. Adaptation, changing the capability itself to keep it fit, is the response.
Adaptation is distinct from and additional to sustainment: sustainment keeps a capability working as it is against decay, while adaptation keeps what it does fit as the world changes. A force can sustain perfectly and still fall behind, because sustainment fights decay but not irrelevance, ending with well-maintained capabilities beside the point.
A force keeps pace by watching for the changes that matter (so it is not overtaken unawares), learning from its own experience and from others (the engine of adaptation, telling it what to change and how), and being willing to change, including the hard discipline of giving up or repurposing a capability the changed world no longer needs.
Giving up the irrelevant is often the hardest part, opposed by attachment, invested means, and advocates, and is as much a matter of honesty and discipline as of foresight, because the obstacle is usually not failing to see that change is needed but being unwilling to act on it. A small state can least afford to carry dead weight.
A small state adapts cleverly rather than lavishly: repurposing what it has for renewed relevance from means already spent, learning quickly to change in good time, and using the affordability and cooperation of Lesson 05 to adapt as well as to build.
Avoid both the failure to adapt (sustaining the irrelevant and falling behind) and fashionable change-chasing (changing for every novelty regardless of real need, which a small state can least afford); adapt by genuine need grounded in the force's real, changing tasks, the task-grounded honesty of Lesson 03 applied to renewal.
Cross-references: keeps fit the capabilities built across PME 510 Lessons 02 to 05 and complements the sustaining of Lesson 10 (sustainment fights decay; adaptation fights irrelevance); frees and redirects means in the prioritisation and balance of investment of Lesson 06; responds to the uncertain, changing future of Lesson 07; uses the affordability and cooperation of Lesson 05; and is grounded in real tasks as in Lesson 03 and the small-state environment of Operational Environment and the Small State (PME 430).

Adapting Capability: Keeping Pace with Change