The Leadership Behaviors That Slow Projects Down

Not Every Leader Is Built for Project Speed

Anyone who's worked on projects long enough knows there's a huge range of leadership styles out there.

Some leaders are genuinely well-tuned for project work. They move at the pace projects require, almost instinctively. Some make it a little harder to get things done. Not because they're bad leaders—because project urgency isn't their natural language.

More often than not, the gap isn't a flaw. It's a real strength that serves them well somewhere else—in the department, in the business, in their career—showing up in a place where it doesn't quite fit.

Six patterns show up again and again with these leaders. Not because they don't care. Because each one is a real strength, overused.

Recognizing the pattern is the first step to designing around it.

The Conflict Avoider

"Let's not make this a bigger issue."

Strength: Protecting relationships.

When overused: Difficult conversations are delayed until they become project problems.

What happens:

• Performance issues linger

• Scope creep grows, unaddressed

• Risks go unmanaged, because naming them feels like starting a fight

• Accountability suffers, because nobody wants to be the one who calls it out

How great PMs overcome it:

• Name the issue in a low-stakes, private conversation before it ever becomes a group conversation

• Frame accountability around the project's success, not the person's failure

• Bring clear data points, not a warning—make it obvious why the issue needs to be addressed and what happens if it isn't

• Work behind the scenes yourself to resolve conflict between other team members, peer to peer, so you can bring the leader a short list of decisions to make—not a conflict to referee

• Document patterns quietly, so a recurring issue doesn't rely on memory alone

The Consensus Collector

"Let's make sure everyone agrees first."

Strength: Building collaboration and buy-in.

When overused: Decisions take too long, and ownership becomes unclear.

What happens:

• Decisions take too long

• Meetings multiply as more stakeholders get pulled in

• Accountability becomes unclear, since a group decision has no clear owner

• Timelines slip while consensus is still being built

How great PMs overcome it:

• Pre-align with key stakeholders individually before the group ever convenes

• Bring a single recommendation for the group to react to, not an open decision to build from scratch

• Set a decision deadline out loud, so "gathering input" has an actual end point

• Clarify who the real decision-maker is before the meeting starts, even in a consensus-driven culture

The Missing Leader

"Can we push this to next week?" (Or they're simply unavailable.)

Strength: Balancing multiple priorities and initiatives.

When overused: Decisions stall waiting on their availability, creating bottlenecks.

What happens:

• Decisions stall

• Approvals become bottlenecks

• Teams lose momentum waiting for an answer

• Vendors and partners wait on decisions that never come

How great PMs overcome it:

• Schedule recurring decision meetings instead of chasing ad hoc time on their calendar

• Bring decisions weeks before they're due, not the week of

• If a meeting is coming up that needs their input, ask to meet with them ahead of time—and ask if they're willing to send a delegate who can sit in and act as their go-between

• Build a bench of trusted advisors—a deputy, a chief of staff, a peer—who can unblock a decision when the leader genuinely can't get to it in time

• Never let something become urgent before you raise it

The Micromanager

"CC me on everything."

Strength: Protecting quality and reducing risk.

When overused: Team ownership declines and work slows to a crawl.

What happens:

• Team ownership declines

• Decisions funnel through one person, creating a bottleneck of their own making

• Work slows, because nothing moves until it's been reviewed

• People stop taking initiative, since initiative gets rewritten anyway

How great PMs overcome it:

• Build a review checkpoint into the plan up front, so oversight has a scheduled home instead of touching everything

• Sometimes you can't design it away—bake it into the plan instead: get deliverables to them sooner, and schedule working review sessions so they have a real chance to weigh in

• Give the team a low-risk deliverable to prove they can be trusted with it

• Ask what outcome they're protecting against, then build a quality check for that specific risk instead of reviewing everything

• Offer visibility without requiring involvement—a summary that answers "is this OK?" without needing sign-off on every step

The Command-and-Control Leader

"Just do what I said."

Strength: Driving consistency and clear direction.

When overused: Concerns go unspoken, and risks stay hidden until they're costly.

What happens:

• Team members stop raising concerns

• Risks stay hidden until they're expensive to fix

• Innovation declines, since nobody offers ideas that might just get overridden

• Problems surface late, when they cost the most to solve

How great PMs overcome it:

• Create a structured way to raise concerns that doesn't require debating the leader directly—a risk log, a pre-read, a written option

• Bring solutions framed as "here's what I'd recommend," not objections framed as "here's what's wrong with your plan"

• Ask questions instead of pushing back directly. "What would need to be true for this to work?" opens a door a direct objection closes.

• Protect the team's ability to flag risk early, even when the final call still sits with the leader

The Removed Leader

"I've done this before—I know how this works."

Strength: Hard-won, hands-on experience.

When overused: Decisions get made on outdated assumptions, without checking what's actually changed.

What happens:

• Decisions get made on a picture of the project that's already out of date

• Nobody double-checks the assumption, because the leader sounds certain

• Team members with real, current expertise get overridden, because their input runs up against a leader who's sure he already knows

• The gap between what they think is happening and what's actually happening grows, unnoticed, until it surfaces as a bigger problem than it needed to be

How great PMs overcome it:

• Confirm the current state out loud before the decision is made, even when they sound sure—"just to make sure we're both looking at the same thing"

• Create direct lines between the leader and the people actually in the weeds. Don't let yourself be the only filter—give subject matter experts real access and a real chance to be asked and heard directly.

• Bring the most recent data point, not the general status, so what's changed is obvious

• Ask what's changed since they were last close to this, rather than challenging what they think they know

When It Becomes a Bigger Problem

One of these patterns is a leadership quirk. Two or more, and it becomes genuinely difficult to manage a project around, this is where great project managers really get to excel and expand. You'll need to draw on more than one of these techniques at once.

What We Actually Do

The Missing Leader in Practice

One executive sponsor was responsible for multiple major initiatives, making it difficult to attend every steering committee meeting. Occasionally, a steering committee conflicted with other executive priorities, even when a critical decision was on the agenda. When we knew they couldn't attend and a decision required their input, we scheduled a 15-20 minute decision briefing beforehand. We came prepared with a recommendation, the key facts, and a clear ask. For routine discussions, a trusted delegate represented the sponsor's perspective and relayed key outcomes afterward. We didn't remove the sponsor from the process, and we didn't delay the project. We preserved executive engagement without creating a decision bottleneck.

The Conflict Avoidant Leader in Practice

One implementation stalled because two departments couldn't agree on ownership of a key process. Rather than escalating the disagreement to executive leadership, we facilitated a working session with both teams, documented the areas of agreement, and narrowed the remaining differences to two clear options. Leadership wasn't asked to resolve a conflict between departments—they were asked to make a business decision. The conversation was shorter, more productive, and preserved relationships on both sides.

The Real Lesson

These leaders aren't failing on purpose. They're leaning on a strength that's working against them here. Understanding that, and using it to set leaders up for success, is what gets you a seat at the better tables, asked to lead the better projects, and ultimately the good promotions. Not many project managers have this skill set.

Project will always be better served by strong leadership, but when you can't choose it, this is the skill that makes the difference.

If any of these patterns sound familiar, in your sponsor, your steering committee, or your own project, let's talk. We coach for these skills.