Leading in the AI Era
This course helps you decide where AI is worth trying in your organization, what evidence and baseline to require before funding a build, how to clear the bottlenecks that stall useful work, and how to support the people doing it.
About 3 hours · 6 modules · 17 short lessons · No technical background or coding tool required · Free, no sign-up
For executives, directors, program managers, mission owners and academic leaders. Every lesson ends with a decision you can make, an action you can take this week, and a measure you can check. Stopping a pilot that misses its bar counts as a good outcome here; Lesson 5.1 shows that decision.
Only have five minutes? Read one of the one-page leadership briefs: Cloud Modernization Patterns, AI Assurance, or Guarded Automation. Each says what one technical training decides and why.
The modules, by the decision each one produces
Take them in order the first time. Each lesson stands on its own afterwards, so a module can be reread before the decision it serves.
Already running a pilot? Lesson 5.1 is the decision and Lesson 6.1 the plan to write it on.
What these systems can and cannot do for your organization
Decide which kinds of work in your organization are worth a look, and name the three limits before anyone proposes a use.
What changed when software stopped following rules and started carrying out work under direction, where that lands in research, operations, modernization and institutional knowledge, and the three limits a leader must be able to name
Rethinking time, cost and capability
Decide which problem deserves a pilot, and what evidence and baseline you will require before you fund a build.
Pick a problem worth a pilot and check the non-AI fix first, keep the prior estimate for comparison with completed work rather than discard it, ask for a working demonstration before funding a build, and judge what a small team with domain knowledge can and cannot deliver
Recognizing organizational barriers
Decide which queue or decision you own, whether waiting or moving now costs more, and what would settle an open concern.
Where the gains go when queues have no owner, how to weigh the cost of delay against the cost of moving without evidence, and how to resolve a concern with the evidence that would settle it
Leading capable people
Decide what you will set (outcome, boundary, checkpoints) and what you will leave to the team.
Set outcomes and boundaries rather than tasks, answer fear of displacement and loss of control honestly, and give people protected time to learn and improve the work
Turning demonstrations into useful capabilities
Decide whether a pilot expands, is revised, waits, or stops, who owns it in operation, and how deep its review goes.
Run a bounded pilot with a named owner and a stop condition, decide on the evidence, and carry security, privacy, reliability and accountability as leadership responsibilities
What a leader should do next
Decide your first 30, 60 and 90 days, the measures you will accept, and what to ask before services pass work to one another.
A 30/60/90 plan with a named decision owner and one obstacle removed, outcome measures that count user results, quality, elapsed time and total cost rather than activity, and the questions to ask before services pass work to one another
Routes for your staff, by role
This course sits inside a larger catalog of trainings on the same site, grouped by who you are. The landing page offers five roles. Use the same five to give each person a first stop.
- Leaders read this course and the one-page leadership briefs.
- Builders take the AI-Powered Development developer path first, then the engineering and delivery trainings.
- Operators, who run systems and are not assumed to code, take the intermediate path and the cloud and delivery trainings.
- Security staff, who secure and authorize systems, start with the Zero Trust and secure delivery trainings.
- Data staff, who work with data and documents, start with the data products and grounded answers trainings.
Match the route to the role, not the seniority. A senior operator is still an operator.
Optional deeper reading
The technical trainings on this site, written for your engineers, use a made-up utility company as their running example, so each one-page brief can be read with no prior context. These three are the briefs this course points to most.
Federal readers: the second lesson of Module 5, Security, privacy, reliability and accountability, carries a dated note on the federal AI policy instruments as of November 2026, with what each requires and what none of them authorizes. Nothing on this site is legal or acquisition advice.