Why council transformation stalls — and how to unstick it.

Every council we have worked with has attempted transformation before. Usually more than once. The intent is real, the budgets are sizeable, and the leadership is committed. And yet, three years in, the operating model looks remarkably like it did before — with a heavier technology stack and a tired workforce.

The pattern is consistent enough to be predictable. Transformation stalls at the second re-org, not the first release.

The first release is the easy part. A vendor delivers a module, a project team celebrates, and there is a photo on the intranet. The second re-org is where the wheels come off. Staff are asked to change how they work, elected members ask for reports the new system cannot produce, and the transformation office quietly retreats into steering-committee theatre.

The pattern

A council will procure a large platform — TechnologyOne, Civica, Dynamics — and treat implementation as the transformation. The system goes live, teams migrate, and the transformation office declares success. Six months later, staff have quietly rebuilt their old spreadsheets alongside the new platform.

The reason is that platforms encode workflows, and workflows encode operating models. A new platform without a new operating model just automates the old dysfunction faster.

You can see it in the field within a fortnight of go-live. Depot supervisors run parallel spreadsheets so they can dispatch crews the way they know works. Rates officers keep their private queries for the reports the platform can't yet produce. Customer service reps re-key data between three tabs. The 'single source of truth' quietly becomes a system of last resort.

What actually moves the needle

Three things separate the councils that unstick from the councils that don't. First, they treat their existing systems as infrastructure — not as strategy. TechnologyOne is a ledger, not an operating model. Second, they invest in the AI and orchestration layer that sits over the platforms, rather than replacing platforms every five years. Third, they run transformation as a series of proof-of-value sprints tied to real service outcomes — roads inspected, rates queries closed, waste requests resolved — not deliverables.

The councils that get this right are not spending more. They are spending differently. Less on capital platform swaps, more on the thin, capable layer that makes the platforms they already own actually work together.

The measurable difference shows up within a single financial year. Community request resolution times fall by a third. Overtime and casual spend on backlog work drop meaningfully. Elected members get the reports they've been asking for since 2019. And the operating model — the actual way work moves through the organisation — starts to change, because staff can finally see and act on the same information at the same time.

Where to start on Monday

Pick one high-volume, high-frustration service — roads defects, missed bins, rates enquiries — and instrument it end-to-end. Not with another dashboard, but with an AI layer that reads what's actually happening in TechnologyOne, Civica and Microsoft, and hands staff and residents a clearer view of what's next. Ship that in eight weeks, measure it in the open, and use the momentum to unstick the rest.