Scoped standing permission (Lecture 6.3)
02 / 04Alex’s 4-part standing rule for personal preparation reminders—with destination readback and immediate exception returns. Alex sets it only after checking action receipts: saved records, such as the calendar entry read back after each booking, showing an action really happened. The Northstar reminders here are a prepared example, so no real receipts sit behind them.
Standing permission rule / personal calendar only15-minute private review preparation reminder
- 1. Permitted action & destination: Create one 15-minute private preparation reminder on Alex’s personal calendar only, 60 minutes before any confirmed Northstar meeting.
- 2. Required evidence: Client review date and time must be explicitly confirmed in the supplied meeting transcript or project record.
- 3. Routine reporting & readback: Read back the saved calendar entry from the destination calendar and log the receipt in the weekly summary report.
- 4. Immediate-return exceptions: Ambiguous date/time, existing calendar conflict (such as Tuesday’s 10 o’clock budget call), unavailable calendar tool, or any action affecting another person must stop and return immediately.
Away-from-desk routes & linked apps (Lecture 6.4)
03 / 04Verify where the task runs, which files it can read, and whether a linked app (the course says linked app to keep it apart from the ChatGPT app on your phone; older guides say connector) has employer policy approval before leaving your desk. Maya’s company has local computer access set up and she has sync on, so before leaving she keeps her laptop on and online and starts a new cloud task (a task begun on the laptop cannot switch to the cloud partway through), then follows up on it from her phone.
| Route | Where work runs | Access & governance check |
|---|
| ChatGPT Work, local | In ChatGPT on your computer | Uses the folders and files you approved on that machine; nothing local follows you to a phone. |
| ChatGPT Work, cloud task | On OpenAI’s own computers, so it keeps going after you leave; check or follow up from the web or your phone | Reaches files on your own computer only through local computer access, with that computer connected, switched on and online; in a company workspace the person who manages ChatGPT usually turns it on. |
| Dot (some plans) | Personal agent with its own cloud computer and browser | Connects to one of your computers only while it is online with ChatGPT open; reads cloud files only through a linked app plus separate employer policy approval. As of 20 October 2026: Pro plans in the European Economic Area, the UK and Switzerland do not include dots. Check your own screen. |
| Permitted summary (Maya’s fallback) | Employer-approved mobile workspace | Prepared before leaving the desk when company policy blocks both a connected laptop and a linked storage app for client bid files. |
Capstone effort comparison & team sharing (Lectures 6.5–6.6)
04 / 04Compare total effort across all 4 buckets—initial setup, explanation, review, and manual correction—before keeping or sharing a workflow.
| Effort bucket | Before the workflow | With the workflow |
|---|
| 1. Initial setup | None | About 1 hour in week one |
| 2. Task explanation | About 10 minutes a week explaining Northstar’s background | One spoken sentence, under a minute |
| 3. Output review | About 15 minutes reading a long unsorted draft | 3 minutes on one organized page |
| 4. Manual correction | About 15 minutes rewriting messages by hand | One minor phrasing tweak, about 2 minutes |
About 34 minutes saved each week, more than half an hour, so the setup pays back within 2 weeks: keep the workflow, using the keep-or-change test from the first section. These minutes are made up for this prepared example. Alex supplies the transcript and a 1-sentence goal. The agent drafts the blocker-focused follow-ups in the style Alex's project notes describe and, because the standing permission is paused from quarter-end, proposes the Monday preparation reminder for Alex to confirm.
The 4 questions that guide any new leadership problem with AI (6.6 Finale)
Principle: You lead the work, and the agent prepares it.
1. Useful result: What result would actually help the next decision?
2. Grounded context & method: What project records and saved skills does the agent need?
3. Return boundaries: Which exceptions or conflicts must return to me immediately?
4. Human ownership: Which tradeoff, judgment, or conversation belongs only to me?
Your first step: Pick one meeting this week whose follow-up you usually end up chasing, run the meeting follow-through workflow on its transcript, and judge the result with the keep-or-change test from the first section.