Accountable Leadership: Leading Without Command and Control

Many project managers learned their trade in organisations where accountability and control were treated as the same thing. If you were answerable for the outcome, you signed off the decisions, reviewed the work before it went anywhere and made sure nothing significant happened without your knowledge. On plenty of projects that approach delivered. It also carries a cost that tends to stay hidden until the project grows. Decisions queue behind one person, and problems travel slowly because people wait to be asked. Over time, the team learns that thinking ahead is somebody else's job.

The opposite mistake is just as common and harder to spot. A project manager who has absorbed the language of empowerment steps back so far that nobody is quite sure who decides anything. Meetings are well facilitated and the team is consulted. Yet when something goes wrong, the answer to "whose call was that?" is an uncomfortable silence.

Accountable leadership sits between those two failures. The leader personally owns outcomes, decisions and consequences, and builds enough clarity around the team that people can act well without asking permission. The leader does not control every action. They do remain answerable for the conditions in which those actions were taken, and they do not pass that answerability down when the news is bad.

Control and accountability are different things

Control concerns actions: who does what, who approves it, who checks it. Accountability concerns answerability: who explains the outcome, owns the consequences and puts things right. The two overlap, but treating them as one creates a predictable problem. A project manager who believes accountability requires control will keep pulling decisions towards themselves, because releasing a decision feels like releasing responsibility for it.

The distinction is familiar from responsibility assignment matrices, where the person responsible for doing a piece of work is not necessarily the person accountable for it. On a live project it plays out daily. A site supervisor, a lead developer or a finance analyst can own a decision within their area. The project manager still answers for whether that decision sat inside a sensible boundary, was based on the right information and was visible to the people who needed to know. Section 3.6 of The Standard for Project Management, published alongside the PMBOK® Guide Eighth Edition, frames being an accountable leader in a similar spirit: ownership, judgement and ethical conduct applied with an eye on context, rather than authority exercised over every task.

Seen that way, neither extreme is truly accountable. Command and control can look accountable because the leader is visibly involved in everything, yet it often produces less real ownership. Problems stay hidden until the leader finds them, and people protect themselves by pushing decisions upwards. Abdication presented as empowerment looks modern but leaves the team exposed. When a sponsor asks why a milestone moved, a leader who answers "the team decided" has not led without control. They have simply stopped leading.

What accountable leadership looks like day to day

The first visible habit is that decision boundaries are made explicit before they are tested. The team knows which calls are theirs, which belong to the project manager and which need a sponsor or governance body. This is less a document than a conversation. It needs revisiting when the project changes shape, because boundaries that suited mobilisation rarely suit commissioning.

Accountable leaders also give intent rather than only instructions. Some people understand what the work is for, which constraints are fixed and what good looks like, and they can adapt sensibly when the plan meets reality. Others have only been given instructions, so they stop and wait, which quietly returns every decision to the leader.

When a decision genuinely belongs to the leader, they make it, on time and with the information available. Some leaders commission another round of analysis to avoid owning an uncomfortable call, which lets them look diligent while dodging accountability. The same leader surfaces bad news early rather than waiting until a recovery plan is ready to go with it. A sponsor who hears late tends to lose confidence in everything else they are told.

Perhaps the clearest marker is how consequences are handled. Sometimes a decision made within agreed boundaries turns out badly. The accountable leader then answers for it to stakeholders and reviews it privately with the person who made it. Defending the team in public and examining the decision in private are not contradictory. Together they keep people willing to use judgement while still improving it.

If you are unsure whether you are leading or controlling, try a simple test. Take any recurring decision and ask three questions:

1. Who should be making this call?
2. What do they need from me to make it well?
3. How would I find out quickly if it were going wrong?

If the third question has no good answer, the instinct to keep the decision is understandable. The remedy, though, is usually better visibility rather than tighter approval.

When the team makes a call you would not have made

Consider a fictional solar farm approaching its grid connection. After a fortnight of heavy rain, the cable installation supervisor finds the planned trench route along a field boundary waterlogged. Pushing plant through soft ground would risk damaging the ducting. Instead, he resequences the crew to complete the substation end first and leaves the field section until the ground firms up. It is a sound engineering decision and well within the day-to-day authority his role carries. It also means the cable run will not be ready for a witness test the network operator had booked, and the next available slot is eleven days later.

The project manager hears about it from the sponsor, who heard about it from the network operator.

The command-and-control reflex is to take the drawing back and insist that every future resequencing comes through the project manager first. That feels like accountability, but it penalises a good decision and slows every later one. It also teaches the supervisor that exercising judgement is risky. The abdicating response is to tell the sponsor that the site team made the change. That is accurate and helps nobody: not the sponsor, not the relationship with the network operator and not the supervisor.

The accountable response has two parts. The first faces upwards: the project manager tells the sponsor they own it. The decision was taken within boundaries they had set, and it protected the asset. It has cost eleven days against the connection milestone, and they explain how that will be recovered or absorbed.

The second part is a separate conversation with the supervisor about what the situation revealed. The engineering judgement was right. What was missing was a boundary nobody had thought to draw: changes affecting a commitment to an external party need a quick heads-up before they happen, even when the decision itself stays on site. The supervisor keeps his authority and the boundary becomes sharper. The sponsor gets a straight answer from the person who should give it.

Notice what the project manager avoided. They did not pretend the slip was unimportant or send the supervisor to explain himself to the sponsor. Nor did they react to one uncomfortable outcome by pulling back decisions that had been working well.

Reading the situation, on the project and in the exam

Accountable leadership does not mean never taking control. Directing can be exactly right in several situations:

• there is an immediate safety concern;
• someone lacks the experience for a particular call;
• a decision exceeds the team's authority;
• speed matters more than consultation.

Taking a decision back in those circumstances is part of the judgement the principle asks for. The difference is that an accountable leader takes control deliberately, for a reason they could explain to anyone involved, and hands it back once the reason has passed.

The form accountability takes also shifts with the delivery approach. In predictive environments it usually runs through formal delegation: authority levels, tolerances, change thresholds and a clear escalation route. Those structures are not the enemy of empowered teams. Used well, they are precisely what allows people to act without checking in every time.

In adaptive teams, the team typically owns how the work is done, and a product owner or equivalent owns priorities. The leader's accountability therefore moves towards the conditions around the team: clearing impediments, keeping stakeholders aligned and protecting the boundaries that make self-management workable. Hybrid projects tend to test accountability hardest at the seams, where a team-level decision quietly touches a governance commitment, as the cable resequencing did.

For a PMP® candidate, this principle sits naturally within the People domain of the current Examination Content Outline, which accounts for 33% of exam items. That domain's task on leading the project team includes:

• setting expectations;
• empowering the team;
• establishing clear roles and responsibilities;
• choosing a leadership style that suits the situation.

PMP preparation can sometimes leave candidates with the impression that empowering the team is the safest response whenever a people problem appears. A more dependable habit is to read a scenario for the facts that decide it: who holds authority, and what is at risk. Ask too whether the people involved have what they need to decide well, and whether the leader should own something rather than hand it on. If you want to build that habit across a wide range of situations, the PMP® Exam Preparation course works through leadership judgement alongside the rest of the syllabus, not as a list of preferred answers.

On your own project, the quickest way to see where you stand is to look at the last decision that went wrong. Did you answer for it, or did someone else? And did your response make the next decision better informed, or simply more centralised? Accountable leadership shows less in how much you control and more in how the project behaves when you are not in the room. It also shows in who stands up when the result is uncomfortable.

Andre Malowney

Interested in going further?

Leadership judgement rarely depends on knowing the principle. It depends on spotting who owns the decision and what is at stake, and structured preparation gives you repeated practice at reading those facts before you choose a response.

To read the accountable leader principle in its full context, alongside the other five principles, go to the PMBOK® Guide Eighth Edition.

Ad · Amazon affiliate link.

References

A039: Servant Leadership in PMP: When It Fits and When It Doesn’t
A043: When Should a Project Manager Escalate?
A149: Coaching vs Directing: Choosing the Right Leadership Response
A197: Before Escalating: What Should a Project Manager Check First?
A041: Empowered Teams Still Need Leadership

PMP and PMBOK are registered marks of the Project Management Institute, Inc.