First Week as Project Manager — What Actually Changed

I got the promotion. Project Manager, effective July 2025. After two and a half years as an Associate PM, I now own three concurrent programs ranging from $1M to $7M each, with 50+ engineers across onshore and offshore teams.

So what actually changed in week one?

The Obvious Stuff

The scope tripled. I went from managing one account with a tight-knit team to juggling three programs simultaneously. The budget conversations are different now. When you are responsible for $7M in program value, people expect you to speak in terms of ROI, burn rate, and delivery risk — not just sprint velocity.

My calendar immediately got heavier. Director-level stakeholders want weekly syncs. Client leadership wants monthly business reviews. The reporting cadence alone could eat your entire week if you let it.

What Stayed the Same

My philosophy did not change. I still believe PMs should understand the technical stack deeply enough to challenge estimates and spot risk early. I still run lean standups. I still build tools when existing ones fall short.

The Engineering Intelligence Platform I built as an Associate PM? Still running, still serving 300+ engineers, still the thing people mention first when they describe my work. That did not change with a title bump.

The Real Shift

The biggest change is not scope or budget. It is decision weight. As an Associate PM, I could escalate ambiguous calls. Now I am the escalation point. When an offshore team misses a milestone, when a vendor underperforms, when scope creep threatens a timeline — those decisions land on my desk.

I am learning to be comfortable with that weight. One week in, the learning curve is steep but the view from here is worth it. More to come as I settle into this role.