My mechanical engineering is sitting in a box somewhere in my parents’ house. Nobody in that program ever mentioned Gantt charts, stakeholder management, or what to do when two directors want opposite things by Friday. It wasn’t even really the plan. But somewhere between engineering and where I am now, 20 plus years and more certifications than I probably needed, I became a project manager. Not because I decided to but because somebody needed one, and I happened to be standing there.
If that sounds familiar, you’re probably an accidental PM too. And I want to talk about what actually gets you through the first couple of years, because it’s not the stuff in the textbooks.
How it actually happens
Nobody wakes up at 22 and says “I want to manage projects.” It’s usually smaller than that. You’re the person who remembers the deadline. You’re the one who notices two teams aren’t talking to each other. You send the recap email nobody asked for, and it turns out to be useful. Then one day someone says, “hey, can you just own this,” and you say yes because saying yes is easier than explaining why you shouldn’t have to.
That’s roughly how it happened for me. I’d made the jump from mechanical engineering into IT through a postgrad program, mostly because the work looked more interesting than what I’d trained for. I wasn’t chasing a PM title, I was just decent at keeping track of things, and in IT that gets noticed fast. Most technical teams are drowning without someone doing exactly that.
So I got handed a project. Then another. At some point the job title finally caught up to what I was already doing.
Nobody tells you about the first six months
Here’s what surprised me: the actual job has almost nothing to do with the Gantt chart. It’s a translation. You’re standing between a developer who thinks in tickets and a VP who thinks in quarters, and your entire job is making sure those two people are actually talking about the same thing without either of them noticing how different their languages are.
You don’t learn that from a template. You learn it by getting it wrong, by walking into a status meeting with a plan that made perfect sense to you, watching six people nod without understanding a word of it, and finding out three weeks later they built the wrong thing because of it.
The other thing nobody tells you is that you will spend a huge amount of your time being the person who says “I don’t know, but I’ll find out.” Early on that felt like a weakness. Twenty years in, I know it’s the opposite. The PMs who pretend to have every answer are the ones nobody trusts by month three.
The moment it stopped being an accident
For a while I treated the PM part of my job like a detour from what I’d actually trained to do. That changed once I’d sat through enough failed projects, mine and other people’s, to notice a pattern. The ones that fell apart almost never fell apart because of technology. They fell apart because nobody managed the people, the expectations, or the risk sitting quietly in the corner that everybody had agreed not to talk about.
That’s when I stopped treating this as something I’d fallen into and started treating it as a craft worth getting good at. I got my PMP. Then a Scrum Product Owner certification, then a Scrum Master one, because I wanted to understand delivery from both the plan-driven side and the agile side instead of picking a religion and defending it forever. None of that made me a better PM on day one. What it did was give me language for things I’d already been doing on instinct, which made it a lot easier to teach the same things to someone else later.
The trap that gets most of us early
For the first year or two I confused being busy with being useful. Back-to-back calls, a color-coded tracker nobody but me looked at, status updates sent at 11pm to prove I was on top of things. It felt like progress. It wasn’t. I was managing the appearance of control instead of the actual risk sitting inside the project.
The wake-up call is usually the same for most people. A project that looked green on your tracker for weeks blows up anyway, and you realize the tracker was never the thing keeping it alive. What was actually happening, the quiet disagreement between two leads, the vendor that had gone dark, the requirement everyone interpreted differently, was never going to show up as a status color. You have to go looking for it on purpose, before it finds you.
Once that clicked, I stopped optimizing for looking organized and started optimizing for knowing what was actually true. Those turned out to be very different jobs, and only one of them matters.
What actually gets you through
If I were sitting across from someone who’d just been handed their first project, no training, no warning, just “can you own this,” here’s what I’d actually tell them. Not the version that goes in a certification prep book.
Ask more questions than feels comfortable, especially in your first few weeks. That’s when you have permission to sound like you don’t know anything. Use it while it lasts, because six months in, that permission is gone. And write things down, then send it back to people, not because you don’t trust anyone, but because half the conflict that shows up later in a project started as two people quietly assuming different things in a meeting neither of them took notes in.
Find the person who’s been at the company the longest and buy them coffee. They know where the real risks are, and it’s never in the project charter. When you’re running a meeting, learn to sit with silence instead of rushing to fill it, because the awkward pause after “does this work for everyone?” is usually where the actual problem surfaces. And protect your team from the noise before it reaches them. Not everything happening upstairs needs to become their emergency too.
None of that shows up on a certification exam. All of it is the actual job.
A quick gut check
You might be an accidental PM if a few of these sound like you. You didn’t apply for this role, it found you. You’re better at reading a room than reading a project plan, and you feel a little guilty about that. You’ve said “let me circle back on that” specifically to buy yourself time to figure out what’s actually going on. You’ve laughed, cried, or both in a parking lot after a launch.
If two or three of those landed, welcome. You’re in the right place. This blog is going to be the thing I wish someone had handed me back when I was faking my way through my first status meeting: real situations, what actually worked, what blew up in my face, and the parts of this job nobody puts in a slide deck.
What’s your accidental PM story, how did you end up here? Drop it in the comments, I read every one.
