This series has explored why projects stall before they start, when planning gets skipped in the rush to act. But even when a project is well-planned, there is another failure mode that is just as common, and just as avoidable. It is the question of who, exactly, is responsible for making it happen.
The accountability assumption
In a small team, a lot goes unsaid. That is often a genuine strength. Growing businesses move quickly precisely because there is less bureaucracy, fewer sign-offs, and a higher degree of mutual trust and understanding between the people involved.
But that same informality creates a particular kind of risk in project work. When responsibilities are assumed rather than agreed, when everyone believes someone else has picked up a task, and when the shared understanding of priorities turns out not to be shared at all, projects begin to drift. And often nobody notices until the drift has become a delay.
This is not a problem that only affects large organisations with complex hierarchies. In many respects it is more acute in smaller businesses, precisely because there are fewer people, roles are less defined, and the assumption of alignment runs deeper.
We’re a small team, we know what we’re doing
One of the most common things I hear at the start of a project in a growing business is some version of: we do not need a lot of process, we all know each other, we communicate well.
And it is usually true, as a general description of how the business operates day to day.
But a project is not day-to-day operations. It is a temporary, specific piece of work with its own timeline, its own dependencies, and its own demands on people who are already busy doing other things. The informal communication that keeps the business running smoothly is not the same as the structured accountability that keeps a project on track.
When those two things get confused, the results are predictable. Tasks sit in the gap between people, each assuming the other has picked them up. Decisions that need to be made wait for a conversation that never quite happens. Priorities shift without the project team being told, because nobody formally owns the communication.
The priority problem
There is a related assumption that is equally dangerous: that everyone involved in a project has the same view of how important it is, relative to everything else they are doing.
In a growing business, most people are operating at or near full capacity. When a project is added to someone’s existing responsibilities, it competes with work that has immediate, visible consequences if it is not done. The project, by contrast, has a deadline that feels further away, and consequences that are less immediate.
Without an explicit conversation about priority, and without someone actively managing the project’s claim on people’s time, the project tends to lose that competition. Not because anyone decides to deprioritise it, but because the day-to-day always feels more urgent.
This is how projects that everyone supports in principle end up being the thing that everyone is too busy to move forward in practice.
The cost of assumed alignment
The damage done by unclear accountability is often invisible at first. The project appears to be moving. People are attending meetings, tasks are being discussed, progress is being reported.
But underneath the surface, the gaps are accumulating. Actions from the last meeting have not been completed. A decision that was discussed has not actually been made. A dependency that was flagged has not been resolved.
By the time this becomes visible, the project is weeks or months behind, and the effort required to recover is significantly greater than the effort that would have been needed to prevent it.
What clear accountability actually looks like
Clarity on accountability does not require a formal project management framework or a dedicated project manager. But it does require a few deliberate habits that smaller businesses often skip in the interest of moving quickly.
It means agreeing, explicitly, who owns each workstream, and what that ownership means in practice. It means documenting decisions and actions, not to create bureaucracy, but because undocumented decisions tend to be unmade decisions. It means having a regular, structured touchpoint where progress is reviewed against commitments, not just discussed informally.
And it means someone taking responsibility for the project as a whole, not just their piece of it. In corporate settings that is the project manager’s role. In growing businesses it can be anyone, but it needs to be someone.
The value of an outside pair of eyes
One of the things external support does particularly well in project work is providing the neutral accountability that internal teams find difficult to sustain.
When everyone involved in a project is also running the business, it is genuinely hard to hold each other to account without it feeling personal. An external coordinator does not carry those dynamics. They can ask directly whether an action was completed, whether a decision has been made, whether the timeline is still realistic, in a way that keeps the project moving without damaging the relationships that the business depends on.
Accountability does not have to be uncomfortable. But it does have to exist. And in many growing businesses, ensuring it exists is one of the most valuable things an experienced outside hand can provide.
If you are running a project and finding that accountability is slipping, or if you are about to start one and want to make sure it does not, I am happy to talk through how the right support can help.
Get Ahead’s team works across the full range of project support, from planning and coordination to delivery and benefits tracking.
Get in touch: fiona@getaheadva.com | Explore our support: getaheadva.com



