Core methods | about 50 minutes | free
Find where variation is handled and design a jointly workable social and technical arrangement.
A basic primary-work-system exercise informed by the socio-technical tradition. It is not a complete participative design process or a substitute for workers' and users' involvement.
This is original learning material, not a reproduced official course. Mechanical checks have determinate answers within the stated case. Worked comparisons for open judgements show defensible reasoning, not the only possible model. Specialist pedagogical review is not recorded.
Fictional case: a repair service introduces handheld job software. The software permits only one fault code per visit. Workers often find several linked faults, but cannot alter the code or order additional parts. A supervisor can approve changes the next morning. Residents then receive extra appointments. Management proposes training workers to comply more consistently. Workers propose discretion to record linked faults, while the safety lead insists that electrical work remains restricted to qualified staff.
Use paper, your own drawing tool or the notes below. Attempt each step before opening its comparison. Describe a diagram in words when that is more accessible.
Produce: A short work-system account rather than a technology inventory.
Primary task: complete agreed safe repairs in residents' homes. Technical arrangements include fault coding, devices, records and parts ordering. Social arrangements include skills, authority, division of work, supervision and resident communication. These interact: a software field can constrain discretion, and an authority rule can turn a technically possible update into a day's delay.
Produce: A variance-control trace.
The observed condition differs from the single coded fault. The worker encounters the variation at the home, but control sits with a next-day supervisor and a rigid data structure. Trace the resulting hand-off, delay and repeat visit. Do not assume all variation should be eliminated; some reflects the actual repair need.
Produce: A paired social/technical proposal with a safety boundary.
Allow linked faults to be recorded and parts requested within defined competence and spending limits. Give suitably trained workers the authority to use that capability. Preserve qualified electrical work and a rapid escalation route for unsafe or unfamiliar conditions. A new app without authority, or autonomy without information and competence, is incomplete.
Produce: Three measures and a participative review question.
Inspect safe completed repairs, resident disruption and worker ability to resolve variation, alongside resource use. Review cases jointly with workers and residents. Faster data entry alone may coexist with more repeat visits. Ask whose work or risk has been moved elsewhere by the redesign.
These checks test the supplied case, not your overall competence. Open answers and model variants still need your judgement.
The project buys the software first and calls a final staff briefing 'participative socio-technical design'.
Involve those doing and receiving the work while task, technology, authority and boundaries are still open to change. Evaluate the combined arrangement, not attendance at the briefing.
Workers can now edit codes, but the parts store still accepts orders only from supervisors. What remains?
The technical edit has not removed the control bottleneck. Examine ordering authority, stock information and exceptions as part of the same work system. A local software improvement may simply relocate the delay.
A different model can be defensible when its purpose, assumptions and reasoning are explicit. A contradiction, incorrect unit, invented fact or unacknowledged change of purpose needs repair. Keep both your first attempt and revision.
No sign-in or submission is required. Notes are not sent by this practice tool. Use fictional information, not identifiable client or learner data. Saving stores this page's attempt only in this browser; clearing browser data can remove it. Export a copy to keep it elsewhere.
The complete original case above is free. Links below distinguish exercises from explanations, recordings, software and paid study. Reading a page or drawing in a tool is not itself a model check.
Read the primary-work-system discussion alongside the joint-design exercise. Keep technical arrangements and human work interdependent.
Public resource page and article attachment listing inspected. Historic work, not a ready-made answer key.
Further reading for each framework row, including the separate references associated with transposing theory.
Public sharing confirmed; approach and theory bibliography inspected. The presence of a reference does not establish that it contains self-check exercises.
Further study of participation and the social and technical requirements of design.
Publisher abstract and access status inspected; subscription chapter not read in full.
Ask for practice with feedback in the named approach, rather than assuming every recording includes assessment.
The page lists coverage including CONAN, INFORMED and multi-methodology. Availability and individual tutor feedback require an enquiry.
Choose another practice area · Task-only version · Worked-answer version