ronutz

The Roles · Who runs it

Systems analyst

Written from published sources

The role that faces two directions at once. The prefix names the subject — network analyst, security analyst, data analyst — and the word analyst names the stance: studying what an organisation currently runs and what it currently needs, and describing each to the other. The framework puts it plainly as bringing business and technology together by understanding the needs and limitations of both.

What the day looks like

  • Studying the systems and procedures as they actually operate, which differs from how they were designed and from how they are described.
  • Gathering requirements from people whose expertise is their own work rather than technology.
  • Translating those requirements into something an engineer can build, and translating the constraints back into something a business can decide with.
  • Measuring: usage, capacity, incidents, cost, and whatever else turns an opinion about the estate into a number.
  • Documenting the current state, which is frequently the only accurate record the organisation holds.

What it answers for

  • The description of the current state being true.
  • Requirements that survive contact with the people who have to build against them.
  • Analysis that leads to a decision rather than to a further meeting.

What it is measured on

  • Recommendations adopted, and the outcomes they produced.
  • Reporting delivered on the cadence the organisation runs on.
  • Requirements accepted without rework by the teams who implement them.

Who it receives from

The business
What they need, expressed in the vocabulary of their own work.
Engineering and operations
What the estate can do, and at what cost.
Monitoring and inventory
The measurements, at whatever quality the organisation maintains them.

Who it serves

Decision makers
A picture of the current state accurate enough to act on.
Engineers
Requirements with the reasoning attached, so a trade-off can be made rather than guessed.
The organisation's memory
Written knowledge of how the estate reached its present shape.

Who else has a stake

  • Every team whose work the recommendation changes.
  • Finance, since analysis frequently arrives attached to a budget request.
  • Audit and compliance, for whom the documented current state is evidence.

What it takes

  • Fluency in two vocabularies, and the patience to move between them all day.
  • Enough technical depth to be corrected by an engineer and to notice when the correction is wrong.
  • Writing, since the analysis outlives the meeting that produced it.
  • Comfort delivering a finding that somebody in the room would prefer stayed unmeasured.

What the job turns on

The analyst holds the only complete picture in the room, and holds it without authority to act on it. That combination is the role: the business knows what it wants, engineering knows what is possible, and the person who knows both is the one who has to make each legible to the other. Influence comes from the description being trusted, which is why accuracy about the current state matters more here than elegance about the future one.

The published sources

Where it leads

Roles that lead here

The work itself

The Practice covers how this work is done — triage, escalation, evidence, handover — across the whole corpus.

Read The Practice