The Importance of Worker-Led Design
For decades, a popular paradigm in product development has been “User-Centred Design” (UCD). While UCD promised to make technology intuitive, in workplace contexts it has frequently degenerated into an instrument of managerial control. For understandable commercial reasons, product teams have tended to design and build enterprise tools specifically for executive buyers. These designs prioritise automated monitoring and efficiency over human agency.
Some argue that establishing structural guardrails and collective bargaining frameworks will inherently stall technological innovation. However, historical evidence demonstrates that mandatory regulations and compliance standards have repeatedly acted as catalysts for pushing emerging technologies from niche innovations into universal adoption across major industries.
The 2009 HITECH Act in the United States established strict data accessibility, safety, and security requirements, pairing them with financial penalties for non-compliance. Driven by these standards, hospital adoption of basic Electronic Health Record (EHR) technology jumped from under 10% in 2008 to over 96% within a decade, standardising digital medical databases and cloud-based patient management platforms nationwide.
"Worker-Led Design ensures that workers have a voice when design choices are made."
Worker-Led Design (or worker-centred design, WCD) has emerged as a vital counter-framework to technological determinism. It rejects the narrative that technology is an autonomous, inevitable force (like the weather) that simply happens to workers. Because workplace systems are designed, produced, implemented, and governed by human choices at every stage, Worker-Led Design ensures that workers have a voice when those choices are made.
The primary purpose of Worker-Led Design is to rebalance power across the technology lifecycle and counter the harms of opaque algorithmic management. As Lisa Kresge of the UC Berkeley Labor Centre in the US points out, technology acts as a mirror of the institutional and regulatory context in which it is developed. When software is deployed without worker input, design criteria routinely fail to account for basic human realities. Regulation, however, can help offset this by requiring developers to recalibrate algorithms.
Sectors that have benefited from this include,
Airlines: Backed by high federal policy frameworks and union density in the US, software developers are now legally required to hardcode safety regulations and collective bargaining rules such as strict rest minimums and seniority bidding directly into scheduling code.
Healthcare: Where regulation focuses on billing structures, systems often default to administrative surveillance. However, state-mandated staffing ratios can force algorithms to prioritise continuity of care and protect clinical workflows.
Retail: Lacking federal scheduling laws and union density, systems historically defaulted to hyper-optimised 'just-in-time' scheduling, creating harmful practices like “clopening” shifts - where workers close a store at night and returns to reopen it only a few hours later. Emerging Fair Workweek policies now require software to hardcode 11-hour rest gaps and advance notice.
Worker-led Design Methodologies
Grounding Worker-Led Design in practical product methodology requires synthesising participatory design traditions with modern Human-Computer Interaction (HCI) practices. Foundational references include Reflective Design (reflecting on unconscious values embedded in computing), Speculative Design (imagining alternative technical futures), and Participatory Design (ensuring affected stakeholders directly shape technical systems).
Sarah Fox, from Carnegie Mellon University in the US, emphasises how meaningful participation must occur upstream during the initial problem definition phase rather than downstream after a tool has already been procured or built.
During an ILO webinar entitled 'At a Crossroads: Worker Voice and the Future of Workplace Technology', she and her colleague, Jodi Forlizzi, outlined a 4-Step Framework for Worker-Centred Technology Design:
Understand: Map the operational reality and worker experiences through observations and interviews, contrasting 'work-as-done' against management's 'work-as-imagined'.
Reframe: Convene collaborative workshops with workers, developers, and managers to challenge default algorithmic goals and surface invisible operational factors.
Materialise: Build low-fidelity prototypes, alternative software interfaces, and training modules that embody worker discretion.
Evaluate & Educate: Feed co-design outcomes back into policy, software sprints, and union contract demands.
In a multi-year study alongside UNITE HERE (including Culinary Workers Union Local 226 and Local 2), Fox and Forlizzi examined algorithmic room-assignment software used by hotel housekeepers. Algorithms initially dictated exact room cleaning sequences to optimise business targets, but overlooked physical workloads, hotel layouts, and heavy linen burdens, causing high frustration and reduced autonomy.
By bringing housekeepers, union representatives, managers, and software engineers into joint prototyping workshops, the team co-designed a feature called 'self-sequencing'. This tool returned control over task ordering back to the housekeepers while maintaining required operational outputs. Software engineers actively integrated workers' insights into their agile development sprints, while union members successfully negotiated contractual rights to self-sequencing into their collective bargaining agreements.
The Benefits of Worker-Led Design
Integrating worker-led practices delivers distinct, tangible benefits across multiple dimensions of product development and governance. Analysis of over 500 collective bargaining agreements by Lisa Kresge reveals that structured, worker participation leads to critical contractual protections.
For instance,
Procedural Rights: Securing advance notice, right-to-bargain timelines, and system information rights before new technology is introduced.
Protected Human Discretion: Nurses have negotiated explicit contract language ensuring AI prediction tools cannot override human clinical judgment (such as automated discharge decisions).
Liability Protections: Entertainment workers (IATSE) negotiated guardrails specifying that workers required to use generative AI tools cannot be held liable for technology output failures.
Workplace tools designed without frontline context frequently fail upon rollout due to unaddressed operational edge cases. Worker participation provides product teams with accurate domain models. Furthermore, demanding system explainability during procurement creates common ground between unions and enterprise buyers, preventing management from hiding behind vendor 'black box' algorithms or locked-in software contracts.
Worker-Led Design can also empower historically excluded populations. Disability justice scholars and accessible computing researchers show that when disabled individuals actively lead the design process, technology evolves from rigid, top-down compliance systems into flexible, empowering workflow tools built around bodily autonomy and authentic human capacity.
Worker-Led Design is not a passive feedback mechanism - it is an active framework for building ethical, effective, and sustainable technology. By moving worker participation upstream, hardcoding rights into system architecture, and aligning product design with collective bargaining, technology can fulfil its true potential: enhancing human capability, preserving dignity, and supporting shared prosperity.
Comments