Framework 201           Sociotechnical System Design: digitally infused work systems and the Platform-STS

Introduction

The digital era has produced a new class of sociotechnical systems (the Platform-STS (P-STS) that requires updating classical sociotechnical systems design (STSD) principles and practices so design and change work operates at ecosystem scale.

Key points:

1. A new class: Platform-STS.
   There are 3 STS “families”:
   1. Industrial-STS (hierarchical, task-focused),
   2. Knowledge-STS (professional, clan/skill based)
   3. The emergent Platform-STS — platforms that mediate, coordinate and extract value across distributed actors and ecosystems (eg, gig platforms, marketplaces, data platforms).

P-STS differs in reach (ecosystem vs single org), governance (market-based mechanisms) and dynamics (real-time data, algorithmic control).

2. Design tensions and limits of old STS principles.
   Traditional STSD assumed bounded workplaces and human-centred participative design inside an organisation. Digital platforms collapse boundaries, introduce powerful automated linkages and new forms of control. So joint optimisation of social and technical elements needs reframing to include inter-organisational and market actors.
3. Proposed new design principle — “redundancy of connectivity” (and DP3).
   To cope with ‘distributedness’ and fragility, it is proposed that a new design principle (sometimes called a third design principle be considered.

It creates multiple, overlapping connectivity channels and alternative pathways so actors/activities are not single-point-dependent on one platform, algorithm or partner.

Redundancy supports resilience, choice and bargaining power within ecosystems.

4. Governance, power and incentives matter.
   Platforms are governed by algorithms, pricing, reputation systems and APIs.

Design therefore must include governance mechanisms (rules, data access, incentives, dispute resolution) as explicit sociotechnical artefacts, not just technical features. This raises fairness, privacy and asymmetry issues.

5. Implications for skills, identity and work design.
   Work mediated by platforms changes roles, autonomy, evaluative metrics and learning pathways. STSD for P-STS must plan for reskilling, transparent metrics and human oversight of algorithmic decisions.

Application to Change Management

Some concise, actionable ways change managers should adapt STS thinking when managing transformations in digitally infused/platform contexts:

1) Re-scope the change: move from org-centric to ecosystem-centric mapping

• Map the platform ecosystem: platform owner(s), third-party developers, users (customers/workers), data providers, regulators, and complementary services.
• Treat external stakeholders as core change sponsors/participants; their incentives shape outcomes.

2) Include platform governance design in the change plan

• Define who controls data, algorithms, API access, pricing rules and dispute processes.
• Build governance artifacts (policies, SLAs, access rules) into the roadmap — these are as much “change” as org-structure or training.

3) Build redundancy of connectivity into resilience and contingency planning

• Avoid single-point dependencies on a single platform or data feed. Create alternative integrations, multiple vendors, offline/manual fallbacks and cross-platform bargaining options.
• Use redundancy not just for tech (APIs, backups) but for social connections (multiple channels to reach customers, alternative partners).

4) Design change around data flows and algorithmic decisions

• Map how data moves across actors, where algorithmic decisions are applied, and how those affect people’s work and incentives.
• Include explainability and human override points in the design (who reviews automated decisions; escalation paths).

5) Rework roles, metrics and learning pathways

• Redefine jobs to reflect platform-mediated tasks and new metrics (e.g., reputation scores, throughput).
• Implement training for platform literacy (APIs, dashboards, algorithmic logic) and support identity shifts for workers/teams.

6) Engage multiple stakeholders early and continuously (co-design at ecosystem level)

• Use cross-partner workshops, data-sharing pilots and joint governance forums to co-design rules and interfaces. Participation reduces downstream resistance and aligns incentives.

7) Anticipate and manage power asymmetries and ethics risks

• Conduct an impact assessment for distributional effects (who gains/losses from platform changes).
• Include mitigation (compensation, transitional supports, policy changes) as part of the change package.

8) Measure success differently — ecosystem KPIs + resilience metrics

• Move beyond internal KPIs to include ecosystem health indicators (participant diversity, alternative connections, latency of data flows, dispute rates). Measure redundancy and the ability to reconfigure when partners change.

Quick checklist for a change manager (7-step)

1. Stakeholder ecosystem maps complete (including platform actors).
2. Governance artifacts (data, algorithm, SLA) drafted and agreed.
3. Redundancy plan (tech & social) created and tested.
4. Algorithmic decision points identified with human override assigned.
5. Role redesign and training plan prepared.
6. Cross-partner co-design sessions scheduled.
7. Ecosystem KPIs and resilience indicators defined.

Summary

(source: Oğuz N. Babüroğlu, et al 2020)

(Source: Oğuz N. Babüroğlu, et al 2020)

The proposed extension of classical STSD to introduce the Platform-STS and the design emphasis on redundancy of connectivity. There is a debate about proposals that extend or add STS design principles; some scholars critique the notion of a distinct “third principle”. However, there are some useful heuristics for change managers working with platforms and distributed digital ecosystems.

(Main sources: Oğuz N. Babüroğlu, et al 2020; Oğuz N . Babüroğlu, 2022)