Talk it through with Aurelius
Library›Aurelius›The problem
Aurelius · Work & Leadership
Knowledge + Guidance

I can operate an HMI. Why can't I build one?

You have spent years in front of a screen someone else built. You trust the buttons because you know what happens when you press them. That is real knowledge. But it is the knowledge of a passenger, not a driver — and no one handed you the keys. Building the interface and the SCADA system behind it (software that gathers data from machines and lets you control them from one place) asks for something different. You must decide what the operator sees, where the data comes from, and what happens when something fails. That is not a bigger version of your old skill. It is a new one, and it is learned in pieces, not all at once. You did not choose to arrive untrained. But you do choose, today, whether to treat this as one impossible mountain or as one small piece your team can finish this week.

◆ How this problem reads on the two dials
GuidanceKnowledge
Coaching
More to learn
1:1 with AureliusWith others (a Pod)
Some one-to-one
Practise with peers
The gap includes real technical knowledge — architecture, tags, design logic — but the paralysis is solved by a team dividing the work into named, ownable parts.
How the two dials adapt to you →
What’s really going on

Operating a system and building one are different skills, and no one taught you the second. That is not failure — it is an untaught gap. Choose one small piece: one screen, one device, one alarm. Build that with your team before you touch the whole system.

🔒 What you’ll build togetherUnlock by starting
A movePick one physical device — one pump, one tank, one line — and build its screen first, nothing else.
A moveSplit the system into four named parts: tags, graphics, alarms, logic. Assign one owner to each.
A moveBefore drawing anything, write the answer to: what should the operator see at 3am when this fails?
A movePair whoever knows the process best with whoever knows the software best. Neither works alone.
A moveShow your unfinished screen to the team this week, not when it feels finished.
PractiseOne Screen, Four Owners · a Pod of 4 · 30 min

What changes unlock by starting

  • A single working screen your team actually built, not just planned.
  • A clear answer to which part of the system you personally own.
  • The project stops being one huge task and becomes four manageable ones.
  • Your team has a shared map of the whole system, even while unfinished.
One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.