Most ChatGPT advice for project managers is useless. "Ask it to summarize your meetings!" Thanks. Groundbreaking.
The prompts that actually save time are the ones that handle the work you're already doing anyway — the writing, the structuring, the translating of messy human problems into clean deliverables. Here are the eight I use most.
1. Writing Project Briefs That Get Stakeholder Buy-In
The problem with most project briefs: they're written for the person who already understands the project. This prompt flips that.
Write a project brief for the following initiative. The audience is senior stakeholders who care about business outcomes, not technical details. Lead with the problem we're solving and the business case. Include: executive summary (3 sentences max), problem statement, proposed solution, success metrics, timeline, and resource requirements. Keep it under one page.
Project details: [describe your project]
The "3 sentences max" constraint forces the model to prioritize. Without it you get five paragraphs where you need five sentences.
2. Creating Realistic Timelines With Risk Buffers
This one is embarrassingly useful and nobody talks about it.
I need to build a project timeline for the following scope of work. After creating the initial timeline, identify the 3 most likely delay risks and add appropriate buffers for each. Show me two versions: an optimistic timeline and a realistic timeline with buffers. Explain what assumptions drive the difference between them.
Scope: [describe deliverables and dependencies]
Team: [team size and roles]
Hard deadline: [date if applicable]
The "explain the assumptions" part is what makes this useful in conversations with leadership. You're not just showing dates — you're showing your reasoning, which is defensible.
3. Writing Status Updates Executives Will Actually Read
Status updates that get ignored have one thing in common: they bury the lead. Executives want to know three things — are we on track, what's the risk, and do you need anything from me.
Write a concise executive status update for a project that is currently [on track / at risk / delayed]. Format: one paragraph, four sentences maximum. Structure: current status + what we completed this period + what's coming next + any escalation needed or explicit "no escalation needed." Tone: direct and confident, not defensive.
Current period summary: [what happened]
Next period plan: [what's coming]
Issues or blockers: [any risks or blockers]
The explicit "no escalation needed" line is worth its weight in gold. Executives interpret silence as ambiguity. Say it directly.
4. Turning Vague Requirements Into Clear Scope Documents
Requirements that say "make it better" or "modernize the experience" are where projects die. Use this prompt in the gap between a vague request and a kickoff meeting.
I've received the following vague requirement. Help me turn it into a structured scope document by identifying: (1) what we know for certain, (2) what's ambiguous and needs clarification, (3) what's likely out of scope, and (4) 5 clarifying questions I should ask the stakeholder before we proceed.
Vague requirement: [paste the requirement]
Context: [describe the product/team/constraints]
Run this before every requirements meeting. You'll show up with better questions than the stakeholder expected, which builds credibility fast.
5. Retro Summaries That Lead to Real Changes
Retros that produce "we should communicate better" as an action item aren't retros. They're venting sessions with documentation.
Summarize the following retrospective notes into a structured report with three sections: (1) What's working — keep doing this with specific reasons why, (2) What isn't working — specific friction points, not general complaints, (3) Action items — maximum 3, each with an owner name, a concrete deliverable, and a due date. If the notes contain vague items like "improve communication," reframe them as specific behavioral changes.
Raw retro notes: [paste notes]
The "reframe vague items" instruction does most of the work. "Improve communication" becomes "Engineering will send a status update to PM every Friday by 5pm."
6. Difficult Conversations With Underperforming Team Members
This is where PMs actually need help and nobody admits it. Writing a performance conversation script is awkward enough that most people avoid having the conversation entirely.
Help me prepare for a difficult performance conversation with a team member. I need: (1) an opening that's direct but not aggressive, (2) specific language for describing the performance gap without making it personal, (3) questions I can ask to understand their perspective, (4) a clear statement of expectations going forward, and (5) how to end the conversation constructively. Keep the tone professional and specific.
Performance issue: [describe the gap]
Context: [any relevant history or prior conversations]
Desired outcome: [what you want to happen after this conversation]
Don't use this to generate a script you read verbatim. Use it to practice the language before you're in the room.
7. Stakeholder Communication Plans
New project, multiple stakeholders, everyone wants different updates at different frequencies. This gets messy fast.
Create a stakeholder communication plan for the following project. For each stakeholder group, define: communication frequency, format, key messages, and who is responsible for sending. Organize by stakeholder group, not by communication type. Flag any stakeholders who have conflicting communication needs that I'll need to negotiate.
Stakeholder groups: [list groups and their roles/interests]
Project: [brief description]
Project duration: [timeline]
The "conflicting communication needs" flag has saved me multiple awkward conversations. Better to surface it in planning than discover it when an executive asks why they're not getting the same level of detail as their direct report.
8. Project Post-Mortems
Post-mortems that go into a folder and never get read are worse than nothing. They give the impression that learning happened when it didn't.
Write a project post-mortem from the following notes. Structure it as: (1) project summary and outcome (2 sentences), (2) what went well and why — focus on root causes, not surface observations, (3) what went wrong and why — be specific, avoid blame language, (4) top 3 lessons that apply to future projects, (5) specific process changes to implement. Format for a 5-minute read. This document will be shared with the entire team.
Project notes: [paste notes or summarize what happened]
"Format for a 5-minute read" is doing real work here. Post-mortems that take 20 minutes to read don't get read.
These prompts work because they give ChatGPT enough context and constraint to produce something useful on the first try. Vague prompts get vague outputs. The more specific you are about audience, format, length, and purpose — the more the output resembles something you'd actually send.
If these were useful — I have 500+ prompts organized by use case including a full section for project managers and team leads. $27, instant download: https://toshleonard.gumroad.com/l/rzenot
![Defluffer - reduce token usage 📉 by 45% using this one simple trick! [Earthday challenge]](https://media2.dev.to/dynamic/image/width=1000,height=420,fit=cover,gravity=auto,format=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fiekbgepcutl4jse0sfs0.png)
