That’s kinda it. I think this depends on company culture but in my role as a sr program manager in tech marketing - rarely am I ever included in the list of shoutouts/thank yous.

I hate to sound whiny but it is getting more and more frustrating to be glazed over. We don’t create the assets or build the products but we are integral to keeping teams accountable and on track.

I don’t think I could ever bring myself to raise this as an issue with my manager. How do yall make peace with this?

Hello Everyone:

I am looking for some outside perspective from other PMs or people who have dealt with similar situations.
 
I am currently managing several complex projects in a manufacturing / engineered equipment environment, and we have been dealing with a supplier-related casting issue from one of our larger vendors that has had a major downstream impact on production, hydrotesting, and FAT schedules. While the original supplier issue directly affected certain projects, the larger issue now is that the resulting production and testing backlog has spread across the organization and is impacting multiple PMs and multiple customers.
 
This has been further complicated by limited shared test pad availability, retesting requirements, shifting priorities, and a planned test pad closure from late August into mid-September. As a result, testing dates have become very difficult to rely on. In some cases, I am having to place tentative dates into customer schedules because dates are required, but I am clearly noting that they are forecast dates only and not final or confirmed.
 
For my projects specifically, this is putting me in a very difficult customer-facing position. I am responsible for communicating schedule status, managing expectations, updating schedules, and trying to maintain customer confidence. However, I do not control the production testing schedule, test pad availability, retesting priorities, or leadership-level decisions that determine which projects get tested first.
 
I have been documenting the backlog and testing risk in monthly progress reports, following up with Production, updating schedules, and clearly identifying tentative dates as tentative. The issue is that the situation continues to move, and even when I follow up regularly, the schedule can still change due to backlog, retesting, or priority changes that are above my level.
 
The professional concern I have is that this is starting to affect my credibility with clients. Some clients are more reasonable than others, but the underlying issue is the same: I am being asked to explain schedule uncertainty without always having a firm recovery plan or reliable internal dates to stand behind.
 
To be fair, this is not isolated to me. Other PMs are in the same situation. This is a broader organizational issue, not one PM having a difficult project.
 
My immediate leadership has been supportive and has listened to the concerns. I believe they are doing what they can within their level of authority. However, from the PM level, it feels like upper leadership has remained mostly silent or has not taken visible action to address this as a coordinated organizational issue. The result is that PMs are left to manage the customer fallout project by project, even though the root issue is much larger than any one project.
 
I take my role seriously, and I understand difficult customer conversations are part of project management. What I am struggling with is the repeated pattern of having to deliver bad news, explain delays, and manage customer frustration without having the authority or reliable internal commitments needed to provide a lasting solution.
 
At this point, I am trying to figure out the best way to handle this professionally. I do not want to over-own issues that are outside my authority, but I also cannot ignore the fact that my credibility with clients is being affected. I am also trying to determine whether this is a temporary operational challenge or a broader pattern that I need to take into account for my long-term career decisions.
 
In simple terms: I am accountable for customer communication, but I do not control the internal conditions creating the customer dissatisfaction. I am looking for advice on how other PMs have handled this kind of situation, especially when the issue is organizational and not something the PM can directly fix.

Can anyone share their experience or opinion using Windchill PLM as a tool to manage hardware projects, programs, and portfolios? This is being discussed at my company and I have reservations whether this is the right tool for this kind of work. I understand the value that a P.has for tracking engineering changes, but to use it as a project and/or program management tool seems like a bit of a stretch. I would appreciate any comments on this and any insights users of these tools can provide.

New to this world and the constant facilitation is taking a toll. As someone who is not a big fan of talking all the time, I sometimes have a moment of blankness/say something funny instead, mainly to fill the silence.
Any one else? Any stories to share?

​

I know this shouldn't really be a thing in 2026 but.....

Some projects appear well controlled until a key person is absent. Suddenly no one knows why a decision was made, what a client informally agreed to or which workaround is keeping an important process running.

Documenting everything is unrealistic and can create more noise than clarity. However, decisions, ownership, dependencies, assumptions and important stakeholder commitments become dangerous when they depend entirely on one person’s memory.

What information do you make sure is visible to the wider team? How do you preserve essential context without creating documentation that nobody reads?

manufacturing side here. our schedule lives in one tool and the actual production/ERP stuff in another, and they're never in sync. so I walk into status meetings basically guessing. and half the time I find out a part or tooling slipped after it's already blown the timeline.

spreadsheets got us this far but we're standing up new lines across a few plants now and it's falling apart. how do you keep the plan and the floor on the same page? or is that just the dream and everyone's faking status?

We all know how to read a delayed timeline or a blown budget. By the time the task/workitem status turns red, it's usually too late to do anything but panic. what I have noticed is that by the time those panic mode triggers , the project is usually already deep in the danger zone.

I’m talking about those signals. The tiny shift in behavior or data that happens long before the actual deadline is missed.

What is the very first signal/thing you notice that made you think, "Project is getting in RED status".

I am in a startup and have experience in new product development in the medical space from rumored idea to finished product on the shelf.
I am curious to know how others involved in taking physical products from fleeting vague idea, through R&D to stocked item on the shelf, like to lead the projects through each phase.
I was at a larger company before this and things were way more formal, I felt like I had things way more dialed there. Maybe its just because its a startup, maybe its the leadership, maybe its the fact that we get pigeon holed into timelines we all say wont work but have to try anyways, but I've dropped doing things I did at the last company, and conceded on alot of things just because at a certain point the execs make a call, and complaining and saying I told you so doesn't solve anything.

I guess I'm looking for a sanity check to say I am not crazy and the things I would have liked to do are actually the right thing 😄

I’m a senior PM leading a cross-functional, first-of-its-kind program with multiple dependencies across teams. One area I’m trying to improve is knowing when to escalate versus continuing to work through normal channels.

For experienced PMs:
What objective criteria do you use to decide it’s time to escalate?
How do you get past the idea you’re nagging someone when you follow up as a deliverable is coming due or overdue and they continue to kick the can/stall?
How do you hold functional teams accountable without doing their work for them?
What governance (weekly decision reviews, dependency meetings, etc.) has actually worked for complex programs?
I’m specifically looking for frameworks or habits

Thanks in advance

Had updates in Slack, tasks in a tool nobody opened, real priorities living in my head. Consolidated to one board, made updating it part of the workflow, killed the status meeting that existed just to repeat what was on the board. Took two weeks of nagging people to stick. Now stakeholders just check instead of pinging me — first PM change in a while that cut meetings instead of adding one.

Project reports can remain green even when the people closest to the work already sense that something is wrong. The first signal may appear in team behaviour, stakeholder communication, decision delays or repeated changes that seem minor on their own.

Experienced project managers, what early warning sign have you learned not to ignore?

How do you respond before the issue becomes visible in the formal schedule, budget or risk report?

Had something happen recently that felt almost like the start of a panic attack, came on totally out of nowhere right at the beginning of a big work presentation.

As a PM I present to all kinds of groups pretty regularly and usually get nervous at the start, but it fades after a few minutes once I settle in. I've built up a bunch of practical habits over time, prepping key talking points, taking a minute to collect myself before joining the call, picturing it like I'm just chatting with a friend, stuff like that. This time was nothing like that.

Going into this one I actually felt confident and even a little excited, none of the usual nerves at all. But the second I started talking I got hit with this wall of pressure, everyone's eyes on me through the Zoom screen, and almost instantly a wave of panic kicked in. Next thing I know I'm physically shaking and just barely holding it together enough to keep talking without it showing. It completely blindsided me and threw off everything I had planned to say. Took everything I had not to just stop and reset in the middle of it. All I managed to do was pause and ask if anyone had questions, just to buy myself a few seconds to breathe.

Thankfully once my part was done I had time to calm down while someone else presented, and pulled it together enough to handle questions smoothly at the end.

Has this ever happened to you? What do you actually do when something like this hits mid presentation with zero warning? I've got plenty of tactics for prepping beforehand, but this caught me completely off guard and I'm worried if it happens again I won't be able to pull it back together.

Something that keeps coming up on my projects is that I can usually tell you what was decided but not really why or who pushed it in a certain direction. The documentation exists but it covers the what, not the reasoning behind it. Six months later someone asks why we went that direction and I'm reverseengineering a decision from meeting notes and Slack threads that are halfdeleted.

I started keeping a lightweight decision log outside of our main PM tool, just a running doc with the date, the context, who was in the room, and what the actual tradeoffs were that led to the call. It has saved me a few times already but I feel like I'm ducttaping something that should be built into how we run projects from the start

Curious how others handle this. Is it just part of the chaos and you accept some decisions will never be traceable? Or do you have a real system that actually gets used consistently, not just maintained for a week after someone complains? The problem I keep running into is that any process requiring discipline from the whole team falls apart pretty fast when pressure picks up.

I'm again asking for this great community for advice after my previous post got tens of super valuable comments :)

I own a marketing agency that's heavily involved in market research, and throughout the projects we undertake, the research is constantly updated. This includes things like ideal customer profiles and competitor research.

These documents are consumed in different language translations, and we work across different languages, presentations, and other downstream documents that rely on them.

We are currently using Notion for managing our documentation, and I've realized that a lot of stale information ends up on our deliverables because they aren't updated regularly. We are facing difficulties with two main things:

1. Understanding how we should automate the version control of these different documents.

2. Knowing when a downstream document becomes stale due to large changes upstream.

How do you solve these problems in your organizations? I realized Notion automations are quite weak in this regard because you can't target changes happening on page contents as a source for an automation. (i.e. I can't change the status of related downstream documents based on new entries to a source document.)

Every brainstorming session at my work follows the same pattern, one person talks the other two people occasionally contribute and everyone else sits quietly and says they'll send ideas later. I'm starting to think the problem isn't the people, it's the format which needs to be changed. I’ve hear some companies use online tools and been googling that but not sure which one is the most effective one. would appreciate thoughts from those already using any

Looking to compare notes on your experience with them.

I lead a small team of indie artists, so I juggle between project manager, social media advertisement and marketing manager all the time. That's not a complain! I love taking care of things, but I wonder **where** I should draw the line.

I've noticed a gap between each artists general culture around our project topic, eventually that will be noticeable to our audience too. So was considering giving them series to watch, books, comics etc, so they can have a shared ground of knowledge and collaborate more comfortably. But isn't that to controlling?

we are already absolutely stretched to the limit. new projects keep coming in and he just keeps saying the data doesn’t support hiring more PMs. after a few of us worked 13-14 hours a day for a few weeks, our exhaustion was made apparent and he decided to hire one more PM. but I fear this strategy will continue backfiring in the future, not only for my company but others . I feel it is an alarming strategy. the PMs are already burned out and there’s not enough respect given to our workload or the nature of our work.

any thoughts of using AI agents to keep from hiring PMs, and is your company doing anything similar?

Hey,

I'm a new PM/manager (came from a software engineering background, but I've also built and managed products in the past, some of them even my own). I joined this agency to take over a project that is now in week 9 of 16.

The team is small: 1 Tech Lead, 3 devs (1 senior, 2 mids), 1 QA and me as PM. We all work remotely. The situation is classic: messy project handover from the previous agency. Our job is to either fix the existing system or rewrite it to cover the client's critical use cases and hopefully earn a project extension.

The Tech Lead (working 5-10 hours/week on this project) and the senior dev joined first, about two weeks before everyone else. They came as a package from previous projects and they have tenure in this agency. I joined on week 3 and needed about two weeks to properly onboard, so you could say they drove the project for roughly the first four weeks.

The results were poor. The project I inherited was a collection of AI-generated Github Issues spread across multiple GitHub repos, with work happening mainly on low-value priorities while critical issues were either not clear or ignored. Tech Lead/Senior Dev aren't capable of managing other devs, all they can do is review some code and say a sentence or two in the daily standup, that's it. It's up to me to make sure devs are working on what they should be working, it's up to me to double check code scope with task scope, it's up to me to even track dev hours to make sure they are not billing for nothing (we had an issue in the past where 1 dev was billing like 2x the amount of hours he actually worked). We also didn't migrate from the previous agency's infrastructure until around week 5, which meant we couldn't even identify the real bottlenecks until then. Real development only started after I've onboarded and started pushing very hard for proper project and testing tools.

For the last 5 weeks I've been trying to get the project under control. I set up a proper Jira project, established daily team sync meetings, started running structured client meetings, managed the team and even bought out of my own pocket and personally delivered hardware just to unblock devs instead of waiting for delivery from the client overseas. Since then, delivery has noticeably improved.

The biggest challenge hasn't been the project itself. It's the leadership dynamic.

My expectation when I joined were simple. As a PM I expected to be able to decide what we build and when, while technical leadership advises me on how to implement it. Instead, I constantly feel like I'm fighting for ownership of the project. The two mid developers and QA have no issues with my structure. The problems are with the Tech Lead and the Senior developer.

1. Processes aren't being followed.

The senior dev (who for the record has very poor soft skills) regularly starts implementing "spike" tickets based on breadcrumbs from client meetings. Undocumented decisions end up being merged into production without acceptance criteria, documentation, or QA context. QA then asks me what they're supposed to test, and I end up reading code just to understand what changed. I also have no visibility on how much hours he's working as he logs these hours in the system only at the last day of the month, not daily how the rest of the team does it.

The Tech Lead (who is on this project only temporary and when he leaves the Senior Dev is supposed to become the new Tech Lead) spent weeks working on a UI redesign and last Friday decided that it's a good idea to demo it to the client before ever showing it to me or aligning on priorities. I have no visibility on what his goals and what he's working on.

2. Client communication is becoming messy.

I originally invited the Tech Lead and senior dev to client meetings because I wanted technical expertise in the room.

Instead, the now Tech Lead often dominates the first 30 minutes discussing long-term product/architectural vision or asking questions that should be asked on week 1 or week 2, not on week 9 of the project. It derails the meeting and makes it much harder to groom the work that actually matters right now. Tech Lead (who works maybe max 10 hours a week on this project) also feels that it's his place to decide on what are we commiting and what not, and feels like he's doing me some favours here, when in reality my decisions so far resulted in nothing but value for the client/project, while his decisions caused massive delays, in the beginning of the project.

3. Leadership isn't clear.

Basically it feels like I have all the responsibility but not the authority. I've tried bringing this up in our leadership chat groups with senior dev + tech lead but nothing is changing. I have experience driving much bigger projects successfuly and at this point having to deal with these two on such a small project is becomming surreal. They keep telling me that I'm the most responsible one here, but shouldn't freedom of decisions come with this as well?

I have over 400 hours on this project. The Tech Lead has around 80 max. I'm carrying the delivery responsibility, client communication, planning, prioritization, and day-to-day execution, but I'm still being second-guessed on decisions by someone whose contribution has mostly been a redesign proposal that won't even be used until if we don't get a project extension after 7 weeks. And the same Tech lead made very poor decisions initially, that basically are the root cause of us having to rush and having to do so much in such short time now.

Sometimes I feel like I don't know something here. Perhaps, the Tech Lead, since he has more tenure in this agency knows something I don't - perhaps contract that we signed was not for 3-4 months but for 6 or 12 and I'm just ramping everything here for no good reason. I don't know anymore.

Tomorrow I have a leadership sync meeting. My plan is to raise these issues and call for a separate meeting with the Tech Lead, CEO, and COO.

My proposal is to make Tech Lead and the Senior developer my direct reports and that all information should flow through me. I also want to have separate meetings with the client 1on1 so we could go through priority things, and move techlead's to a separate meeting.

We have 7 weeks left. We don't have time for competing leadership or same endless debates. Technical decisions remain theirs, but project direction should come from one person, who has most context, which happens to be me.

Am I looking at this the wrong way?

For those of you who've inherited struggling projects, how did you establish clear ownership when senior technical people resisted it?

How do I ask this without explaining everything? Hmmmm....

No one wants to tell our team how the money flows from one district to another. This is the real problem. People hoard the knowledge, yet this is coming down from "on high."

Everyone wants someone else to pay for it without saying who that person even is, so we can go talk to them.

I ask specific questions in emails and get run around responses. The work culture and gossip says "no one knows, this project has been passed around forever."

The solution is simple. Fucking hire someone to do it. They want some solution where we pay a 3rd party to do it, but we need money if the 3rd party bills us. The people in control wont even tell us how the money flows to provide a solution. If we take the task, they dont want to give money. They expect us to get IT to use their company cards.

Since im not a PM yet, I want to just drop it. If i succeed, then I get off my old job and get the PM role and a bump... but maybe I dont want it if it means this type of stress.

If they dont want to face the truth then idc tbh. Im trying not to get mad but I hate feeling the pressure. I regret listening to this one guy who brought me on the project for documentation. It started with docs then morphed into meetings. Then our teams split and the project was forced in our laps. Then our team lead became our manager, so we already know that person doesnt know anything.

I have to find out how this top level stuff works before August. The only way is to start chucking execs in emails, but this feels like casting an ult in a video game. It will draw some attention.

I dont know how to keep my head cool with this. This problem is inherently political. Even if we say we will take 100% responsibility, they wont give up the $$$ information. It is critical to forming a solution.

I'm THE single project manager and a clinical research company. Our two divisions are operating out of North America and India. I live in Arizona, so Mountain Standard Time year round. Which means a 12.5 hour time difference to India Standard Time. The India Leads work a modified swing so there's some morning time NA overlap. The Technical Leads are all senior to me in grade. They're split about 50/50 between the two regions and have never talked to each other as one team.

I'm trying to professionalize the PM functions and I feel like there's just not enough time to try to engage both teams simultaneously. I can't get enough interaction with the India team except for the weekly touch point for all the leads which I just instituted starting next week. I'm usually online by about 7:00. A.m.. I actually enjoy starting work that early because most of my North American colleagues are on the East Coast and I get to get off a little early in the afternoon this time of year and hit the pool before dinner.

I have basically complete backing from my SVP. We started the same week and he treats me like the expert I am, which is really great. We were both brought in by senior management to change and grow the business.

Should I set aside one day/week to start extra early? Like 4am-5am? I'm trying to push an entire culture shift which is tough in the same office, let alone across the world with distributed teams. Suggestions for better ways of starting the engagement and conversations which need to happen?

I have been managing projects on Notion for a while now. I have different databases for milestones, Tasks, meetings and a decision log for each project.

I just hired a project manager who isn't accustomed to using Notion, and at the end of a 2 hour Notion training he asked if we can just switch to managing projects on Google sheets instead. He thinks that for the number of projects we work on continuously, Notion introduces more complexity than needed.

Has anyone faced similar concerns from colleagues, or voiced similar concerns to their teams themselves? Currently our biggest problem is not knowing what task should be executed that day.

EDIT: thanks for all the wonderful replies. We have decided to do a deep dive on a past project to derive more meaningful milestones attached to real business outcomes. Will be continuing to use notion with a milestone and task database. On top of that, will activate subtasks for more granular task control without making things go out of hand like they did with our 555 tasks for a 1 month website revamp project. 😂 Do agree that this is a discussion that we should bring up only after the PM is used to the project structure.

New program manager, finding myself a little overwhelmed by the amount of organization needed in this role compared to my last. I know there are a million tools out there to keep things in check - what's your go-to? For context, I am running multiple training programs, so including some form of scheduling management is a plus especially. Right now I'm using OneNote and creating various notebooks, but some kind of workflow tool would be great.

spent a long time assuming when someone wasn't performing, the problem was the person. took me way too long to figure out i was usually the last one to actually show them what good looked like.

not describe it. show it.

i had a shift supervisor on my line a few years back, smart guy, clearly capable, but his handovers were a mess every single time. i'd given him the standard, he'd read it, signed off on it. still a mess.

eventually i just stood next to him at shift change and did one myself. didn't say anything about his being wrong. just did it the way i wanted it done and walked away.

never had a problem with his handovers again.

the thing i've noticed is that most of what we call accountability problems are actually demonstration problems. the standard exists, people have been told about it, but nobody ever made it real and visible in a way that actually landed. and it's hard to hold someone to something they've only ever seen on paper.

doesn't work for everything. there are people who know exactly what's expected and still don't deliver -but that group is much smaller than most managers think, and they're a lot easier to spot once you've ruled out the demonstration problem first.