For decades, traditional service design operated under an expert-driven model. High-level executives, external management consultants, and specialized design teams would retreat into closed boardrooms, analyze secondary market research, and draft strategic service frameworks in isolation. These services were then rolled out top-down to customers and frontline staff, driven by the assumption that expert design teams inherently knew what was best for the people using and operating the system. Unsurprisingly, many of these top-down solutions failed upon exposure to real-world operational realities.
When organizations design for people rather than with them, they create a fundamental disconnect between institutional assumptions and lived realities. Co-design and participatory design dismantle this outdated dynamic. By bringing end users, community members, customer support reps, field technicians, and administrative staff directly into the creative and decision-making process, organizations shift from designing in a vacuum to building resilient, high-impact services grounded in authentic human experience.
1. What Is Co-Design? Shifting Power Dynamics in Design
Co-design (collaborative design) and participatory design are methodologies that treat users and frontline employees not merely as research subjects or passive consumers, but as active, equal co-creators throughout the entire design lifecycle.
In traditional human-centered design, designers interview users to gather insights, retreat to synthesize the data privately, and return months later with a finished product or service concept. Co-design transforms this relationship by sharing creative power and decision-making authority. It acknowledges a fundamental principle: people with lived experience are the true experts in their own lives and daily work environments.
The Spectrum of Public and User Participation
To understand the depth of participatory design, organizations often look at the spectrum of engagement across four distinct levels:
- Design FOR People (Inform/Consult): Passive engagement. The organization collects survey data or conducts one-way focus groups, retains total decision-making control, and delivers a pre-determined solution.
- Design WITH People (Co-Design): Active partnership. Users, communities, and frontline staff participate directly in problem definition, ideation workshops, prototyping, and iterative testing.
- Design BY People (Empower/Lead): Community-led initiatives. Professional designers act purely as facilitators and resource providers, giving community members full ownership over decision-making and implementation.
Shifting from designing for to designing with ensures that services are not only desirable to customers, but also operationally feasible for frontline workers and sustainable for the enterprise.
2. Why Frontline Worker Involvement Is Non-Negotiable
A frequent point of failure in organizational transformations is prioritizing the external customer experience while completely excluding the internal employee experience. Frontline staff—call center agents, triage nurses, bank tellers, delivery drivers, and retail associates—are the individuals responsible for bringing a service to life every day.
When frontline workers are excluded from service design, leadership creates severe operational friction:
- Unrealistic Workflows: Executives design "ideal" processes on paper that fail to account for system lag, high-stress customer interactions, or missing physical tools.
- Shadow Systems and Workarounds: When official tools are clunky, frustrated staff invent unauthorized workarounds—using personal messaging apps, manual spreadsheets, or paper notes—creating massive data-security and operational risks.
- Burnout and High Turnover: Forcing employees to use fragmented, unintuitive systems daily leads directly to cognitive exhaustion, decreased morale, and high attrition rates.
The Power of Frontline Insights
Frontline staff possess an intuitive, real-time understanding of system flaws that executive leadership rarely sees. They know exactly which policy rules trigger customer anger, which software screens slow down intake times, and which departmental handoffs routinely drop tasks. Involving frontline staff in co-design workshops builds immediate internal buy-in, eliminates operational friction early, and creates software tools that genuinely empower workers.
3. Practical Co-Design Methods and Workshop Toolkits
Co-design requires structured, inclusive facilitation tools that allow non-designers—whether a rural healthcare patient or a warehouse technician—to comfortably articulate their ideas and contribute to solution architecture.
1. Generative Toolkits and Visual Boundary Objects
Raw text and abstract technical terminology create barriers during collaborative workshops. Co-design facilitators use generative toolkits—such as physical card decks, visual icon blocks, journey canvas boards, and storyboarding grids. These "boundary objects" provide a shared neutral language, allowing diverse stakeholders to visually map steps, highlight friction points, and build service flows together.
2. Collaborative Scenario Role-Playing
Services unfold dynamically over time. Role-playing allows co-design participants to act out proposed service interactions in real time. Frontline workers and users physically test new service scripts, counter layouts, or digital handoffs in a low-stakes environment, immediately exposing awkward phrasing, spatial bottlenecks, or missing process steps before any code is written or infrastructure built.
3. Low-Fidelity Paper Prototyping and Desktop Walkthroughs
High-fidelity digital prototypes can intimidate non-technical participants and create a false sense of completion. Co-design utilizes 3D paper models, rough foam cutouts, sketch pads, and simple digital wireframes. Because paper prototypes look deliberately unfinished, participants feel completely comfortable tearing them apart, rearranging components, and proposing radical improvements on the spot.
4. Equal-Voice Facilitation Protocols
Power dynamics can easily derail a co-design session if a senior executive dominates the conversation over a junior customer service representative or a community member. Skilled facilitators enforce strict workshop protocols—such as silent brainwriting, round-robin idea sharing, dot-voting allocation, and anonymous feedback loops—ensuring every participant has equal influence over prioritized outcomes.
4. Case Studies: Co-Design in Action Across Sectors
Case Study 1: Public Social Services and Community Support
- The Challenge: A city government struggled with low enrollment in its public housing assistance program despite high local demand. The existing application process was overly complex and intimidating.
- The Co-Design Approach: Instead of hiring external software vendors to rebuild the portal, service designers held participatory co-design sessions in local community centers. Applicants, housing advocates, social workers, and IT administrators sat together at the same table.
- The Outcome: The team discovered that applicants felt humiliated by intrusive background questions early in the digital form. Together, they restructured the journey—moving sensitive questions to later phases, replacing dense legalese with conversational language, and allowing phone-photo uploads for documentation. Application completion rates rose by over 40%.
Case Study 2: Enterprise Banking and Backstage Workflows
- The Challenge: A commercial bank experienced severe delays in processing small business loan applications, leading to high client churn.
- The Co-Design Approach: The bank conducted a series of co-design sprints bringing together commercial loan applicants, underwriting officers, branch managers, and software developers.
- The Outcome: Underwriters revealed that they spent up to two hours per application manually cross-referencing customer data across three legacy databases. The co-design squad created a simple internal dashboard that consolidated data automatically, cutting processing times from two weeks to under two days.
5. Overcoming Ethical and Operational Challenges in Co-Design
While co-design is extraordinarily effective, organizing participatory processes requires careful ethical consideration and operational discipline.
1. Avoiding Tokenism: Inviting community members or staff to a single workshop simply to check a box—without granting them genuine influence over final decisions—is performative and damages institutional trust. Organizations must clearly communicate how participant feedback will directly shape execution.
2. Fair Compensation and Reciprocity: Asking community members or vulnerable users to share their lived experience and emotional labor without fair compensation is exploitative. Always budget for competitive hourly stipends, child care support, accessible transportation, and catered meals for participants.
3. Managing Conflicting Stakeholder Needs: In any co-design process, customer desires may collide with technical realities or legal compliance rules. Facilitators must maintain clear transparency about operational constraints from day one, framing challenges around shared goals: "How might we meet regulatory requirement X while keeping the user experience simple for Y?"
The Democratic Future of Service Design
Designing services with people is fundamentally an act of institutional humility. It recognizes that no single boardroom executive, strategy consultant, or software engineer possesses all the answers to complex operational and social challenges.
By opening up the design process to the people who rely on services to live their lives and the frontline staff who work tirelessly to deliver them, organizations build more than just efficient systems. They foster deep trust, create accessible and dignified experiences, and build resilient, highly adaptable service ecosystems that stand the test of time.