Transition Plan: Maintaining an updated transition plan is crucial for project continuity after a core member departs.
Risk Assessment: Conducting a rapid risk audit is essential to identify potential blockers before replacing a team member.
Replacement Strategy: Decide whether to replace a departing PM or continue without one, based on documentation quality.
Familiarity Advantage: Utilizing familiar talent for replacements can ease transitions, but adequate resourcing remains necessary.
Systematic Staffing: Implementing an efficient staffing system helps quickly fill vacancies without creating chaos.
A project manager quitting mid-project is one of the most disruptive things that can happen. The instinct is to panic — but experienced leaders have a playbook. Here's what they actually do first, and why preparation before the crisis matters just as much as the response during it.
Pull Out the Transition Plan — If You Have One
The single most important move when a core team member walks out the door is knowing where your documentation stands. For Bill Dow, Director of Enterprise PMO at UW Medicine, that means going straight to a transition plan that should have been kept current all along. "Every PM has to have a transition plan no matter what," Dow says, adding that "a transition plan is the first place I go, which is why I always make sure they are up to date." In his experience, when a PM leaves mid-project under any circumstances, having that plan ready to go means a successor can immediately understand the project's status and locate key documents — no scrambling required.
Every PM has to have a transition plan no matter what. It’s the first place I go.
Immediately Assess Risk and Uncover Hidden Blockers
Before you even think about who's going to fill the empty seat, the smartest move is a rapid risk audit. Nalini Vadivelan, Sr. Principal Technical Program Manager at Oracle, tells us where her head goes first: "If a project manager leaves mid-project, the number one thing is to ask, 'Is there anything that is a huge risk to the project?' Just find out. Are there any blockers? You need to find out and manage those risks." The goal isn't to assign blame — it's to surface anything that could quietly derail the project if left unexamined.
If a project manager leaves mid-project, the number one thing is to ask, ‘Is there anything that is a huge risk to the project?’ Was there any blockers? You need to find out and manage those risks.
Decide Whether to Parachute in a Replacement or Keep Going
Once you've done that initial risk sweep, leadership faces a fork in the road. Vadivelan frames it plainly: "the two options that you have are: parachute someone new into this project, or keep the project going without the PM." The deciding factor, she notes, often comes down to how disciplined the departing team member was in their tracking habits — "if the tracking was well done, I think any other PM who's roped in should be able to take forward from there." Good documentation doesn't guarantee a smooth transition, but without it, neither option is realistic.
Lean on Familiar Talent When You Can
When a replacement is needed, the best option isn't always a fresh face — sometimes it's someone already close to the work. Marissa Taffer, Founder and President of M. Taffer Consulting, describes one such scenario from her own experience: "One of the big projects I did it was because the PM ended up leaving, and I was already there doing some other work. They asked, 'Is there any way you would take this project back on? The context I already had helped a lot.'" But even with that context, the scope of the work still demanded backup — "when I did [come on], I still needed a second partner. The project was that big." The lesson: on large, complex projects, familiarity with the work is an asset, but it doesn't eliminate the need for adequate resourcing.
One of the big projects I did it was because the PM ended up leaving, and I was already there doing some other work. They asked, ‘Is there any way you would take this project back on? The context I already had helped a lot.
Move Fast on Staffing — With the Right System
When a seat goes empty, speed matters. But speed without a system just creates more chaos. Alexandria O'Bannon, Staffing Manager (Project Operations Manager) at JUMP! Foundation, has built a workflow specifically designed to compress the time it takes to identify and place available talent. "One of the biggest bottlenecks that I'm having is the time that it takes me to go through 300 or so things," she explains — so she streamlined the resourcing process entirely: "I put all my job listings that I have coming up [in a system], I click all the regions that I want to send people and it generates a list for me of who's available in what countries on what dates and I just staff it from there." The result is a rapid-response capability that turns what used to be a time-consuming back-and-forth into a near-instant match.
I put all my job listings that I have coming up [in a system], I click all the regions that I want to send people and it generates a list for me of who’s available
The Best Preparation Happens Before the Crisis
The common thread running through every one of these approaches is that the PMs who handle sudden departures best aren't reacting from scratch — they're executing a plan they've already built. Transition documents kept current, disciplined project tracking, staffing systems designed for speed: none of these things can be conjured in the moment a resignation lands. The best time to prepare for a core team member quitting is well before it happens. When that day comes — and eventually, it will — the difference between a minor disruption and a full-blown crisis often comes down to the work that was done long before anyone said goodbye.
Want more insights like these? Sign up for a free DPM account to hear from more experts like these.
