Continuous Improvement Planning

Continuous improvement planning makes ongoing assessment and improvement of technology part of ordinary planning. It includes upgrades, replacement, retirement, documentation, and operating or supplier changes where they address an unmet need. GOV.UK recommends it to help reduce future legacy accumulation and support iterative migration. Regular attention can make remedies easier to plan before risks become urgent, but some systems still require substantial replacement programs.

What it costs, and what it requires

GOV.UK’s guidance calls for time and budget to make and document changes, check compatibility, and review systems. Supplier contracts may need to include this work, and senior managers need to understand its benefits. A practical plan records each component’s support lifecycle: confirmed dates, release-dependent conditions, unknowns, and an owner to check changes. Choose review frequency using risk, change rate, and the time needed to act, alongside event-driven checks when policies or needs change.

Assess whether systems meet a legacy system criterion, then compare remedies using impact, dependencies, cost, and available capacity. Findings enter the technology roadmap as candidates for assessment; approved work receives an owner, resources, and an agreed time commitment. The budget must cover the chosen remedies and review work, not simply every upgrade suggested by a calendar. Accepted residual risks also need owners and reconsideration dates.

A fictional utility’s forty-one unsupported systems accumulated across several planning cycles. Its recovery program retired twelve after dependency and records checks, modernized twenty-one onto supported components, and retained eight on the risk register with interim controls. Continuing funds supported lifecycle monitoring and approved remedies. That practice made emerging risks and deferred work visible; it could not guarantee that eight would never become forty-one again. How these commitments relate to migration, modernization, and business transformation is explained in Three Hundred Servers Moved and Nothing Changed.

References

• Government Digital Service and Central Digital and Data Office, Managing legacy technology, 2019 (Open Government Licence v3.0).