Rewiring the Public Sector

UNDER CONSTRUCTION — WORK IN PROGRESS
This page forms part of a developing public proof of concept. Content, structure and illustrations may change as the project develops.

WORK IN PROGRESS — UKRAINE AS AN ACCELERATED LEARNING SYSTEM

Ukraine: Accelerated Learning Under Pressure

War does not make institutions wise. It makes the cost of remaining unwise immediate.

Ukraine provides an unusually stark example of what happens when feedback is immediate, the environment changes continuously, and failure cannot easily be hidden behind procedure.

The purpose of this section is not to romanticise war, nor to suggest that civilian public services should behave like military organisations. It is to examine a systems question: what can public institutions learn from environments in which adaptation has to happen quickly because the consequences of slow learning are visible?

1. Why learning accelerates

Wars can generate technological and systemic change faster than almost any other human situation because consequences arrive quickly, failure is difficult to conceal, and the opposing system is itself adapting.

That creates a compressed learning loop:

  1. Observe what happened.
  2. Identify what failed or changed.
  3. Modify technology, process, training or doctrine.
  4. Deploy the change.
  5. Measure the result.
  6. Feed the evidence back into the next iteration.

Learning becomes practical rather than ceremonial because the environment continuously tests whether the change actually worked.

2. The short learning loop

A central lesson from the Ukraine Systems and Strategy work is that advantage does not come simply from possessing new technology. It comes from connecting observation, engineering, production, training, users and doctrine in a short learning loop.

Front-line experience can expose a failure. Engineers can alter hardware or software. Manufacturers can change production. Training can adapt. Users can test the result. Evidence can return to the design process.

The technology matters. The learning loop matters more.

3. Engineering capacity is a strategic resource

The Ukraine work highlights the importance of a dense engineering ecosystem in which electronics, hardware, software, radio-frequency systems, power electronics, artificial intelligence and operational users can interact rapidly.

This is systems capacity, not simply industrial capacity. A country or organisation may possess technology yet still adapt slowly if design, production, procurement, training and users are separated by long information delays.

The correct question after removing a bottleneck is where the constraint has moved and whether the whole system now performs better.

4. Adaptation is system-wide

New technology rarely works in isolation. A new system may also require changes to communications, sensing, power, maintenance, supply chains, training, authority, data and operational practice.

This is why technology policy must also be systems policy. Counting how many units have been purchased or deployed may create the appearance of progress without establishing whether the whole system is more effective.

The relevant question is not simply “Did we deploy the technology?” but “Did the operational result change?”

5. Redundancy and distributed resilience

The Ukraine material also reinforces a principle familiar in resilient engineering: systems survive disruption better when they are not dependent on a single fragile point.

Distributed communications, alternative pathways, backup power, local decision-making and the ability to reroute activity can all reduce the consequences of a single failure.

Redundancy can look inefficient when nothing is going wrong. Under stress, it becomes capacity for survival and recovery.

Unused capacity is not necessarily waste. Sometimes it is resilience.

6. The difference between a lesson identified and a lesson learned

One of the most important connections with Rewiring the Public Sector is the meaning of “lessons learned”.

A report, announcement, recommendation or procurement decision is only an intermediate output. The lesson has been learned when behaviour or system design changes and evidence shows that the change works.

That is the same distinction between administrative closure and verified improvement that runs throughout this project.

The promise to learn is not the same as evidence that learning occurred.

7. What public services can take from this

Public institutions should not need a catastrophe to develop the discipline of learning under pressure.

The opportunity is to recreate some of the useful characteristics of an accelerated learning system without the destructive conditions that produced them:

  • shorter feedback loops;
  • faster movement of evidence from failure to redesign;
  • greater permission for users to challenge systems that do not work;
  • closer contact between designers and the people operating the system;
  • rapid testing of changes;
  • independent verification of results;
  • resilience through alternative pathways and spare capacity;
  • continuous adaptation when conditions change.

The goal is not permanent crisis management. It is to create institutions capable of learning continuously rather than waiting for scandal, inquiry or collapse.

8. Eight questions for any learning system

  1. What operational result are we trying to change, and how will we measure it?
  2. How quickly does evidence travel from the point of failure to the person able to alter the system?
  3. Can users challenge a design or process without passing through the hierarchy that approved it?
  4. What has the environment changed since the last decision?
  5. If this intervention succeeds, where will demand, delay, risk or scarcity move next?
  6. What must change alongside the technology in training, authority, data, maintenance and procurement?
  7. Who owns verification after deployment?
  8. What evidence would cause us to stop, reverse or redesign?

What is distinctive about this interpretation?

Ukraine is already being studied as a case of resilient governance. The additional question here is whether its wartime adaptation can be understood as an accelerated learning system — and whether elements of that learning architecture can be deliberately designed into peacetime public administration.

Existing work on Ukraine already examines resilience, co-ordination, public-service learning, information integrity, digital capability and rapid adaptation. Defence analysis also discusses accelerated “learn and adapt” cycles. This project takes a further systems-engineering step by bringing those ideas together around a common learning architecture:

failure → rapid feedback → redesign → deployment → verification → changed outcome → next iteration

That architecture is then connected to other engineering principles used throughout Rewiring the Public Sector: headroom, redundancy, distributed resilience, information integrity, independent verification and short user-to-designer feedback loops.

The lesson for Rewiring the Public Sector

Ukraine demonstrates the difference between a system that merely records experience and one that is organised to learn from it.

The wider proposition is not that public services should imitate wartime institutions. It is that they should not need a crisis before they shorten feedback loops, connect users with designers, preserve engineering capacity, build redundancy, test changes rapidly and verify whether those changes actually work.

Public institutions should not need a catastrophe to develop the discipline of learning under pressure.

Source basis for this private draft: Ukraine as an Accelerated Learning System, Revision 4, 19 October 2026.