How Much Project Management Is Enough?
Not every project needs a full-time project manager.
And not every project needs a detailed methodology, endless meetings or a small mountain of reporting.
But every project needs enough project management to keep it under control.
So how much is enough?
The answer depends far more on the project you are dealing with than on how big it is.
Start with the type of project
One of the first things I ask about a project is:
How well do you know what the finished result will look like?
Then:
How well do you know how you are going to get there?
Those two questions matter.
If you have done something very similar several times before, know exactly what needs delivering and understand the route to get there, you may not need much project management at all.
You have a plan.
Follow it.
But plenty of projects aren't like that.
You may know what you want to achieve but not yet know exactly how you are going to achieve it.
Or you may be introducing something genuinely new, where both the solution and the route towards it will develop as the project progresses.
That changes the amount and type of management you need.
If you don't know all the activities at the start, you probably don't know all the risks either.
Your initial timescales may change.
Your budget may prove optimistic.
And pretending otherwise by producing an increasingly detailed plan doesn't solve the problem.
You need an approach that allows you to test, learn and adapt.
So before deciding how much project management you need, understand what sort of project you are actually dealing with.
Small doesn't necessarily mean simple
This is where organisations can get caught out.
A project might have a relatively small budget and only involve a handful of people.
That doesn't automatically make it straightforward.
Installing a new piece of equipment might affect production, IT, suppliers, training and customers.
Introducing a new system might change how several parts of the business work.
Moving premises might only happen once every twenty years.
These aren't necessarily enormous projects.
But getting them wrong can create enormous disruption.
The amount of project management required should reflect the delivery challenge, not just the size of the budget.
What does every project need?
The detail changes.
The basics don't.
For me, it comes down to three things:
Clarity. Ownership. Control.
Clarity
Do we actually know what we are trying to achieve?
Why are we doing it?
What business goal does it support?
What does success look like?
You would be surprised how many projects get underway before those questions have really been answered.
If the destination isn't clear, adding more project management won't help.
You need clarity first.
Ownership
Someone has to genuinely own delivery.
Not just have their name on a document.
Not simply chair a meeting once a month.
Someone needs to know what is happening and make sure things keep moving.
Senior leaders also have a role.
They need to remove barriers, support decisions, protect resources and stay involved when the project needs them.
Approving a project and then walking away isn't sponsorship.
Control
Once the project is moving, you need enough information to know whether it is still under control.
That doesn't mean a forty-page report.
It means knowing:
What needs to happen?
Who owns it?
What are the important priorities?
Where are the risks and bottlenecks?
What decisions need making?
And are problems being spotted early enough to do something about them?
That's control.
The amount of project management can change
A project doesn't necessarily need the same level of management all the way through.
It may need quite a lot at the beginning.
That is when you establish what you are trying to achieve, understand the project, work out the approach, identify who needs to be involved and build a credible plan.
Once things are moving, the requirement might reduce considerably.
A good weekly conversation, a sensible action list and a clear view of risks might be enough.
Then things can become more intense again as you approach implementation, handover or another major milestone.
This is particularly important for smaller businesses.
The choice isn't simply:
Full-time project manager or no project management.
There is a lot of space in between.
How do you know when you haven't got enough?
There are normally clues.
Everyone is busy, but nobody seems quite sure where the project stands.
Actions repeatedly roll from one meeting to the next.
Dates move without anyone really understanding why.
Decisions sit unresolved.
Problems appear late.
People assume somebody else is dealing with something.
The project keeps losing out to the day job.
And eventually someone senior asks:
“How did we get here?”
At that point, the problem isn't a lack of project management paperwork.
It's a lack of clarity, ownership or control.
Possibly all three.
And you can have too much
There is another side to this.
Project reporting is not a performative art.
A smaller project does not need to behave like a major infrastructure programme just because somebody has discovered a project management methodology.
Meetings, reports and trackers should have a purpose.
They should help people understand what is happening.
They should identify problems.
They should prompt decisions.
And they should help the people doing the work know what is expected of them.
If a project is producing large amounts of reporting but nobody is making better decisions as a result, you haven't necessarily got good project management.
You've got paperwork.
So how much project management is enough?
Enough that you can answer these questions with confidence:
What type of project are we dealing with?
Are we clear about what we are trying to achieve?
Does somebody genuinely own delivery?
Do we have a realistic route forward?
Can we see problems early enough to act?
If you can answer those questions, you may not need very much project management at all.
If you can't, adding some structure will probably save you time rather than create bureaucracy.
The objective isn't to manage projects more.
It is to manage them enough.
No Fluff takeaway
Use enough project management to give the project clarity, ownership and control.
Then stop.
The purpose of project management isn't to create more project management.
It's to deliver the project.
Not sure whether your project has enough clarity, ownership and control? The No Fluff Project Assessment gives you a structured way to understand where the project really stands.
Comments