People and Technology Together: Sociotechnical Systems Theory

UPI Study › Courses › Software Engineering › Free lessons › Lesson 15.6 Free with a free account

People and Technology Together: Sociotechnical Systems Theory

Software Engineering · Chapter 15: Distributed Systems, Services, and Sociotechnical TopicsSection 15.6 · lesson 100 of 1035 min · free with a free account

← Engineering Services: From Definition to DeliveryNext lesson: Conceptual Models: What They Are and How to Use Them →

Earn 3 college credits for Software EngineeringRecommended for credit by NCCRS · Computer Science 301 · self-paced · one payment, lifetime access
Enroll in Software Engineering · $250 →Download the syllabus (PDF)

In this lesson

Sociotechnical systems theory: why correct software can still fail.

  • Explain why a software system is more than its code
  • Name the 3 interacting elements of a sociotechnical system
  • Explain why a technically correct system can still fail
  • Describe what sociotechnical thinking changes about engineering

Transcript

Everything said in the video, section by section (696 words). Read along, or search it.

Distributed Systems, Services, and Sociotechnical Topics

People and Technology Together

A piece of software can be built exactly to specification, and still fail completely once real people are asked to use it. This section covers sociotechnical systems theory, which explains why.

More Than Code

Software Never Runs Alone

It is tempting to think of a software system as just the code. Something that either works correctly or does not, judged purely on technical grounds. In practice, no software system operates in isolation. It is used by people, and embedded in an organization's existing processes. Its real success depends on all of that context. A sociotechnical system is the name for this whole picture. The technology, together with the people who use it, and the processes it operates within. It is understood as a single interacting system, rather than a piece of software with users attached afterward.

Figure 1

Where the 3 Overlap

Sociotechnical systems theory names three elements. People, process, and technology. Picture them as three overlapping circles. The sociotechnical system is not any one of the circles on its own. It exists where all three overlap.

Table 1

The 3 Interacting Elements

People are the individuals who use, maintain, and are affected by the system, along with their skills and expectations. Process covers the organizational workflows, rules, and habits the system is meant to operate within. And technology is the software and hardware itself, the part most engineering effort is traditionally spent on. The overlap is the point. A change to the technology changes what is possible for people and process. And a change in how people actually work, can make a perfectly good piece of technology unworkable in practice.

Correct, but Unused

A Hospital's New Records System

Consider a hospital adopting a new digital records system. It is built precisely to its stated requirements, and it passes every test. But during a busy shift, it turns out slower, and more awkward to use, than the paper process it was meant to replace. Nurses do not simply tolerate the inconvenience. They route around it. Nothing about the code changed. What changed was whether the system fit the people and process it was dropped into.

Think About It

Which Kind of Problem Is It?

Think about this. The records system is technically correct. So is its failure a technology problem, a people problem, or a process problem? It is not really any one of the three in isolation. The technology did not account for how the existing process, and the people working within it, would respond. That is exactly the kind of failure sociotechnical thinking is meant to catch, before it happens.

Engineering Practice

What Changes

Treating a system as sociotechnical changes what counts as part of the engineering work itself. Requirements gathering has to consider how people actually work, not only what the system is functionally supposed to do. Success is measured by whether the system is genuinely adopted and used as intended, not solely by whether its code passes its tests. And a failure after release can often be traced to a mismatch with people or process, even when every technical requirement was met exactly.

Apply It

Back to the Spreadsheet

Let's apply that. A team ships a project-tracking tool that passes every functional test. But employees keep updating a shared spreadsheet instead, because the tool does not match how their team actually reviews work each week. What kind of failure is this? A sociotechnical one. The technology may be functionally correct, but it does not fit the existing process. So people route around it, just as the nurses did.

Key Terms

The Vocabulary of This Section

Let's lock in the key terms. A sociotechnical system is the technology, the people who use it, and the process it operates within, understood as a single interacting system. People, as an element, are those who use, maintain, and are affected by a system, along with their skills and expectations. Process is the organizational workflows, rules, and habits a system is meant to operate within. And technology is the software and hardware itself.

Key Takeaways

What to Carry Forward

To pull this together. A system is its technology, the people who use it, and the process it operates within, all together. The sociotechnical system exists in the overlap between those three, not in any one of them alone. A technically correct system can still fail, if it does not fit its people and process. So requirements gathering has to reflect how people actually work. And success is measured by genuine adoption, not only by passing tests.

About Software Engineering at UPI Study

Software Engineering (Computer Science 301) is a self-paced online course of 103 video lessons in 15 chapters, from process models and agile to requirements, design, user interfaces, reliability, security and project management. It carries a NCCRS credit recommendation for 3 semester credits.

Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Enroll now → Course details Download the syllabus All Computer Science courses Every course with PRO →

Compare: Software Engineering vs Systems Analysis

Why take it here

Why students take Software Engineering with UPI Study

How professional software gets builtSoftware Engineering covers how teams turn requirements into working, maintainable software: process models, agile, requirements, design, testing, reliability and project management. It is a core course in computer science and software degrees.
Credit at a fraction of the priceThe same 3 credits can cost $750 or more at a US college. Here it is one payment, self-paced, with lifetime access.
Finish your degree soonerTransfer credits reduce the courses you still owe, so you can graduate earlier or lighten a heavy semester.
Strengthen an applicationA completed college-level course on an official transcript shows admissions and scholarship committees you can do the work.
Study on your own scheduleNo start dates, no deadlines. Watch the lessons, practice, and take the final when you are ready.
130,000+students helped with college creditsACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Where the credit goes

Universities that work with NCCRS

Software Engineering carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Thomas Edison State UniversityThomas Edison State UniversitySigned partnerUniversity of the PeopleUniversity of the PeopleSigned partnerCharter Oak State CollegeCharter Oak State CollegeSigned partnerStrayer UniversityStrayer UniversitySigned partnerColumbia Southern UniversityColumbia Southern UniversitySigned partnerIndiana TechIndiana TechSigned partnerPenn StatePenn StateWorks with NCCRSSouthern New Hampshire UniversitySouthern New Hampshire UniversityWorks with NCCRSSUNYSUNYWorks with NCCRS +many more cooperating universitiesFind my college →

Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.

FAQ

Questions students ask us

About People and Technology Together: Sociotechnical Systems Theory

What is a sociotechnical system?
A sociotechnical system is the technology together with the people who use it and the processes it operates within, understood as one interacting system. It treats software not as code with users attached afterward but as part of a larger whole. In this view, a system's real success depends on how well all three elements fit together.
What are the three elements of a sociotechnical system?
The three elements are people, process, and technology. People are those who use, maintain, and are affected by the system, with their skills and expectations. Process covers the organization's workflows, rules, and habits. Technology is the software and hardware itself. The sociotechnical system exists where the three overlap, so a change in one affects the others.
Why can a technically correct software system still fail?
A technically correct system can fail when it does not fit the people and processes it is dropped into. A hospital records system can meet every requirement and pass every test yet prove slower than paper during busy shifts, so nurses route around it. The failure is not purely technical, human, or procedural; it is a mismatch among all three.
How does sociotechnical thinking change software requirements and success?
Sociotechnical thinking expands requirements gathering to include how people actually work, not only what the system must functionally do. Success is then measured by whether the system is genuinely adopted and used as intended, not solely by passing tests. For example, a project-tracking tool that employees bypass for a shared spreadsheet has failed despite meeting its functional requirements.

About the Software Engineering course

How many college credits is Software Engineering?
Software Engineering (Computer Science 301) carries a NCCRS credit recommendation for 3 semester credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
How much does Software Engineering cost and what is included?
$250, paid once, with lifetime access: all 103 video lessons, a practice quiz after each, the graded work and final exam, and an official transcript when you finish. Students who want several courses choose UPI Study PRO instead.
Which universities accept UPI Study credits?
UPI Study has signed partner agreements with universities such as Thomas Edison State University, University of the People and Charter Oak State College, and works with universities such as Penn State, SNHU and SUNY. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities. Use "Find my college" on this page to check yours.
How long does Software Engineering take?
It is self-paced with no deadlines. The 103 lessons total about 11 hours of video; most students add reading and practice time and finish in a few weeks to a few months, on their own schedule.
How are the exams done?
Quizzes and assignments are online in the course. The final exam is taken online with proctoring; a person on the UPI Study team checks assignments, usually within two days.
How do my credits reach my college?
When the course shows 100% complete, request the official transcript from your dashboard. It is sent to the college you name, and you can send it to more than one. Check your college first with "Find my college" on this page, or ask Athena.

Ready for the full course? Earn 3 credits in Software Engineering.

103 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.

Enroll in Software Engineering →Download the syllabusEvery course with PRO →
Software Engineering
3 credits · NCCRSEnroll →