AI in practice

A working guide to using an AI assistant in a project manager's week, written for the chapter's members. Concepts first; what each assistant calls them second. No product is recommended, no price is printed, and a named person re-checks it every quarter.

The guide

  1. Start here

    Most people tried an assistant once, signed out, in a browser tab, and got the worst version of it. What changes when you sign in, use the app and give it your files.

    Start heresettingsbefore / after6 min
  2. Context

    It has read the internet. It has not read your project. The one idea that separates useful answers from generic ones, and the documents you already own that supply it.

    checklistbefore / after5 min
  3. Four ways to ask

    The vendors use four words for four different things. One table, one analogy each, and the one-project-per-project rule.

    tablechecklist6 min
  4. Ten everyday jobs

    The page to bookmark. Each job with the before and the after, the prompt to copy, what to give it, and what you still check yourself.

    ten cardsprompts9 min
  5. What never goes in

    You hold the client’s contract, the team’s salaries and the tenant’s personal data. The red list, the law in one paragraph, and the thirty-second anonymiser.

    red listthe law6 min
  6. Trust, but check

    The assistant is a confident junior who never says “I don’t know”. Where it fails, the five-line check, and when not to use it at all.

    five-line check4 min
  7. PMBOK and PMI

    The ten jobs mapped to the PMBOK Guide’s performance domains, and the AI material PMI already offers a member, dated.

    tablesources5 min

12 prompts

Prompt library

Every prompt from the ten jobs, filterable, with a copy button. The board adds to it through the CMS.

10 questions

Self-check

Ten situations, four options each, in the exam trainer’s format. Two minutes; send it to your team.

3 so far

The weekly question

One question a week, one best answer, and the page that explains it.

This week

The weekly AI question ·

Monday, again

Every Monday you explain the project to the assistant from scratch - who the sponsor is, what the report looks like, which language - before you can ask for anything. What fixes this?

Pick one, then show the answer
Show the answer

Best answer

BOne project workspace per real project: the charter, the WBS and last report uploaded once, the standing instructions written once.

Four words for four things: a prompt is the ask, custom instructions are how you always want it to behave, a project is a folder that remembers, a skill is a recipe it can run. The one-project-per-project rule puts the project's documents and instructions where they belong, once.

Why, option by option

  1. AIt works, and it is what most people do. But it is the manual version of a feature all four assistants have, and the pasted document counts against the room the conversation has for this week's material.
  2. BThis is what a project workspace is for. Set it up once and every Monday's message is just "here are this week's notes".
  3. CCustom instructions apply to every chat, including the ones about other projects and the recipe you asked for on Sunday. They are for how you always want it to behave, not for one project's facts.
  4. DMemory holds preferences and small facts about you, not a charter. It is also the one place you should be most careful about what goes in.

Read why: Four ways to ask

A new question every Monday. Written in advance; the date on it is when it was published.Earlier questions

Myth or fact

  • MythIt will replace project managers.

    Fact

    It drafts. It does not own the outcome, hold the relationship or sign the report. The judgement, and the name at the bottom, stay yours.

    Trust, but check
  • MythIt knows my project.

    Fact

    It knows what is in front of it in this conversation and nothing else. Give it the charter and it knows the charter.

    Context
  • MythIt is private because I did not log in.

    Fact

    Signed out is the state with the fewest data controls, not the most. Sign in, check the two settings, and use a temporary chat for one-offs.

    Start here
  • MythIt never makes up sources.

    Fact

    It will cite a PMBOK section that does not exist, in a confident voice. Open every quote before it leaves your hands.

    Trust, but check
  • MythThe free version is fine for work.

    Fact

    The free tiers are for learning. For work material the tool under your employer’s contract, or a paid plan, is the one: more room for your documents, projects, and no shared-account surprises.

    What never goes in
  • MythI need to learn prompt engineering.

    Fact

    You need to say who is asking, who is reading, what you want back, and to attach the documents. That is a paragraph, not a discipline.

    Four ways to ask
  • MythUsing it is cheating.

    Fact

    The Code of Ethics has no AI exemption and no AI prohibition. The report is yours either way; what it asks is that you check it and stand behind it.

    Trust, but check
  • MythMy company’s Copilot is the same as ChatGPT.

    Fact

    Same idea, different contract. The employer’s tool sits under the employer’s agreement, which is exactly why it is the one for work material.

    What never goes in

What each assistant calls it

Five concepts, four names each
ConceptChatGPTClaudeGeminiMicrosoft Copilot
A folder that remembersProjectProjectGemAsk your IT team
Standing preferencesCustom instructionsPreferences and project instructionsInstructions in a GemAsk your IT team
Remembering you across chatsMemoryCheck the settingsDepends on the accountAsk your IT team
A chat kept apartTemporary ChatIncognito chatDepends on the accountAsk your IT team
A repeatable procedureProject instructionsSkillsA Gem with instructionsAsk your IT team

Names change; the concepts do not. Where an assistant is provided by an employer, the answer depends on how the organisation set it up, which is why the last column says to ask.

Ten questions, two minutes

The self-check, in the exam trainer's format. See where you stand, then send it to your team.

Take the self-check

Last checked by Petar Trajchevski. Product names and settings paths were walked through on that date; the concepts do not move. Report a change