Project managers leave, initiatives get reshuffled, budgets get tighter—but when PM transitions are announced, we act surprised every time.
Inevitably, when these “emergency” transitions are announced, we have just weeks or days to make the switch. Months of context compressed to a few hurried days of meetings.
Usually, with a high-stakes deadline looming around the corner.
Which makes me wonder: Why are we still so bad at project hand-offs—and what would it look like to design for the reality we actually face?
Disruption We Pretend is Unusual
Last year, I had a front-row seat to five sudden PM switches.
One project was canceled. Another switched from an external PM to an internal one. And following layoffs, several companies had to make up ground by bringing in contractors.
None of this is rare. And none of it should surprise anyone who’s worked in project delivery for more than a few years. And yet, every time it happens, it still triggers a scramble—as if this were an unfortunate interruption to “normal” operations.
We like to tell ourselves that change is constant. But if you look at how most PMOs actually operate, it’s clear we don’t really believe that.
Clearly, there’s a gap between what we know intellectually and what we design operationally—and that gap shows up most clearly when someone has to step into a project cold.
Here’s what it usually looks like:
- Incoming PMs trying to reconstruct context from calendars, inboxes, and half-familiar artifacts
- For months, status meetings become “explain to the PM what is happening” instead of spaces to solve problems
- Risks go unnoticed for weeks because the PM is still figuring out where the landmines are
- Stakeholders (and the team) lose confidence, even when the PM is competent—a first impression that’s hard to undo later
The Two-Week Fantasy
Best-case scenario, you make the PM switch yourself and have time to orchestrate a long transition. In the next-best case, a PM leaves or is moved and gives two weeks’ notice.
And when you look at what we expect to happen in those two weeks, it feels absurd. In that window, the incoming PM is supposed to:
- Understand the nature of the project, based on an explanation drowning in acronyms and shorthand
- Figure out where the project really is—from reading old status reports
- Make sense of a schedule they didn’t build, using assumptions they didn’t make
- Learn your org’s PM/PPM systems
- Comb through someone else’s notes, logs, folders, and tools—often without knowing what matters most
- Meet the team and key stakeholders
- Sit in on recurring meetings and somehow understand the history behind them
- Learn how this PMO actually works (not how it works on paper)
This isn’t even remotely realistic—especially when the outgoing PM is still trying to close out their own work, attend meetings, and be helpful at the same time.
The truth is that we’ve normalized an impossible expectation: that someone can absorb months of nuance, relationships, and judgment calls in a couple of weeks—and then perform as if they’ve been there all along.
When that doesn’t happen, we treat it as an individual shortcoming.
That isn’t fair to the incoming PM or the team.
Why PMOs Get Caught Flat-Footed
If this pain is so predictable, why does it keep repeating?
A few reasons show up almost everywhere I work:
- Priority gravity. Live issues, deadlines, and stakeholder demands always outrank preparation for a hypothetical future transition.
- Normalcy bias. We know portfolios are fluid, but we plan as if today’s configuration will hold—at least for this quarter.
- Low immediate value. Transition prep rarely helps a PM with today’s work, so it’s easy to defer.
- High perceived effort. Anything that smells like “extra documentation” gets quietly deprioritized when capacity tightens.
These responses are rational reactions to current systems.
The problem is that these same forces all but guarantee we’ll be underprepared when disruption shows up—which is why every transition is 10x harder than it should be.
What Actually Works: A Low-Lift Way to Protect Your Projects
As external consultants, my teams move off and on projects (and entire client sites) all the time. For that reason, we’ve had to become quite good at it. Here’s what we’ve learned actually works.
(Note that the approach below is an analog solution. AI is making hand-offs radically easier. Keep reading to see how LLMs and AI agents can make quick work of transitions, depending on your available tech stack.)
You need two simple tools ready to be completed as soon as a transition is announced.
Tool 1: Project Field Guide
This is a short, practical orientation document for someone brand new. It pulls together the most important elements of your project artifacts into one coherent narrative.
And it isn’t something PMs have to maintain continuously (though AI agents can do that for you). Instead, it sits in reserve until a transition is announced.
When that happens, the outgoing PM completes it—typically in two focused hours or less—using existing documentation.
A good Field Guide answers four concrete questions:
- What is this project? Its scope, a short history of how it got here, and where it truly stands right now.
- Who’s involved? Key stakeholders, vendors, decision-makers, and who influences what.
- How does the work run? How schedule, scope change, budget, risk, and status are managed—and where key artifacts can be found.
- What language does this project use? Acronyms, jargon, and shorthand that only make sense once you’ve been around for a while.
Tool 2: Transition Agenda
This is a simple, time-based checklist for walking someone into the project once the handoff begins. This can be reused across transitions and adjusted to fit the time you have. The best ones I’ve seen follow a strategic arc:
- Day 1: Orientation. Big picture. Introductions. Where things live. What not to touch yet.
- Week 1: You watch, I do. Observe meetings, decisions, and rhythms without owning outcomes.
- Week 2: You do, I watch. Start leading, with real-time feedback while the stakes are still manageable.
The agenda gives shape to a limited overlap time. It replaces improvisation with shared expectations.
Together, these two tools work because they’re designed for reality.
The PMO does the upfront thinking once.
The PM does a short, focused burst of work when it actually matters.
That’s what makes this approach low-lift. You’re not asking PMs to prepare endlessly for hypothetical futures. You’re making sure that when disruption shows up—as it inevitably will—the team isn’t starting from zero.
I’ve Made This Easy For You:
If you want to try this without overthinking it, I’ve included templates for both tools that you can steal and adapt for your own PMO.
Grab them here
How AI Can Make Transitions Even Easier
Used well, AI can reduce the scramble that comes with project handoffs—but it works best when a few fundamentals are in place:
- Clearly and consistently labeled documentation (i.e., file naming, document titles, short “purpose statements” at the top of the doc) helps AI understand what it’s looking at.
- Basic hierarchy rules define which documents are authoritative when things conflict. (For example, if a status report is different from your issues log, what wins?)
- Meta-documents (like an acronym list for company-specific terminology) improve interpretation.
- Clean space where AI can access only what you want it to, without the clutter of archived or irrelevant documentation.
It’s also worth noting that many PPM tools are beginning to build this capability directly into the platform—streamlining data and document hygiene, improving retrieval, and fine-tuning models and agents—so this kind of support is becoming easier to access over time.
With that context, here are three ways AI can help during a real transition, from simplest to most advanced.
Option 1: Use an LLM to draft the Field Guide during handoff
When a transition is announced, the outgoing PM uses an AI chat tool to draft the Project Field Guide from existing artifacts, the template, and information provided in the prompt. The PM edits for accuracy and judgment, but avoids starting from scratch. This compresses hours of summarizing into a much smaller window when time is limited.
Option 2: Use an agent to periodically update the Field Guide
In this approach, an AI agent drafts an updated Field Guide on a set cadence using current project artifacts and guidance from the PM. The PM reviews it for accuracy and provides feedback that helps the agent improve over time, while also using the document to periodically step back and see how the project’s story is evolving. If a transition happens, there’s already a recent, coherent snapshot ready to go.
Note: Many organizations are still not granting AI access to document libraries and/or don’t have technology enabled to build custom agents. These have to be in place for this to work, but expect this functionality to be widely available to the average non-technical user within the next year or two.
Option 3: Use an agent to support the incoming PM beyond the handoff
Here, the agent goes beyond producing the Field Guide and also acts as a support resource for the incoming PM even after the original PM is gone. It can answer questions, explain terminology, surface relevant documents, and provide historical context after the outgoing PM has rolled off.
AI won’t fix poor handoffs on its own. But when it’s paired with a clear handoff design, it can remove just enough friction to make good transitions achievable—even when time is short, and disruption is unavoidable.
If You Only Do One Thing
Don’t roll out a new process. Don’t ask your PMs to do anything differently—yet.
Just download the tools and have them ready to share with your team.