LearnWithZavi home

Planning ยท Lesson 1

Where AI Actually Helps a Project Manager

The parts of the job it speeds up, and the parts it must never own.

The job nobody sees

Ask someone outside the profession what a project manager does and they will say something about Gantt charts. Ask a project manager and you get a different answer: chasing, translating, rewording, reminding, reconciling three versions of the same spreadsheet, and writing the same update in four registers for four audiences.

Very little of that is glamorous, and a surprising amount of it is text. That is good news, because text is the thing AI assistants are genuinely good at. It is also a trap, because the parts of the job that matter most look like text too, and they are not.

This course is about telling those apart. It is not about a particular tool, and it does not assume you have one approved at work. It assumes you run projects, you are busy, and you would like to spend less of your week rephrasing things.

In plain English

Scope:
What the project will deliver, and just as importantly, what it will not.
Milestone:
A checkpoint with a date and a clear test for whether you reached it. Not a task, a moment.
Dependency:
Something your work cannot finish, or start, without. Often owned by someone who does not report to you.
RAG status:
Red, amber or green. A one-word summary of project health that is only useful if it is honest.
Hallucination:
When an AI states something false with complete confidence. Dates, names and numbers are the usual casualties.

Four verbs it is good at

Nearly everything AI does well for a project manager fits under four verbs.

Drafting. The first version of a status report, a kick-off email, a scope statement, a polite chase to someone who has missed three deadlines. You will edit it. The point is that editing is faster than staring at a blank page at half past five.

Summarising. A forty-message email thread, a long requirements document, a set of meeting notes from a meeting you could not attend. You want the decisions and the open questions, not the journey.

Structuring. Turning a rambling brief into headings. Turning a brain dump into a list of workstreams. Turning a list of tasks into something with phases. Structure is where AI saves the most time, because imposing it on a mess is tedious for people and trivial for a model.

Checking. Reading your plan and asking what is missing. Spotting that a milestone has no owner, that two tasks contradict each other, or that your update never actually says what you need. A second pair of eyes that does not get bored.

Notice what these four have in common. In every case you already know the answer is roughly right when you see it, because you know the project. AI is doing the typing and the tidying. You are doing the knowing.

Four things it must never own

The other list is shorter and far more important.

Estimates it cannot know. An AI can produce a number for how long a data migration will take. It will even sound reasonable. It has no idea how clean your data is, how many people are on leave in August, or that the last migration took twice as long as planned. A confident estimate from something with no knowledge of your organisation is worse than no estimate, because it anchors everyone.

Trade-offs. Cut scope or move the date? Add a contractor or accept the risk? These are decisions about what your organisation values, and they belong to the people who will live with the consequences. AI can lay out the options neatly. It cannot choose.

Accountability. Your name goes on the plan, the report and the recommendation. If a generated risk register missed the risk that actually happened, "the tool did not flag it" is not an answer anyone will accept, nor should they.

People. Motivation, conflict, a team member who is struggling, a stakeholder who is quietly hostile. The work of a project manager is largely social, and the social part cannot be drafted.

Checkpoint

AI earns its keep drafting, summarising, structuring and checking; estimates, trade-offs, accountability and people stay with you.

A quick sort of your own week

Before the rest of the course, it is worth sorting your own work. You will probably find that some of your writing is a good candidate and some of it only looks like one.

Prompt you can copy: sort your week

I am a project manager. Below is a list of things I did last week. Sort them into two groups:

  1. GOOD CANDIDATES: work that is mostly drafting, summarising, structuring or checking, where I will review the result before anyone else sees it.
  2. KEEP: work that involves an estimate, a trade-off, a judgement about people, or something I am personally accountable for.

For each item in KEEP, say in one sentence why. If an item is a mix, split it into the part AI could help with and the part I keep. Do not add tasks I did not list.

My week: [paste your list]

That last instruction, splitting mixed items, is where the real value is. A status report is a mix: the drafting is a candidate, the RAG rating is not. Planning is a mix: the structure is a candidate, the estimates are not.

The honest caveat

If your team has already been through a wider exercise on where AI fits, the AI for Managers course covers the team-level version of this audit, including ground rules and reviewing other people's AI-assisted work. This course stays with the project manager's own desk.

And check your organisation's rules before pasting anything into an AI tool. Plans, budgets and supplier names are often confidential. Lesson five deals with this properly.

Checkpoint

Most project work is a mix, so split each task into the part AI can draft and the part you have to decide.

๐Ÿ“ Quiz

Question 1 of 4

Which of these is the best fit for an AI assistant on a project?

Found this useful? Pass it on.