I'm a Senior PM at a software company, and I was drowning in status reports, kickoff docs, and uncomfortable conversations.
Then I started treating AI as a thought partner rather than a writing tool — and everything changed.
Here are the 5 prompts that genuinely transformed how I work. I'm sharing these publicly because I think most PMs are massively underusing AI.
Prompt 1: The Stakeholder Update Generator
The problem: 45 minutes every Friday writing a status update nobody fully reads.
I need to write a weekly stakeholder update for [project name].
Here is the raw data: [paste your notes/Jira summary/Slack messages].
Write a 3-paragraph update that starts with the most important news,
explains any risks or blockers clearly, and ends with what is needed
from stakeholders. Keep it under 200 words and avoid technical jargon.
Why it works: AI synthesizes messy input into clean narrative. Paste in notes, get a polished draft in 30 seconds, edit for 5 minutes.
Time saved: ~40 min/week
Prompt 2: The Meeting Agenda Optimizer
The problem: Meetings run long because the agenda is vague.
Here's my meeting agenda for a 60-minute [type] meeting: [paste agenda].
Rewrite this so every item has: a clear decision or outcome needed,
a time box, and the one person responsible. Flag any items that could
be an async update instead.
Why it works: Often, agenda items are FYI updates that did not need a meeting at all.
Time saved: 20-30 min of wasted meeting time per session
Prompt 3: The Risk Surface Finder
The problem: The risks you do not see are the ones that derail projects.
I'm managing a [describe project: type, team size, timeline, tech stack].
What are the top 10 risks I should be tracking? For each: plain-English
description, likelihood (H/M/L), impact, and one early warning sign.
Why it works: AI has absorbed patterns from thousands of similar projects. It surfaces risks you would not think of until too late.
Time saved: 2-3 hours at project kickoff
Prompt 4: The Difficult Conversation Prep
The problem: You need to tell a stakeholder their feature is getting cut.
I need to have a difficult conversation with [their role] about [the issue].
Key facts: [facts]. I want to come across as direct but respectful, focused
on solutions not blame. Write me an opening 2-3 sentences and suggest 3 ways
they might respond and how I should handle each.
Why it works: Roleplay prep with AI is underrated. Seeing likely responses makes you far less anxious going in.
Prompt 5: The Scope Creep Detector
The problem: Scope creep sneaks in through small asks that individually seem fine.
Here is the original scope: [paste scope/SOW]. Here are the requests that
have come in since kickoff: [list]. For each: (1) does it fall within
original scope? (2) complexity estimate? (3) what should I say to the
stakeholder who asked?
Why it works: Turns a judgment call into explicit analysis. The scope conversation is easier when you have thought it through first.
The Bigger Picture
These prompts save me 3-4 hours per week. More importantly, they let me focus on the actual work of project management: alignment, decision-making, and unblocking my team.
If you are a PM wanting to go deeper on this, I write a free weekly newsletter called Ahead of Schedule — practical AI tools and strategies specifically for project managers. One thing you can use this week, every week.
Subscribe at: https://buttondown.com/marcustillerman
What prompts are you using? Drop them in the comments.
Top comments (0)