Government service delivery reflections
An exploration of service delivery not as a single interaction problem, but as a structural challenge requiring clarity across strategy, operations, and design.
Designing for public services means working with complexity in plain sight. The constraints are visible, the stakes are real, and the path to improvement rarely follows a straight line.
Context
This project began with a seemingly simple question: why do citizens struggle with services that, on paper, should work well? The answer, as with most systemic challenges, lay not in any single interface or touchpoint, but in the invisible architecture connecting policy, operations, and experience.
Working within a large government department, I was tasked with understanding delivery failures that had persisted despite multiple redesign efforts. Each previous intervention had focused on the visible layer—forms, websites, call scripts—while the underlying structures remained unchanged.
Observation
Many delivery issues stem from fragmentation between strategy, operations, and design. Teams work in silos. Policy intent gets lost in translation. Operational constraints shape user experience in ways that designers never see.
Better services often depend less on new artefacts and more on clearer relationships between decisions, delivery, and responsibility.
The most significant insight wasn't about user needs—those were well documented. It was about organisational needs: the unstated requirements, competing priorities, and structural constraints that shaped every decision downstream.
Approach
Rather than starting with solutions, we mapped the decision landscape. Who makes choices? When? With what information? This revealed a pattern: decisions made early in the policy cycle constrained options available to operational teams, who then constrained options available to design teams.
The intervention became less about redesigning the service and more about redesigning the conversations between these layers. We introduced structured touchpoints, shared models, and explicit handoff protocols.
Key interventions
The work focused on three interconnected areas:
- Decision visibility: making policy constraints explicit at the operational layer
- Feedback loops: ensuring delivery insights reached strategy teams
- Shared models: creating common language across organisational boundaries
Implication
Service improvement often requires clearer operating models, decision boundaries, and collaboration patterns. The tools we use—journey maps, blueprints, prototypes—are valuable not for what they produce, but for the conversations they enable.
The real design challenge wasn't the service. It was the organisation's capacity to see itself clearly.
Reflection, end of project
Reflection
This project changed how I think about service design scope. The tendency is to focus on what we can directly control—interfaces, journeys, touchpoints. But sustainable improvement often requires working at the edges of our mandate, influencing systems we can't redesign and decisions we can't make.
The most valuable skill wasn't mapping or prototyping. It was translation: helping different parts of the organisation understand each other's constraints and possibilities. Design as diplomacy.