Everyone Is Busy - But Who Actually Owns the Project?
One of the strangest things about struggling projects is that everybody can be incredibly busy.
Meetings are happening, emails are flying around, actions are being chased, people are solving problems, suppliers are being contacted, updates are being prepared.
From the outside, it can look like a lot is happening.
And yet the project still drifts.
Why?
Because activity and ownership are not the same thing.
Plenty of activity. Not enough ownership.
A project can have lots of people involved without anybody really being accountable for moving the whole thing forward.
That is particularly common in smaller organisations.
The project might sit somewhere between operations, finance, IT, sales and a supplier.
Everybody owns their piece.
But who owns the project?
Who is looking across all of it?
Who is checking whether the different pieces still fit together?
Who is making sure decisions happen when they need to?
Who knows whether the overall project is still on track?
If the answer is unclear, that is a warning sign.
Ownership isn't the same as doing everything
Project ownership doesn't mean one person has to carry out every task.
Quite the opposite.
Good project delivery depends on different people taking responsibility for their own areas.
But somebody still needs to maintain the overall picture.
That means knowing:
what needs to happen next
who is responsible for it
what is late
where decisions are needed
what risks are increasing
whether one delayed activity is affecting something else
whether the original completion date is still realistic
Without that overall ownership, the project can become a collection of separate tasks rather than one coordinated piece of work.
The gaps are where projects get into trouble
Most organisations are reasonably good at dealing with clearly allocated work.
Finance deals with finance.
IT deals with systems.
Operations deals with operations.
Suppliers deal with their contractual responsibilities.
The problems often appear in the gaps between them.
A supplier is waiting for a decision from the business.
Operations assumes IT is arranging something.
IT thinks the supplier is doing it.
Nobody realises an approval is required until the deadline is almost here.
Individually, everyone may have done exactly what they thought they were supposed to do.
But the project still slips.
That is why somebody has to own the connections between the work, not just the individual activities.
Meetings can hide the problem
Regular project meetings can sometimes create a false sense of control.
There is an agenda, there are updates, people attend, actions are recorded.
But that does not necessarily mean the project is being actively managed.
A useful project meeting should help answer some basic questions:
What has changed since the last meeting?
What needs to happen next?
What is getting in the way?
What decisions are required?
Who owns each action?
What happens if something doesn't happen on time?
And does any of this change our confidence in the overall delivery?
If the meeting is simply a sequence of people giving updates, the project can remain busy without becoming any clearer.
"We all own it" usually means something else
Shared responsibility sounds positive.
And there are certainly projects where several people need to feel genuine ownership of the outcome.
But there is a danger in saying:
"We all own the project."
Because operationally, somebody still needs to coordinate it.
Shared commitment is useful.
Shared accountability without clear roles is much less useful.
Projects need people to own tasks, decisions and outcomes.
But they also need somebody with responsibility for seeing the whole picture.
This doesn't always mean hiring a project manager
For smaller projects, the answer may simply be to make one person's role much clearer.
Give them authority to coordinate the work.
Give them enough time.
Make sure they can get decisions when they need them.
Provide some simple tools for tracking progress, actions, risks and issues.
For larger or more complex projects, more formal project management support may be needed.
The important thing is not the job title.
It is whether somebody is actually managing the project as a whole.
A useful warning sign
If you want a simple test, ask this:
If I wanted to know exactly where this project stands today, who would I ask?
There should be an obvious answer.
And that person should be able to explain:
what has been completed
what still needs to happen
what is currently causing concern
what decisions are outstanding
whether the project is realistically on track
If there isn't an obvious answer, the project may have an ownership problem.
Assessing the bigger picture
Unclear ownership is rarely the only issue.
It often sits alongside other warning signs such as weak planning, unclear scope, delayed decisions, overloaded people or poor visibility of risk.
That is why looking at the whole project rather than one symptom can be useful.
The No Fluff Project Assessment is designed to identify those practical delivery issues and show where attention is needed before they become bigger problems.
No Fluff Takeaway
Clear ownership does not need complicated governance.
For many projects, it comes down to something much simpler:
one person understands the whole picture
people know what they are responsible for
decisions have clear owners
actions are followed through
problems are surfaced early
And somebody is accountable for making sure all those separate pieces come together.
A project can have a lot of activity without having much control.
“Everyone is busy” is not the same thing as “the project is being managed.”
Comments