What are we looking at?
Among all the specialists, what exactly does a systems analyst do that makes things stall without them?
A role that is rarely noticed
In any system, technical, social or organisational, there are plenty of specialists: software engineers, accountants, sales managers, doctors, financial analysts and so on. But among them there is one role that gets less attention: the systems analyst. They don’t only know the components; they also understand the relations, goals and overall structure. And if they aren’t in the system, even the best specialists may fail to solve the problem.
The holistic observer
A systems analyst is like someone looking at the whole valley from the top of a mountain. They aren’t just busy with how each component performs; they pay attention to how the components work together. They ask questions others ask less often: How do these components connect? Is the path to the goal designed properly? Are the different parts of the system aligned? Depending on the situation they appear as questioner, modeller, scenario analyst, and sometimes the person who changes the structure.
Purpose, components and structure
In a systems view every system has three main elements:
| Element | Explanation |
|---|---|
| Purpose | The final destination all components work for |
| Components | The independent or semi-independent elements of the system |
| Structure | How components are organised and connected to reach the purpose |
The analyst’s job is to tune these three together and bring them into alignment. Does the structure properly support the components? Are the components really working toward the purpose, or is each going its own way? And is the system’s purpose clear and reachable?
A bridge between specialties
In complex systems, each specialist knows one part of the system well. But when the parts come into conflict or lose contact, someone has to build a common language between them. That is the systems analyst’s job: an interdisciplinary translator, a coordinator, and the person who holds the picture of the whole system in their head.
In an ERP project, for example, the finance team wants numerical accuracy, the HR team focuses on staff satisfaction, and the technology team thinks about infrastructure and security. The analyst has to put these needs together with an eye on the organisation’s overall goal and design a structure that turns conflicts into cooperation. In complex systems I think this role is vital and has no substitute.