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

I automate human work for a living. Did I build anything real?

You did not accidentally become skilled. You chose it, hour by hour, and the skill is real. What you are noticing is not that the work is wrong. It is that you never pointed it at anyone in particular. Efficiency, output, process — these are shapes without a face in them. This is not confined to you. Ask your team and you will find the same quiet in most of them: they can name what the system now does, and cannot name whom it did it to. That is worth noticing together, not privately stewing over. A career is not redeemed by feeling bad about it. It is redeemed by what you build next, and by whether you can name, specifically, who is better off. That is available to you now. Start there.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Some one-to-one
Practise with peers
The reframe (abstract skill vs. purposeful skill) needs to be taught clearly once, but the real work is a team doing the naming and choosing exercises together.
How the two dials adapt to you →
What’s really going on

You built the skill honestly. What you did with it stayed abstract. That is not a character flaw — it is an unexamined choice, and choices can be revised. Pick one person your work touches, learn what it cost or gave them, and let that judgment guide the next project you take.

🔒 What you’ll build togetherUnlock by starting
A moveWith your pod, list every process your team has automated in the last year. For each one, name the actual person on the other side of it — not 'the customer,' a specific role or face.
A movePick the automation you are least sure about. As a group, find out what happened to the people whose work it replaced. Do not guess. Ask, or research until you know.
A moveChoose your next project before it is assigned to you. State, out loud to your pod, one person or group it must visibly help, and how you will know if it did.
A moveSet a standing question for your team's project reviews: 'Who can we now look in the eye about this?' If no one answers, the project is not finished, however well it runs.
A moveIf the honest answer is that your work has harmed people and that sits heavy, say so plainly to someone you trust, and consider a conversation with a counselor — this is worth carrying with support, not alone.
PractiseName the Face · a Pod of 4 · 30 min

What changes unlock by starting

  • A written list of your team's automations, each with a named person or group affected — not an abstraction
  • One project redirected or reshaped because you could not name who it served
  • A standing habit, shared across your pod, of asking who benefits before calling work finished
  • Less quiet dread about the work, because you are now choosing its direction instead of drifting

Related problems

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.