Empowerment is the point of the other three. When communication is clear, collaboration is fluent and results are measured, the model stops being a novelty and starts removing the work that never needed a human — leaving the judgement, the taste and the accountability where they belong.
Where the leverage is
- Drafting. First versions of documents, code, tests and plans are cheap to generate and easy to judge.
- Understanding. Summarising a long thread, explaining unfamiliar code, translating jargon for another audience.
- Doing. With tools, a model can search, query, run and file — not just answer. See Agents & Tool Use.
- Access. People without the specialist skill — SQL, regex, legalese — can now ask for the outcome in plain language.
Keeping the human in charge
- Own the decision. The model proposes; a person accountable for the outcome disposes.
- Verify what matters. Facts, numbers, citations and anything irreversible get checked before use.
- Gate the irreversible. Payments, deletions and production changes need explicit approval, not autonomy.
- Grow the skill. Save the prompts that work; a good prompt library compounds across a team.
Example
Vague
Can you do my weekly report?
Better
Every Monday I write a status report from three sources. SOURCES: this week's merged PRs, the incident log, the support queue export. TASK: draft the report as: 1) shipped, 2) incidents and resolution, 3) top 3 customer issues. Rules: only facts present in the sources; mark anything ambiguous as NEEDS REVIEW. I will review and send it — do not draft an email to anyone.