Leadership · 2026-05-09
Leading Without Authority: How Project Managers Build Influence
Project managers carry no formal authority over their teams — yet real project success depends on commitment and performance. Here's how to build genuine influence through Ethos, Pathos, and Logos — with real-world examples and three tactics most PMs overlook.
As project managers, we carry a crucial mandate from our sponsors: form a team and get a project done. But building a team isn't easy — especially if you're a stranger to them. Best practices tell us to define project roles and responsibilities. But that's not enough. A clear Roles & Responsibilities matrix won't automatically make people follow your lead.
So what's a PM to do? We can't just run to the sponsor every time there's an issue. That quickly breaks trust with your project team members. ("Did the PM really say that about me?!") Real project success comes from a motivated, dedicated team — not from forcing people.
The Eternal Truths of Influence: Logos, Pathos, and Ethos for PMs
When we lead without a title, we lean on old but powerful ideas: Logos, Pathos, and Ethos. You can read about them in articles like Harvard Business Review's "The Art of Persuasion Has Not Changed in 2,000 Years." But what do these three pillars look like for a Project Manager? Let's break them down.
Ethos: Below-Zero Authority
For a Project Manager, Ethos is the main challenge. A CEO or CFO walks into a room and people just listen. They have built-in authority. We don't. In fact, we often start with zero — or even negative — authority. We are often seen as the "non-expert" who just pushes people, without really understanding their work and profession.
So the first, most important rule is to respect their skills, their knowledge, their experience, and their professionalism.
Our Ethos isn't given to us. We build it, little by little, throughout the project. It grows when we show our worth. When our help makes a real difference. When work goes smoothly, when things are coordinated well, when our plans make sense, and when we fix problems fast. When team members feel heard, and their hard work matters — that's when our credibility grows.
Logos: The Clear Reason
My advice on which lever to use first? Start with Logos — logic and clear reasons. A big mistake many project managers make is pushing people in a given direction without explaining why.
The power of "because": Your most important hidden job is to truly understand and explain the "why." Why are we doing this project? How does it fit with the company's big picture? Why should anyone work extra hard for it? As Robert Cialdini found, people are much more likely to do something when you not only ask, but also explain the reason — even if the reason isn't perfect.
Next, make clear the "what" — exactly what needs to be done and what we need to deliver. Finally, talk about the "how." Key tip: involve team members in designing the "how" as much as possible. When people help plan the work, they become far more invested. They feel ownership over the plan. They take an active role in the project.
Pathos: Using Emotions
Pathos is about feelings and understanding. It can be a powerful tool — but it always needs a solid base of logic (Logos). From my own experience, there are a few things you must avoid if you don't want people to disengage. (More on that in a future article on stakeholder management.)
Are we really sure we want to stop this big train that's finally moving fast in the right direction? If we do, we need a very strong reason — and prepare for an unexpected conversation with the rest of leadership.
Real-life example: I once faced a critical Go / No-Go decision on a project. We were in a good position, and I'd already done the hard work of convincing the tough stakeholders. But another participant — who should have been an easy "Yes" — started raising doubts and slowing things down. I realized they hadn't kept up with the project. They weren't present when we worked through the big issues.
Instead of pushing, I used pathos — mixed with an analogy. The quote above is exactly what I said. It immediately made them think. They imagined themselves having to explain their weak doubts to the full leadership team. It worked. They got back on board.
Notice: I never positioned this as a battle between me and the stakeholder — even though it was exactly that. I used "we" the whole time, maintaining the appearance of being on the same side.
Subtle Influence: Hidden Ways to Get the Team on Your Side
Beyond the classic pillars, there are quieter — but equally powerful — ways to earn trust and make people genuinely want to work with you.
The "PM Gets It" Moment
When you talk about the work, dig into the details of their tasks. Have real, deep conversations. Try to step into their shoes — imagine a factory worker's specific job, a software developer's technical challenges, or a finance expert's rules and constraints. This takes real focus and effort, even when you're not the expert.
The moment that changed almost all my relationships with team members was when they saw that I "got it." That I truly heard them, understood how their task worked, and — most importantly — knew their limits. Only then did my requests and challenges truly matter to them.
Your Unofficial Role: Servant Leader
When you ask team members for their commitment, make a clear promise in return: "I will help any way I can." And you must follow through. Think of yourself as a bulldozer, clearing the path ahead of your team.
As a PM, you might not do their exact work — but you can handle the support tasks that are a pain for them: checking documents, writing drafts, gathering information, chasing approvals. When you consistently offer this kind of help, you earn the right to ask for what they need to deliver.
The Zero-Project Conversation
Here's a simple but powerful trick: don't talk only about work. When you bump into team members in the hallway, at the coffee machine, or in the elevator — resist the urge to jump to project tasks. Talk about something completely different. Close the chat without mentioning work or expectations at all.
This small habit makes you seem less like "the annoying PM" and helps build a more human connection. That connection pays back every time you need to ask for something difficult.
Leading without formal authority isn't about power plays or escalations — it's about mastering influence. Build your Ethos by proving your worth, day by day. Use Logos to give people clear reasons to commit. Apply Pathos to make it resonate.
That's how you truly lead — even when you're not the boss.