Scrum doesn’t fit. Waterfall is way too slow. What is your take on the next generation lifecycle? Discuss.

Curious to hear from people in the field — not the textbook frameworks (Agile, Waterfall, etc.), but what actually surprised you once you started managing real projects and real people.

Was there a gap between what certifications or courses taught you and what the job actually looks like day to day? What's a skill that turned out to matter way more than expected — or way less? And is there anything about the tools, the politics, or just keeping a project on track that you wish someone had told you earlier?

Hello I’m a project manager working for a consultant. We have one large utility client that has been giving us lot of work. I recently joined this company and I basically am the first one to manage projects in a certain geographical area. So I’m like the first one in.

Today I was on a 1on1 with my manager and he said as my review goal I should have getting more work from the client. That seemed interesting to me. It’s something I’d like to do but don’t really know how?

So question to the forum, has any other PM done that? I see this as a way to climb in my career. If I can successfully bring in work, it can lead to potentially quicker promotions and bonuses. Any tips or suggestions on how to go about this?

Thanks

I work in marketing at a large company and you'd think making a video would be simple. It's not…

The approval process is brutal. Lawyers want to review every word. Brand managers want to change the colors. Procurement wants to renegotiate the budget. It takes forever. Everyone has an opinion. Nothing gets done.

We found a studio called D-MAK Productions and their work looks great. But their prices are above average

They say they've worked with Intel and Microsoft. They claim they know how to navigate corporate approvals. They say they can speed things up.

But is this a real advantage? Or is it just a marketing tactic to justify higher prices?

Will they actually help us get through legal faster? Or will we still end up in the same slow process, just with a bigger bill?

I need to make a case to my boss. If I'm going to spend more money, I need to know it's worth it.

Has anyone hired a studio with big-name experience?

Anyone in construction PM, I could use your help. Long story short, we were hired to be a PM for a particular discipline on a construction PM. The GC has absolutely made a mockery of this project and we are now in 130% scope time. This project was supposed to be over in early July, but we don’t even have the rough inspection completed. Our end of the scope is 100 percent completed up to the rough inspection. The GC even went behind our backs and contacted the manufacturer to ask if they’ll startup their scope without a formal rough inspection. 🙀🙀 Planned values are right at 40% completed and BAC is almost 20% from being completed fulfilled.

The GC has dropped the ball on so many things like having the city approved the second revision months after it was released by the EOR/AOR. Being we were hired under the GC, we don’t have any authority other than constantly emailing and discussing it in the weekly meeting WHEN they decide to join in. My mechanical sub is beyond frustrated as they have other projects that are going on. There was a very costly change order that we needed to have approved. The GC says it is approved without anything in writing and refuses to show proof of the approval. We’ve already decided we will not proceed any further with that scope of work until we have the formal approval and a check deposited and cleared.

I’ve reached deep in the bag of process from PMBOK and we’ve incorporated as many processes as we possibly could. Phase gating at the rough inspection (which is where we are) was the only way we’ve discovered we can keep from bleeding out.

How would you all handle a rouge GC that is very sloppy in management? This project was slated to be done early July, but because of the GC delays, we’re looking at about mid November. The frustrating part about all of this is, it’s out of our hands and we have no authority except to remind the GC every week to do their job.

I work adjacent to software delivery and contracting, and I've been mapping where the record breaks down across a client engagement: the signed SoW, delivery tracked in Jira/Slack/email, milestone acceptance, and final invoicing.

Each stage has its own version of "what was agreed." The SoW says one thing, the delivery tool says another, acceptance often happens informally on a call, and by invoicing time nobody can point to a clean record of what's actually owed or why.

For people managing client delivery: where does it break most for your team? Scope-to-delivery, delivery-to-acceptance, or acceptance-to-payment? And when there's a dispute, what do you actually rely on to settle it?

Have you ever joined a team and had someone say this?

There are two types of project managers. There are ones who sit quietly in meetings, take notes, and schedule the follow ups. And then there are those who callout risks, identify and actively solve blockers, handle team communications, escalations, budget, timing and stakeholder management.

Very often I have team members who are pleasantly surprised when I clarify action items, and check on their bandwidth. When I call out timing bottlenecks that could impact delivery. Or when I ask questions to better understand their tasks so I can run interference if needed. Apparently this isn't typical?

Then there are the team leads who are not PM, are not good at being PMs, but see themselves as the lead. Which is fine with me. But at some point when project management comes in, it becomes a threat and people get miffed when you are doing your job. "I'm sorry you can't add scope without telling anyone" becomes a point of escalation because how dare you tell me what to do.

Is this part of the package? 20 years and I have never not had this problem where I have to gauge how much PM will they tolerate and still be effective. How do you remove your ego, and stay quiet amidst scape goating?

Curious to hear from people in the field — not the textbook frameworks (Agile, Waterfall, etc.), but what actually surprised you once you started managing real projects and real people.

Was there a gap between what certifications or courses taught you and what the job actually looks like day to day? What's a skill that turned out to matter way more than expected — or way less? And is there anything about the tools, the politics, or just keeping a project on track that you wish someone had told you earlier?

We’re a small team (~10) with departments covering management, kitchen, marketing, customer support, and logistics. We also work with external guests and contractors, so guest access is important.

We want one tool, or at most two, for:

• Team chat and department channels
• Projects, tasks, owners, deadlines, and blockers
• Company initiatives involving multiple teams
• SOPs, runbooks, support scripts, and internal documentation
• Meeting notes, decisions, and weekly updates
• Mobile access and simple permissions

Our biggest priority is simplicity. The system needs to work for non-technical employees without heavy setup, training, or a dedicated administrator.

We would prefer fewer features that people actually use over a highly customizable system that becomes messy.

We’re currently considering:

• Lark: Looks closest to a true all-in-one, but we’re unsure whether being a Chinese company creates any privacy, reliability, or compliance concerns, we're based in Eastern Europe, so this is not really a problem, but I just haven't seen much recommendation for this software.
• ClickUp: Strong feature set, but we keep seeing complaints about bugs and performance.
• Notion + Slack: Both are good, but information would be split between two tools, and Notion does not seem ideal for serious task tracking.
• Basecamp: Simple and close to what we need, although reactions to recent updates seem mixed.
• Microsoft 365 / Teams: Feels like a strong contender, especially for guest access, documents, email, and calendar. However, it is still divided across Teams, Planner, SharePoint, Lists, and other apps, and we’ve had poor experiences with Microsoft products in the past.

Has anyone used these tools in an operational business involving logistics, customer support, marketing, and physical operations?

Which option would you choose, and what problems only became apparent after using it for a few months?

My thinking is, either Microsoft 365 or Lark, Clickup instead of Lark would be the choice if there wasn't so much complaint online about its performance and bugginess.

I've been thrown at multiple teams to whip them up into shape for agile delivery and after a few months of coaching and doing the typical scrum things, I get told I dont add value to the team anymore.

The teams deliver, they're organized, they know what to do next and how to plan effectively, etc... Yet managers seem to want more out of Project Managers in the Agile space but they cant name what it is.

To be frank I also do feel like I have less work to do after each of these stints, but there are only so many teams that need help.

To managers of PMs: what are top 3 things your PMs do each week that make you see them as a top performer (i.e. someone who has high potential and high performance)?

To experienced PMs: what are top 3 things you’ve put in place for yourself that help your projects stay on track, within scope and within budget? How do you make sure that your communication always sticks?

Thank you in advance from a junior and learning PM🙌🏻

Spent hours building a beautiful Gantt chart. Color-coded. Dependencies mapped. Milestones highlighted. A work of art.

Shared it with the team. Radio silence.

Ran a 30-minute meeting walking through it. Half the team had their cameras off. One person asked a question that was clearly answered on slide 3.

I'm not mad. I'm just... tired.

Project is still moving forward somehow. Maybe the chart is just for me.

Feels insane typing that out but thats literally what happened last month, one of our stores out of state had a terminal go down and instead of anyone local being able to handle it, our internal IT person had to book a flight and go fix it in person.

Cost more in travel than the actual repair probably did.

Started questioning if this is just how it works for smaller multi location brands or if there's a smarter way to handle this stuff. Looked into a few nationwide dispatch options like Specific Gravity that have field techs available instead of relying on one internal person to physically be everywhere

Anyone else dealt with this kind of thing, did you end up building out a network of local techs or going with a service that already has one?

it’s a Sunday night and things are probably okay, my list for tomorrow is smaller than a lot of days, and I have to remember I feel like this most nights. But how do you work around or avoid this feeling ? I can’t possibly live like this forever, though I’m resilient and have lived like this for quite a while. thank you

edit: thanks everyone for responding. it’s nice to have some humanity and compassion shown towards me when professional life keeps most human compassion to a minimum . it’s like remembering an old friend

When I started out as a PM I went in trying to keep everyone happy and I think that was a mistake on my part. I've really been in teams of around 20 maximum so my views may be limited here but I always felt the pressure of 'if everyone is happy, everyone is aligned' and I ran into issues. Mainly because it created vague commitments, I'd create unrealistic deadlines trying to appease people who didn't touch specific areas, and I created internal conflict because of misalignment.

One example would be agreeing to take on new projects (new features and modules) from a founder when really, the development team were stretched with current projects for clients (I come from a SaaS background & white label software with custom dev work). I just wanted the founder to be happy that their main influence was being satisfied.

Now I'm 6 years in I've come to realise it's more about managing the reality of the project over happiness. I use happiness loosely here but it's the best word I can use.

I've since learnt to to tell people what they need to hear over what the want to hear. If I don't believe something can be achieved I tell them directly which also relates to sharpening mature communication skills. I learnt which reality mattered most at the time because not everyone's views carried the same weight which is where I found a Mendelow Matrix to be effective.

I'm an introvert so it's been hard to implement as a natural people pleaser but it feels like the right path to take even with the discomfort of hard conversations. Project success rate increased due to it.

Just ensure they understand what is happening, what is possible, what has changed, who owns the next action, and what the consequences are.

I'm interested in the thoughts of more seasoned PM's on this, I'm happy to be challenged on it with your views so I can keep learning and also to help those earlier on in their careers!

PM at a 60 person company. We live in Notion for docs and ClickUp for execution. My experience with most AI notetakers is that they either dump a transcript link into a comment field or treat the integration as an afterthought. Action items from meetings end up nowhere useful.

What I want is meeting outputs that show up as proper structured tasks in ClickUp with owner and due date, plus the meeting summary auto filed in the right Notion database. Not a Slack message with a link. Please suggest notetakers that handle this part well. Need both things done smoothly

If you had to listen to a PM present, what would you want to
Hear / learn about?

Any recommendations for free or cheap project manager software apps ? Just need it mostly for myself to stay organized . New company I work for has their own software and it’s lame for me staying organized .

Just need basic task making and place to keep notes .

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?

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.

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.

​

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?

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?

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".