A system in which social (human actors, organisations, norms, incentives) and technical (machines, tools, procedures, infrastructures) components are interdependent such that the system’s behaviour, performance and risks emerge from their interactions rather than from either domain alone.

Principle

Because behaviour and outcomes arise from interactions between social and technical elements, interventions that modify only one side (for example, deploying a new technology without changing workflows or incentives) will often produce unintended consequences or fail to achieve intended performance.

Demonstration

Illustrative scenario — Situation: An organization installs an automated scheduling tool to optimise nurse rostering. Recognition: Despite technically improved schedules, staff bypass the tool because it ignores informal workload tradeoffs and local practices. Action: Redesign includes participatory workflow changes, training and incentive alignment. Consequence: Tool adoption increases and overall performance improves because social practices and technical features were co‑designed.

Misapplication

Treating the system as purely technical (assuming that a technical fix alone will change behaviour) or purely social (ignoring constraints and affordances provided by technology). The error is isolating one domain and failing to analyse interaction effects that determine real outcomes.

Consequence

Policy or design measures that neglect sociotechnical interactions can cause reduced effectiveness, user workarounds, safety hazards, or perverse incentives; conversely, integrated interventions can produce synergistic improvements but may require more complex coordination and governance.

Reversal

In very small, tightly controlled technical artefacts with negligible human interaction (e.g., a sealed microelectromechanical device), the social component may be minimal for the device’s in‑service behaviour, but sociotechnical considerations reappear at deployment, maintenance and organizational adoption scales.

Boundary

Clearly within: an air traffic control system including controllers, procedures, radars, and software. Boundary case: a single tool used by isolated individuals — it may constitute a sociotechnical system only when embedded in organizational processes. Clearly outside: a purely mechanical passive device with no human interaction in its life cycle.

Semantic Tension

Trade‑off between standardization (uniform technical procedures for reliability) and local autonomy (allowing human judgment and adaptation): tighter standardization can increase predictability but reduce adaptability to local contexts.

Synthesis

Understanding and improving sociotechnical systems requires iterative co‑design, methods that model both human and technical elements (workflows, affordances, feedbacks), and governance that aligns incentives, accountability and technical constraints — interventions succeed when they treat the social and technical as mutually constitutive.