At some point in your public sector career, someone says, “Can you help move this forward?”

It usually doesn’t come as a clear assignment. It shows up as a meeting invite, a half-formed idea, a deadline that already slipped, and the line you’ve heard a hundred times: we just need someone to pull it together (translation: you).

A week later, you find yourself chairing meetings, drafting the executive update, tracking decisions, and chasing inputs across teams without the power to clear the roadblocks (but with a calendar full of them).

You’ve become the project manager. Not by title, but by default.

And you still have to do the job you were hired to do. That’s the accidental project manager - the person who turns a messy situation into a plan because the work can’t wait.

Why this keeps happening

Public sector work is complicated: shared ownership, changing priorities, and work that crosses teams. When no one clearly owns the work, someone still has to pull it together—so a reliable person steps in and starts project-managing it, often without training.

What accidental project managers get right

Accidental project managers build real skills. They lead without formal authority, turn unclear direction into a simple plan, and keep work moving when attention shifts to the next urgent file. That’s leadership.

The problem with leaving things informal

Here’s the problem: the expectations are high, but organizations don’t always provide the support. You’re responsible for timelines and updates without the authority, time, or help you need to fix what’s stuck—so you end up doing project management by vibes.

In practice, that means chasing updates you can’t enforce, running “alignment” meetings where no one can decide, and keeping key risks and dependencies in your head.

The organization pays a price too. When every project is run differently, teams lose track of decisions and leaders don’t get the clear updates they need.

So, how can we make our accidental roles better and more predictable?

I’ve been the accidental project manager more times than I can count. For a long time, I tried to borrow “official” project guidance and scale it down, and I wasn’t sure if I was doing it right. Later, when I did my PMP, I realized my instincts were solid—and the basics really do work.

If you can get these basics clear up front, you’ll save time, reduce stress, and make it much easier to deliver.

  • One-page brief: what we’re doing, why, and what “done” looks like.
  • Clear roles: who decides, who does the work, and who needs to be consulted.
  • Simple schedule: key dates, dependencies, and the next milestone.
  • One tracking place: decisions, risks, and blockers (plus a clear way to escalate).

If you’re the accidental project manager right now, this is your way to ask for what you need. Put the one-pager, roles, schedule, and decision/risk tracking in front of your team or director and say: “This is how I can deliver—if we agree on this, and if I have time to run it.”

That ask can be simple: confirm who makes decisions, set a basic cadence for check-ins, agree on what counts as “done,” and name how you’ll escalate issues. You’re not asking for more process—you’re asking for fewer surprises.

If you’re doing this work without the title, you’re not alone. Start with these basics—and use them to ask for the clarity, decisions, and time you need to deliver.

 If this sounds like you, share your story—and your best tip—for the next accidental project manager.