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

If the machine decides, who is still responsible?

You did not lose your conscience when the software took the trigger. You moved it upstream, into a design meeting, a sign-off, a policy you barely read before approving. That is still a choice. A quieter one, made by more hands, which is exactly why it is easier to pretend no one made it. Your team will be tempted to talk about the system as if it acts alone — 'the model flagged it,' 'the algorithm chose the target.' Watch that language. It is how a group spreads out a decision until no single person feels its full weight. The weight does not vanish. It just gets harder to find. You are not confused about technology. You are avoiding a plainer question: when the hard call is made by code you built, who answers for it? Not the machine — it answers to no one. You do. So does everyone on your team who touched the decision and said nothing.

◆ 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
The core work is confronting evasion of personal responsibility, not learning new facts, so guidance dominates.
How the two dials adapt to you →
What’s really going on

The machine did not remove your judgment. It removed your excuse for not using it. You wrote the rules it follows, you approved the system, you chose to look away or keep watching. The choosing is still yours — only earlier, and easier to hide from. Stop asking what it decided. Ask what you decided.

🔒 What you’ll build togetherUnlock by starting
A moveName, out loud in your team, every point where a human could have stopped the system and did not — write these down as a list, not a feeling.
A moveFor each rule the system follows, find the person who approved it. If you cannot find that person, treat that as the actual finding of your review, not a gap to smooth over.
A moveBefore your next deployment, have each person on the pod say in one sentence what they personally are answerable for. If someone says 'the system decides that part,' push back — ask who signed off on giving it that.
A movePractice separating two questions your team keeps merging: 'was the outcome acceptable?' and 'did a person here exercise judgment?' A good outcome with no judgment exercised is still a warning sign.
A moveAssign one person, by name, to own the consequences of the system's next serious mistake — before it happens, not after.
PractiseTrace the Decision · a Pod of 4 · 30 min

What changes unlock by starting

  • Your team stops using 'the algorithm decided' as a way to end a conversation, and starts using it to open one.
  • You can point to a specific person accountable for each major decision the system carries out, not just the system itself.
  • You catch at least one point in your current process where responsibility was quietly assumed to belong to no one.
  • You and your pod can state, plainly, what judgment you are still exercising and what you have handed away.

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.