Field Notes · Topic
Sociotechnical Systems
The interplay between social and technical subsystems — structuration theory, work systems, joint optimization, and adaptive design.
- AI & Agentic SystemsHuman-AI Collaboration Needs Two Parties Who Know Different ThingsA model and a person who know the same things make a weak team. In the evidence, the gains come from what one side knows and the other does not, and that is an information system design question.
- IS TheoryPeople Use Tools Inside Activity Systems, Not in a VacuumActivity theory says you cannot understand tool use without the full activity system around it. The same tool in two systems means two completely different things.
- IS TheoryActor-Network Theory: Why Your ERP System Is an Actor TooANT treats software, databases, and infrastructure as actants with the same analytical standing as humans. In IS research, that changes everything about how we study implementation.
- AI & Agentic SystemsWhen AI Acts Like a Colleague: Structuration in the Agent EraMultiagent AI systems are not just tools being used. They act, and their outputs become part of the organizational structure that shapes the next cycle.
- AI & Agentic SystemsAI's Energy Problem Is a Sociotechnical Systems ProblemTraining AI models consumes staggering amounts of energy. Trist and Bamforth showed in 1951 why optimizing only the technical subsystem creates a collapse.
- AI & Agentic SystemsAI Implementation Failures Are Often SociotechnicalBostrom and Heinen said in 1977 that MIS failures are sociotechnical. Half a century later, AI implementation fails the same way.
- AI & Agentic SystemsAI as a Participant in the Work System, Not Only a ToolAlter's work system framework already has a slot for AI. It is not the technology element. It is the participant element.
- AI & Agentic SystemsAI Through the Lens of Task-Technology FitGoodhue and Thompson said performance follows fit, not features. AI is a family of tools, and the wrong one for the task will fail the same way every time.
- Comps & ReflectionsWhy the Spreadsheet Everyone Complains About SurvivesStar and Griesemer's boundary objects are plastic enough to serve local needs but robust enough to hold shared identity. That is why the spreadsheet survives.
- Platforms & EcosystemsCognitive Load and Why Enterprise Software Exhausts PeopleWhen enterprise software exhausts its users, that is not a training problem. It is a design problem with a cognitive load explanation.
- Comps & ReflectionsMy Study Partner Said I Was Wrong About Structuration TheoryI confused structuration theory's three modalities with institutional theory's three pillars for months. A study partner caught it, and getting corrected was the best thing that happened to my comps prep.
- Comps & ReflectionsThe Theory Map That Keeps GrowingOne page of sticky notes became a wall of connected IS theories. RBV, dynamic capabilities, structuration, affordances, institutional theory: the connections between them matter as much as the theories themselves.
- Comps & Reflections56% of IS Papers Do Not Theorize TechnologyReading Sarker et al. (2019) for the third time during comps prep, the 56% stat finally hit me: more than half of IS papers do not theorize technology at all.
- IT Governance & StrategyConway's Law and Why Your Software Architecture Looks Like Your Org ChartMelvin Conway observed in 1967 that organizations produce systems that mirror their communication structures. Once you see it, you cannot unsee it.
- Sociotechnical SystemsDigital Twins: The Sociotechnical Artifact Few Teams Prepare ForA digital twin sounds simple: a virtual replica of a physical thing. In practice, building one that actually works requires better data infrastructure than most organizations have.
- Platforms & EcosystemsDistributed Team Coordination in IS ProjectsDistributed IS projects face coordination overhead that project plans rarely account for. COVID made this everyone's problem at once.
- AI & Agentic SystemsEdge AI Moves Computation Into the Physical World. STS Says That Changes Everything.When AI runs on a factory sensor or hospital monitor instead of the cloud, the technical subsystem becomes physically distributed and harder to monitor. STS theory warned us seventy years ago what happens next.
- Organizational TheoryWhy CIOs Get Fired After ERP ImplementationWhen ERP implementations fail, the postmortem always says the software was fine and the change management was missing. That phrase hides what actually happened: the organization lacked the political will to standardize processes.
- IT Governance & StrategyWhy ERP Implementations Keep FailingAfter decades of high-profile disasters, large organizations still repeat the same ERP mistakes. The problem is rarely the software.
- IS TheoryInformation Processing Theory: Organizations Are Processors, Not MachinesGalbraith (1974) said organizations design themselves to handle the information their tasks demand. IS exists to close the gap between what a task requires and what people can process alone.
- IS TheoryMove Fast and Break Things Is the Longwall Method for SoftwareTrist and Bamforth showed in 1951 that optimizing only the technical subsystem destroys the social one. Silicon Valley rediscovered this lesson and called it a strategy.
- AI & Agentic SystemsRLHF Is Structuration Theory: We Train AI, Then AI Trains UsRLHF mirrors Giddens' duality of structure, creating a recursive loop where human preferences shape AI outputs and reshape human preferences.
- AI & Agentic SystemsShadow AI Is Shadow IT All Over Again, Just FasterFollowing Ferneley and Sobreperez, three workaround types explain why employees bypass official AI tools. Shadow AI is task-technology fit failure, not compliance failure.
- IS TheoryJoint Optimization Is Not a Feel-Good SloganThe origin story of sociotechnical systems theory is not a feel-good tale about teamwork. It is a cautionary tale about what happens when you optimize only the machines.
- IS TheoryGiddens in IS: Why the Same System Produces Different OrganizationsGiddens built structuration theory around structure and agency being mutually constitutive. Orlikowski pointed it at technology, and IS has never been the same since.
- IS TheorySame Tool, Different Department, Total DisasterWhy the same ERP or Slack deployment thrives in one department and collapses in another, explained through structuration theory, Orlikowski's duality of technology, and adaptive structuration.
- Comps & ReflectionsThe Tool Is Not Broken. It's Just Wrong for Your Job.Goodhue and Thompson showed that performance depends on fit between task and technology, not on whether the tool is good in the abstract.
- IS TheoryWhat TikTok Understands About User Behavior That Your Enterprise App Does NotVenkatesh added hedonic motivation, habit, and price value to UTAUT for consumer contexts. Enterprise software still runs on the utilitarian-only version. That gap is why TikTok and Slack win while expense reporting tools get memed.
- AI & Agentic SystemsVibe Coding Is Sociotechnical Systems Theory Testing Its LimitsAI-native platforms let anyone generate code from a prompt. Trist and Bamforth showed in 1951 why optimizing only the technical subsystem creates a maintenance crisis.
- Comps & ReflectionsWhen Employees Break the System, That's a Requirements DocumentFerneley and Sobreperez argued workarounds are not user failure but evidence of system-task misfit. The workaround is the real requirements document.
No notes found. Try another word or topic.