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

Drones now decide things mid-flight — how do we adapt as a team?

Your drone flags a target, adjusts a flight path, aborts a run — faster than you can think it through. You call this a threat to your judgment. But no machine has taken your judgment. It has taken one decision, and only because someone, somewhere, agreed to give it that decision. Here is what you are actually afraid of: the line between what the machine decides and what you decide was never drawn clearly. So it feels like the line is moving on its own. Your pod feels this differently but together — one operator argues against every new function, another goes quiet and lets the machine run. Both are the same fear, wearing different clothes. Draw the line. Not as a feeling, not as a policy memo from someone else — as a list, with actual decisions named on it, that your whole pod reads before the next mission. What you don't name today, the fear will decide tomorrow.

◆ 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 operators already know their aircraft; what they lack is a shared, concrete boundary, which is a coaching problem, not an information gap.
How the two dials adapt to you →
What’s really going on

The drone's autonomy hasn't replaced your judgment. It has taken over one narrow decision — and only the ones your pod agreed to hand over. Stop arguing about the technology. Sit down together and name, in writing, which calls are still yours. What remains unnamed, the fear decides for you.

🔒 What you’ll build togetherUnlock by starting
A moveThis week, with your pod, make a two-column list on paper. Left column: 'decisions the autonomy makes faster than us.' Right column: 'decisions only a human signs off on.' Name actual calls — target confirmation, flight path change, abort — not categories like 'safety' or 'ethics.'
A moveAfter your next mission, sit with the pod for ten minutes and ask one question: which call did the autonomy make that one of you would have made differently? Say the specific moment out loud. Don't let it pass as a general feeling.
A moveAssign one person per week to be the override — the one watching the machine's decisions with authority to flag or reverse one. Rotate the role so everyone learns the boundary from inside it, not just in argument.
A moveBefore you argue against a new autonomous function in a meeting, write the fear in one sentence first — 'I'm afraid this means I stop being trusted to call the abort.' Separate the fear from the argument you make out loud. Bring both, but know which is which.
A moveOnce the list exists, post it where the pod briefs before missions. Update it after every disagreement. A boundary nobody can see is not a boundary — it's a guess everyone is making alone.
PractiseDraw the Line · a Pod of 4 · 30 min

What changes unlock by starting

  • Your pod has a written, shared line between machine calls and human calls — not just an unspoken feeling everyone guesses at differently.
  • Arguments shift from 'should we trust the autonomy' in general to specific, answerable questions about specific decisions.
  • Fewer frozen moments in the field, because the hard call was already made in the briefing room, not mid-flight.
  • Trust inside the pod grows, because the boundary is named on paper, not assumed and then quietly resented.
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.