Search for AI for project managers and you get two kinds of page and no third. One is a catalog listing: two days, three days, sixteen hours, a price, sometimes a module list. The other explains the topic — what an assistant does for scheduling, risk, resourcing — without describing a room. Across the course pages reviewed for this piece, not one states how many people belong in the session, what participants bring, or how many minutes are hands-on.
Those three omissions separate an AI enablement session that changes next week’s status meeting from one that produces a certificate. What follows is the inside of a working session for the people who run projects and delivery at a company of 50 to 500.
Who is actually in the room
Eight to twelve people, grouped by the documents they write rather than by title: the project managers, the delivery or implementation managers who own client onboarding, the program manager, whoever runs reporting into the executive team, the scrum master, and the coordinator whose job description says administration and whose actual job is the weekly status pack. Invite that last person — they write more of the company’s recurring project prose than anyone else.
What they share is not software-versus-services. All of them spend the week converting messy inputs — a meeting, a thread, a half-updated board — into a written statement someone else acts on. That is one skill, and the one the session trains.
Two groups belong elsewhere. Engineers need a different discipline, because their assistant sits inside the editor and the failure modes are code-shaped — that is its own session, covered in our guide to training engineering teams on coding assistants. Product managers overlap more, but their artifacts are specs and research synthesis — the case for a separate curriculum is in our read on product management teams.
Eight is the floor because the third exercise requires participants to critique each other’s work. Twelve is the ceiling because above it one facilitator cannot sit beside people while they work. None of those pages states a number, a reliable sign the room is larger than it should be. The reasoning behind function-sized rooms is in our playbook on why one company needs nine different curricula.
The pre-work that decides everything
Every provider promises hands-on practice. None publishes a list of what to bring, which means every one of those agendas can be run on invented examples — and that is a lecture with a keyboard in it.
The request goes out two business days ahead, in one short email, asking for four things:
- One live plan they own — the schedule, the implementation timeline, the sprint board export. Whatever they would open if a sponsor asked where things stand.
- One recurring written deliverable. Last week’s status note, steering-committee update, or client progress summary. The real one, not the template.
- One long inbound thread they had to read closely. A change request, a scope dispute, a redlined statement of work.
- Raw notes from one meeting last week — with the question of whether that recording may be pasted anywhere settled before the email goes out.
Each person also writes one sentence describing a task they have done more than twenty times and could explain to a new hire in a minute. That sentence becomes exercise four.
Two things make or break collection. The ask goes to participants, not to the executive who bought the session, because a buyer’s idea of a representative document is rarely the one the team fights with. And the facilitator reads the submissions beforehand, because the exercises are sequenced around what arrived.
The run of show, three hours
Three hours, one break, 115 of the 180 minutes on participants’ own material. That ratio is the number to ask any provider for, and the one none of them publishes.
| Time | Block | What happens |
|---|---|---|
| 0:00–0:20 | What the tool is doing | What a language model is actually doing when it writes your status note, and the one rule. |
| 0:20–0:35 | Accounts and boundaries | Which tenant, which assistant, what may be pasted, where a client’s document may not go. |
| 0:35–1:05 | Exercise 1 | The status update, built from raw material. |
| 1:05–1:35 | Exercise 2 | The inbound thread, compressed into decisions, asks and owners. |
| 1:35–1:45 | Break | — |
| 1:45–2:15 | Exercise 3 | The plan review, with the assistant as critic rather than author. |
| 2:15–2:40 | Exercise 4 | The repeat task, turned into a prompt someone else can reuse. |
| 2:40–3:00 | Verification and write-up | The three-check habit, and the two artifacts that leave. |
The four exercises, with a pass test each
An exercise without a success condition is a demonstration. Each of these has one, and the participant decides whether it passed.
| Exercise | The work | Pass test |
|---|---|---|
| 1. The status update | Paste last week’s meeting notes and the board export. Produce the status note in the format your sponsor receives. | Shorter than your hand-written version, contains no date, number or owner you cannot point to in the source, and names the item you were tempted to soften. |
| 2. The inbound thread | Paste the change request or escalation chain. Extract what was decided, what is asked, who owes what, what is open. | Someone else reads your extract without the thread and correctly states the ask and the owner. |
| 3. The plan review | Ask the assistant to argue against the plan: missing dependencies, unstated assumptions, the duration that looks invented. | It raises one real objection you had not written down, and you can name one of its objections as wrong and say why. |
| 4. The repeat task | Turn the twenty-times-a-month task into a written prompt with its inputs named, then hand it to the person beside you. | Their output is usable without asking you a question. |
Exercise three converts people, and none of the published agendas contains it. Competing outlines treat the assistant as a producer of artifacts; used as a critic of one the human already owns, it is safer as well as more useful, because a wrong objection costs nothing while a wrong status note reaches a steering committee.
Exercise four is what survives the week. A prompt that works only for its author is a trick; one a colleague can run is a shared standard, which is the actual deliverable. That distinction — individual skill versus team capability — is the argument our enablement manifesto makes at company level.
The one rule: never assert a fact about the project
The assistant may rephrase, compress, structure and argue with what you give it. It may not state a fact about the project that you did not give it: no invented dates, no inferred owners, no dependency it decided must exist, no percentage complete.
Project work is the hardest place to hold that line, because the failure does not look like one. A fabricated case citation in a legal memo is checkable in thirty seconds. A plausible dependency between two workstreams, a confidently named owner, a milestone reconciled against the wrong baseline — these read as competence, and get presented.
The uses where that line is thinnest are the most popular. The Project Management Institute’s 2023 Annual Global Survey on Project Management found the top three ways project managers use AI are reporting (34%), decision support (33%) and communication (26%) — and the first two are exactly where the model is asked to say something about the state of the world.
So the session teaches a three-check habit for every generated draft:
- Trace every specific. Each date, number, owner and status must map to a line in what you pasted. Anything that does not gets deleted rather than corrected — correcting it teaches you nothing about where it came from.
- Read for the omission. The error is easy to catch; the gap is not. Usually the draft dropped the blocked item, the quiet risk, or the thing you dreaded telling the sponsor.
- Read it as the sponsor. Generated project prose is fluent and faintly confident. If the tone implies more control than you have, the draft is wrong even when every fact is right.
That habit, not any tool, is what the three hours are for. The same instinct applied to exception queues and SOPs is the backbone of our session for operations teams.
Three traps specific to project work
Teaching tool features instead of fluency. The AI panels inside project tracking suites demo beautifully and transfer nowhere. They also carry configuration cost: practitioners describe spending sprints teaching a tool their work breakdown structure only to have it suggest tasks from another project. Fluency moves with the person when the company changes tools. Leave in-product features to a vendor hour.
Starting with forecasting. Delay prediction and automated risk scoring are what executives ask about and the worst place to begin. Both need historical project data that is clean, consistently labeled and plentiful, which at 50 to 500 people it is not. The widely quoted forecast that 80% of project management work will be run by AI — a Gartner projection first stated in 2019 — is why sponsors arrive asking.
Treating a client’s documents as your own. The delivery manager’s problem, routinely missed because the agenda was written for internal project managers. An implementation manager’s plan, notes and status pack often describe someone else’s business under an agreement with its own confidentiality terms. The answer is not a blanket ban but a named list, produced in the room, of which accounts’ material may go into which tool — the same list our session for sales teams builds from the pipeline end.
The walk-out artifacts
Two documents exist at 3:00 that did not at 0:00, and participants write both. One is a prompt sheet of three to five entries, each naming its inputs so a colleague can run it. The other is a one-page do-not-paste list: approved tools, the material that may go into them, and the accounts whose documents may not.
The Monday test: a week later, has anyone added an entry nobody wrote in the room? If yes, the habit took. If the sheet is untouched, you bought a pleasant afternoon.
What it costs against the published alternatives
| Option | Published terms | Where it stops |
|---|---|---|
| Webucator’s three-hour public workshop | $289.10 per student; five blocks ending in a case study | The most detailed outline published, still silent on group size and pre-work |
| New Horizons’ three-day instructor-led course | $1,350; ten modules through a capstone | Three days of generic project material |
| Global Knowledge’s two-day virtual course | $1,350 excluding VAT, dated sessions published | Course overview section is empty — a price and a date, no curriculum |
A facilitated session for one function runs roughly $2,000 to $15,000 at market rates, the spread driven by whether the facilitator prepares against your material or runs a standard deck. Then add the line most budgets omit: ten people for three hours plus an hour of pre-work is 40 hours of project management time, frequently the larger number on the page. A session run on invented examples consumes the same 40 hours and returns less, which is the strongest argument for insisting on the pre-work.
A catalog course builds the individual who wants depth; a facilitated session builds a function that writes to one standard. Treating one as a cheaper version of the other is the common mistake.
What to check thirty days later
Resist the usage dashboard. It tells you logins rose, which answers a question nobody asked. Three checks a manager can answer in a month:
- Has the prompt sheet grown? Entries added after the session are the only direct evidence of transfer.
- Has one named deliverable moved? Time the weekly status pack now against the week before. Use your own baseline: published figures for the time project managers lose to reporting run from 20–30% in a 2014 practitioner survey to vendor claims above 50%, with no shared method behind them.
- Has anyone asked a new boundary question? The first time someone asks whether a specific client’s document can go into a specific tool, the do-not-paste page is working.
For the starting point: the Project Management Institute reported in September 2023 that only 18% of project professionals had extensive or good practical experience with AI tools, while 82% of senior leaders expected AI to affect how projects are run within five years. The distance between those numbers is the work.
Frequently asked questions
What should an AI workshop for project managers cover?
Four things, in order: what a language model is doing when it writes project prose, the status update built from raw material, the inbound thread compressed into decisions and owners, and the assistant used to argue against a plan. Skip tool feature tours and delay forecasting.
How long should the session be?
Three hours for eight to twelve people, with at least 110 of those minutes on participants’ own live documents. Ninety minutes covers status and thread work only. A full day is two sessions, a week apart.
How many people should be in the room?
Eight to twelve. Below eight you lose the peer-critique exercise that makes failure modes visible. Above twelve the hands-on minutes become a demonstration, whatever the agenda claims. None of the published course pages states a number — ask directly.
What do participants need to bring?
One live plan they own, one real recurring deliverable from last week, one long inbound thread, and raw notes from one recent meeting — plus a sentence describing a task they do more than twenty times a month. Collect it from participants, not from whoever approved the budget.
Is this the same as learning the AI features in our project tracking tool?
No. In-product features are vendor training. Fluency with a general assistant survives a tooling change and applies to every document the team writes.
Should delivery managers and project managers be in the same room?
Yes, at this company size — they write the same artifacts from the same messy inputs. They diverge on confidentiality: client-facing delivery managers need the do-not-paste list and internal project managers mostly do not, so that block runs with both groups present.
Can we use real client documents in the exercises?
Only on an enterprise tenant configured to exclude your inputs from training, and only for accounts whose agreements permit it. Settle it account by account before invitations go out. Otherwise bring an internal project.
What does a session like this cost?
Roughly $2,000 to $15,000 for a facilitated session at market rates. Published alternatives run $289 per student for three hours and $1,350 for two or three days of generic material. Add 40 hours of staff time.
Key takeaways
- None of the published AI course pages for project managers states a group size, a pre-work list, or a hands-on minute count. Those omissions predict whether the session changes anything.
- Three hours, eight to twelve people, 115 of 180 minutes on participants’ own documents is the shape that holds.
- Group the room by the documents people write, not by title, and the pre-work is the session: one live plan, one recurring deliverable, one long thread, one meeting’s raw notes, collected from participants rather than the buyer.
- The rule everything hangs from: the assistant may restructure what you gave it and may never assert a fact about the project. Invented dependencies and owner names read as competence and survive review.
- Reporting (34%) and decision support (33%) are the most common uses in the Project Management Institute’s 2023 survey, and the two where that rule bites hardest — so use the assistant as a critic of a plan rather than its author, and skip forecasting until the reporting data is trustworthy.
- Two artifacts leave the room: a prompt sheet with named inputs, and a one-page do-not-paste list for client-owned material.
If you want a read on which of these blocks your project and delivery function needs, book a free AI readiness call. We will walk your weekly status process and tell you where the three hours should go.
Arthur Wandzel