5 Signs You Have a Lazy Project Manager

A project manager can have a packed calendar, immaculate reports and a very busy week while avoiding the work that would actually help the project.

When I say “lazy”, I’m talking about a repeated reluctance to investigate, think ahead or exercise judgement. You won’t establish that by counting meetings or checking who worked latest.

Here are five behaviours worth examining.

1. They report what they’re told without challenging it

“Workstream says green” goes straight into the status report as green.

There’s no discussion about what supports that assessment, whether milestones have moved or which assumptions are becoming less credible.

A PM doesn’t need to interrogate every update. They do need to notice when the evidence and the story don’t agree.

If testing starts next week but the environment is unavailable, a green update needs an explanation. Passing it on unchanged leaves the next person to discover the contradiction.

2. Every problem becomes a meeting

Something goes wrong, so the PM books a meeting. A decision is needed, so they book another.

Meetings can be essential. The question is whether the PM has done enough preparation to make the conversation useful.

What needs resolving?

Who can resolve it?

What information do they need?

Could a short conversation between two people settle it?

Getting fourteen people together without a clear purpose consumes time and often leaves the original issue untouched.

3. They escalate without working through the options

“There’s a problem. What do you want us to do?”

Some issues require immediate escalation, even before all the facts are available. A PM should never delay raising a serious concern just to produce a polished recommendation.

Where time permits, though, an escalation should explain the issue, its impact, the options and the decision required. It should also identify when that decision is needed.

The PM may lack the authority to decide. They can still make the decision easier to take.

4. Their plan records the past without helping manage the future

The schedule is beautifully updated after things happen. Nobody is examining where delivery will become difficult next.

A useful plan helps the team look ahead.

Will two workstreams need the same specialist?

Is a supplier date squeezing testing?

Does a milestone depend on an approval nobody has requested?

Keeping records accurate matters. So does using them to prepare for what comes next.

5. They hide behind process

“The template requires it.”

Sometimes there’s a sound reason for a control, including contractual, regulatory or assurance requirements. A PM needs to understand those obligations.

They should also be able to explain how the process helps delivery. When a report is duplicated, a meeting has lost its purpose or an approval route creates avoidable delay, the PM should raise it and propose an appropriate change.

Following a process still requires judgement.

Check the conditions before judging the person

These behaviours can also reflect overload, limited experience, poor support or an organisation that discourages challenge.

Look for a pattern, discuss it and understand what’s driving it. A capable PM carrying an impossible workload needs support. An inexperienced PM may need coaching.

The question is what happens next. Does the PM investigate, adapt and help people move forward, or keep repeating activities that leave the same problems unresolved?