For the Working PM — Stephanie Urso, PMP
The Working PM

Tools & Skills for
the Field.

You passed the certification. Now build the career. This page is for PMs who are already in it — the AI tools saving hours every week, the books that change how you think, the soft skills no exam teaches, and the interview prep that lands the next role.

10
AI Tools Profiled
12
Books Every PM Should Read
40+
Interview Questions & Tips
For PMs in the field

AI Tools for Project Managers

AI won't replace project managers — but PMs who use AI will outperform those who don't. These are the tools worth your time, with the exact use cases that save real hours.

Writing & Communication
Claude
🤖
Anthropic's AI assistant — exceptional for long-form writing, document analysis, and nuanced stakeholder communications.
Best for:
  • Drafting executive status updates and project briefs
  • Summarizing lengthy requirements documents or vendor proposals
  • Rewriting risk narratives for different audiences
  • Generating meeting agendas and retrospective facilitation guides
Try this prompt
"Draft a status update for executive stakeholders. The project is 2 weeks behind due to a vendor delay. We have a recovery plan. Tone: transparent but confident. Keep it under 200 words."
Writing & Ideation
ChatGPT
💬
OpenAI's flagship model — fast, versatile, and excellent for generating options, brainstorming, and quick formatting tasks.
Best for:
  • Brainstorming project risks, mitigation options, or stakeholder concerns
  • Creating meeting agendas, email templates, and project naming conventions
  • Generating multiple versions of the same communication
  • Quick RACI drafts, decision logs, and sprint goal statements
Try this prompt
"Give me 10 retrospective questions for a team that just finished a high-pressure product launch. Mix prompts for what went well and what to improve."
Integrated Productivity
Microsoft Copilot
🪟
AI built directly into Teams, Word, Excel, Outlook, and PowerPoint — the most workflow-integrated option for Microsoft shops.
Best for:
  • Auto-summarizing Teams meeting transcripts with action items
  • Creating PowerPoint decks from bullet-point outlines
  • Drafting Outlook emails with full context from your calendar
  • Analyzing Excel project data and generating charts instantly
Try this in Teams
"Summarize this meeting, list all action items with owners, and flag any unresolved decisions."
Meeting Transcription
Otter.ai
🎙️
Real-time transcription that joins your Zoom and Teams calls automatically, detects action items, and builds a searchable meeting history.
Best for:
  • Capturing every decision and action item without taking manual notes
  • Searching across months of meeting transcripts for specific discussions
  • Sharing summaries with team members who missed the call
  • Creating an audit trail of project decisions
How to use it
Connect Otter to your calendar. After each meeting, open the transcript and ask: "What action items were assigned, and to whom?"
Meeting Intelligence
Fireflies.ai
🔥
Meeting recorder with AI-powered summaries, topic detection, and cross-meeting search — ideal for PMs managing multiple workstreams.
Best for:
  • Querying across all your past meetings ("What did we decide about the Q3 release?")
  • Auto-generating follow-up emails from meeting summaries
  • Tracking topic trends across recurring meetings
  • Integrating meeting data into your CRM or PM tool
Power feature
Use "Ask Fred" — Fireflies' AI — to ask questions across your entire meeting history. "What blockers have come up in the last 30 days?"
Documentation
Notion AI
📝
AI embedded inside Notion workspaces — write, summarize, and generate project documentation without leaving your source of truth.
Best for:
  • Writing and improving project wikis, onboarding docs, and SOPs
  • Summarizing long meeting notes into key decisions
  • Generating first drafts of project briefs and retrospective summaries
  • Brainstorming within documents without switching tools
Try this
Paste your project brief into Notion and prompt: "What risks is this project not accounting for? Give me five I should add to my risk register."
Smart Scheduling
Motion
An AI that automatically schedules your tasks around your calendar — and rebuilds your entire day when priorities shift.
Best for:
  • Automatically scheduling tasks with deadlines into your actual calendar
  • Recovering from a day of back-to-back meetings — Motion reschedules everything
  • Managing personal task load across multiple projects
  • Protecting time for deep, focused PM work
How to use it
Add all your tasks with deadlines and time estimates. Motion builds your daily schedule automatically and adjusts in real time when new meetings appear.
Presentations
Gamma.app
🎨
AI presentation builder that transforms bullet points and notes into polished, stakeholder-ready decks in minutes.
Best for:
  • Building executive status decks from raw project notes
  • Creating kickoff presentations and project overviews quickly
  • Producing visually clean retrospective summaries
  • Iterating on deck structure without starting from scratch
Try this prompt
"Create a 6-slide executive project status update. Include: summary, progress against milestones, budget status, top 3 risks, upcoming decisions needed, and next steps."
Async Communication
Loom
🎬
Record short video updates with AI-generated summaries and chapter markers — replace unnecessary meetings with async video.
Best for:
  • Replacing project status meetings with a 3-minute recorded walkthrough
  • Onboarding new team members to complex project context
  • Walking stakeholders through a dashboard or document async
  • Building a video library of project decisions and demos
Best practice
Record a weekly 3-minute project pulse video and share the link with stakeholders. Loom auto-generates transcripts — stakeholders can read or watch at their pace.
Calendar Management
Reclaim.ai
🗓️
Intelligent calendar management that protects focus time, auto-schedules tasks, and manages meeting habits automatically.
Best for:
  • Setting up "Deep Work" blocks that automatically defend against meetings
  • Auto-scheduling recurring tasks like weekly reviews and report prep
  • Finding optimal meeting times across your team without back-and-forth
  • Building calendar habits (exercise, planning, learning) that actually stick
Quick win
Set up a "Weekly Project Review" habit for 60 minutes every Friday afternoon. Reclaim defends it from meeting requests and reschedules it if Friday fills up.
💡
The PM's AI stack, simplified: Use Claude or ChatGPT for writing and thinking. Use Otter or Fireflies to capture meetings. Use Motion or Reclaim to protect your time. Use Gamma or Loom to communicate visually. You don't need all of them — start with one from each category and see what sticks.

Books Every PM Should Read

Not theory for its own sake — books that change how you actually work. These are the ones worth your time, organized by what they'll teach you.

S
Agile · Scrum
Scrum: The Art of Doing Twice the Work in Half the Time
Jeff Sutherland
Written by the co-creator of Scrum. Explains the why behind sprints, retrospectives, and velocity through compelling real-world stories — not textbook definitions.
P
Leadership · DevOps
The Phoenix Project
Gene Kim, Kevin Behr & George Spafford
A novel about an IT organization in crisis. You'll recognize every character. Essential for tech PMs — it reframes how IT work, flow, and constraints actually function.
M
PM Fundamentals
Making Things Happen
Scott Berkun
The most practical PM book ever written. Berkun draws from years at Microsoft to cover how projects actually get delivered — candid, specific, and immediately useful.
C
Communication
Crucial Conversations
Patterson, Grenny, McMillan & Switzler
The PM's guide to difficult conversations — with executives who move goalposts, resistant stakeholders, and teammates in conflict. A framework you'll use constantly.
F
Team Leadership
The Five Dysfunctions of a Team
Patrick Lencioni
A business fable revealing why even talented teams underperform. Trust, conflict, commitment, accountability, results — the pyramid every PM needs to understand.
D
Motivation
Drive
Daniel Pink
The science of what actually motivates people — autonomy, mastery, and purpose. Read this and you'll manage your team completely differently. Career-changing for servant leaders.
R
Feedback & Culture
Radical Candor
Kim Scott
The framework for caring personally while challenging directly. The best book on giving feedback — the skill PMs are expected to have but rarely taught. Practical and honest.
L
Agile · Innovation
The Lean Startup
Eric Ries
The Build-Measure-Learn loop applies far beyond startups. Every PM managing iterative delivery needs this framework — it makes the case for why we work in sprints at all.
T
Leadership
Turn the Ship Around!
L. David Marquet
A Navy submarine captain transforms command-and-control leadership into "leader-leader." One of the most powerful books on empowerment and servant leadership ever written.
D
Productivity
Deep Work
Cal Newport
In a world of constant meetings and Slack pings, Newport's case for focused, uninterrupted work is revelatory. PMs who protect thinking time make better decisions.
T
Decision Making
Thinking, Fast and Slow
Daniel Kahneman
Nobel laureate Kahneman's deep dive into cognitive bias and decision-making. PMs who understand System 1 vs System 2 thinking make better choices under pressure and tight deadlines.
T
Process · Execution
The Checklist Manifesto
Atul Gawande
A surgeon's case for the profound power of simple checklists in complex, high-stakes environments. Deceptively simple, deeply applicable — and it will make you rethink your PM processes.

Soft Skills That Define Great PMs

The PMP tests your knowledge of frameworks. Real projects test your ability to lead, influence, communicate, and navigate people. These are the skills that actually determine whether your projects succeed.

Leading People
Servant Leadership in Practice
The exam describes servant leadership; working PMs live it. It means removing obstacles before your team hits them, defending your team's capacity from unreasonable demands, and measuring your success by your team's success — not your own visibility. Ask yourself daily: what is blocking my team right now, and what can I personally remove?
Managing Up
Your sponsor and leadership team need proactive communication, not surprises. Frame everything in business impact. When raising a problem, bring it with 2–3 options and your recommendation. Never just bring a problem. The PM who manages up effectively gets budget, resources, and cover when things go sideways.
Giving & Receiving Feedback
Use the SBI model: Situation → Behavior → Impact. Make feedback timely, specific, and for negatives — always private first. Build a culture where feedback flows in both directions. The best PMs actively seek critical feedback about their own leadership and use it. When you model vulnerability, your team follows.
Conflict Resolution
Conflict is normal. Avoiding it is the problem. Address friction early — it compounds. Listen to all sides before forming conclusions. Focus on the issue, not the person. Find shared goals to anchor the resolution. Document what was agreed. Escalate only when the team cannot resolve it themselves — and when you do, escalate with a recommendation, not just a complaint.
Emotional Intelligence Under Pressure
Projects create pressure. PMs who can stay regulated under stress — who don't visibly panic during scope changes or deadline pressure — create psychological safety for their team. Identify your own triggers. When you feel reactive, pause before responding. The way a PM behaves when things go wrong sets the team's entire emotional tone.
Influence & Communication
Influencing Without Authority
PMs rarely have formal authority over their team members. Influence comes from credibility, relationships, and framing. Know what each stakeholder cares about and connect your requests to their goals. Build trust before you need to spend it. The PM who has relationships before the crisis has options during the crisis.
Stakeholder Management
Map stakeholders by power and interest. High power, high interest → manage closely. High power, low interest → keep satisfied. Low power, high interest → keep informed. Low power, low interest → monitor. No stakeholder should ever be surprised. Proactive communication prevents resistance. Resistance that's already formed is far harder to overcome than resistance that never develops.
Difficult Conversations
When you need to push back on scope, deliver bad news, or address underperformance: lead with facts, not feelings. Use "and" instead of "but" — "but" negates everything before it. "I understand the deadline is critical, AND here's what the current plan realistically delivers." Give the other person a way to save face wherever possible. Hard truths land better when delivered with care.
Active Listening
Most people listen to respond, not to understand. PMs who truly listen — who summarize back what they heard, ask clarifying questions, and resist filling silence — surface information that others miss. The stakeholder who feels heard is far more cooperative than the one who feels processed. In difficult meetings, repeat back: "What I'm hearing is..." before offering your own view.
Negotiation Fundamentals
Know the difference between positions ("I need this by Friday") and interests ("I need to show progress to my board by Monday"). Focus on underlying interests — that's where solutions exist. Know your BATNA (Best Alternative to a Negotiated Agreement) before every negotiation. Never give something without getting something. Scope, time, cost, and quality are all levers — use them explicitly when asked to compromise.

PM Interview Preparation

Whether you're moving from coordinator to PM, PM to Senior PM, or making a lateral move into a new industry — these are the questions you'll face and the frameworks that turn good answers into great ones.

The STAR Framework — Use this for every behavioral question
S
Situation
Set the context. Where were you, what was the project, what were the stakes?
T
Task
What was your specific responsibility or challenge in that situation?
A
Action
What did YOU specifically do? Use "I", not "we". Be concrete and specific.
R
Result
What was the outcome? Quantify wherever possible. What did you learn?
Pro tip: Prepare 6–8 detailed STAR stories before your interview. Most behavioral questions can be answered from the same core set of stories — just emphasize different elements depending on the question.
Behavioral Questions
"Tell me about a time a project went off the rails. How did you handle it?"
This is the most common PM interview question. Interviewers want to see self-awareness, problem-solving, and composure under pressure.
  • Don't hide the failure — they want to see how you faced it, not that everything always worked out
  • Show that you diagnosed the root cause, not just the symptom
  • Demonstrate stakeholder communication — who did you tell, when, and how?
  • End with a clear recovery plan and what you personally learned
"Describe a situation where you had to manage a difficult stakeholder."
This tests your EQ, communication, and influencing skills.
  • Don't make the stakeholder the villain — show empathy for their perspective
  • Explain how you listened first to understand their underlying concern
  • Show the specific action you took and why you chose it
  • Demonstrate relationship preservation even through disagreement
"Tell me about a time you had to make a decision with incomplete information."
PMs make ambiguous decisions constantly. This tests decisiveness and judgment.
  • Show your risk assessment process — what did you know vs. assume?
  • Explain how you documented assumptions so the decision was transparent
  • Demonstrate that you communicated the decision and its uncertainty to stakeholders
  • Show willingness to revisit the decision as new information emerged
"Tell me about a time you failed on a project. What did you learn?"
A test of self-awareness and growth mindset. Generic answers here kill candidacies.
  • Pick a real failure — vague or minor "failures" signal avoidance
  • Take personal accountability — don't blame the team, vendor, or circumstances alone
  • Articulate the specific lesson you took from it
  • Show how you applied that lesson on a subsequent project
"Give me an example of how you've influenced without authority."
Core PM competency — most PMs don't formally manage their team members.
  • Show how you built credibility and trust before the moment of influence
  • Explain how you framed your ask in terms of the other person's goals
  • Demonstrate patience — influence takes multiple touchpoints, not one conversation
  • Show the outcome — what changed because of your approach?
Situational Questions
"You inherit a project that's already 3 months behind. What do you do in your first 30 days?"
This tests structured thinking and stakeholder orientation.
  • Listen first — interview the team, key stakeholders, and the sponsor before forming conclusions
  • Audit the plan: scope, schedule, dependencies, risks, and team capacity
  • Identify the critical path and what is actually blocking delivery
  • Set a realistic recovery baseline — don't inherit someone else's optimistic schedule
  • Communicate your assessment to leadership within 30 days: here's where we are, here's the realistic path forward
"Your sponsor asks you to cut scope to hit the deadline. How do you handle it?"
Tests your understanding of the triple constraint and decision-making under pressure.
  • Clarify the trade-off explicitly: "We can hit the date if we reduce scope. Here is specifically what that means for the end product."
  • Present options — scope cut vs. timeline extension vs. cost increase — with the impact of each
  • Get the decision in writing. Scope changes agreed verbally disappear later.
  • Update the project charter and communicate the change to all affected stakeholders
"Two senior stakeholders have conflicting priorities. How do you resolve it?"
Tests escalation judgment and stakeholder management maturity.
  • First, meet with each separately to understand the underlying business need — conflicts are often about different goals, not the same goal differently prioritized
  • Bring data — what is the cost of prioritizing each option?
  • Facilitate a joint meeting if appropriate, with the goal of reaching a shared decision
  • If they cannot agree, escalate to the project sponsor with a clear recommendation — don't just hand the conflict upward, bring a proposed resolution
PM Process & Knowledge
"Walk me through how you build a project plan from scratch."
A structured answer demonstrates real PM competency. Cover: requirements gathering → scope definition → WBS → schedule → resource plan → risk register → communication plan → baseline and sign-off.
  • Mention stakeholder involvement at each stage — a plan built without input is a plan no one owns
  • Address how you handle assumptions and constraints explicitly
  • Talk about how you baseline the plan and manage changes from that point
"How do you manage scope creep?"
Every interviewer asks this. Stand out by going beyond "change control process."
  • Prevent it upstream: clear scope statement with explicit exclusions agreed at kickoff
  • When a change request comes in, analyze the impact on timeline, cost, and quality — never say yes immediately
  • Use a formal change log so every addition is visible and traceable
  • Teach stakeholders the cost of "just one more thing" — scope creep is often a communication and expectation problem, not a control problem
"How do you measure project health?"
Go beyond schedule and budget.
  • Schedule: % complete vs. planned, critical path status, milestone achievement
  • Cost: CPI (Earned Value ÷ Actual Cost) — anything below 1.0 means over budget
  • Quality: defect rate, rework rate, stakeholder satisfaction
  • Team: velocity trend, morale signals, attrition risk
  • Risk: open risk count, risk aging, new risks identified vs. mitigated
  • Use RAG status (Red/Amber/Green) for stakeholder reporting — keeps status visible and action-oriented
"How do you choose between Agile and Waterfall?"
The answer is: it depends on the project. Show that you understand both and when each applies.
  • Waterfall: fixed requirements, regulatory constraints, construction/manufacturing, low tolerance for change
  • Agile: evolving requirements, software products, need for frequent feedback, uncertain scope
  • Hybrid: fixed budget and deadline (Waterfall) but iterative delivery within phases (Agile)
  • The best answer shows you've used both and can articulate a specific decision you made and why
"How do you handle a team member who is consistently underperforming?"
Tests leadership maturity and willingness to have hard conversations.
  • Start by understanding the root cause: is it skill, motivation, unclear expectations, or personal circumstances?
  • Have a direct, private conversation early — don't let it fester
  • Set clear, measurable expectations with a specific timeline for improvement
  • Document the conversation and the agreed plan
  • If improvement doesn't follow, escalate to HR or your manager with documentation — don't carry the problem alone indefinitely
"How do you handle risks on a project?"
Go beyond "I maintain a risk register." Show a real risk management mindset.
  • Identify risks early and continuously — not just at kickoff
  • Score each risk: Likelihood × Impact = Risk Score. Prioritize the highest scores.
  • Assign a risk owner — not just the PM
  • For each risk: what is the mitigation (reduce likelihood)? What is the contingency (if it happens)?
  • Review the register at every status meeting. A risk register that isn't reviewed is just a document.
Questions to ask the interviewer — always come prepared with these
What does success look like in this role in the first 90 days?
What are the biggest challenges facing the PM team right now?
How mature is the project management practice here — is there a PMO?
How does leadership support PMs when they need to escalate?
What tools does the team use for project tracking and communication?
How are PMs supported in professional development and certification?
What does the relationship between PMs and engineering/product look like?
Can you tell me about a project that didn't go well and what the team learned from it?