6-lesson course · about 2 hours
Catch slipped dependencies and broken assumptions while they're still cheap to fix
For CEOs, founders, managing directors, business owners and senior leaders
Everything for CEOsSet up a weekly AI review that flags overdue dependencies and changed assumptions and drafts follow-ups and escalations for named owners. You keep the decisions. About two hours, no code.
What you’ll be able to do
By the end, you can…
How it works
A tutor that meets you where you are
- Lessons that adapt to youSix self-paced lessons. Later lessons are written for your level as you reach them, using your own project as the working example.
- An AI tutor you can ask anythingType or speak your questions at any point, such as how to phrase an assumption so it can be checked, or whether an item counts as overdue.
- Quizzes and flashcards for each lessonShort checks tied to each lesson help the distinctions stick, such as commitment versus dependency, or follow-up versus escalation.
- Progress tracking and a certificateSee where you are across both modules and receive a certificate of completion when you finish.
Curriculum
The curriculum
The course has two modules. First you map one live project, define your warning signals and set boundaries on information. Then you write the agent's weekly brief, add escalation rules and practise reviewing its output.
Module 1Prepare the Ground: Your Project Map, Signals and Boundaries3 lessons
1Map Commitments, Dependencies and Decision Assumptions for One Project
- Distinguish a commitment, a dependency and a decision assumption using examples from your own project
- List at least one of each for a live project, with a named owner and a due or review date
- Spot items in your list that are too vague for anyone to check, and rewrite them
2Define What Counts as Overdue and What Counts as a Changed Assumption
- Write a plain-language definition of overdue that covers missed dates, missing updates and at-risk items
- Write, for each decision assumption, the evidence that would show it has changed
- Choose where the agent should look for that evidence each week
3Decide What Information the Agent May Use
- Sort your project sources into allowed, restricted and excluded
- Identify which AI tools your organization has approved for which kinds of information, and confirm this with the people responsible
- Rewrite a sensitive register entry so it can be reviewed without exposing restricted detail
Module 2Run the Weekly Review: Brief, Escalate, Approve3 lessons
4Write the Weekly Review Brief for Your AI Agent
- Write a weekly review brief that names the sources, the definitions, the boundaries and the output format
- Run the brief once against your register and check the agent's findings against what you know
- Set up a weekly routine, either scheduled in an approved tool or run by hand at a fixed time
5Set Escalation Rules and Decision Rights
- Write rules that sort flagged items into routine follow-ups and escalations for decision
- Name who receives each type of message and who holds the decision at each step
- Add the escalation rules to your weekly review brief
6Review, Approve and Act on the Agent's Weekly Output
- Check each flag against its cited evidence before acting on it
- Approve, edit or reject each draft follow-up and escalation, and give a reason for each edit or rejection
- Choose for each flagged item between deciding now, talking with the owner, or no action this week
- Adjust the brief or rules based on what the review shows
Who it’s for
Made for you if…
Made for: CEOs, founders, managing directors, business owners and senior leaders
A CEO or managing director running several projects through other people
You get status packs, but you hear that a dependency slipped only after the damage is done. A weekly check surfaces it while there is still time to act.
A founder or business owner whose plans rest on a few key assumptions
You will write down what would show each assumption has changed, and have an agent look for that evidence every week.
A senior leader who wants AI help without giving up control
The agent drafts and you decide. Nothing goes to an owner until you have approved it, and the escalation calls stay with you.
Questions
Good to know
Do I need to write code?
No. You need basic comfort with an AI chat tool. Coding and custom software are outside this course.
What do I need before starting?
Access to the tracker, document or list where one live project's commitments and owners are recorded, and a project with at least one dependency and one decision assumption you can name.
How long does it take?
About two hours across six self-paced lessons.
Will the agent send messages to my team on its own?
Not in the routine you set up here. The agent drafts follow-ups and escalations, and you approve, edit or reject each one before anything is sent.
Do I need a particular AI tool?
No. The course does not compare or recommend vendors. You will identify which tools your organization has approved for which kinds of information, and run the weekly review either scheduled in an approved tool or by hand at a fixed time.
How does the course handle confidential information?
You sort your project sources into allowed, restricted and excluded, confirm with the people responsible which tools are approved, and practise rewriting a sensitive entry so it can be reviewed without exposing restricted detail.
Does it cover board decks, budgets or market monitoring?
No. The course focuses on commitments, dependencies and assumptions for one project. Strategy packs, budget trade-offs, news monitoring, HR judgments and multi-agent setups are not covered.