Public Design Patterns: an emerging language for government design
Five Lessons from the Global Public Design Conference 2025
Last September, I had the privilege of joining over 200 public-sector designers and policy teams from around the world in London for the Global Public Design Conference. As Senior Tutor in Service Design at the Royal College of Art, I co-convened this gathering with Andrew Knight, Head of the Policy Design Community for the UK Civil Service. The event was part of the World Design Congress’s Design Safari.
The discussions held at this conference represent a convergence of my work across different dimensions of public design. Through my position at the RCA, I lead research into how design can transform government services and how governments can build their design capabilities. Through Unit, we partner with governments across Latin America and beyond, helping them redesign everything from citizen services to internal processes. And through Diseño Público, we’ve built a community of practice connecting Spanish-speaking government designers who would otherwise work in isolation. Across all these roles, I’ve witnessed the same pattern: teams struggling with identical challenges, reinventing solutions that already exist in the ministry next door, unaware that others have already solved the problems that keep them awake at night.
Over the summer, our research project engaged 48 government teams across nine sectors—Education, Health, Justice, Welfare, Tax, Local Places, Business & Trade, Cross-Government Services, and Policing—examining recurring challenges in their systems. In London, we brought these findings together to compare insights and explore whether shared patterns could strengthen how governments design and coordinate services.
We explored design patterns as “evidence-based solutions to common design problems”—reusable building blocks that help governments avoid duplicating effort whilst learning from each other’s successes and failures. Our goal was to identify patterns emerging across different governments and establish foundations for international collaboration in developing and sharing them.
The conference featured presentations from Christian Bason (Transition Collective), Sabine Junginger (Northumbria School of Design), and Nicola Goger and Martin Ford-Downs (Ministry of Justice). Teams from our summer mini-conferences shared their insights, and audience members participated in activities led by designer volunteers.
In this article, I outline the core lessons that emerged from those exchanges: why patterns matter, how they operate at different scales, and what they reveal about the conditions needed for genuine transformation. The five lessons I highlight—on trust, scale, context, language, and creative tensions—are grounded in real cases from participating governments. Together, they demonstrate that governments worldwide face remarkably similar problems and often duplicate effort, even when better solutions already exist elsewhere.
My main conclusion is straightforward: if governments want to improve their services whilst reducing unnecessary duplication, they need systematic ways to share knowledge. Pattern languages offer a practical path forward by documenting what works, explaining why, and making these insights usable across contexts. This isn’t about imposing uniform solutions but about creating frameworks that help teams learn from each other whilst respecting local needs.
The insights presented here synthesise early reflections sparked by presentations and discussions. You can watch our video to hear public design leaders speak directly about the transformative potential they see. Over the coming weeks, each sector team will publish detailed findings on the UK Government Blog, providing practical resources.
The conference made clear that the appetite and capacity for this shift already exist. What comes next is continuing to build the evidence, strengthening organisational capabilities, and sustaining the collaborations that can turn isolated innovations into a shared global practice.
Why patterns matter now
In the 1970s, architect Christopher Alexander sought to address a fundamental challenge: how to create cities and buildings that genuinely improve human life amid growing urban complexity. His response was to develop “pattern languages”—systematic documentation of repeatable solutions that had proven successful across cultures and contexts. Alexander and his colleagues believed that the wisdom for creating humane environments already existed in successful spaces worldwide; it simply needed to be identified, documented, and made accessible to builders and planners. Their vision was that by creating a shared language of patterns—from the scale of regional planning down to construction details—communities could build environments that supported human flourishing rather than hindering it. This framework has since transformed fields from software engineering to urban planning, yet its application to government services remains largely untapped.
Government organisations worldwide face a fundamental paradox. Whilst they confront remarkably similar challenges—from processing applications to supporting citizens through life transitions—they typically work in isolation, each developing their own solutions. The UK Civil Service illustrates this challenge starkly: across 44 departments and over 400 agencies and public bodies, employing over half a million people, teams routinely duplicate effort, creating parallel solutions to identical problems without awareness of each other’s work.
This duplication represents more than inefficiency. Every hour spent recreating existing solutions is an hour not spent addressing the unique needs of specific communities or tackling novel challenges emerging from technological disruption, demographic shifts, or climate change. When governments operate in silos, they sacrifice their capacity for innovation on the altar of reinvention.
Pattern language theory offers a way forward. Effective patterns operate across scales, creating what Alexander called “living structure”—systems where small patterns nest within larger ones, each reinforcing the whole whilst maintaining local integrity. For government services, this multi-scalar approach means patterns can function from the smallest interaction (how to display an error message) through service components (how to verify identity) to complete life journeys (how to support someone through unemployment). This nested hierarchy enables coherent user experiences even when services span multiple agencies with different systems, cultures, and constraints.
Five lessons from a global practice
The conference discussions revealed fundamental insights into how design patterns function in government contexts—insights that challenge conventional assumptions about public-sector transformation. These lessons emerged not from theoretical speculation but from practical experience across nine sectors in different countries, as teams grappled with implementing patterns in real-world conditions.
Before exploring these lessons, it’s important to clarify what we mean by “design patterns” in government. A pattern is not a service itself, but rather a documented, reusable solution to a recurring design challenge. Just as architects use patterns to create welcoming entrances or natural lighting, government designers use patterns to address common challenges such as verifying identity, processing applications, or supporting citizens through life transitions. These patterns provide structured guidance whilst allowing adaptation to specific contexts—they’re frameworks for thinking, not rigid templates.
The following five lessons represent the conference’s most significant discoveries about how pattern languages can transform government services.
Lesson 1 – Trust is the foundation, not the outcome
In government services, design patterns must be built first on trust rather than efficiency, reversing the typical design sequence.
Traditional approaches to government reform typically focus on making services faster, cheaper, or more accurate, assuming that trust will follow from improved performance. The conference revealed this assumption to be fundamentally flawed. When government teams begin with efficiency metrics, they create patterns that may work perfectly in theory but fail in practice because citizens don’t trust them enough to engage.
This appeared particularly relevant to police services. The policing teams from Scotland, France, Norway and the Netherlands discovered this most acutely. Their work demonstrated that streamlined reporting patterns mean nothing if communities don’t trust police enough to report crimes in the first place. The French team’s victim journey mapping specifically identified trust breakdown points at service handovers between health, education, police, and justice services, leading them to design patterns that maintain confidence throughout multi-agency interactions.
Consider how this manifests more broadly: a highly efficient pattern for online applications might process claims in minutes rather than weeks. But if citizens don’t trust that their data is secure, that decisions are fair, or that they’ll receive what they’re entitled to, they may not use the service at all—or may submit incomplete information that ultimately creates more work for everyone.
Pattern languages address this by embedding trust-building elements at every level of design guidance. Rather than adding “trust features” after designing efficient processes, patterns start with trust requirements: How will citizens know what’s happening with their application? How can they correct errors? What recourse exists if something goes wrong? These questions shape the pattern from inception, creating design solutions that are trustworthy by design rather than by assertion.
Lesson 2 – Patterns must work across multiple scales simultaneously
Effective pattern languages create coherent experiences by connecting micro-interactions to macro-journeys through nested hierarchies.
A pattern language is a collection of interconnected patterns that work together, much like words combine to form sentences and paragraphs. In government, this means having patterns for tiny interactions (how to display an error message), patterns for complete tasks (how to apply for something), and patterns for entire life journeys (how to support someone through unemployment). These are not separate services but different levels of design guidance that ensure consistency across all government touchpoints.
The UK Ministry of Justice exemplified this multi-scalar approach through their nine core service patterns: record, understand, inform, request, apply, book, evaluate, decide, and pay. Meanwhile, the welfare teams from the Department for Work and Pensions (UK) and Ireland’s Department of Public Expenditure articulated this as “orders of patterns,” demonstrating how component-level interactions connect through service journeys to orchestrate life events.
Imagine trying to build a house where the architects, plumbers, and electricians each work from different plans that don’t align with one another. This is essentially how most governments operate—different departments create solutions that work in isolation but fail when citizens need to navigate between them. Pattern languages solve this by using nested hierarchies in which smaller patterns fit within larger ones.
For example, a micro-pattern for error messages (use clear language, explain what went wrong, provide next steps) sits within a pattern for form completion (save progress automatically, provide contextual help, show timeline), which sits within a pattern for applications (check eligibility first, gather documents systematically, track status transparently), which sits within a life event pattern (coordinate multiple services when someone loses their job).
This nested approach solves a persistent challenge: maintaining consistency without rigidity. Each level of pattern provides enough structure to ensure coherence whilst allowing flexibility for specific contexts. An error message pattern might be implemented differently in tax versus healthcare services, but both follow the same principles of clarity and actionability. This creates what citizens experience as “joined-up government” even when services are delivered by entirely separate organisations.
Lesson 3 – Context determines everything
Patterns are frameworks for thinking about design problems, not templates for copying solutions—they must be interpreted and adapted to local contexts to succeed.
One of the most counterintuitive findings was that the “best” patterns (those that worked brilliantly in one context) often failed when transplanted unchanged to new contexts, whilst “adequate” patterns adapted to local conditions succeeded brilliantly. This challenges the common assumption that patterns are universal solutions to be implemented identically everywhere.
The tax administration teams from the UK, Finland and Australia discovered this paradox directly. Whilst user interface patterns translated easily across their vastly different organisations, service and policy patterns required significant adaptation due to regulatory frameworks and organisational cultures. Similarly, the Thailand Institute of Justice’s successful transformation of prosecutor offices for child witnesses demonstrated that patterns succeed through adaptation to institutional contexts, not through rigid implementation.
Think of patterns like recipes rather than manufactured products. A recipe for bread provides essential elements—flour, water, yeast, salt—and basic techniques—mixing, kneading, rising, baking. But successful bakers adjust for altitude, humidity, flour types, and local tastes. The pattern remains recognisable as “bread-making” whilst producing contextually appropriate results.
Government design patterns work similarly. A pattern for “identity verification” might specify core principles: confirm the person is who they claim to be, prevent fraud, respect privacy, and provide alternatives for those without standard documents. But implementation varies dramatically. Countries with national ID systems might verify identity in seconds; others require multiple documents. Rural areas might emphasise in-person verification whilst cities prioritise digital methods. Some cultures expect formal procedures, whilst others demand simplicity.
This contextual adaptation isn’t pattern failure—it’s pattern success. By providing design principles and proven approaches whilst allowing local interpretation, patterns enable knowledge transfer without imposing inappropriate solutions. The pattern helps teams think through problems systematically rather than starting from scratch or blindly copying others.
Lesson 4 – Language shapes what’s possible
The words we use to describe patterns and design challenges don’t just communicate ideas; they fundamentally shape what solutions become possible.
Language in pattern development works like a photographer’s lens: it determines what comes into focus and what remains invisible. The education teams from the UK and Canada made this explicit by reframing “hard to reach” groups as “easy to exclude”. This linguistic shift fundamentally changed the pattern focus from extending services to examining institutional barriers.
When government teams describe certain populations as “hard to reach”, the implied design solutions focus on extending current services further—longer hours, more locations, additional languages. But when reframed as “easy to exclude”, the pattern focus shifts to examining why current approaches actively (if unintentionally) exclude people—complex forms, inflexible requirements, cultural assumptions.
The health teams from the UK, Peru and Canada similarly transformed their approach by conceptualising treatment plans as “living objects” rather than static documents. This linguistic change enabled patterns supporting continuous adaptation throughout patient journeys across multiple providers.
This linguistic dimension affects how we conceptualise patterns themselves. Consider the difference between a pattern for “processing applications” versus “helping people apply”. The first framing leads to patterns optimised for efficiency: batch processing, automated decisions, standardised outcomes. The second leads to patterns supporting human needs: saving progress, providing guidance, and offering alternatives. Same underlying challenge, fundamentally different pattern solutions.
The conference revealed that successful pattern languages require deliberate vocabulary development. Teams must agree not only on which design challenges to address but also on how to describe them. This shared language becomes the medium through which design knowledge transfers between teams, organisations, and even countries. Without linguistic alignment, patterns can’t travel—even perfect solutions remain trapped in their original contexts because others can’t understand what problem they solve or how they work.
Lesson 5 – Creative tensions can drive innovation
The most effective pattern languages don’t resolve tensions but harness them, using opposing forces to create adaptive, resilient design solutions.
Traditional design approaches treat tensions as problems to solve: choose efficiency or effectiveness, standardisation or customisation, expert knowledge or citizen input. Pattern languages recognise these tensions as generative forces that, when properly balanced, create better solutions than either extreme could achieve alone.
The business and trade teams from the UK and Canada demonstrated this through their pattern for policy-delivery alignment, which maintains standardised governance whilst allowing local variation in implementation. The local places teams from London boroughs (Lambeth, Camden, Hammersmith and Fulham) went further, developing modular patterns that explicitly preserve tension between global standards and local needs.
Consider the perpetual tension between standardisation (which enables efficiency and equity) and localisation (which ensures relevance and adoption). Rather than choosing one, effective patterns create what architects call “structure-preserving transformations”—changes that maintain essential qualities whilst allowing variation. A pattern for benefit applications might standardise the decision logic and evidence requirements whilst allowing local variation in support services, channel options, and communication styles.
The cross-government teams—including the U.S. Office of Personnel Management, Sweden’s Experia Lab, the EU Policy Lab, the Scottish Government, and the UK Policy Lab—articulated this as “technical democracy”, the challenge of combining professional expertise with democratic participation. Their work showed that patterns must be technically sound whilst remaining democratically legitimate, orchestrating productive dialogue between different forms of knowledge.
These creative tensions prevent pattern languages from becoming rigid dogma. They force continuous evolution, ensuring patterns remain living systems that adapt to changing contexts rather than becoming frozen “best practices” that eventually fail. The tension itself becomes the engine of innovation, pushing teams to find new balances as contexts shift.
The work ahead
These lessons demonstrate why pattern languages—collections of interconnected design solutions—offer such promise for government transformation. They provide structured approaches to common problems without mandating identical implementations. They enable knowledge sharing about design challenges without imposing inappropriate solutions. Most importantly, they transform isolated innovations in individual services into collective capability, allowing governments worldwide to learn from each other whilst respecting the unique contexts in which they operate.
The Global Public Design Conference demonstrated both appetite and capability for pattern-based transformation of government services. The challenge now lies in sustaining momentum and building infrastructure for long-term success.
Three priorities emerge clearly. First, continued documentation and evidence building to establish what works where and why. Second, the development of organisational capabilities that enable effective pattern adoption and adaptation. Third, nurturing relationships that transform isolated innovations into collective wisdom.
As governments worldwide face mounting challenges with diminishing resources, patterns offer practical mechanisms for learning at scale. They transform isolated innovations into shared capability, allowing governments to focus on genuinely unique challenges whilst building on proven solutions for common problems.
The patterns are emerging across sectors and continents. The community is forming through conferences, working groups, and informal networks. The transformation has begun, moving government services from isolated efforts toward collective intelligence. Join us in building this future, where government designers worldwide share knowledge, accelerate learning, and deliver better outcomes for citizens everywhere.
