Your first AI wins: five everyday tasks

When you finish, you can write a clear prompt for five common project tasks and check each result.

Win one: a charter draft

Weak prompt: “Write a project charter.” You will get a generic template. Strong prompt: “Draft a one-page charter for moving a clinic’s paper forms to a digital system. Sponsor: practice manager. Team: two admins, one IT contractor. Constraint: finish before the busy season. Include scope, out-of-scope, deliverables, assumptions and risks. Label guesses as assumptions.”

What to check: are the assumptions actually true? Is anything in scope that the sponsor has not agreed to? Does it match how your organization defines success? Take the draft to your sponsor as a starting point, never as a finished agreement.

Win two: status updates

Weak prompt: “Write a status report.” Strong prompt: “From these notes write a weekly update with progress, next week, risks and decisions needed. Use plain language. Say on track, at risk or blocked only if my notes say so. Do not add facts.” Paste only non-confidential information.

Check that nothing is softened or exaggerated. A tool may turn “we are worried about the supplier” into “minor supplier delay”. Stakeholders rely on your honesty. Read the update as if you were the sponsor and ask what is missing.

Win three: meeting follow-up

Meetings produce decisions and then fog. Weak prompt: “Summarize this meeting.” Strong prompt: “From these notes list decisions, action items with owner and due date (write ‘not stated’ if missing) and open questions. Then draft a short follow-up message.” Send within a day while memories are fresh.

Check every owner and date. If the tool assigned a task to someone who did not agree, fix it or ask them. A published action item with the wrong name causes confusion and resentment. Keep ‘not stated’ visible so gaps are filled on purpose.

Win four and five: risk lists and plan reviews

Ask for risks across people, schedule, scope, suppliers and technology, each with an early warning sign and a possible response. Weak: “What could go wrong?” Strong: “Ten risks for this project, with early signs and responses, without probability numbers.” Then add the risks only your team knows about.

Use the tool as a skeptical reviewer: “List the five weakest assumptions in this plan and three questions a sponsor might ask that I cannot answer yet.” This is one of the best uses. It reveals blind spots before they cost you. You still decide which concerns are real, and talk to the team about them.

Practice now

Draft a charter for a made-up project with the strong prompt. Circle every assumption and mark whether it is true.
Convert real meeting notes (with private details removed) into decisions, actions and open questions. Check each owner and date.
Ask the tool to review a plan summary as a skeptic. Pick the two concerns that matter most and write how you would test them.

Use any AI assistant you have. Do not paste private, client or patient information into it.

Check yourself

1. Why tell the tool to write 'not stated' when an owner or date is missing?

2. A status draft says 'minor supplier delay', but your notes say 'we are worried about the supplier'. What is the problem?

3. What is a strong use of AI as a reviewer?

Ask the AI tutor

Ask anything about this lesson, in any language. The tutor is an AI: it can be wrong, and it never needs your personal details.

Next lesson: Guardrails for project managers

AI-drafted. Checked by an automated validator and a separate AI reviewer; a person has not read every lesson. Translations and tutor answers are AI-made. Found a mistake? Tell us. AI can be wrong. General information only, not professional advice. Not affiliated with any AI company named. Current University is not accredited.