Leading Without Authority: How Project Managers Get Things Done

The authority gap is one of the most disorienting aspects of project management for people coming from functional roles. A functional manager has a team, a reporting line, and — in theory — the authority to direct people's work. A project manager typically has none of these things. The developers, engineers, analysts, and specialists who will do the actual work report to their functional managers, not to the project manager. Their performance reviews are written by someone else. Their priorities are set by someone else. The project manager is accountable for the outcome but does not control the means of producing it. This is not an oversight or a structural flaw that better organisations have fixed — it is the normal condition of project work in most organisations. The project managers who are effective in this environment have learned to lead through influence rather than authority.

Influence techniques that actually work

1. Building credibility early. Influence starts before the project does. People extend discretionary effort to project managers they believe know what they are doing. In the first weeks of a project, demonstrating that you understand the technical context, the business problem, and the constraints the team is working within buys you credibility that is very difficult to earn later. Asking good questions — not knowing the answers yet, but knowing which questions matter — is often more effective at establishing credibility than displaying expertise.

2. Making stakeholders look good. People will help you when helping you makes them successful. The most effective project managers think explicitly about how their key stakeholders define success and how the project can be positioned to serve those goals. A business analyst whose performance is evaluated on how well requirements are delivered to development is more likely to invest discretionary effort if the project manager creates visible recognition for their contribution. This is not manipulation — it is alignment.

3. Creating clarity. People follow clear direction. In environments where priorities are shifting, resources are contested, and stakeholders have competing agendas, a project manager who provides precise, current, and credible clarity about what needs to happen next exercises influence that has nothing to do with authority. Ambiguity is the enemy of discretionary effort: when people are uncertain about priorities, they default to their functional manager's priorities — not yours.

4. Reciprocity and the influence bank. Cialdini's principle of reciprocity applies directly to project work. Project managers who help team members solve their problems — removing bureaucratic obstacles, advocating for resources, running interference with difficult stakeholders — build a relationship bank they can draw on when they need extraordinary commitment. The influence bank is not transactional in a cynical sense: it is the natural result of genuine investment in people's success over time.

5. Using the sponsor's authority judiciously. Every project should have an executive sponsor whose formal authority can be invoked when influence alone is insufficient. The project manager's skill is knowing when to invoke it and when not to. A project manager who escalates to the sponsor routinely signals that they cannot manage their own stakeholder relationships. A project manager who never escalates may be absorbing risks that the sponsor needs to be aware of. The right pattern is: exhaust influence-based approaches first, escalate cleanly with a clear framing of what decision or intervention is needed, and do not use the sponsor's authority as a substitute for doing the influence work yourself.

What to do when influence fails

There are situations where influence will not be sufficient. A team member who is chronically under-delivering because their functional manager has redirected their priorities is a resource conflict, not an influence problem. The appropriate response is escalation — not to punish anyone, but to surface the conflict to the level at which it can actually be resolved. Escalation through the sponsor is the first option. If the sponsor engagement does not resolve the issue, the risk must be formally logged: the project is at risk because of a resource constraint that is outside the project manager's control, and the decision to accept that risk or address it belongs to the steering committee or executive team, not the PM.

Authority versus accountability

The authority-accountability mismatch in project management is a feature of the role, not a bug. Organisations structure work this way because functional specialisation produces better specialists than project-dedicated teams in most contexts, and because maintaining functional expertise requires that specialists report into functions, not projects. The project manager's accountability is real — for timeline, budget, scope, and quality outcomes — and so is the absence of commensurate direct authority. Accepting that condition and developing the influence skills to operate effectively within it is what separates experienced project managers from those who are still waiting for an authority structure that will never arrive.

If your organisation is investing in project management capability and finding that certified PMs are still struggling to deliver results, XNM's program and project delivery advisory can help you understand whether the gap is methodology, influence skill, or governance — and build the capability that actually closes it.