Can you be accountable for a project without having the authority to make every decision?
For many project managers, the answer is yes.
You're expected to deliver projects on time, within budget, and to the required quality standards. Yet, critical decisions often depend on sponsors, functional managers, or senior leadership.
This creates one of the most challenging aspects of project management: being accountable for outcomes you cannot fully control.
Table of Contents
Accountability Doesn't Mean Control
Accountability means taking responsibility for managing delivery, communicating progress, and addressing challenges.
Authority, however, is the formal power to make decisions, allocate resources, and approve changes.
The distinction matters.
A project manager may be responsible for meeting a deadline but lack the authority to approve additional resources or resolve competing organisational priorities.
The challenge isn't necessarily a lack of authority. It's knowing how to lead effectively within those boundaries.
Influence Is a Project Management Skill
Effective project managers don't rely solely on their position.
They build relationships, communicate clearly, and provide decision-makers with the information needed to act.
Three practices make a difference:
Clarify decision rights: Understand who can approve changes, allocate resources, and resolve escalated issues.
Communicate consequences: Explain how delayed decisions affect cost, schedule, and risk.
Escalate proactively: Raise issues early, with practical options and recommendations.
These actions help maintain momentum without overstepping authority.
Leadership Goes Beyond Job Titles
Project management isn't about controlling every decision.
It's about creating alignment, enabling informed decisions, and maintaining accountability throughout delivery.
You don't need authority over everyone to lead a project effectively. But you do need clarity about who decides what.
This Week's Reflection
Are you being held accountable for outcomes without having the authority needed to influence them?
And more importantly, have you established the right relationships and escalation pathways to bridge that gap?
I'd be interested to hear your perspective.
P.S. If we haven't connected yet, let's connect on LinkedIn and exchange perspectives on engineering, project management, and leadership.
If you found this useful, feel free to share it with another project professional.
And if you haven't already, subscribe to The Saturday Mindset to receive practical insights in your inbox every Saturday.
Thanks for reading, and until next Saturday!
