Outcome
Name the north star before asking an agent to move. What result would make the work useful?
Field guide for agentic leadership
A practical field guide for people learning how to manage agentic workers: outcomes, boundaries, evidence, cadence, attention, escalation, and human judgement.
The shift
When people use AI well, they are not only producing output. They are setting intent, shaping tasks, judging quality, checking evidence, protecting attention, and staying responsible for what goes out into the world.
That is management. Not management as hierarchy, but management as a human literacy: knowing what good looks like and keeping yourself in the loop.
Field guide
Use these as a practical check before giving an agentic worker more autonomy, more context, or more trust.
Name the north star before asking an agent to move. What result would make the work useful?
Say what the agentic is doing, what the human owns, and who is accountable for the final decision.
Define what it can read, change, publish, spend, remember, or escalate before autonomy gets wider.
Ask what changed, which sources matter, what is uncertain, and what would make you reject the answer.
Create a rhythm for review, exceptions, drift, lessons, and decisions that need human judgement.
Protect the scarce thing. Decide where attention belongs instead of letting tools and feeds spend it for you.
Pause when stakes rise, signals conflict, the pattern is novel, or the decision is not yours to make.
Attention and agency
If all a person does is click the button and accept what comes back, they are not in the loop. The value is in the judgement: what they asked, what they rejected, what evidence changed their mind, and where they chose to put attention.
First steps
This is not about banning AI or pretending it is magic. It is about showing people how to use it well enough that their own thinking becomes more visible.
Write three signs of a good answer before the agent produces one.
Give context, audience, constraints, source expectations, and a clear stopping point.
Mark down work that could have come from anyone. Add judgement, taste, evidence, and yourself.
Keep a small trail: what you asked, what you accepted, what you rejected, and why.
Batch interruptions, review exceptions, and ask whether this signal deserves time.
Curated starter resources
This is a starter directory, not a giant database. The point is to help educators, leaders, parents, students, and operators find credible first routes into AI literacy and management literacy.
School and college staff
Open resource GlobalCurriculum designers and educators
Open resource GlobalEducation leaders
Open resource OECDPolicy and assessment teams
Open resource EuropeOrganisations using AI systems
Open resource GlobalLeaders working with technology, facts, values, and ethics
Open resource UK and global partnersTeachers and young people
Open resource US and globalGrades 6 to 12 educators
Open resource US-origin, globally usefulK-12 standards and curriculum teams
Open resource MultilingualAdults and general learners
Open resourceFollow-on essay
The canonical essay lives on Tonywood.org and makes the deeper argument: we should teach people how to manage themselves, tools, tasks, attention, risk, evidence, and outcomes.
Tony's writing
The follow-on essay: why AI makes management a general literacy, not a specialist title.
Tonywood.orgThe classroom argument for teaching attention, delegation, judgement, and interruption management.
Tonywood.orgHow students can look for human debt, learn what good looks like, and use AI without outsourcing judgement.
Tonywood.orgA practical note on roles, boundaries, success tests, escalation routes, and evidence trails.