What I wish someone had told me when I became a project manager

I technically became a project manager because someone saw it in me before I saw it in myself. But the truth is, I had been doing project management for years.

I started in editorial working at a startup (I was 21 in the midst of the dot com boom), juggling deadlines, writers, revisions, and impossible expectations. Eventually, I moved into agency account management, where I was translating client requests into something the team could actually execute. I was managing scope, negotiating tradeoffs, smoothing over tension, and quietly protecting the work from chaos.

No one called it project management there, but that’s what it was. In fact, I'd say I'm an accidental project manager.

When I was recruited into my first formal project manager role, I felt behind. I assumed that “real” project managers had some kind of training I had missed. That they understood things in a way I didn’t, or at least felt confident in rooms where I was still figuring out what to say.

Looking back, there are a few things I wish someone had told me then.

1. You are not starting from zero

If you became a PM by accident, it’s usually because you were already operating like one.

You were connecting dots, asking the question that slowed the room down just enough to avoid a bad decision, and probably noticing misalignment before it turned into fallout.

The title doesn’t create that instinct. It makes it visible. So, you’re not starting from scratch! You’re formalizing something you were already doing intuitively.

2. You don’t need to feel ready

For a long time, I thought confidence would come from more structure, more training, or more certainty. I thought there would be a moment where I’d feel fully equipped.

That moment never really arrived.

What actually builds confidence is experience. Repetition. Being in hard conversations that don’t go perfectly. Sitting in meetings where you have to say, “I’m not sure we’re solving the right problem.” Navigating scope conversations that make your stomach tighten a little before you speak.

Over time, those moments build something more useful than certainty. They build judgment. Confidence in this role comes from recognizing patterns and trusting yourself to respond thoughtfully instead of reactively.

You don’t need to feel ready. You need reps.

3. Speed is not leadership

Early in my career, I thought my value was in being fast.

I responded immediately. I solved things before anyone asked. I kept conversations moving because it felt productive.

Sometimes it helped. Other times, I was solving the wrong problem because I hadn’t slowed down long enough to understand what was actually happening.

Not every project needs acceleration. Some projects need stability. Some need containment. Some need someone willing to pause and say, “Before we move forward, let’s make sure we’re aligned on what this actually is.”

That moment of pause is leadership. It requires more restraint than speed ever will.

4. Boundaries are part of the job

I used to think being collaborative meant absorbing whatever came my way.

If a deadline was unrealistic, I would quietly try to make it work. If expectations were vague, I would fill in the gaps. If tension rose, I would carry it.

That approach can look helpful for a while, but it also trains everyone around you to rely on your flexibility instead of their own accountability.

Being a strong PM means holding the line when it matters, asking for clarity instead of compensating for its absence, and protecting the team from churn that could have been avoided with one uncomfortable conversation.

Boundaries aren’t friction. They’re part of how the work gets done well.

5. You are shaping how work feels

This is the part I didn’t understand at all when I first became a PM. I thought I was there to manage tasks, timelines, and deliverables. I didn’t realize that the way I facilitated meetings, clarified expectations, and responded to tension was quietly shaping how people experienced the work.

Project managers influence whether pressure turns into panic or settles into focus. They influence whether conflict gets avoided or addressed. They influence whether expectations stay fuzzy or become clear. And most people step into that responsibility without being taught how to handle it.

In many environments, the role isn’t fully understood or respected. You might feel like you don’t quite fit. You might sense that the team doesn’t fully understand what you do. Sometimes you’re still figuring it out yourself. That makes it easy to question how much impact you’re actually allowed to have.

But culture isn’t shaped by titles! It’s shaped by behavior. It’s shaped by the person who asks the extra clarifying question, who slows the room down, who doesn’t let tension sit unspoken.

If someone saw potential in you and asked you to step into this role, it probably wasn’t random.It means you were already steady under pressure and already uncomfortable with ambiguity left unaddressed.

The title didn’t create that impact. It gave it structure.

You grow into this role

There isn’t a moment where you arrive and suddenly feel like a fully formed, confident project leader. I’ve been doing this for a long time, and I still learn something new every time I navigate a complicated stakeholder dynamic or hold a tense conversation that could have gone sideways.

This role is something you grow into...continuously. By practicing, reflecting, and by noticing where you reacted too quickly and where you held steady, and truly by staying in the room when it would be easier to step away (and oof, that is the toughest part sometimes!).

If you became a PM by accident, there’s nothing wrong with that origin story. In many ways, it’s the most common one. You don’t have to pretend you planned this career. You just have to keep getting better at it.

T L : D R - If you became a PM by accident, you were probably already doing the work before anyone gave you the title. You don’t need to feel ready. You need experience.

Leadership in this role is judgment, not speed. And whether you realize it or not, you influence how work feels for the people around you. There’s nothing accidental about that.