SUMMARY - Co-Design and Inclusive Tech Creation

Co-Design and Inclusive Tech Creation

A technology company builds an app to help people manage chronic health conditions. The team includes software developers, user experience designers, health professionals, and business strategists. Conspicuously absent: people who actually live with chronic health conditions. The resulting app makes assumptions about daily routines, energy levels, and cognitive load that don't match the realities of chronic illness. Features that seemed helpful in design sessions prove burdensome in practice. The app is technically sophisticated but practically unhelpful.

This pattern—building solutions for people without involving those people in the design—repeats across technology, policy, and service design. Co-design offers an alternative: centering the expertise of those who will use, be affected by, or live with what is being created.

What Co-Design Means

Co-design goes beyond consultation or user testing. It involves affected communities as partners throughout the design process, from problem definition through implementation and evaluation.

Consultation asks people for input on decisions others will make. User testing asks people to evaluate solutions others have created. Co-design shares decision-making power throughout the process.

The distinction matters because the early stages of design—defining the problem, identifying requirements, generating possibilities—shape everything that follows. When affected communities enter only at testing stages, fundamental assumptions have already been locked in.

Why Co-Design Matters for Inclusion

People experiencing barriers understand those barriers differently than outside experts. A mobility aid designer without a disability may focus on technical functionality while missing the social experience of using equipment that marks one as different. A digital service designer without experience of poverty may not understand how assumptions about stable addresses, phone numbers, and internet access exclude people in precarious situations.

Lived experience expertise complements—does not replace—technical expertise. The goal is bringing different forms of knowledge together, not substituting one for another.

Co-design also addresses power imbalances. Technology is not neutral; it embeds the assumptions, priorities, and blind spots of its creators. When creation happens without those affected, it tends to serve those already served while further marginalizing those already marginalized.

Co-Design in Practice

Principles

Early and ongoing involvement: Affected communities participate from project conception through implementation and evaluation, not just at designated "consultation" points.

Real decision-making power: Community input shapes outcomes, not just legitimates decisions already made. This may require governance structures that share authority.

Accessibility of the process: Co-design processes must be accessible to the communities involved. Meetings at inaccessible times or locations, materials in inaccessible formats, or processes assuming particular capabilities exclude the people whose involvement matters most.

Compensation: Expecting people to donate their time and expertise while others are paid devalues lived experience. Co-design should compensate participants fairly.

Transparency: Participants should understand how their input is used and why decisions are made. When community input is overridden, reasons should be explained.

Challenges

Representation: Who speaks for a community? Communities are not monolithic. Ensuring diverse voices within communities—not just organizational representatives—requires intentional recruitment and multiple engagement methods.

Power dynamics: Even in co-design processes, power imbalances persist. Technical experts may dominate discussions. Organizational participants may have more resources and institutional backing. Facilitation must actively address these dynamics.

Timeline and budget: Genuine co-design takes more time and resources than conventional design. Organizations facing deadline and budget pressures may shortcut meaningful involvement.

Scope limitations: Co-design cannot address constraints participants don't control. A co-designed service operating within an unjust system may be better than alternatives but cannot fix systemic problems.

Examples in Canada

The development of the Accessible Canada Act involved extensive consultation with disability communities, though advocates debated whether the process constituted genuine co-design or elaborate consultation. The ongoing development of accessibility standards under the Act includes community participation, with ongoing debates about the adequacy of that participation.

Indigenous-led technology initiatives often embody co-design principles, with communities directing projects rather than serving as input sources for external organizations. The First Nations Information Governance Centre's work on data sovereignty reflects community-driven approaches to technology governance.

Municipal governments increasingly use co-design for service redesign, though quality varies widely. Toronto's approach to redesigning city services has involved affected communities, while other jurisdictions' "co-design" amounts to surveys and town halls.

Critiques and Tensions

Some argue that co-design expectations can become extractive—asking marginalized communities to repeatedly educate organizations while those organizations profit from the knowledge gained. If co-design becomes a requirement without adequate resources, the burden falls on already-burdened communities.

Others note that co-design can be performed without substance—checking boxes of community involvement while fundamental decisions remain with institutional actors. The language of co-design can legitimate exclusionary processes.

There are also genuine questions about expertise and efficiency. Technical decisions may require specialized knowledge that affected communities don't have. Democratic input may conflict with technical best practices. Balancing community authority with technical requirements creates ongoing tension.

The Question

If technology shapes life chances, and if technology embeds the assumptions of its creators, then who creates technology is a question of justice. How can co-design move from aspiration to standard practice? What resources and structures would enable genuine power-sharing in technology creation? And how can organizations be held accountable for meaningful co-design rather than performative consultation?