Is it wrong to build what replaces us?

You built something that works. It does the job faster, cheaper, and it never complains. Now you watch it take the chair of someone who used to sit there. You call the feeling guilt, but guilt is for choices made badly. This is something else — you did your work well, and that is exactly the problem. You are not only afraid for your own job. You are caught between two true things: you made something useful, and you are not sure useful and good are the same word here. That gap is the real weight, and no amount of praise for the tool will close it. Your team feels this together, even if no one says it out loud. The question is not whether to feel bad. It is what you will decide, together, about the next build, the next deployment, the next person it touches.

◆ How this problem reads on the two dials

GuidanceKnowledge

More coaching

A little to learn

1:1 with AureliusWith others (a Pod)

Some one-to-one

Practise with peers

This is less a gap in what you know and more a decision you and your team are avoiding, so the page leans toward action over instruction.

How the two dials adapt to you →

What’s really going on

The tool is not good or evil. You and your team are the ones who decide who it serves and who pays for it. That is your choice to make today, not someday. Stop asking whether the work is good. Ask what you will do with the power it hands you.

🔒 What you’ll build togetherUnlock by starting

A moveWrite down, by name or role, exactly who is affected by what you are building — no abstractions like 'the workforce.'

A moveAs a team, choose one concrete change to how the tool is deployed or who it serves, and make it this week.

A moveSeparate 'we can build this' from 'we should build it this way' — agree on one thing you will refuse to build.

A moveSet up one real support for people displaced by the work — an action with a date, not a statement with good intentions.

A moveStop arguing about automation in general. Argue about the one decision sitting in front of you right now.

PractiseThe Named List · a Pod of 4 · 30 min

What changes unlock by starting

You stop treating the discomfort as noise and start treating it as information you act on.
You and your team have a specific list of who is affected, not a vague unease.
Your team makes at least one real change to the work, not just a conversation about values.
You carry the weight of the choice honestly, instead of pretending the tool made it for you.

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.