Ongoing stewardship · JNAGA perspective
Why does a promising digital pilot fail to become normal work?
A successful demonstration answers a narrow question. Routine use asks many more.
Published 25 September 2026
Check what the pilot actually proved
A small group may succeed with close support, carefully selected cases and temporary workarounds. That can be valuable evidence, but it does not prove that a wider team has the time, information or authority to use the new approach each day. Record the conditions that made the pilot possible.
Look closely at cases excluded from the trial. Exceptions, permissions and handovers often reveal the real work required for adoption.
Plan the operating model
Who will train new users, update instructions, answer questions and repair errors? Who decides when the process changes? A pilot can rely on the project team to solve these informally; an enduring service cannot. Build the responsibilities and capacity into the next stage.
Wider use may also require different integration, performance or support arrangements. Do not assume the technical conditions of a trial are the conditions of normal work.
Scale the learning, not the demonstration
Before expanding, revisit the outcome and test a more representative set of cases. Change the design where the pilot exposed friction. A slower, well-owned transition may deliver more than a rapid rollout that leaves people to invent their own workarounds.
Imagine five volunteers complete a pilot with a project specialist nearby. A wider team faces different cases, less time and no immediate expert support.
Before rollout, repeat the test with representative cases and assign support, exception and change ownership. Scale what was learned from the pilot, not merely the pilot configuration.