What is a system? Systems thinking starts with purpose
Use a monthly reporting example to explore a system through its purpose, components, resources, management, and environment.
When someone says, “Let’s rethink the system,” one person may think of replacing the software while another pictures the steps from intake to processing. Even when everyone uses the same word, they may mean quite different things. Ask what the system was supposed to accomplish, and their answers may diverge further.
Start by asking what the system exists to do, then look at what works toward that purpose and how. That brings into view the connections among procedures, tools, people, time, and constraints from outside. The same perspective applies to software, workflows, and organizations.
Five ways to look at a system
Here, a system is an arrangement in which components and resources work toward a purpose in an environment. We write it as S = { V, C, R, M | E }.
| Aspect | What to look at |
|---|---|
| V (Value, Purpose) | Why does it exist, and what is it meant to achieve? |
| C (Components) | How do functions, procedures, and rules work together toward the purpose? |
| R (Resource, Resources) | Which people, equipment, funding, time, and information do the components need to operate? |
| M (Management) | What activities adjust and control components and resources and coordinate with the environment to achieve the purpose? |
| E (Environment) | Which conditions and parties outside the system affect how it works? |
The vertical bar before E marks the boundary of the system under consideration. If you are studying one department’s work, another department’s deadline is an external condition. If the scope is company-wide, the process for setting that deadline becomes part of the system you can examine. The scope determines what you can change and whom you need to coordinate with.
As discussed in What is management?, achieving a purpose can mean redesigning arrangements and procedures, reallocating people and time, and negotiating with parties outside the system as needed. That adjustment is needed both when building the system and when conditions change after it goes into operation.
Example with monthly CSV reporting
Suppose you are asked to automate monthly reporting. If you define the purpose (V) as delivering a report by the next working day after the deadline, with figures that can be traced back to their sources, totals alone are insufficient. The components (C) include checks for the column names and reporting month, aggregation of the line items, and a way to record the files used. The source CSVs, column definitions, equipment that runs the process, and the people and time needed to check the figures are resources (R).
Submission formats and deadlines across departments, permissions at the storage location, and rules for handling personal information are conditions the reporting team cannot change on its own. They form the environment (E). If revised files keep arriving after the deadline, the team can change how it accepts them and reruns the report (adjusting C), assign reviewers and set aside time (adjusting R), or agree with submitters on deadlines and how to communicate replacements (coordinating with the environment). Choosing and making changes that keep the figures traceable and the report on time is management (M) in this example.
With that much in view, you can write tasks and deliverables in the WBS (Work Breakdown Structure), such as creating validation rules or agreeing on a replacement procedure with submitters. The first meeting does not have to settle everything. If the open question is who can accept a CSV after the deadline, you know whom to look for next.