There’s an uncomfortable truth floating around the world of project management that too few are willing to say out loud: a shocking number of people walking around with “Project Manager” in their email signature are not actually managing anything. They are PMs in name only (PMINOs), and the gap between the title and the behavior is a massive drag on organizational performance.
You’ve seen them. You’ve probably worked with them. Hell, if you’re honest, maybe earlier in your career, you were one before you got punched in the face by reality. A PMINO is someone who believes their value is derived from the title rather than the outcomes. Their job becomes an endless cycle of meetings, note-taking, talking through dependencies, updating trackers, exporting Gantt charts into PDFs, and creating slide decks for executives who don’t read them anyway.
But here’s the thing: none of those actions actually leads projects. None of those items connect strategy to execution. None of that ensures delivery or helps the organization change. Those things are administrative. They are service tasks. They are the minimum wage chores of project management. But because PMINO culture is deeply embedded across organizations, these tasks have been mistakenly elevated to the level of “project leadership.”
And leadership is the exact missing ingredient.
The best project managers are leaders. Full stop. They are translators of strategy. They are communicators of reality. They are facilitators of decision-making. They are protectors of outcomes and shepherds of risk. They have a bias for clarity and action. You don’t have to guess whether you’re dealing with one because the work moves. Teams align. Blockers surface. Decisions get made. Stakeholders understand what’s going on. And projects close.
In contrast, PMINOs spend their days inside the administrative comfort zone, never stepping into the arena where accountability and influence live.
Titles don’t equate to Leadership. A title is a label. It’s a box on an org chart. It costs nothing to hand out and even less to update. Slap a title on someone and it often creates the illusion that capability has been assigned.
But capability in project management is not derived from authority or proximity to the work. It’s leadership in context, and leadership in project environments is inherently messy.
Projects exist precisely because something new needs to happen. Something unknown must be created. Something has to change. Something must be delivered.
That requires navigation through ambiguity, constraint, conflict, limited resources, shifting priorities, and the ever-present “this would be easier if everyone just did what they were supposed to do” frustration that every project leader has tasted at some point.
A PMINO, confronted by that environment, tries to administer their way through it. Real PMs lead their way through it.
PMINOs worship the plan. Leaders navigate the reality. Another telltale sign of PMINO culture is the obsession with the plan as if the plan is the point. They labor over Microsoft Project files. They fight tooth and nail to defend dates that were never realistic. They create detailed artifacts that executives skim for eight seconds before asking, “So are we on track?”
But plans are guesses. They are necessary guesses. They are structured guesses. But they are guesses nonetheless. The point was never to protect the plan. The point is to deliver the outcomes the plan points toward.
I’ve watched PMINOs sit silently as the reality of the project diverged wildly from the plan because they believed their job was simply to “document what happened,” not to actually alter the trajectory.
That’s not project management; that’s stenography.
Leadership shows up when you’re willing to tell the truth about the gap between plan and reality, and then ask the hard question: “What are we going to do about it?”
One of the most toxic traits of the PMINO class is their instinct to avoid accountability at scale. They relentlessly disperse responsibility outward so nothing ever lands on them.
They hide behind phrases like: “Well, the team didn’t provide the updates.” “That’s a dependency outside of my control.” “I escalated it.” “No one told me the scope changed.” “I don’t have the authority to make that call.”
Listen closely and you’ll hear the subtext: “I refuse to own outcomes.”
Real project leaders have a default setting of ownership. That doesn’t mean they take accountability for the work itself (project management is coordination, not construction), but they take accountability for ensuring the work can happen.
They surface risks early. They broker decisions. They escalate effectively. They create clarity. They drive alignment. They push blockers off the tracks. They negotiate priorities. They protect the critical path. They adjust the plan when the situation changes. They make sure no one can credibly say, “I didn’t know.”
The PMINO, on the other hand, confuses “sharing updates” with “managing the project.”
One is communication. The other is leadership.
PMINOs think communication = transmission. Real PMs communicate for clarity & alignment. Sending information is not the same thing as communicating.
PMINOs push data: spreadsheets, slide decks, meeting summaries, emails, and Shopify-length project updates that bury the signal under a mountain of noise.
They assume that if the information left their outbox, communication has been achieved. This is the same logic a teenager uses when they grunt at the dinner table and then assume their parents fully understood their emotional world.
Leaders communicate for alignment, not for transmission.
Alignment means: people know the plan, they understand the why, they see their role, they know the risks, they know the next step, they know the timeline, they know who owns what, and they know what success looks like.
Everything else is administrative theater.
One of the more underappreciated differentiators is innovation. You can tell a lot about someone’s mindset by what they do when they encounter inefficiency, dysfunction, or organizational drag. The PMINO shrugs. The PMINO accepts. The PMINO adapts. The PMINO complains privately. The PMINO schedules another meeting.
The leader asks, “Why do we do it this way?” and then proceeds to innovate on the answer. They improve the system because they understand that the system produces the outcomes. Broken systems produce broken projects. Slow systems produce slow projects. Dysfunctional systems produce dysfunctional projects.
Leadership is not merely completing the project within the system. It’s improving the system so future projects aren’t forced to suffer unnecessarily.
This innovation dimension is why so many organizations stagnate. They’ve stacked their PM function with PMINOs who believe their role is project compliance rather than project acceleration.
The PMINO phenomenon is not just a talent problem; it’s a systems problem. Organizations have convinced themselves that project management is a title instead of a competency. So they hire to fill a title rather than to fulfill a strategic requirement. You don’t need someone who can run standups. You don’t need someone who can create trackers. You don’t need someone who can color-code Kanban lanes. You don’t need someone who can transcribe stakeholder conversations into Confluence pages.
You need someone who can drive change. Projects exist for one reason: the organization needs something to change. That change may be technological, operational, cultural, financial, structural, or strategic, but it is change nonetheless.
Where change exists, leadership is non-negotiable.
When organizations treat PMs like administrative staff, they get administrative outcomes: slow progress, endless meetings, and slide decks full of colorful status report delusion. When organizations hire for project leadership, the behavior changes.
But most companies don’t know how to screen for project leadership because they think in terms of certifications, software, and years of experience—none of which correlate strongly with delivery capability.
You can have a certification and still be a PMINO. You can have 10 years of experience and still be a PMINO. You can know how to use Jira, Asana, Smartsheet, and Microsoft Project and still be a PMINO.
Tools don’t make leaders. Titles don’t make leaders. Templates don’t make leaders. Leadership makes leaders.
At the core of the PMINO problem is a lack of courage.
Leadership requires courage because telling the truth is risky. Surfacing risk is uncomfortable. Pushing decisions creates tension. Challenging scope feels confrontational. Protecting teams creates conflict. Escalating blockers creates visibility. Negotiating resources creates friction. Insisting on clarity disrupts the comfortable fog of ambiguity.
PMINOs avoid these things. They gravitate toward activities that feel productive but are actually inert, like documenting, meeting, socializing ideas, formatting artifacts, organizing spaces, collecting updates, and capturing action items.
Real PMs don’t seek comfort. They seek resolution.
If you recognize yourself or someone you know in this article, good. That’s the point. Awareness is step one. Leadership skills can be developed, but they require humility and a willingness to sacrifice the comfort of the title for the discomfort of the role.
Here are five brutally direct shifts required to make the leap:
Shift from Reporting to Owning: Don’t just describe what’s happening. Influence it.
Shift from Updating to Aligning: Don’t just inform. Drive shared understanding and shared commitment.
Shift from Planning to Decision-Making: The plan is not the battle. The decisions are the battle.
Shift from Compliance to Change: The organization hired you to change something. Be a catalyst, not a clerk.:
Shift from Avoiding Risk to Surfacing Risk: Problems don’t get easier when ignored. They get more expensive.
The PMINO problem is crippling the effectiveness of organizations, slowing the pace of delivery, and watering down the strategic importance of project management as a discipline.
Project management at its best is not project paperwork. It is not administrative upkeep. It is not meeting hygiene or spreadsheet governance. It is not ceremonial status reporting.
Project management is leadership disguised as coordination. And leadership is the part that too many are skipping.
There is a widening chasm between project managers in name and project leaders in practice. The organizations that close this chasm (by hiring, developing, and empowering real project leaders with SKILLS) will consistently outperform those who continue to treat project management as an administrative cost center.
The future belongs to the project leader. The PMINO era is ending. And frankly, good riddance.
