Most project managers use ChatGPT wrong. They type vague requests and get vague responses.
The secret is specificity. Give ChatGPT context, constraints, and a clear output format—and it becomes genuinely useful.
Here are 25 prompts I use regularly. Copy them. Modify them. Save hours every week.
Status Updates & Reporting
1. Weekly Status Report
I need to write a weekly status report for [PROJECT NAME].
Here are my raw notes:
[PASTE YOUR NOTES]
Create a status report with these sections:
- Executive Summary (3 sentences max)
- Accomplishments This Week (bullet points)
- Planned for Next Week (bullet points)
- Risks and Issues (table format: Risk | Impact | Mitigation)
- Key Decisions Needed
Tone: Professional, concise. Reader is a VP with 2 minutes to scan this.
2. RAG Status Justification
My project is currently [GREEN/YELLOW/RED] status.
Here's the situation:
[DESCRIBE CURRENT STATE]
Write a 2-3 sentence justification for this status that I can include in my steering committee deck. Be direct about what's working and what's at risk.
3. Executive Summary from Details
Here's a detailed project update:
[PASTE LONG UPDATE]
Summarize this into 3 bullet points for an executive who will spend 30 seconds reading it. Focus on: progress, blockers, and what's needed from leadership.
Risk Management
4. Risk Brainstorming
I'm managing a [TYPE] project to [OBJECTIVE]. The timeline is [X WEEKS/MONTHS] and the team is [SIZE].
What are the top 10 risks I should track? For each risk, include:
- Risk description
- Likelihood (High/Medium/Low)
- Impact (High/Medium/Low)
- Suggested mitigation
Focus on risks that are commonly overlooked, not just the obvious ones.
5. Risk to Plain English
Here's a technical risk description:
[PASTE TECHNICAL RISK]
Rewrite this so a business stakeholder with no technical background understands:
1. What could go wrong
2. How it would affect their business
3. What we're doing about it
Use simple language. No jargon.
6. Mitigation Strategy
Risk: [DESCRIBE RISK]
Current mitigation: [CURRENT APPROACH]
This mitigation isn't working because [REASON].
Suggest 3 alternative mitigation strategies, ranging from low-effort to high-effort. For each, explain the tradeoff.
Stakeholder Communication
7. Difficult Conversation Prep
I need to tell [STAKEHOLDER ROLE] that [BAD NEWS - e.g., project is delayed, budget is exceeded, feature is cut].
They will likely react by [EXPECTED REACTION].
Help me structure this conversation:
1. Opening (how to frame the news)
2. Key message (what exactly to say)
3. Anticipated objections and responses
4. Proposed path forward
5. Closing (next steps)
Tone: Direct but empathetic. Don't sugarcoat but don't be harsh.
8. Stakeholder Update Email
Write a stakeholder update email for [AUDIENCE].
Context:
[KEY UPDATES]
The email should:
- Be scannable (bullet points, headers)
- Lead with the most important information
- End with clear next steps or asks
- Be under 200 words
Tone: [Professional/Casual/Formal]
9. Escalation Email
I need to escalate [ISSUE] to [EXECUTIVE LEVEL].
Background:
[CONTEXT]
What I've tried:
[PREVIOUS ATTEMPTS]
What I need:
[SPECIFIC ASK]
Write an escalation email that is:
- Factual, not emotional
- Clear about impact if unresolved
- Specific about what decision/action is needed
- Respectful of their time (under 150 words)
Meeting Management
10. Meeting Agenda
I'm facilitating a [MEETING TYPE] meeting with [ATTENDEES].
Purpose: [MEETING GOAL]
Time available: [DURATION]
Create an agenda that includes:
- Time allocations for each item
- Who's responsible for each section
- Specific questions to answer or decisions to make
Optimize for outcomes, not just discussion.
11. Meeting Summary
Here are my raw meeting notes:
[PASTE NOTES]
Create a meeting summary with:
- Key decisions made
- Action items (who, what, by when)
- Open questions/parking lot items
- Next meeting date/purpose
Format it so I can paste it directly into an email.
12. Difficult Meeting Facilitation
I need to facilitate a meeting where [DESCRIBE CONFLICT OR DIFFICULTY].
Attendees have different perspectives:
- [PERSON A]: [THEIR POSITION]
- [PERSON B]: [THEIR POSITION]
Suggest a meeting structure that:
1. Allows both sides to be heard
2. Focuses on shared goals
3. Drives toward a decision
4. Prevents the meeting from going off-track
Include specific facilitation phrases I can use.
Planning & Estimation
13. Work Breakdown Structure
I need to break down this deliverable: [DESCRIBE DELIVERABLE]
Create a work breakdown structure (WBS) with:
- Major phases or work packages
- Subtasks under each (3-5 levels deep)
- Suggested duration ranges for each task
- Dependencies between tasks
Assume a team of [TEAM SIZE] with [SKILLSETS].
14. Estimate Validation
My team estimated [TASK] at [X DAYS/WEEKS].
Here's what's involved:
[DESCRIBE WORK]
Does this estimate seem reasonable? What are we likely underestimating? What questions should I ask the team to validate this estimate?
15. Sprint Planning
Here's our backlog for next sprint:
[PASTE BACKLOG ITEMS]
Team capacity: [X STORY POINTS or DAYS]
Help me prioritize this backlog based on:
1. Dependencies
2. Risk (do hard things early)
3. Value delivery
Suggest what to include in sprint vs. what to defer.
Documentation
16. Project Charter Draft
I need to write a project charter for:
Project name: [NAME]
Problem: [WHAT ARE WE SOLVING]
Solution: [HIGH-LEVEL APPROACH]
Stakeholders: [KEY STAKEHOLDERS]
Timeline: [EXPECTED DURATION]
Budget: [IF KNOWN]
Create a project charter with:
- Project purpose and justification
- Objectives and success criteria
- Scope (in/out)
- Key milestones
- Risks and assumptions
- Roles and responsibilities
17. Process Documentation
I need to document this process:
[DESCRIBE PROCESS]
Create step-by-step documentation that:
- Uses numbered steps
- Includes decision points (if/then)
- Notes who's responsible for each step
- Highlights common errors or exceptions
Write it so a new team member could follow it without asking questions.
18. Lessons Learned
Here's what happened on my project:
[DESCRIBE PROJECT EVENTS - GOOD AND BAD]
Create a lessons learned document with:
- What went well (and why)
- What didn't go well (and why)
- Recommendations for future projects
- Specific actions to implement the learnings
Be honest and specific. Avoid vague statements like "communication could improve."
Problem Solving
19. Root Cause Analysis
We have a problem: [DESCRIBE PROBLEM]
It first appeared: [WHEN]
It affects: [WHO/WHAT]
We've tried: [PREVIOUS FIXES]
Walk me through a 5 Whys analysis to find the root cause. Then suggest 3 potential solutions targeting the root cause, not the symptom.
20. Decision Matrix
I need to choose between these options:
[OPTION A]
[OPTION B]
[OPTION C]
Criteria that matter:
[LIST CRITERIA - e.g., cost, time, quality, risk]
Create a decision matrix scoring each option against each criterion (1-5 scale). Then make a recommendation with reasoning.
21. Tradeoff Analysis
I'm facing this tradeoff: [DESCRIBE TRADEOFF]
Option A: [DESCRIBE]
Option B: [DESCRIBE]
Analyze the pros/cons of each option. Consider short-term vs. long-term implications. What questions should I ask stakeholders before deciding?
Team Management
22. Performance Feedback
I need to give feedback to a team member about [SITUATION].
What happened: [DESCRIBE BEHAVIOR/OUTCOME]
Impact: [EFFECT ON PROJECT/TEAM]
What I want to change: [DESIRED BEHAVIOR]
Write talking points for a feedback conversation that is:
- Specific and behavior-focused
- Not personal or attacking
- Clear about expectations
- Constructive and forward-looking
23. Team Motivation
My team is struggling with [ISSUE - e.g., burnout, low morale, unclear direction].
Context: [DESCRIBE SITUATION]
Suggest 5 specific actions I can take this week to address this. Focus on things a PM can actually control.
24. Delegation Brief
I need to delegate [TASK] to [TEAM MEMBER].
Their experience level: [JUNIOR/MID/SENIOR]
Deadline: [DATE]
My availability: [LIMITED/AVAILABLE FOR QUESTIONS]
Write a delegation brief that includes:
- Clear description of the task
- Expected outcome/deliverable
- Boundaries (what they can decide vs. escalate)
- Check-in points
- Resources available
Quick Helpers
25. Jargon Translator
Translate this technical explanation into plain English:
[PASTE TECHNICAL TEXT]
The audience is a business executive who understands their domain but not IT. Use analogies if helpful. Keep it under 100 words.
Tips for Better Results
-
Include context: ChatGPT doesn't know your project. Give it background.
-
Specify format: "Bullet points," "table format," "under 200 words" — be explicit.
-
Define the audience: "Write for a VP" vs. "Write for a developer" produces very different outputs.
-
Iterate: If the first response isn't right, say "Make it more concise" or "Focus more on risks."
-
Check the output: AI makes things up. Verify facts, especially numbers and dates.
Want a custom prompt library for your PMO? Let's build it together.