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.
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 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.