u/Longjumping-Cat-2988

been chewing on this for a while and i think it's one of the least discussed traps in leadership. the higher you climb, the worse your information gets, and it happens so gradually you don't notice.

when you're junior, people tell you the truth constantly, they vent, they flag what's broken, because there's no risk in it. then you get promoted and the raw truth starts getting filtered. people tell you the version that won't cost them. by the time you're a few levels up, you're often the last to hear a project is in trouble, because every layer sands off a little bad news until what reaches you has been polished into fine.

here's the unsettling part: your access to reality gets worse at the exact moment your power to change things gets bigger. authority goes up, signal quality goes down and they cross in the middle.

and a lot of leaders misread quiet as agreement. you float an idea, nobody pushes back, you leave thinking there's alignment. but silence isn't agreement, it's a reading on how safe people feel telling you no. taken as endorsement, it lets you walk confidently in a direction half the room already knows is wrong. what makes it worse is that it feels good, all that smooth agreement feels like you've gotten better at the job, when sometimes you've just gotten more insulated.

so i've started to think real senior leadership is partly fighting your own blindness: going around the filter, talking to people a couple levels down without their managers there, treating a lack of bad news as a warning sign and rewarding the person who tells you the uncomfortable thing, because flinch once and you teach everyone to stop.

do you feel your information getting more filtered as you've moved up? what actually works to hear the stuff people are incentivized not to tell you?

Hi everyone. I've spent about 10 years as a PM in corporate IT, mostly at a large financial services company, running software delivery projects with a proper PMO structure behind everything. Jira was our default and it worked fine there, we had dedicated admins, a whole ecosystem of plugins and teams big enough to justify the complexity.

I just accepted a PM role at an early-stage startup (around 15 people, B2B software), and I'm realizing the tooling question is a lot harder than I expected. Jira feels like massive overkill here, no admin support, way fewer people and half the workflows we had in corporate just don't apply to a team this small. Setting it up properly would probably take more time than it'd save.

I looked at Trello as the obvious lighter alternative but honestly it makes me a little nervous going the other direction. It feels almost too simple for what I need, no real dependency tracking, no timeline/Gantt view and I'm worried I'd outgrow it within a few months once we're running more than 2-3 projects at once.

Has anyone made a similar jump from a heavy enterprise tool to a startup environment? What did you land on that gave you enough structure (dependencies, some kind of timeline view, decent reporting) without the corporate-level overhead?

i need to get this off my chest because the RTO push is making zero sense for our role specifically and i can't be the only one.

my company just went to four days in office. the reasoning was the usual: collaboration, culture, spontaneous conversations. fine. except my job as a PM is coordinating teams that are spread across different offices, timezones and a couple of vendors who aren't even in the same country. so what actually happens is i commute in, sit at a desk and spend the entire day on video calls, headphones on, talking to people who are not in this building. i could be doing the exact same thing from my kitchen, except now with a 45 minute drive on both ends and worse coffee.

and the spontaneous collaboration is a fantasy for us anyway. nobody on my project is physically colocated. the whole point of the role is stitching together people who will never be in the same room. me being in an office doesn't create serendipity, it just means i overhear a sales team's conversation while i try to run a standup with people in another state.

the part that actually gets me is that this decision came from people who mostly don't do the coordinating. leadership sits in one HQ, sees each other, feels the energy and assumes everyone's job works like theirs. but the person whose entire function is remote by nature gets treated like they're slacking if they want to do that function from a quiet place. it's like mandating a phone operator be in the building so you can see them holding the phone.

and don't get me started on how it lands with the team. i've now got great people quietly updating their resumes, not because they hate the work but because the commute back ate the flexibility that was keeping them sane. and guess who has to keep those projects on track while half the team is disengaged and job hunting. me. the RTO decision made my job harder in three separate ways and solved a problem i'm not convinced actually existed.

i'm not even anti-office. some in person time genuinely helps. but a blanket four day mandate applied to a role that is fundamentally about connecting distributed people is just theater, and it's the kind of theater that costs you your best people.

been sitting on this for a while and i think i finally have to say it. a big chunk of what i do isn't project management, it's compensating for problems the company has decided not to solve. two teams that don't talk to each other? my job is to be the messenger between them forever, instead of anyone fixing why they don't talk. no clear prioritization from leadership? i spend my week manually refereeing which fire is biggest. a process that breaks every single time we hit the same step? i'm the one who manages around it, quarter after quarter, instead of it ever getting fixed.

and here's the part that actually bothers me. the better i am at this, the more invisible the underlying problem becomes. i smooth it over so well that from above it looks like everything's fine. so nobody ever feels the pain that would force a real fix. i've basically become the reason the dysfunction is survivable, which means i'm also the reason it never gets addressed. i'm not solving the problem, i'm making it comfortable to live with.

it's a weird spot. do the job well and you quietly enable the thing that makes the job necessary. do it badly and everything you were absorbing suddenly becomes visible and it's why can't the PM keep things on track. either way the root cause just sits there.

and i think this is why the role is so hard to defend when budgets get tight. our biggest wins are invisible by design. the crisis that didn't happen, the conflict that got quietly defused, the fire that never spread. you can't put problems you never saw because i handled them on a slide. so we're constantly proving our value by pointing at chaos we prevented, which by definition nobody experienced.

i don't have a clean answer. sometimes i think the move is to stop being such a good buffer, let some of the dysfunction actually surface so the people who could fix it finally feel it. but that's a scary game to play with your own reputation.

do you see your role this way too, as the workaround for stuff that should be fixed structurally?

hey all

been trying out a bunch of Asana alternatives lately and honestly i'm starting to think a lot of people stay on Asana just because it's what the team started with, not because it's the best fit. figured i'd share quick takes from what i've actually used and see what everyone else landed on.

for context i bounce between a few setups depending on the team and over time it feels like every tool has its own niche instead of being a true Asana killer. quick thoughts from what i've tried:

ClickUp is stupidly powerful, does basically everything but that's also the problem. took ages to set up and half my team got overwhelmed by the amount of options. great if someone's willing to own configuring it.

Monday is nice if you think visually, boards look clean and it's easy to get people on board. but the pricing climbs fast once you add people and the good features are on the higher tiers.

Trello is still the easiest thing to recommend if you just want simple kanban and nothing else. falls apart the second you need timelines or anything cross-project though.

Jira if you're eng-heavy, but for a mixed team it's honestly overkill and everyone who isn't a dev hates opening it.

Linear i really liked for the speed and how clean it is, but it's pretty focused on software teams, didn't fit the non-dev work as well.

what i keep struggling to find is one thing that does the day to day task stuff AND the longer term timeline/roadmap without either being an afterthought. everything seems to nail one and be mediocre at the other. any recommendations?

we've been running our team out of Notion for a while and i keep hitting the same wall. it's genuinely great for docs, notes, wiki type stuff. but the second we try to actually plan work in it, it starts to fall apart.

the specific thing im struggling with: we need something that does daily planning well, like what's everyone actually doing this week, whats moving, whats stuck, AND long-term planning, the quarter-level roadmap, how the big pieces line up over months. in Notion i end up building both by hand with databases and it's fragile, nobody keeps it updated and the daily view and the long-term view never really talk to each other.

so i'm looking at moving the planning side somewhere purpose-built (might keep Notion just for docs, undecided). what im after: a proper board or task view for the day to day that people will actually maintain, some kind of timeline / roadmap view for the longer horizon that doesn't take an afternoon to set up, the two staying connected so updating daily work actually reflects up into the bigger plan, instead of me reconciling them manually. we're not a huge team, so i don't want something enterprise-heavy that needs a consultant to configure.

for those of you who moved off Notion for planning, what did you land on? appreciate any real experiences.

ive seen a bunch of how am i supposed to handle this and i think i messed up posts from newer PMs lately and honestly it makes me want to reach through the screen and tell yall to relax a bit. i have ~14 years doing this and i STILL have weeks where i feel like im just winging it. i think thats most of us. the people who seem unbothered are usually just better at hiding it.

quick background so this isnt just some anonymous trust me bro, i fell into pm sideways. started in operations, got handed a small software rollout because nobody else would touch it, it went ok and suddenly that was my job forever. no cert for the first 6 years. eventually got capm then pmp, mostly because it helped me get interviews, not because it taught me how to actually do the work.

anyway here's some stuff in no particular order, take what's useful:

1. the status update is not the job. removing the blocker is the job. i wasted years being a really efficient reporter of bad news. nobody promotes you for accurately documenting that something is on fire.
2. when youre new, over communicate. like way more than feels normal. you will not get in trouble for hey just confirming we're still aligned on X. you WILL get in trouble for assuming. the only exception is execs, for them, shrink everything down to time and money and the one decision you need from them. they do not want the saga.
3. dont surprise people in front of their boss. if you have to deliver something someone won't love, give them a heads up first, privately. you basically never want a stakeholder hearing bad news about their area for the first time in a room full of people. they will remember it and they will not help you next time.
4. escalating is not snitching. took me forever to get over this. asking nicely 3 times and getting nothing isnt patience its just you absorbing someone elses miss. "hey this is now a week late and im going to have to loop in your manager so we can reprioritize" is normal, professional and honestly people respect it more than the silent resentment thing.
5. own your screwups fast and plainly. "yeah that was my call and it didnt work, here's what im doing about it" buys you SO much more trust than any amount of spin. people can smell the spin.
6. you are going to feel like an imposter and it mostly never fully goes away, you just get more comfortable not knowing things. the skill isnt having all the answers. its being calm and useful while you go find them.
7. relationships are the actual deliverable. the plan, the gantt, the tool, whatever, thats all secondary. the reason things get unstuck is usually that someone likes you enough to do you a favor. invest in that constantly, before you need it.

idk this got long. point is if youre newer and panicking, you're probably doing better than you think. what would yall add to this?

For me it would be this: the hardest part isn't finding a tool with enough features. It's finding a tool your team will still willingly use 12 months later.

Early in my career I used to evaluate tools almost entirely based on capabilities. More automations? Great. More dashboards? Great. More reporting? Even better. I thought the tool with the longest feature list would naturally be the best choice. Turns out that's not how it works at all.

A few times we picked tools that looked incredible during demos and pilot projects. Then real work started. Teams grew. Projects became messier. Priorities changed. And suddenly nobody wanted to update anything anymore. The tool wasn't bad. It was just too much work to maintain.

That was probably the moment I realized adoption matters more than features. A simple tool that everybody updates honestly is usually more valuable than an advanced tool that half the team quietly avoids. Would've saved me a lot of frustration if somebody had told me that earlier.

What's one lesson about PM tooling that would've been a huge relief to know sooner?

Not generic advice like communicate more or manage stakeholders. I mean the real lessons that only hit after enough projects go sideways.

For me it would probably be trying to solve everything quietly by myself because I thought good PMs should always look in control. I delayed escalations way too long early in my career because I thought I could fix it before it becomes a problem. Usually it just became a bigger problem later.

Also used to think overworking automatically made me a better PM. In reality being permanently reactive just made me worse at seeing risks early.

Nobody talks enough about the corporate honeymoon phase when you join a new company. First few months everything feels exciting. People are nice to you, meetings feel important, projects sound bigger than anything you worked on before. You think finally, this place is organized properly compared to my old company. Then slowly the real structure starts revealing itself.

You start understanding which meetings are actually useful and which ones exist because nobody wants to be the person removing them. You realize some decisions are already made before discussions even start. Certain projects move fast not because they are important but because the right person cares about them.

As a PM this part hits especially weird because at the beginning you think your job is mostly about coordination and delivery. Then after enough time you realize half the role is navigating invisible organizational dynamics nobody explains directly.

Who actually influences decisions. Which priorities change every week. Which teams are overloaded but politically cant say no. Which updates leadership wants honestly vs which ones are expected to sound under control.

I also noticed during the honeymoon phase everybody assumes the systems and processes make sense because they already exist. Later you discover half the workflows were built around problems from 3 reorganizations ago and nobody remembers why certain steps even exist anymore.

And honestly the strangest realization for me was understanding that most companies are not nearly as coordinated internally as they appear from the outside. A lot of corporate life is just very smart people trying to keep complex systems functioning through communication, relationships and constant improvisation.

Not saying this in a negative way even. It actually made me calmer over time.

we had a period where leadership became obsessed with visibility gaps. every issue somehow traced back to the same conclusion: people dont have enough information. so over time more and more systems got added to solve it: roadmaps in one tool, delivery tracking in another, documentation somewhere else, alerts in slack, sprint reporting in dashboards, incidents in another platform, capacity planning in spreadsheets and i continue to name more and more.

but for a while it looked like maturity. more systems, more visibility, more process. leadership loved it because technically everything became measurable. but what actually happened underneath was kind of the opposite, the project slowly stopped existing in one shared reality.

every team started seeing a different version of the work depending on which tool they lived in most. engineering trusted jira. product trusted roadmap dashboards. leadership trusted portfolio reporting. ops trusted slack threads because thats where things actually happen. none of the systems were fully wrong but none of them reflected the whole situation either.

so now instead of solving project problems, people spend insane amounts of time translating context between systems. half of PM work became: yes the dashboard says green but the dependency isnt actually resolved yet, yes technically the task is done but deployment is blocked, yes the roadmap says next week but engineering already moved it, ignore that status, its outdated, yada, yada.

and the weird thing is the tooling was introduced to reduce confusion. but eventually the amount of interpretation required became bigger than before. i honestly think this is one of the reasons large software organizations feel so heavy operationally. not because people are bad but because project understanding gets split across too many layers and systems until nobody can fully hold the whole picture in their head anymore

at some point adding another tool stops creating clarity and starts creating competing realities. anyone else see this problem as well? or am i the only one? because i've also seen people who see no problem in here and they basically say that it's a part of the job.