The first three things I’d focus on as an accidental project manager

Most people use “accidental project manager” to describe how they got into the role.

There's a very common thread among project managers: we found our way into the role through another career path. I should know because I’ve experienced it. Project management work shows up, someone needs to hold things together, and before long you’re doing PM work without ever having planned to.

But there’s another kind of accidental project management that doesn’t get talked about as much. It’s what happens when an experienced PM is dropped into a project midstream. Another PM leaves unexpectedly (or is fired, laid off, quits...you pick the saucy scenario). The work, of course, is already in motion, so you step in and feel like decisions exist without much context, the budget is uncomfortably tight and was likely "mismanaged," the timeline is optimistic and out of date, and the client is uneasy before you’ve even said hello.

I’ve actually spent a lot of my career in that second category.

One moment stands out clearly. A PM on my team left the company with no notice, and I was asked to step into a big, messy project that was already over budget, running late, and surrounded by confusion and other frustrated emotions. There was no handoff or time for a good briefing—just a lot of history, a frustrated client, and a team doing their best under the circumstances.

It was not fun.

That situation, and many others like it, taught me something important. When you step into a project like this, the instinct is to move fast, fix things, and restore confidence. But urgency can push you into action before you understand the situation you’re actually dealing with.

Over time, I’ve learned that a few priorities consistently make these moments easier to navigate, and harder to make worse. They’re about how you show up to the work before you start changing it.

Here are the first three things I’d focus on.

Get grounded in what kind of project you’ve inherited

On that project, my first assumption was that everything needed fixing. The budget was off. The timeline was strained. The client was unhappy. It all pointed to execution problems.

But once I slowed down enough to really look at the situation, the pattern became familiar. The project plan looked reasonable on paper, but no one could explain why certain dates were locked. A key dependency kept coming up in conversations, yet no one was actually tracking it. Decisions were being referenced in meetings (“we already agreed on this” felt like the chorus to a song), but when I asked where that agreement lived, the room went quiet. Different stakeholders were using the same words to mean very different things, and everyone assumed someone else had made the final call.

The work was moving, but it wasn’t aligned.That’s when it became clear that the real issue wasn’t delivery. The project had never been properly anchored. Things hadn’t gone wrong so much as they had never fully settled.

Until you understand whether you’re dealing with unanchored work, inherited decisions, accumulated mess, or a project under real strain, you can’t choose the right kind of leadership. Taking the time to understand the terrain allows you to lead with intention rather than reacting to whatever allows you to lead with intention rather than like the top priority.

Create shared understanding before pushing for momentum

Early on, there was pressure to project confidence. The client wanted reassurance, and the team wanted clarity. In the end, everyone wanted to feel like things were finally under control. I mean, isn't that what we always want?

The temptation in those moments is to prioritize speed. Keep meetings moving. Lock plans quickly. Show visible progress. But speed without shared understanding was exactly what had gotten the project into trouble in the first place.

What helped most wasn’t a new plan or a more detailed status update. It was slowing conversations down just enough to surface where meaning had drifted. What did “done” actually mean at this stage? Which decisions were real, and which were assumed? What outcomes were people optimizing for without realizing it?

One well-placed clarifying question often did more to stabilize the work than hours of coordination.

Asking those questions builds confidence and gives people a chance to align on what they’re actually working toward before more work piles on top.

Make the invisible project work visible

When I stepped into that inherited project, I was carrying an enormous amount of context in my head just to keep things from unraveling further: half-made decisions (abd lots of dissenting opinions), dependencies no one clearly owned, and risks everyone felt but hadn’t really acknowledged yet.

That cognitive load adds up quickly. It exhausts PMs and quietly turns them into bottlenecks.

One of the most effective moves I made was getting that invisible work out of my head and into a shared space. Not heavy documentation, but just enough structure to separate what was actually decided from what was still open, and to make real tradeoffs visible to the people affected by them. I made that in a spreadsheet and in a Google doc. I figured it needed to be readable and translatable by everyone, so I'd show two formats.

That move didn’t just help the project. It reduced stress across the team and made it easier to rebuild trust with the client.

What I realized in that moment was that while it can feel like writing things down is heavily bureaucratic, it’s actually how you stop being the single point of failure.

What this actually gives you

None of these priorities made me look impressive in the moment. They didn’t magically fix the budget or erase the timeline issues overnight.

What they did was reduce panic, create shared footing, and give everyone—including me—room to think more clearly. That’s what this version of accidental project management often requires: steady judgment applied in the right order.

If you’re stepping into a messy project right now, you’re not behind. You’re doing leadership work in conditions that rarely come with clean beginnings. Focusing on understanding the situation, creating shared meaning, and making the work visible gives you a foundation to lead without burning yourself out trying to fix everything at once.

T L : D R - If you’re stepping into a project midstream, resist the urge to fix everything immediately.

Take time to understand what kind of project you’ve inherited, slow conversations down enough to create shared understanding, and get critical context out of your head and into the open.

These moves may not feel dramatic, but they’re what allow real leadership to take hold.