Two ways accountability fails

Accountability fails in operational organisations in two distinct ways, and they pull in opposite directions.

The first is an absence of accountability — environments where performance gaps persist without consequence, where commitments are regularly missed without serious follow-up, where the gap between what was agreed and what was delivered is habitually rationalised rather than addressed. These organisations underperform consistently and often without fully understanding why.

The second is a version of accountability that has collapsed into bureaucracy — where the drive to hold people to account generates so many reviews, reports, escalation processes, and governance layers that the organisation's capacity to move quickly is fundamentally compromised. People spend more time managing accountability systems than doing the work those systems were designed to support.

Neither of these is a healthy operating state. The goal is something more difficult to achieve: environments where high performance is genuinely expected and supported, where accountability is clear and exercised consistently, and where the overhead of managing that accountability is minimal enough that it does not become the dominant activity of the people it involves.

What makes accountability work

Accountability requires two things that are frequently treated as optional. The first is clarity about what is expected — genuine clarity, not the kind that exists in a document that no one reads, but the kind that lives in the shared understanding of a team about what success looks like, who is responsible for it, and by when.

This sounds like it should be straightforward to achieve. In practice, it is one of the most consistently underdeveloped conditions in underperforming organisations. Responsibilities are defined at a level of abstraction that does not translate easily into observable outcomes. Targets are set without the specificity required to evaluate whether they have been met. The ownership of cross-functional outcomes — the ones where multiple teams contribute to a shared result — is diffuse enough that accountability cannot meaningfully be held.

The second condition is a consistent response to performance — one that is not subject to discretion based on who the individual is, how well-regarded they are, or how uncomfortable the conversation would be. Selective accountability — where standards are enforced rigorously for some and managed leniently for others — does more damage to the conditions for high performance than no accountability system at all. It communicates, in the clearest possible terms, that the standard is negotiable, and that negotiation favours those with seniority, relationships, or political capital over those who simply do the work well.

The bureaucracy trap

The bureaucracy that accountability generates typically originates in a genuine intention to improve performance. A project misses a milestone. The response is an additional review process to ensure milestones are not missed again. A piece of work is delivered below standard. The response is an additional approval step to ensure quality is reviewed before delivery. Each individual intervention has a reasonable rationale. The cumulative effect is an organisation that has added layer upon layer of process to manage a performance problem, with the result that the capable people in the organisation — the ones who would perform well without those layers — spend an increasing proportion of their time navigating them.

The test for whether an accountability mechanism is earning its overhead is simple: does it generate information or decisions that improve performance, or does it generate activity that satisfies the requirement to have a process without materially changing outcomes? Most organisations have a significant proportion of the latter, often inherited from an earlier period when the mechanism had a purpose that is no longer current.

Reducing bureaucratic overhead is not a matter of lowering standards. It is a matter of designing accountability mechanisms that are proportionate to the risk they are managing and honest about the value they are generating. The review that takes three people two hours to prepare for and produces no decisions that would not have been made anyway is not accountability — it is its simulation.

Building accountability into how teams work

The most effective accountability in high-performing teams is not predominantly top-down. It exists within the team — in the norms and expectations that team members hold each other to, in the peer pressure that a high-performing group exerts when someone's contribution falls below the standard the team has set for itself.

This kind of accountability is both more effective and less costly than externally imposed mechanisms. It is more effective because it is immediate — it responds to emerging performance issues without waiting for a formal review cycle. It is less costly because it does not require a parallel governance structure to sustain it. And it is more robust because it does not depend on any single leader's willingness to enforce it.

Building team-level accountability requires a different kind of investment than building formal governance structures. It requires time spent on the clarity of shared expectations — ensuring that each team member genuinely understands what the group is trying to achieve and how their contribution connects to that objective. It requires the development of psychological safety that makes it possible for team members to raise performance concerns directly without damaging their relationships. And it requires a team culture in which high standards are a source of professional pride rather than an external imposition.

The leadership role

The leader's role in an accountable team is not to be the sole enforcer of standards. It is to create the conditions in which standards are owned by the team itself, to model the behaviour they want to see replicated, and to ensure that the formal accountability mechanisms they maintain are fit for purpose — adding genuine value rather than simply generating the appearance of rigour.

Leaders who are consistently direct about performance — who name gaps clearly, hold the standard even when it is uncomfortable, and demonstrate through their own behaviour that the commitments they make will be kept — create teams that reflect those qualities. The inverse is equally true: leaders who manage around performance problems, who allow commitments to be renegotiated without adequate justification, or who hold different people to different standards based on factors other than their performance, produce teams that replicate those patterns.

Accountability is not primarily a system. It is a culture — one that is built through the daily practice of holding and being held to clear standards, and sustained by the trust that practice generates over time.