Project leaders are often accountable for outcomes produced by people they do not control.
Many project managers discover a difficult truth only after they receive the title: responsibility can increase faster than authority.
A project manager may be accountable for schedule, cost, scope, risk and delivery while critical engineers still report to functional managers, procurement follows separate policies, contractors answer to commercial agreements, and senior stakeholders retain key decisions. The leader is expected to integrate the system without owning every part of it.
This is not an exception in modern organisations. It is the normal condition of cross-functional work.
The Strategic Context
The supplied project-leadership material distinguishes project environments from functional management. Functional managers normally operate within continuing organisational structures, often with clearer authority over people and specialist capability. Project managers operate through temporary structures that cut across those functions.
This creates a form of structural dependency. Projects need people, information, decisions and cooperation from units whose priorities may differ. The project manager therefore works through a network of relationships rather than a single chain of command.
The Karpin review reinforces a similar point at enterprise level by discussing the need to move beyond an assumption of authority toward negotiating interdependencies. That insight is especially relevant to programs, transformations, alliances and matrix organisations.
What Leaders Commonly Misread
A common response to limited authority is to seek more authority. Sometimes that is justified, particularly where decision rights are genuinely unclear. But formal authority cannot solve every dependency.
The second misreading is assuming that stakeholder engagement is mainly communication. Sending reports is not the same as creating commitment. A functional leader who loses a scarce engineer to a project incurs an opportunity cost. A sponsor who approves change accepts political and financial consequences. A supplier asked to accelerate work may need to reconfigure its own capacity.
Influence begins by understanding those interests rather than merely repeating project needs.
The third mistake is confusing consensus with leadership. Influence does not require universal agreement. It requires sufficient alignment to move the work forward while making disagreement visible and governable.
Reframing the Issue
The project leader's job is not to command a temporary organisation. It is to assemble a workable coalition around an outcome.
That coalition has four elements:
- shared understanding of the objective;
- clear decision and accountability boundaries;
- credible commitments of people and resources;
- a mechanism for resolving conflict when interests diverge.
When these are weak, the project manager becomes a courier between functions. When they are strong, the project becomes an integrating mechanism for the organisation.
Influence Starts With Dependency Mapping
Most project plans map tasks more precisely than dependencies between decision-makers. Yet the latter often determine whether the former can happen.
A practical dependency map should identify not only who performs work, but who controls scarce skills, who can accept risk, who approves money, who owns operational transition, who can stop the work and who will live with the result after closure.
In a matrix structure, the most important relationship may not be with the person performing the task. It may be with the functional manager who decides whether that person remains available next month.
Credibility Is a Form of Operating Capital
Influence becomes easier when other leaders trust the project manager's judgement. Credibility is built through consistent behaviour: surfacing bad news early, making trade-offs visible, avoiding artificial certainty, respecting specialist knowledge and not escalating every disagreement prematurely.
A leader who exaggerates urgency eventually devalues urgency. A leader who hides uncertainty loses the right to ask others for trust when uncertainty becomes unavoidable.
This is why integrity and influence are closely connected. People are more willing to share scarce resources and accept difficult choices when they believe the process is fair and the information is reliable.
Negotiation Is Part of Delivery
Negotiation in projects is not limited to contracts. It occurs continuously around priorities, people, scope, sequence, risk and timing.
A strong project leader approaches these discussions with an enterprise perspective. Instead of saying, "My project needs this engineer," the better question is, "Which use of this engineer creates the greatest organisational value, and what consequence follows from each option?"
That shift matters because functional leaders may be protecting equally legitimate commitments. The goal is not to win resources at any cost. It is to make the opportunity cost explicit and move the decision to the level that can legitimately resolve it.
Influence Depends on Understanding Other People's Systems
Influence is often taught as a communication skill, but effective influence requires system understanding. A functional manager protecting a specialist may be responding to maintenance commitments, customer deadlines, capability risk or their own performance measures. A supplier resisting acceleration may face contractual, workforce or technical constraints that the project cannot see.
Project leaders become more persuasive when they can describe those constraints accurately. That creates the possibility of a real trade-off rather than a contest of urgency.
This is particularly important in programs where dependencies cross several projects. A request that looks small inside one workstream can create cascading disruption elsewhere. Influence improves when leaders understand those second-order effects before seeking commitment.
Sponsor Authority Should Be Used Carefully
Sponsors can resolve deadlock because they carry organisational authority. Overuse of that authority, however, can weaken the relationships the project needs to function.
If every resource dispute goes to the sponsor, functional leaders learn that negotiation is optional and project managers learn that escalation is easier than coalition-building. A strong sponsor therefore protects project legitimacy while expecting the project leader to resolve issues at the lowest sensible level.
Escalation should be based on consequence, not frustration. It is justified when a decision exceeds delegated authority, affects enterprise priorities, changes accepted risk or cannot be resolved within the time available. That keeps executive authority available for the decisions that genuinely need it.
Decision Framework
When influence is required, test the situation across five dimensions.
| Dimension | Leadership question |
|---|---|
| Outcome | What shared result can the parties align around? |
| Interest | What does each party gain, lose or risk? |
| Authority | Who has the formal right to decide? |
| Dependency | Whose cooperation is required even after the decision? |
| Escalation | What threshold justifies moving the issue higher? |
The framework prevents two common errors: escalating too early and negotiating indefinitely when a legitimate authority should decide.
From Strategy to Execution
Immediate action: identify the ten relationships most critical to the project's next major outcome. Clarify what each party controls, what they need from the project and where commitments are weak.
Medium-term capability building: establish decision rights, resource agreements and escalation rules with functional leaders. Build regular forums around real dependencies rather than creating meetings simply because a governance template expects them.
Long-term strategic positioning: design the organisation so temporary initiatives can access capability without repeatedly destabilising functional operations. This may require portfolio-level resource governance, stronger program structures or explicit capacity reserves for strategic work.
Related article: RACI Is Not Accountability: Designing Decision Rights in Matrix Projects
Related article: Resource Planning Is a Strategic Choice, Not a Staffing Exercise
Signals to Monitor
Warning signs include repeated resource promises that do not translate into availability, decisions revisited because affected functions were not genuinely aligned, excessive reliance on sponsor escalation, project managers acting as intermediaries for conversations that should occur directly, and functional leaders treating project work as optional.
Positive signals include early surfacing of constraints, direct cross-functional problem-solving, stable commitments, rapid resolution of genuine decision conflicts and stakeholders who understand not only what the project wants, but why it matters.
Questions for the Leadership Team
- Where does accountability currently exceed formal authority in our major initiatives?
- Which dependencies are managed mainly through goodwill rather than explicit agreements?
- What scarce capabilities are several projects competing for simultaneously?
- Are our escalation paths resolving issues or merely moving them upward?
- Which stakeholders have the power to delay value without having formal decision rights?
- Do our project leaders understand enterprise trade-offs well enough to negotiate credibly?
Closing Perspective
Formal authority is useful, but it is an incomplete theory of delivery.
Complex work crosses boundaries that hierarchy cannot remove. The project leader who waits for complete control will either become frustrated or become authoritarian. The stronger alternative is disciplined influence: understand dependencies, build credibility, negotiate interests, clarify decisions and escalate only when the issue genuinely exceeds delegated authority.
The measure of leadership is not how many people report to you. It is whether people who do not report to you can still combine their efforts to produce the intended result.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.