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

If the model can plan the city, what's left for me to decide?

You watch the model run and the map appears, clean and confident. Your team goes quiet. Someone says, 'well, the data shows...' and no one argues. That silence is the problem, not the software. You are not losing the job to the model. You are losing your grip on what made the job matter. The weighing. The naming of tradeoffs. The taking of blame when a plan goes wrong. The model does not take blame. It cannot own a mistake in a neighborhood. Only you can. With others, the danger doubles. A team defers together faster than one person alone. It feels safer to nod at the machine than to argue with a colleague. Refuse that comfort. Decide, out loud, what you still owe each other, and the city.

◆ 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 isn't about learning new facts — it's about practicing the choosing you already know how to do, so guidance leads.
How the two dials adapt to you →
What’s really going on

The model outputs a map. It cannot decide what the city should value, who bears the cost, or what risk carries your name. That judgment is yours. Stop asking if you're obsolete. Start naming, out loud, the call only you can own.

🔒 What you’ll build togetherUnlock by starting
A moveTogether, name the last decision you let the model make by default. Ask if it should have.
A moveIn the room, say aloud what the model cannot see — who gets displaced, whose voice isn't in the data.
A moveAssign one person, each week, to sign their name to a judgment call. Not the model's output — the choice.
A moveBefore you ask what the model says, ask what you owe this decision.
A movePractice explaining a hard call to the person it hurts most, without pointing at the software.
PractiseName the Blind Spot · a Pod of 4 · 30 min

What changes unlock by starting

  • Your team can say, precisely, which calls are yours and which belong to the model.
  • You stop nodding along and start choosing on purpose, together.
  • Meetings shift from praising the output to naming what it left out.
  • Each of you can name, plainly, what you're accountable for that no model is.
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.