Accountability is easy to establish in a programme plan. Maintaining it when delivery becomes difficult is something else entirely.
On paper, accountability is explicit and visible. Then the programme comes under pressure.
Decisions that were clear become complicated. Timelines slip. Competing priorities emerge across functions. The people who were named as accountable begin to find that the boundaries of their accountability are less clear than they appeared. Ownership that was assigned starts to feel shared. And shared accountability, under pressure, becomes invisible accountability.
This is not a governance failure in the first instance. It is a leadership failure. And it is one of the most consistent patterns in complex transformation programmes that fragment under pressure.
Understanding why accountability diffuses under pressure is more useful than simply observing that it does.
When a programme is under stress, the instinct of most leadership teams is to focus on resolution. On solving the immediate problem. On managing the relationship with the board, the regulator or the funder. On protecting the programme’s forward momentum.
Accountability in that environment can feel like a distraction. The question of who owns a problem feels less important than the question of how to fix it. And so ownership quietly becomes collective while the focus shifts to the solution.
The problem is that collective ownership is not accountability. It is the absence of accountability dressed as collaboration. And when the next problem emerges, the same pattern repeats.
Most accountability frameworks are built for the conditions that exist at the start of a programme. Clear scope. Stable leadership. Defined responsibilities. Those conditions rarely persist unchanged across the life of a complex programme.
As the programme evolves, the accountability structures that were established at the outset become less precise. New workstreams emerge that do not map cleanly onto the original ownership model. Leadership changes. Functions that were separate begin to overlap. The structures that were designed to hold accountability in place stop fitting the reality of what the programme has become.
When accountability structures no longer fit the programme, accountability diffuses. Not because anyone has decided to abandon it. Because the structure that was supposed to hold it in place no longer applies.
In high-risk programmes, accountability requires that people name problems clearly and own them visibly. That requires an environment where doing so is safe. Where bad news is received as useful information. Where the person who surfaces a risk is not treated as the person responsible for creating it.
That environment does not always exist. In organisations where accountability has historically been associated with blame, the instinct under pressure is to manage risk quietly rather than surface it visibly. Problems get absorbed at the level where they are visible. Escalation routes that exist in theory are not used in practice. And accountability, which requires visibility to function, becomes invisible.
Shared accountability is the enemy of genuine accountability. When an outcome is owned by a team, a function, or a programme board, it is effectively owned by no one. The test of genuine accountability is whether a named individual will be the person who answers for the outcome if it goes wrong.
That does not mean individuals should be exposed to unreasonable risk. It means that at every significant decision point in the programme, there is a named person who owns the outcome and is visibly accountable for it.
The real test of an accountability structure is not how it functions when the programme is going well. It is how it functions when delivery is difficult, when the news is bad, and when the pressure to manage perception is strongest.
Maintaining accountability under those conditions requires active leadership discipline. It requires decision forums that hold their structure even when the situation is uncomfortable. Reporting that surfaces risk even when the news is difficult. An environment where naming a problem is understood as the responsible thing to do rather than a sign of failure.
Accountability requires that problems reach the people who have the authority and the responsibility to act on them. That means escalation routes that are understood, used, and taken seriously.
In many programmes, escalation exists as a theoretical mechanism that is rarely used in practice. Problems that should reach the board are resolved at programme level in ways that address the immediate issue without surfacing the underlying risk. The board believes the programme is under control. The programme is managing a set of risks the board does not know about.
That gap between what the board believes and what is actually happening is one of the most dangerous conditions in high-risk transformation. And it is a direct consequence of accountability structures that are not functioning as they should.
Accountability cannot function in an environment where surfacing problems is punished. Where the person who escalates a risk becomes associated with the risk itself. Where bad news is managed rather than acted on.
Creating an environment where accountability can function requires deliberate leadership effort. It requires that the people at the top of the organisation model the behaviour they are asking of others. That they receive difficult information with the same discipline they expect when they ask for honest reporting. That they make accountability visible by being visibly accountable themselves.
Not because they are accountable for everything that happens in the programme. But because the conditions in which accountability either functions or fails are conditions that leadership creates.
When leadership maintains discipline under pressure, when decision forums hold, when reporting is honest, when escalation routes are used, accountability functions. When leadership allows those conditions to erode, accountability erodes with them.
The Eleven17 Change Framework addresses accountability directly across the Align and Reinforce stages. Establishing the shared priorities and behavioural standards that accountability depends on, and then reinforcing the structures that hold it in place under sustained pressure.
Organisations often ask for greater accountability when programmes begin to lose momentum. In reality, accountability rarely emerges because people are told to take more ownership.
It develops when leaders create clarity around priorities, decisions, responsibilities, and outcomes. When those conditions are absent, accountability becomes difficult to sustain, regardless of individual capability or commitment.
In complex transformation programmes, executive accountability is therefore less about applying pressure and more about creating the environment in which responsibility can be exercised with confidence.
Leaders who understand this distinction are often better positioned to maintain momentum, navigate uncertainty, and support successful delivery.
If this reflects challenges within your organisation, we’d be happy to start a conversation.
The Eleven17 Change Framework sets out the full progression in detail.
Accountability does not disappear suddenly. It diffuses quietly at the points where leadership discipline weakens under pressure. If your programme requires stronger accountability structures and clearer governance oversight, we work directly with boards and senior teams at the points where it matters most.