Start a project
Journal

Digital government2 min read

Why digital transformation stalls between strategy and delivery

Most programmes do not fail in the strategy document. They fail in the months after it, when nobody owns the path to a running service.

Governments rarely lack ambition. Most digital strategies in the region are clear about the goal: fewer office visits, faster decisions, one record per citizen and business. The trouble starts after the strategy is approved.

The gap

A strategy is written by one team, procurement is run by another and delivery goes to a third. Each hand-off loses context. By the time a vendor starts building, the original reasons for each decision are gone, and the system is built to a specification, not to an outcome.

What closes it

Three habits make the difference.

  • Define every service by a measurable outcome, such as the number of visits a citizen makes or the days a permit takes.
  • Keep the people who wrote the roadmap involved in delivery, at least as reviewers.
  • Ship a small working service early, then widen it, instead of waiting for the full platform.

Shared foundations first

Identity, payments, notifications and data exchange between agencies are needed by almost every service. Building them once, as shared components, makes each later service faster and cheaper, and it gives citizens a consistent experience.

Keep the plan and the system connected

This is why we work on both sides: we advise on the roadmap, and we build and run the platforms it describes. When the people who shaped the plan also answer for the running service, the reasons behind each decision survive delivery.

Keep reading

All articles

Working on something similar?

Tell us about the system, the transformation or the venture. A senior member of our team replies within one business day.

Start a conversation