Why workflow matters more than systems

It’s not something that gets much limelight, but when you boil it down, workflow is a fundamental element of local government technology.

Almost everything councils do is a workflow. A development application, managing an abandoned vehicle, delivering capital works, responding to a customer request. In every case, there is a sequence of tasks that need to be completed by particular people, in a particular order, using particular information.

Historically, this was visible. A file moved from in-tray to in-tray. Work progressed, stalled, or escalated in ways people could see. As councils have digitised, that same workflow has not disappeared. It has simply become embedded inside IT systems.

By workflow, I mean the end-to-end path work actually takes through the organisation. From request to decision to outcome. Across systems, teams, and handoffs. In all councils, this workflow exists whether it has been designed intentionally or has simply evolved through habit.

For council IT, workflow matters because it is where efficiency is created or lost. Automation does not happen at the level of individual systems. It happens at the level of workflow. The more clearly defined, connected, and interactive a workflow is across systems, the more opportunities exist to remove manual effort, eliminate handoffs, and reduce rework.

---

If workflow is fundamental, why do we rarely design it deliberately?

If workflow is so central to how councils operate, it raises an obvious question. Why do we so rarely talk about it explicitly, let alone design it deliberately?

One reason is that workflow sits awkwardly between business and technology. It is not owned cleanly by either. Business areas focus on service outcomes, not the mechanics of how work flows between systems. IT is often drawn into conversations about platforms, security, and infrastructure, rather than the end-to-end path work actually takes. Workflow lives in the gap.

There is also

a historical reason. When work moved physically through an organisation, workflow was visible. As councils digitised, that visibility faded. Workflow became embedded inside applications, email, and documents. What was once observable became implicit, and what is implicit is rarely questioned.

Procurement reinforces this pattern. Councils buy systems to support specific functions or services. Each system arrives with its own assumptions about workflow, optimised for a narrow purpose. Over time, councils accumulate many well-intentioned systems, each managing a small slice of work, without ever stepping back to ask how those workflows interact or what they add up to as a whole.

Finally, workflow is often seen as operational detail rather than a leadership concern. It feels mundane compared to topics like cyber security, data strategy, or digital transformation. Yet it is precisely this layer where efficiency is won or lost, and where automation either becomes possible or remains out of reach.

---

What it would mean to treat workflow as a first-class concern

If workflow were treated as a first-class concern, the most obvious change would be in how councils make technology decisions. Workflow would stop being an implicit by-product of systems and start becoming something IT actively evaluates, designs, and governs.

This would show up immediately in procurement. CIOs already apply rigorous standards around security, privacy, resilience, and compliance. Treating workflow seriously would mean applying the same discipline to how systems manage and expose workflow. Not just what a system does for a particular service, but how it participates in the organisation’s wider flow of work.

A workflow-ready system would be expected to integrate cleanly with other platforms. It would be able to signal when meaningful events occur, respond to events from elsewhere, and allow work to move between systems without manual intervention. Systems that cannot expose progress, status changes, or decisions beyond their own boundary create friction regardless of how capable they are in isolation.

Workflow maturity would also become a factor in architectural decisions. How flexible is the workflow inside the product? How easily can steps be added, removed, or changed as services evolve? Systems that manage workflow well would become more central over time, while others would remain specialist tools with clearer limits.

Treating workflow as first-class would also change how IT engages with the business. Conversations would shift from “what system do you need?” to “how does work need to flow end to end?”. Over time, this builds a shared understanding that workflows are organisational assets, not side effects of individual systems.

---

Closing reflection

Councils will continue to acquire new systems. Services will continue to change. Expectations around efficiency and digital service delivery will continue to rise. In that environment, the long-term sustainability of a council’s technology landscape is shaped less by any individual system and more by how work moves between them.

Workflow maturity is what determines whether change compounds or accumulates cost. When workflows are fragmented, every new requirement introduces another exception, another integration, another workaround. When workflows are understood and designed deliberately, councils gain a stable foundation that allows systems to change without constantly re-engineering how work gets done.

This is also where automation either becomes possible or remains out of reach. Automation does not emerge from isolated systems or individual features. It emerges when workflows are clear, connected, and adaptable. The more deliberate councils are about how work flows end to end, the more opportunities exist to remove manual effort, reduce rework, and improve consistency over time.

Treating workflow as a first-class concern is therefore not about finding the right tool or enforcing a single model. It is about asking better questions. About understanding where effort is spent, where handoffs occur, and where design choices today will limit or enable automation tomorrow.

In the long run, councils that invest in workflow maturity are not just optimising today’s processes. They are creating the conditions for sustainable change. They are building organisations that can adapt, automate, and improve without continually adding complexity. And in a sector defined by long time horizons and constrained resources, that may be one of the most important digital decisions a council can make.