Project Manager
For optimal results, replace the bracketed information [like this] with the specific details of your project. The more context you provide, the more tailored and insightful the AI’s response will be.
Category 1: Strategic Planning & Project Initiation
1. The “Executive-Ready” Project Charter
Act as a senior program manager at a Fortune 500 company. I am initiating a new project: [briefly describe the project, e.g., "a mobile app for our loyalty program"]. Generate a comprehensive and persuasive Project Charter. The document must include: 1. **Executive Summary:** A high-level overview for a C-suite audience. 2. **Business Case:** The problem we are solving and the value proposition. 3. **Project Goals & Objectives:** Defined using the SMART (Specific, Measurable, Achievable, Relevant, Time-bound) framework. 4. **Scope Statement:** Clearly delineate what is In-Scope and what is Out-of-Scope. 5. **Key Deliverables & Success Criteria:** How we will measure success. 6. **High-Level Timeline & Milestones:** Key phases and target dates. 7. **Initial Risk Assessment:** Top 3 potential risks and their high-level mitigation. 8. **Stakeholder Register:** A list of key stakeholders and their interests. 9. **Resource & Budget Estimate:** An order-of-magnitude estimate for initial approval.
2. The Work Breakdown Structure (WBS) Generator
I need to create a Work Breakdown Structure (WBS) for my project: [Project Name and a one-sentence goal]. The major phases are [Phase 1, Phase 2, Phase 3, etc.]. Decompose each phase into a three-level WBS. Level 1 should be the major deliverable/phase, Level 2 the control accounts, and Level 3 the specific work packages. Present this in a hierarchical list format. The WBS should be comprehensive enough for a team to begin detailed task planning.
3. The “Pre-Mortem” Risk Analysis
Imagine you are a panel of seasoned project risk managers. My project, [Project Name], is about to kick off. Its primary goal is [Project Goal]. We are now conducting a "pre-mortem" exercise. Brainstorm a detailed list of 10 potential reasons this project could fail spectacularly. For each potential failure, describe a plausible scenario and then propose a proactive mitigation strategy we can implement from day one. Frame the output as a table with three columns: "Potential Failure," "Failure Scenario," and "Proactive Mitigation Strategy."
4. The Agile User Story & Acceptance Criteria Crafter
Act as an expert Agile Product Owner. I need to develop user stories for a new feature: [Describe the feature, e.g., "a user profile dashboard"]. The primary user persona is a [Describe the user, e.g., "tech-savvy marketing manager"]. Generate 5 detailed user stories for this feature. Each story must follow the format "As a [persona], I want [action], so that [benefit]." For each story, also provide a comprehensive set of acceptance criteria in a bulleted list, written in the Gherkin format (Given/When/Then).
5. The Stakeholder Influence Matrix
I am managing a complex project to [describe project]. My key stakeholders include [List stakeholder roles, e.g., 'Head of Engineering,' 'VP of Marketing,' 'External Vendor Lead,' 'End-User Group Rep']. Analyze these roles and map them onto a Power/Interest Grid. Then, for each quadrant (High Power/High Interest, High Power/Low Interest, etc.), provide a tailored communication and engagement strategy. The goal is to maximize support and minimize resistance.
Category 2: Communication & Stakeholder Management
6. The “Difficult Stakeholder” Communication Plan
I have a key stakeholder, [Stakeholder Title], who is consistently [describe the challenging behavior, e.g., "requesting changes that cause scope creep," "publicly questioning the project's value," or "unresponsive to requests for approval"]. Act as a communications expert and conflict resolution coach. Provide three distinct strategies to manage this relationship and protect the project. For each strategy, include: 1. The psychological principle behind it. 2. Specific talking points or a sample email. 3. The potential risks of that approach.
7. The Executive Status Report Distiller
My project is currently at this stage: [Provide 5-7 bullet points of raw data, e.g., "Task X is 80% complete but 3 weeks behind schedule," "Budget is trending 12% over," "Team morale is low due to recent setbacks," "We hit a major technical milestone," "A new risk has emerged with Vendor Y"]. Translate this raw data into a concise, professional executive summary (max 200 words). The summary must follow a "Past, Present, Future" structure, be written in a confident tone, and clearly state what decisions or support you need from leadership.
8. The Project Kick-Off Meeting Agenda
Generate a detailed agenda for a 60-minute virtual kick-off meeting for [Project Name]. The attendees will be a mix of technical team members, business stakeholders, and senior leadership. The agenda should be designed to inspire confidence, establish clarity, and build momentum. For each agenda item, include the topic, the designated speaker/lead, the objective, and the allocated time. Include a section on "Rules of Engagement" and "Definition of Success."
9. The “Bad News” Delivery Script
I need to inform the Project Steering Committee that a critical milestone, [Milestone Name], will be delayed by [duration]. The root cause is [explain the cause briefly, e.g., "an unforeseen integration issue with a third-party API"]. Act as a strategic advisor. Draft a communication plan and script for this announcement. The script should: 1. Acknowledge the negative impact directly. 2. Clearly and concisely explain the root cause without placing blame. 3. Present a credible and detailed recovery plan with a revised timeline. 4. Reaffirm commitment to the project's ultimate success and rebuild confidence.
10. The Cross-Functional Dependency Alignment Request
Draft a formal but collaborative email to the lead of a dependent team, [Team Lead's Name] of the [Team Name] team. My project, [Project Name], has a critical dependency on their team's deliverable: [Specific Deliverable]. Our deadline for this is [Date]. The purpose of this email is to formally request a joint planning session to map out dependencies, define SLAs, and establish a communication rhythm to prevent misalignment. The tone should be proactive and partnership-oriented, not demanding.
Category 3: Team Leadership & Productivity
11. The Delegation & Empowerment Framework
Act as a senior engineering manager known for building autonomous teams. A team member, [Team Member Name], is highly skilled but hesitant to take ownership. I need to delegate a complex task: [Describe the task]. Create a delegation framework for my conversation with them. It should include: 1. How to frame the task to connect it to their skills and career growth. 2. Key questions to ask to ensure they understand the "what" and "why," leaving the "how" to them. 3. How to define the boundaries, budget, and checkpoints without micromanaging. 4. A statement of trust and support.
12. The “Unblocking a Stuck Team” Workshop
My project team is showing signs of reduced velocity and analysis paralysis on [a specific complex problem]. Design a 90-minute workshop to help them get "unstuck." The workshop's goal is to break down the problem, identify the core blocker, and generate actionable next steps. Provide a step-by-step facilitator's guide, including activities like "Brainwriting," "Impact/Effort Matrix," and "Defining the 'Next Wise Step'."
13. The Constructive Feedback Model for Underperformance
I need to have a difficult conversation with a team member whose performance on [task/area] has been below expectations. Act as an HR Business Partner. Provide a script using the Situation-Behavior-Impact (SBI) model for delivering this feedback. The script should be empathetic but direct, focus on observable facts, and pivot towards a collaborative solution and a performance improvement plan.
14. The RACI Matrix Clarifier
For the following project process, [describe a process with multiple teams, e.g., "the quality assurance and bug fixing cycle"], there is confusion about who does what. The teams involved are [Team A, Team B, Team C]. Generate a RACI (Responsible, Accountable, Consulted, Informed) matrix in a table format to clarify roles and responsibilities. Provide a brief explanation for why each role was assigned, especially the single "Accountable" person for each task.
15. The “End-of-Sprint” Retrospective Questions
My team's sprint retrospectives have become stale and repetitive. Provide 10 creative and insightful questions to spark deeper conversation beyond the standard "What went well / what didn't." The questions should encourage reflection on process, teamwork, tools, and personal well-being. Categorize them into "Looking Back," "Looking Inward," and "Looking Forward."
Category 4: Advanced Problem Solving & Analysis
16. The Root Cause Analysis with “5 Whys”
Our project experienced a significant failure: [Describe the failure, e.g., "The user registration service went down for 3 hours during peak traffic"]. Apply the "5 Whys" technique to perform a root cause analysis. Start with the problem statement and drill down through at least five levels of "why" to uncover the systemic root cause, moving beyond surface-level technical issues to potential process or organizational problems.
17. The Decision Matrix for Technology Selection
My team needs to choose between three potential solutions for [a technical problem, e.g., "a cloud database provider"]. The options are [Option A], [Option B], and [Option C]. The key decision criteria are [Criterion 1, e.g., 'Scalability'], [Criterion 2, e.g., 'Cost'], [Criterion 3, e.g., 'Ease of Integration'], and [Criterion 4, e.g., 'Vendor Support']. Create a weighted decision matrix to help us make an objective choice. Assign a weight (out of 100) to each criterion based on its importance to the project, score each option against the criteria, and calculate the final weighted score to recommend the best path forward.
18. The Scope Creep Triage Protocol
A stakeholder has just submitted a new request: [Describe the new feature or change request]. This was not in the original scope. Create a "Scope Creep Triage Protocol" that I can use to evaluate this request. The protocol should be a checklist of questions I need to answer, covering: 1. **Alignment:** Does this align with the core project objectives? 2. **Impact Analysis:** What is the estimated impact on timeline, budget, and resources? 3. **Value Assessment:** What is the ROI or business value of this change? 4. **Dependency Check:** Does this create new dependencies or risks? Based on the answers, provide a framework for categorizing the request as "Accept & Reprioritize," "Defer to Phase 2," or "Reject & Justify."
19. The Critical Path Analysis Scenario
Analyze the following sequence of project tasks and their durations: - Task A (5 days) -> Start - Task B (7 days) -> Depends on A - Task C (3 days) -> Depends on A - Task D (4 days) -> Depends on B - Task E (6 days) -> Depends on C - Task F (3 days) -> Depends on D and E Identify the Critical Path for this project and calculate the minimum project duration. Now, assume Task B is delayed by 3 days. What is the new Critical Path and the total project delay? Explain the concept of "float" or "slack" in relation to Task C.
20. The Burn-Down Chart Anomaly Interpreter
I am looking at my Agile project's burn-down chart. Describe three common but problematic patterns I might see, and for each pattern, explain the likely underlying cause and suggest corrective actions. 1. **The Plateau:** The line is flat for several days. 2. **The Cliff Drop:** The line drops vertically near the end of the sprint. 3. **The "Burn-Up":** The remaining work line is actually going up.
Category 5: Project Closure & Career Growth
21. The Lessons Learned Facilitation Guide
Design a framework for a "Lessons Learned" document based on a recently completed project: [Project Name]. The project's outcome was [e.g., successful but over budget, a failure, delivered on time with high team stress]. The framework should capture not just what went wrong, but also what went right and why. Create sections for: - Project Performance vs. Baseline (Scope, Schedule, Budget) - Key Successes & Contributing Factors - Major Challenges & Root Causes - Analysis of Risk Management Effectiveness - Actionable Recommendations for Future Projects (Categorized by Process, People, Technology)
22. The Project Handover Checklist
I am transitioning a completed project, [Project Name], to the ongoing operations/maintenance team. Generate a comprehensive handover checklist to ensure a smooth transition and no dropped knowledge. The checklist should be organized into categories like "Documentation," "Technical Access & Credentials," "Key Contacts & SMEs," "Recurring Processes," and "Open Issues/Known Bugs."
23. The “Quantify My Impact” Resume Builder
Act as a career coach for project managers. I just completed a project with the following details: - **Project:** [Project Name and goal] - **Budget:** [$X] - **Team Size:** [Y people] - **Timeline:** [Z months] - **Outcome:** [Describe the outcome, e.g., "Launched on time, resulting in a 15% increase in user engagement"] Translate these facts into 3 powerful, quantified resume bullet points using the STAR (Situation, Task, Action, Result) method. The bullet points should highlight my leadership, financial acumen, and impact on the business.
24. The Professional Development Path Generator
I am a Project Manager with [X] years of experience using [methodology, e.g., Waterfall]. I want to transition to a role that requires expertise in [new skill, e.g., Agile/Scrum at scale, Program Management, or managing AI/ML projects]. Create a 3-month professional development plan for me. Include recommendations for certifications (e.g., PMP, CSM, SAFe), key books or blogs to read, online courses to explore, and practical ways I can apply these new skills in my current role.
25. The “Elevator Pitch” for My Project
My project, [Project Name], is complex. I often struggle to explain it concisely to executives or stakeholders in other departments. Synthesize the following information into three compelling elevator pitches: - **Project Goal:** [What it aims to achieve] - **Problem It Solves:** [The pain point it addresses] - **Key Stakeholders:** [Who it benefits] - **Current Status:** [One sentence on progress] Generate three versions: 1. A 30-second version for a true elevator ride. 2. A 60-second version with more detail on the business value. 3. A version framed as an exciting opportunity for a potential new team member.