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

How much of this work should we let the machine do?

Your team drafts notes with it now. It pulls research, writes summaries, drafts the first pass of nearly everything. It saves real hours. Good. But someone feels a quiet worry: the work may be slipping into the machine's hands. That worry is not foolish. Name it now, before it hardens into blind trust or blind refusal. The question is not whether a machine belongs here. It is which parts of the work are yours to decide. Which parts were only ever fetching and arranging? Draw that line together, now, before it draws itself.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Some one-to-one
Practise with peers
The team already knows the facts about the tool; what's missing is the practiced habit of claiming judgment, so guidance leads.
How the two dials adapt to you →
What’s really going on

The machine can gather and arrange. It cannot judge. Give it the fetching — notes, summaries, drafts. Keep the choosing for your team: what matters, what is true, what you will stand behind. If you cannot name which parts you decided, the tool is doing your work, not helping with it.

🔒 What you’ll build togetherUnlock by starting
A moveBefore you open the tool, agree as a team: which part of this task is yours to choose, and which is just fetching.
A moveAfter the machine drafts something, have each person say what they would have written, before reading its version.
A moveStrip the machine's output from a finished piece of work. If you can't explain the judgment behind what's left, you didn't make it.
A movePut a name next to every judgment call in a document — who chose it, not who prompted it.
A moveOnce a month, list what tasks moved from your team to the machine. Ask whether you chose that, or just let it happen.
PractiseDraw the Line · a Pod of 4 · 30 min

What changes unlock by starting

  • Your team can say exactly which parts of the work are theirs.
  • Less quiet guilt about using the tool, because the line is agreed and visible.
  • Faster output without losing the habit of judgment.
  • A team that catches drift before the machine quietly runs the show.

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.