u/impossible2fix

I’ve been seeing a lot of posts lately from newer PMs asking things like “how do people actually survive this role?” or “does everybody feel lost all the time?” and honestly I relate to those posts way more than people probably expect.

I kind of drifted into project management accidentally. I wasn’t one of those people who dreamed about becoming a PM or studied specifically for it. In my earlier roles I just kept becoming the person organizing things when projects became messy. Somebody needed to coordinate teams, follow up on dependencies, calm people down when timelines started slipping and somehow I naturally ended up in the middle of it.

At first I thought good PMs were people who always had answers and complete control over the situation. After some years I realized most experienced PMs are just much better at operating inside uncertainty without panicking publicly.

One thing that changed a lot for me was understanding that projects rarely fail because of one giant catastrophic mistake. Usually they slowly drift off course because small uncomfortable conversations keep getting delayed. People hope issues will fix themselves. Teams avoid escalating early because they don’t want to create tension. Dependencies stay probably fine until suddenly they really aren’t.

I also learned pretty quickly that visibility matters more than perfection. Early in my career I used to disappear into problem-solving mode because I thought the best PMs quietly handled everything in the background. In reality, silence makes people nervous. Even imperfect updates are usually better than letting teams or stakeholders feel blind for too long.

Another thing nobody explained properly is how much of PM work is emotional management. Not fake positivity but absorbing pressure without spreading chaos everywhere else. Teams watch your reactions more than your words. If you look overwhelmed all the time, everybody else starts feeling unstable too.

A few other things I learned the hard way:

• documentation is boring until you desperately need it 4 months later
• quick calls create huge confusion if decisions never get written down
• people almost never get angry about overcommunication but they remember being surprised very clearly
• leadership usually wants clarity more than detail
• the longer you delay hard conversations, the heavier they become

And honestly the biggest mindset shift for me was realizing PMs are not there to magically control everything. Most of the job is creating enough alignment and visibility so problems become manageable before they become disasters.

I still have days where I feel like I’m improvising half of this role. I think most PMs do, even the experienced ones. They just get better at recognizing patterns and staying calm while figuring things out.

Not openly. On paper they actually sound compatible. Cross-functional collaboration, flexible teams, shared ownership, all that. But the longer I work in matrix setups, the more it feels like agile starts breaking in very strange ways once people belong to too many contexts at the same time. Because technically you’re in a squad but you also report somewhere else. You have sprint priorities but also department priorities. One manager cares about delivery, another cares about utilization, another suddenly pulls people into something more important. And now everybody is agile… until priorities collide.

What usually happens is teams still run ceremonies, boards still look organized, sprint planning still happens but underneath it there’s constant invisible context switching that the agile process itself doesn’t really account for. People commit to sprint work while already mentally split across 4 different initiatives. Dependencies become political because nobody fully owns the people involved. Teams look stable on org charts but in reality availability changes every week depending on who escalated something higher. And the weirdest part is the tooling often makes this look way cleaner than it actually is.

Boards show dedicated teams. Capacity looks planned. Work looks assigned. Meanwhile half the coordination is happening outside the system because matrix reality is too messy to represent properly. I honestly think this is why some agile transformations feel successful during workshops but painful during actual execution. The framework assumes stable ownership and stable priorities much more than matrix organizations can realistically provide.

Others working in matrix environments, do you feel this tension too or your org somehow solved it?

I’ve been thinking about this for a while after working with a few different teams and tools and honestly… a lot of the popular PM tools feel like they push you away from being truly agile without you even noticing it.

Asana starts simple and feels flexible but over time it turns into a place where everything needs to be structured, categorized, tracked and updated constantly. Instead of adapting quickly, teams spend time maintaining the system so it stays clean.

ClickUp gives you everything but that’s kind of the problem. Too many options, too many ways to structure things. Teams end up building their own versions of process and suddenly, agility turns into configuration debates and inconsistent workflows.

Monday looks great and is easy to pick up but it pushes you into this very structured, almost spreadsheet-like way of working. It works fine for tracking but real iteration and quick changes start feeling heavier than they should.

And what all of them have in common is this quiet shift: instead of helping teams move faster, they slowly encourage more process, more tracking, more keeping things updated instead of actually delivering.

What’s interesting is that I’ve seen some tools that handle agile workflows much more naturally, especially around dependencies and real-time visibility but nobody really talks about them. And I don’t think it’s because they’re worse. It’s because they’re not spending millions on marketing. They’re just building around how teams actually work instead of how tools want teams to behave.

Kind of ironic that in a space that’s all about agility, the most visible tools are often the ones adding the most friction.