Table of Contents
Introduction
A project manager once described a project she still thinks about. The team was committed and the work was moving along. But things started feeling shaky around week six, the kind of slow-moving uncertainty that makes leadership notice and ask for more visibility. First came a weekly update call. Then a biweekly check-in. Then a standing Thursday session. By month two, the team was spending close to a third of their hours in meetings about the project.
The work didn’t speed up. It just got better documented.
That’s not a story about a lazy team or bad intentions. It’s a story about how good projects get buried under the weight of managing them. And it happens more than most project post-mortems will ever admit.
A Familiar Story
Some of the slowest projects I’ve seen were also some of the busiest. Not fake busy. Genuinely, exhaustingly busy. People pitching in, solving problems, putting in real hours. And still watching the project inch forward like it’s moving through wet cement.
There’s a truth most project managers learn the hard way: effort and progress are not the same thing.
A team can be responsive, collaborative, and deeply committed and still lose days to waiting, rework, unclear decisions, or meetings that result in wheels spinning without gaining ground. This is especially true in complex projects, where the work crosses platforms, vendors, stakeholders, engineers, and priorities all at once.
Here are four of the most common reasons that happens.
1. Dependencies Turn Into Waiting Rooms
Dependencies look tidy on a roadmap. In real life, they’re waiting rooms.
Your team may be ready. The next task may be clear. But if the approval, environment, or upstream deliverable isn’t there, the work has nowhere to go and stalls. And these delays rarely appear as one dramatic roadblock. They arrive as small pauses. Two days waiting for an answer. A meeting pushed to next week. A sign-off on hold because the right person is traveling. Each pause seems manageable on its own. Together, they can turn a six-week effort into ten.
💡A simple fix: Build a dependency watchlist with three columns: owner, needed-by date, current status. Ask weekly: what are we waiting on that could slow us down next? It won’t eliminate the delays, but it will stop you from being surprised by them.
2. Communication Gets Spread Across Too Many Places
Most project teams don’t have a communication problem because no one’s talking. They have a problem because everyone’s talking everywhere.
The decision is in a Teams chat. The background is in email. The file is in SharePoint. The real conversation happened in a meeting no one documented. The final answer lives in someone’s memory, which is definitely never ideal.
When information is scattered, people stop trusting that they know where to find the current answer. So they ask again. Or make assumptions. Or rely on the last thing they personally heard, even if the project has moved on. That’s how the same question gets revisited three times.
💡A simple fix: Decide where the source of truth lives for three things: decisions, dates, and open blockers. A basic decision log does more for project clarity than a beautifully formatted status deck that nobody updates after Thursday.
3. Meetings Start Replacing Momentum
Meetings aren’t automatically bad. Some are necessary. But they become a problem when they turn into the main way a project proves it’s still alive.
A project feels risky, so someone adds a status call. Then a working session. Then a leadership update. Then a prep call for the leadership update. Before long, the team is spending more time talking about the work than doing it. That’s how meetings can feel like progress, even when they only produce more coordination overhead, more follow-ups, and more re-explanations.
This gets worse when no one is clear on what the meeting is actually supposed to produce. Decision? Status update? Problem-solving? Alignment? If the answer is some combination of all four, that meeting is mostly a vehicle for containing anxiety.
💡A simple fix: Before adding a recurring meeting, define what it needs to produce. If it won’t create a decision, unblock work, or resolve a risk, replace it with an asynchronous update. A short written summary sent before the work week ends often does more than an hour-long call that spawns three more.
4. Process Complexity Accumulates Until It Feels Normal
No one sets out to make work complicated. It just happens one reasonable step at a time.
A new approval because something went wrong last quarter. A new checkpoint for visibility. A new spreadsheet because the system report doesn’t show the right thing. Each layer made sense when it was added. That’s what makes accumulated complexity so hard to question. Nobody chose it intentionally. It came about through good intentions: reduce risk, improve accountability, prevent rework.
But over time, a simple task starts requiring three approvals, two tools, a meeting, and a reminder to update a tracker that only exists because the original system wasn’t trusted. At that point, the work is supporting the process, not the other way around. Teams adapt. They build workarounds. They stop asking whether a step still adds value because that’s just how things are done.
💡A simple fix: After each major phase, ask the team one question: what slowed us down without improving quality or reducing risk? Then simplify one thing before the next phase starts. Small simplifications compound, and the habit of asking the question is worth as much as any single answer.
Conclusion: The Answer Is Not Always More Effort
When a project slows down, the instinct is to push harder. More follow-up, more pressure, more urgency applied to people who are already stretched thin. Sometimes that’s the right call. But often the better question isn’t how to get people to work harder. It’s what is making the work harder than it needs to be.
Building conditions where the right work can move forward with less resistance might be one of the most underrated skills in the whole job.
