The PMINO Problem

There’s an uncomfortable conversation that project management needs to have. Too many organizations think they have project managers. They don’t. They have meeting organizers. They have schedule maintainers. They have people who update dashboards. They have coordinators. They have note takers. They have software administrators. They have status collectors.

What they too often don’t have… is actual project leadership. I call this the PMINO problem: Project Managers In Name Only. And before anyone gets defensive, this is not meant as an attack on individual project managers.

Most PMINOs are not bad people. Most are trapped inside systems that trained them incorrectly. Organizations create PMINOs every day. Then they act surprised when projects fail.

Somewhere along the way, project management became administrative. Organizations started believing project management was little more than updating schedules, filling templates, sending reminders, maintaining RAID logs, documenting meetings, or managing project software.

Of course, those things matter. But they aren’t project management. Those are tools.

Project management is leadership under uncertainty. That means they have the ability to create clarity, make decisions, align stakeholders, manage resistance, reduce ambiguity, drive accountability, and protect the organization’s desired outcomes.

A project manager who can’t influence outcomes is not managing projects. They’re simply documenting projects. And documentation doesn’t help organizations get where they need to be.

You hear this constantly. “The team owns delivery.” “The sponsor owns delivery.” “The business owns delivery.” “The PM just coordinates.” Wrong.

Don’t get me wrong, the PM shouldn’t perform every task, but the PM absolutely owns creating the conditions for success. That means they own visibility, escalation, communication, prioritization, decision velocity, stakeholder engagement, issue management, and execution rhythm.

Think of it this way: if a quarterback doesn’t throw every block, do we say they are not responsible for the offense? Of course not.

Leadership is not doing all the work. Leadership is creating movement required for project success.

There are typically five things I look for when diagnosing PMINOs. They are

They Report Status Instead of Changing Status: PMINOs become professional observers. Every week its Green. Yellow. Green. Yellow. Red. Nothing changes. No interventions. No escalation. No decision requests. No recommendations. Status reporting is little more than theater.

A real PM asks: “What action changes this outcome?” A PMINO asks: “What color should I make the dashboard?” Those aren’t the same thing.

They Manage the Schedule Instead of Managing Reality: Schedules become comfort blankets for PMINOs. But schedules are often little more than predictions. Reality wins every time. PMINOs become obsessed with percent complete, due dates, Gantt charts, dependency arrows, and meetings.

Meanwhile, Stakeholders are disengaged. Risks are growing. Teams are overloaded. The scope is expanding. No amount of schedule maintenance fixes leadership failures.

A schedule should reflect execution. It should never replace execution.

They Fear Escalation: One of the biggest PMINO indicators I see is that they avoid uncomfortable conversations. They hope. They delay. They protect feelings. They hide risk. They soften language.

Then one day, the leadership team asks: “How did this happen?” Well… Because nobody escalated. Escalation isn’t failure. Escalation is leadership.

A PM should escalate blocked decisions, resource conflicts, unresolved risks, changing assumptions, stakeholder misalignment, or anything that will get in the way of achieving the desired deliverables.

When you escalate properly, you aren’t being difficult. You are protecting delivery.

They Think Communication Means Meetings: If your project requires twelve meetings to stay alive… It may already be (is probably) dead. PMINOs confuse activity with communication.

Communication isn’t calendar invites. Communication is clarity.

Good communication answers some highly relevant questions. What are we doing? Why are we doing it? Who owns it? What changed? What matters now? What happens next?

If meetings create more confusion than decisions… Cancel them.

They Avoid Decision Ownership: This one hurts. PMINOs often say, “I’m waiting.” Waiting for sponsor input. Waiting for team updates. Waiting for leadership. Waiting for approvals.

Real PMs create decision momentum. They say things like, “Here are three options.” “My recommendation is option two.” “Decision needed by Friday.”

That’s project leadership.

So, why do PMINOs exist?  Simple. Organizations reward administration.

Think about what gets praised. People say things like, “She keeps everything organized.” “He sends great notes.” “She built an amazing tracker.” “He updates everything.”

Important? Absolutely. Enough? Not even close. Nobody says she accelerated decisions, he aligned resistant stakeholders, she removed barriers, he protected team focus, or she prevented failures. Those are infinitely harder to measure. So they get ignored. Until projects fail.

PMINOs aren’t harmless. They create organizational drag. Projects become slower, more expensive, more political, more exhausting, and far less predictable.

So your teams begin asking, “What does the Project Manager actually do?” That question alone should terrify leaders. Because once teams lose confidence in project leadership… coordination starts collapsing.

Then everyone self-prioritizes. Communication fractures. Decisions slow, and execution drifts. Eventually, someone says, “Project management doesn’t add value.”

No. Bad project management doesn’t add value.

Here’s my stance. Project managers exist to reduce uncertainty. That means doing five things exceptionally well.

Create Clarity: Translate strategy into action. Turn: “We need transformation…” into: “These six outcomes happen by September.” Clarity beats motivation.

Create Alignment: Different stakeholders want different things. Someone must align timelines, expectations, resources, and priorities. That someone is usually/should be the PM.

Drive Decisions: Projects slow when decisions slow. A PM should constantly ask: What decision is holding us back? Who owns it? When is it due? What recommendation should I provide?

Manage Human Systems: Projects are emotional. People resist. People fear. People compete. People protect territory. Ignoring people is amateur project management.

Maintain Momentum: Projects rarely explode. They drift. Momentum prevents drift. Small wins. Fast decisions. Visible progress. Clear ownership. Movement creates confidence.

If you want to make sure you don’t become a PMINO ask yourself these questions.

This week: Did I solve problems, or document them? Did I escalate, or hope? Did I influence, or observe? Did I recommend, or wait? Did I clarify, or complicate? Did my stakeholders leave interactions with greater certainty?

If the answers are ‘no’, you may be operating as a PMINO. And that’s okay.

Awareness creates improvement. The first step is admitting you have a problem, right?

If you lead PMs, stop rewarding administrative excellence alone. Start rewarding: decision acceleration, stakeholder alignment, risk reduction, execution velocity, business outcomes

Ask your PMs, “What are you changing?” Not: “What are you tracking?”

Projects aren’t spreadsheets. They are an organized change. And project managers are supposed to lead change.

Project management was never meant to be passive. It was never meant to be a calendar role. It was never meant to be a reporting function. The best project managers I know are not always the most certified. They are the people who walk into uncertainty and create movement.

They create clarity. They make hard calls. They communicate relentlessly. They protect outcomes. They lead.

Because at the end of the day, a project manager who cannot influence delivery… isn’t managing projects. They are watching them happen.

Don’t be a PMINO.