Socio-technical systems and participatory design: the organisation is part of the artefact

Year 3 / Module 17 Theories of interaction / Unit 8 / Socio-technical systems and participatory design: the organisation is part of the artefact

Socio-technical systems and participatory design: the organisation is part of the artefact

HCI3101 · Unit 8 of 10

The socio-technical claim is that technology and work organisation are a single design problem, so a system can pass every acceptance test and still fail by relocating exceptions and coordination work; the tradition survives as principles and project scoping rather than as a validated intervention method, a gap its own advocates concede.

Socio-technical systems and participatory design: the organisation is part of the artefact

The socio-technical tradition claims that technology and work organisation are one design problem. A system can pass every functional test and still fail, by moving its exceptions and its coordination work somewhere unmeasured. As the eighth of ten units, it argues that the claim was earned by a founding case and a set of principles, and that the tradition now survives mainly as principles and project scoping rather than as a validated intervention, a gap its own advocates name.

The founding case: a better machine broke the work group

Trist and Bamforth (1951) studied the mechanisation of coal-getting in British pits, setting the older hand-got method against the conventional longwall method that replaced it. Under hand-got working, small teams chose their own partners, completed the whole cycle and shared the pay, an arrangement the authors called responsible autonomy. The longwall method spread the same workers along a long coal face and split the cycle across three shifts. No group owned the whole task. The authors reported higher absence, more blaming between shifts and a failure to realise the promised productivity.

Their diagnostic move is the unit's hinge. A workplace has a technical side, the machines, layout and method, and a social side, the roles, relationships and sense of responsibility among the people. The two are coupled, so a change to one changes the other. They also described a composite longwall arrangement in one pit, where a large group carried the whole cycle across all shifts and did better. The same machinery with a different organisation produced a different result: the fit, not the machine, decided the outcome.

Cherns made joint optimisation teachable and checkable

Emery (1959) named the lesson. He formulated the socio-technical system as a joint optimisation problem: the social and technical subsystems must be designed together for either to work. Cherns (1976) turned that into nine design principles, among them minimum critical specification and the management of variance where it arises. Variance control, one of them, restates the coal-getting lesson: disturbance is handled where it arises. The longwall arrangement did the opposite, pushing every interruption up to the next shift or the supervisor. The composite group in the same pit absorbed it at the face.

Cherns (1987) revisited the list and found that most of it had stood, but that modifications were needed. The design-process principles, he found, were more closely bound to the design principles than he had allowed. Clegg (2000) offered a revised set for system design, extended from Cherns and sorted into meta, content and process types. His verdict on their status is the unit's second thread: the principles are necessary but not sufficient.

The gap its own advocates concede

Clegg (2000) records that joint design and optimisation of social and technical systems remains rare. Most investment in information technology is technology-led, and users seldom have substantial influence, so interventions take the technology as given. Baxter and Sommerville (2011) begin from the same observation. A socio-technical approach is acknowledged to produce systems more acceptable to users, and yet is rarely practised. Their paper reviews the better known methods, identifies problems with them, and proposes a framework that would close the gap it concedes: this unit reads it as evidence for the gap.

The tradition talks of actors, and participation carries two justifications

The tradition's HCI-facing version of the claim is Bannon's (1995) argument. The human-factors framing shrinks the user to a set of task parameters, and design should treat people as actors within a social setting. Eason (1988) drew the design consequence. He argued that technical and organisational choices are interdependent, and cannot be settled one after the other. If the organisation is part of the artefact, then a design that fixes the screen leaves half the problem to chance. It trusts the work to rearrange itself.

The participatory branch answers who decides. Bjerknes and Bratteteig (1995) analyse Scandinavian system-development projects against working-life democracy. They argue that the field moved from politics to ethics, recasting the political rationale for participation as good practice. They want it back. Their reading separates two honest justifications. On the quality argument, participation improves the product because users know the work. On the democracy argument, participation is owed to the people whose work is being redesigned, whatever it does to the product. A project can hold either, and the two do not always point the same way.

Participation is a negotiated arrangement, not a technique

Bodker (1996) complicates the tidy version. She argues that the subject has been posed from the researchers' side, as the problem of gaining access to users, and should be examined from the user's side, as the question of the conditions under which participation can occur at all. She notes that the collective-resource projects worked in circumstances quite different from those of 1990s corporations, and presents a later one to show the conflicts involved. That project joined Aarhus University with the Danish National Labour Inspection Service from 1990, and managers took part along with inspectors and secretaries, so the conflicts ran through the user side as well: inspectors writing their own letters collided with the secretaries who had done that work, and efficiency of inspection pulled against its quality. Participation is not a step that reliably transfers knowledge from users to designers; it is a negotiated arrangement whose conditions decide what it can achieve.

The tradition can show a varied practice, not a method

What the tradition can show for itself is a large and varied practice rather than a validated method. Halskov and Hansen (2015) reviewed ten years of full papers at the Participatory Design Conferences, from 2002 to 2012. They found contributions in five main categories and a spread in how participation was defined. Frauenberger, Good, Fitzpatrick and Iversen (2015) make the matching demand from inside, proposing a tool that guides reflection through four lenses: epistemology, values, stakeholders and outcomes. Accountability and rigour, they insist, are delivered through debate and reflection rather than through the positivist framework the field rejects. It is coherent, and also hard to check.

Contested question: is there a validated intervention, or only principles and scoping?

The dispute is not whether the socio-technical claim is true, since these papers agree that technology and organisation are coupled, but what the tradition has to show for it. Clegg (2000) and Baxter and Sommerville (2011) hold that the approach works when it is applied, and that the failure is one of diffusion and method. Their framework is meant to repair that failure.

A second position is that the recurring call for rigour signals a demonstration not yet made. Frauenberger and colleagues (2015) locate accountability in debate and reflection rather than in outcome measures. Halskov and Hansen (2015) document a field too plural for a common criterion. If rigour is defined internally, a study cannot fail the criterion, and a method that cannot fail is not yet a validated one.

A third, most recent, position is that participation as practised still fails the people it claims to serve. Udoewa (2022) argues that participatory design initiated by an organisation commonly maintains or strengthens the power imbalance between designer and community. Jang, Liu, Carrington and Begel (2026) measured the gap rather than argued it: coding 120 CHI and ASSETS papers, the ASSETS half from the accessibility community's own venue, against a nine-level scale of shared authority, they found mean participation no higher than consultation, over 80 per cent of works never reaching shared decision-making, and works naming participatory design scoring lowest of all. Power-sharing peaked in solution generation and was lowest in problem framing.

What would settle it is a comparison the tradition has not reported. It would follow two systems for the same work past go-live, one designed through joint optimisation and one designed technically, far enough to show where the exceptions and the coordination work landed. Clegg's (2000) prediction that unresolved design issues produce systems that do not meet their objectives is a testable claim of exactly this kind. Until it is reported, the honest verdict is the tradition's own: principles and project scoping, not a validated intervention.

The evidence is uneven in kind. The founding case is a natural comparison observed in working pits rather than an assigned one, and the tradition's claims rest on it. Halskov and Hansen (2015) review ten years of conference practice and document plurality rather than effect. The demand for rigour from Frauenberger and colleagues (2015) is a position paper. Jang and colleagues (2026) supply the first measurement at scale, recording how authority was shared, not whether the systems worked. While the dispute is open, a designer should fix the joint-optimisation arrangement before go-live and fund a follow-up recording where the exceptions and the coordination work land. The strongest objection is that the unit applies a standard it applies nowhere else. No tradition in this module reports a two-arm comparison past go-live, and a natural comparison is weak evidence rather than none.

Where the argument is heading

Ang, Sankaran and Liu (2025) review socio-technical principles for human-robot teams. They modify those that still apply and add new ones, arriving at thirty-four principles in seven themes. Eight concern adaptive autonomy, transparency, workload management and trust. That the list must grow is the finding: in an intelligent robot the tradition meets a component that is neither simply technical nor simply social. Udoewa (2022) pushes from the opposite direction, arguing that the tradition's own processes carry coloniality. The question is whether the approach can be specified tightly enough to be tested without losing the democratic commitment that Bjerknes and Bratteteig (1995) are still trying to recover.

The sources this unit rests on

Ang, K. C., Sankaran, S. and Liu, D. (2025). Advancing sociotechnical systems theory: New principles for human-robot team design and development. Applied Ergonomics 129. doi:10.1016/j.apergo.2025.104604 Adapts socio-technical principles for human-robot teams, giving thirty-four principles in seven themes plus eight new ones. The still-growing list shows the tradition is not settling.
Bannon, L. J. (1995). From Human Factors to Human Actors. In Readings in Human-Computer Interaction. doi:10.1016/b978-0-08-051574-8.50024-8 Argues that the human-factors framing shrinks the user to task parameters, and that design should treat people as actors in a social setting. It bridges socio-technical design into HCI.
Baxter, G. and Sommerville, I. (2011). Socio-technical systems: From design methods to systems engineering. Interacting with Computers 23(1). doi:10.1016/j.intcom.2010.07.003 Notes that a socio-technical approach is widely acknowledged to give better systems and yet is rarely practised, analyses the known methods, and proposes a framework joining organisational change and system development. The clearest admission of the gap by its own advocates.
Bjerknes, G. and Bratteteig, T. (1995). User Participation and Democracy: A Discussion of Scandinavian Research on System Development. Scandinavian Journal of Information Systems 7(1). https://aisel.aisnet.org/sjis/vol7/iss1/1/ Analyses Scandinavian projects against working-life democracy, finding a shift from politics to ethics and arguing the political dimension should return. The unit's source for the quality argument and the democracy argument.
Bodker, S. (1996). Creating Conditions for Participation: Conflicts and Resources in Systems Development. Human-Computer Interaction 11(3). doi:10.1207/s15327051hci1103_2 Argues that participation has been posed from the researchers' side, as gaining access to users, and should instead be examined as the conditions under which users can participate. Participation as a negotiated arrangement, not a transferable technique.
Cherns, A. (1976). The Principles of Sociotechnical Design. Human Relations 29(8). doi:10.1177/001872677602900806 Sets out nine principles for socio-technical design, covering minimum critical specification, variance control and boundary management. It made the tradition teachable and checkable.
Cherns, A. (1987). Principles of Sociotechnical Design Revisited. Human Relations 40(3). doi:10.1177/001872678704000303 Reviews the author's own 1976 principles, finds most have stood but that modifications are needed, and binds the design-process principles to the design principles. The principles were always provisional.
Clegg, C. W. (2000). Sociotechnical principles for system design. Applied Ergonomics 31(5). doi:10.1016/s0003-6870(00)00009-0 Offers a revised set of principles extending Cherns, and records that joint optimisation remains rare, most investment is technology-led and users seldom have influence. It concludes that principles are necessary but not sufficient.
Eason, K. D. (1988). Information Technology and Organisational Change. Taylor and Francis. doi:10.1201/9781482275469 Develops a user-centred socio-technical analysis of information technology and organisational change, arguing that technical and organisational choices are interdependent and cannot be settled sequentially. The unit's design consequence of coupling.
Emery, F. E. (1959). Characteristics of socio-technical systems. In Trist, E. and Murray, H. (eds), The Social Engagement of Social Science, Vol. 2. doi:10.9783/9781512819052-009 Formulates the socio-technical system as a joint optimisation problem, in which the social and technical subsystems must be designed together for either to work. The theoretical statement of the coal-getting lesson.
Frauenberger, C., Good, J., Fitzpatrick, G. and Iversen, O. S. (2015). In pursuit of rigour and accountability in participatory design. International Journal of Human-Computer Studies 74. doi:10.1016/j.ijhcs.2014.09.004 Argues a diversified field needs a discussion of accountability and rigour, rejects the positivist framework, and proposes four lenses: epistemology, values, stakeholders and outcomes. The internal standard that makes the criterion hard to check.
Jang, J., Liu, J., Carrington, P. and Begel, A. (2026). Proceedings of the 28th International ACM SIGACCESS Conference on Computers and Accessibility. doi:10.1145/3797867.3829026 Coded 120 CHI and ASSETS papers claiming participatory methods against a nine-level scale of shared authority: mean participation rose no higher than consultation, and works naming participatory design scored lowest.
Halskov, K. and Hansen, N. B. (2015). The diversity of participatory design research practice at PDC 2002 to 2012. International Journal of Human-Computer Studies 74. doi:10.1016/j.ijhcs.2014.09.003 Reviews ten years of participatory design research from the Participatory Design Conferences against five fundamental aspects, finding five categories of contribution and a spread in how participation was defined. Evidence that participatory design means many things.
Trist, E. L. and Bamforth, K. W. (1951). Some Social and Psychological Consequences of the Longwall Method of Coal-Getting. Human Relations 4(1). doi:10.1177/001872675100400101 Analyses the mechanisation of coal-getting, contrasting intact hand-got work groups with the shift-divided longwall method, and reports higher absence, more blaming and a failure to realise the promised productivity, while a composite arrangement did better. The founding case for treating technology and organisation as one design problem.
Udoewa, V. (2022). An introduction to radical participatory design: decolonising participatory design processes. Design Science 8. doi:10.1017/dsj.2022.24 Argues that participatory design initiated by an organisation commonly maintains or strengthens the power imbalance between designer and community, and that disappointment is greater because participation raised expectations. Radical participatory design answers with a typology of degrees.

Check your understanding & apply it · 4 questions, 1 essay

1A supplier runs a technical pilot on a simulated ward and reports function coverage, task times and error rates. What does the pilot leave unmeasured, and why does that matter?

2A new rota pushes every interruption up to the next shift or to the supervisor. Which of Cherns's (1976) principles does the arrangement violate, and what does the same pit show?

3A project joins a university with the local branch of a national labour inspection service. Managers take part alongside inspectors and secretaries, and inspectors who begin writing their own letters collide with the secretaries who had done that work. What does the unit draw from the conflict?

4A review of a decade of participatory design papers finds contributions in five categories with participation defined in many ways, and a companion paper locates rigour and accountability in debate and reflection. What is the unit's verdict on the tradition's evidence?

5Essay A hospital trust is introducing an electronic handover system for shift changes. The supplier will run a technical pilot on a simulated ward and report function coverage, task times and error rates. Write a socio-technical assessment of that plan. Say what the pilot will miss and why, using Trist and Bamforth (1951) and Clegg (2000); say who should participate and under which justification, including staff who use assistive technology and staff on the night shift, using Bjerknes and Bratteteig (1995) and Bodker (1996); state the standard you would hold the participation to, using Frauenberger and colleagues (2015) and Halskov and Hansen (2015); and propose one comparison the trust should run to test whether the system works, naming what it would measure. Ground each part in named sources from this unit.

The pilot measures the technical subsystem and leaves the social subsystem unmeasured, which is the error Trist and Bamforth (1951) diagnosed in mechanised coal-getting: a method that split work across shifts and broke the intact groups produced higher absence and mutual blaming, and the promised productivity did not arrive. A simulated ward cannot show whether the handover system moves the exception path and the coordination work onto some other person, which is exactly what their coupling argument predicts. Clegg (2000) supplies the diagnostic question: joint optimisation of social and technical systems remains rare, most investment in information technology is technology-led, and users seldom have substantial influence on development, so a supplier-run technical pilot is the pattern he warns against, and his own verdict that principles are necessary but not sufficient should temper any claim that passing the pilot settles the design. Participation should include the people who hold the work together at shift change, not a representative sample of staff. Bjerknes and Bratteteig (1995) let me name the justification rather than assume it: participation can be argued for on quality, because the participants know the work, or on democracy, because the people whose work is being redesigned are owed a say, and the trust should state which it intends, since a quality argument can be satisfied by consulting a few experts while a democracy argument cannot. Bodker (1996) adds that participation is a negotiated arrangement whose conditions decide what it can achieve, so the plan must say what time, information and authority participants will actually have rather than treating a workshop as sufficient. I would hold the participation to the standard Frauenberger and colleagues (2015) propose, using their four lenses of epistemology, values, stakeholders and outcomes to make the choices explicit, while noting that they locate rigour in debate and reflection, and to the accountability Halskov and Hansen (2015) imply when they show a field spread across five main categories with participation defined in many ways. The test the trust should run is the comparison the tradition has not reported: introduce the system on two comparable wards, one designed through joint optimisation with the handover group and one adopted as supplied, and follow both past go-live, measuring not only error rates and task times but the frequency of unrecorded workarounds, the number of handovers that need a second person to reconstruct, and staff absence and reported strain in the weeks after the change. That is roughly Clegg's (2000) prediction made checkable, since he expects an unresolved design issue to produce a system that does not meet its objectives.