Walk into almost any government digital team today and you will hear the similar language that includes user research, personas, journey maps, co-design workshops, human-centred design and design thinking. These have become accepted vocabulary of public sector transformation, taught in workshops, and quoted in strategy decks across federal, provincial, and municipal levels. But ask the same teams whether human-centred design has actually reshaped how their organisation makes decisions, and the answer is often no. The tools got adopted but the mindset didn’t.
This gap between practice and culture is one of the most persistent and least discussed problems in public sector innovation. Governments have spent the better part of two decades bringing in design thinking from the private sector, hiring service designers, building innovation labs, and running countless human-centred design pilots. We have done a lot of government training and initiatives around design thinking / human centred design. Many of those pilots produced genuinely better services. But very few of them changed how government works at its core. The pattern repeats so often that it deserves a look, not as a leadership failure but as a structural one.
Structures Built for a Different Era
One of the reasons human-centred design struggles to stick is that it keeps getting treated as a pilot rather than a practice. A team runs a successful project, redesigns a benefits application form, shortens a wait time, improves a citizen satisfaction score, and the project gets celebrated. Then the funding ends, the contract wraps up, or the champion who pushed it through moves to another department, and the work slowly stops. The organisation never builds the muscle memory to repeat it without that specific team or that specific budget line.
Design thinking was never meant to be a one-off intervention. It is a way of working that depends on continuous contact with the people a service is meant to serve. When it is treated as a discrete project with a start date and an end date, it behaves like any other government initiative, subject to the same funding cycles, political turnover, and organisational amnesia that undermine long-term change everywhere in the public sector (or large organizations).
Government organisations were largely built around hierarchy, compliance, and risk avoidance, values that made sense for delivering consistent, accountable public services at scale. Human-centred design asks for something almost opposite: comfort with ambiguity, permission to fail small before scaling, and decision-making that starts with user needs rather than policy intent or departmental mandate.
These two logics do not blend easily. A design team can prototype a better way to deliver a service, but if the underlying procurement rules, reporting structures, and approval chains were not built with iteration in mind, the prototype dies in translation somewhere between the lab and the legislature. Many public servants who have tried to bring design thinking into their departments describe the same experience: the workshop goes well, the energy in the room is great, and then the idea hits the existing machinery of governance and slows to a stop. We have seen this and talk more and more about systems and systems thinking.
Empathy Without Authority
Another reason human-centred design fails to be embeded is that the people doing the work often lack the authority to act on what they learn. User research can reveal, with total clarity, that a service is failing people. But if the team running that research sits several levels away from the people who control budget, policy, and legislative change, empathy becomes a report rather than a decision.
This is not a failure of the design process itself. It is a failure of where that process sits inside the organisation. Design thinking works best when it is close to power, not adjacent to it. When it is positioned as a service delivered by an innovation lab to the “real” departments, it stays a nice-to-have rather than becoming how the organisation actually thinks.
There is also a simpler, more human reason human-centred design struggles in government: the language itself can alienate the people it needs to convince. Terms like empathy maps, ideation sprints, and co-creation workshops can sound, to a skeptical program manager or a budget-conscious director, like consultant jargon rather than a serious method for solving hard public problems. When design teams fail to translate their process into the language of outcomes, risk, and accountability that government leaders already speak, they lose the room before the work even begins.
The teams that succeed tend to be the ones that stop selling design thinking as a philosophy and start showing it as a practical way to reduce complaints, cut costs, and improve service uptake. Sometimes we even have teams rename the tools, like calling empathy maps unarticulated needs maps. The mindset shift matters, but it tends to follow results rather than precede them.
Turnover, Politics, and Institutional Memory
Public sector leadership changes far more often than private sector leadership, and each change in political or executive direction can reset priorities overnight. A human-centred design initiative championed under one minister or one city manager can lose all momentum under the next, regardless of how well it performed. This turnover creates a structural fragility that private companies rarely face in the same way. Institutional memory in government tends to live in individuals rather than in systems, so when those individuals leave, the practice often leaves with them.
This is why the organisations that manage to sustain human-centred design over time are the ones that embed it into policy, procurement standards, and staff competencies rather than relying on a single team or a single champion to keep it alive. Design needs to become infrastructure, not initiative.
The public sector organisations that have managed to make human-centred design durable share a few common traits. They train frontline staff and middle managers in design methods, not just specialist teams, so the practice isn’t owned by a small group that can be defunded or reorganised away. They build feedback loops into how policy gets evaluated, so user insight becomes part of governance rather than a separate stream of research. And they measure success in terms leadership already cares about, service efficiency, cost avoidance, and public trust, rather than design-specific metrics that only resonate within the design community itself.
None of this is quick. Culture change in large public institutions rarely is. But the organisations that treat human-centred design as a long-term capability rather than a temporary methodology are the ones seeing it survive budget cuts, leadership turnover, and shifting political priorities.
Where This Leaves Public Sector Teams
Human-centred design has proven, again and again, that it can produce better public services when it is given the room to work. The challenge was never whether the method is effective. The challenge is whether government structures can hold onto it long enough for it to become normal rather than novel. Closing that gap is less about running another workshop and more about rethinking how public institutions govern, fund, and reward the work of understanding the people they serve.
For public servants and leaders trying to build that kind of lasting capability, Future Proofing By Design by Nilufer Erdebil offers a practical roadmap for using design thinking to build more resilient teams and services in the public sector, with real government examples rather than borrowed corporate theory.