The Accidental Project Manager
A lot of project managers never actually applied for the job.
They were simply the person who knew the business, understood the problem, or could be trusted to get things done.
Then somebody said:
“Can you lead this?”
And suddenly they were managing a project alongside their day job.
This is particularly common in SMEs.
A business might be introducing a new system, changing a process, moving premises, launching a product, implementing something for a major customer or installing new equipment.
These are all projects.
But they may not be large enough to justify bringing in a full-time project manager.
So the work lands with somebody already in the organisation.
And often that is entirely sensible.
They usually have something a project manager doesn't
The accidental project manager often understands the business extremely well.
They know the people, they understand how things really work, they know the customers, suppliers, operational pressures and history behind the change.
That knowledge can be hugely valuable.
In many cases, putting an experienced project manager into the organisation who understands none of that context would create a different set of problems.
The issue isn't that the wrong person has been asked to lead the project.
The issue is what happens next.
“You know the business, so you'll be fine”
Knowing the business and knowing how to organise a project are two different things.
The accidental project manager may suddenly be expected to:
work out exactly what needs to be delivered
build some form of plan
coordinate several people or departments
deal with suppliers
manage risks and problems
keep senior management informed
chase actions and decisions
deal with changing requirements
somehow keep their normal job going at the same time
And quite often nobody has actually explained how to do any of this.
So they improvise.
They create a spreadsheet.
They arrange meetings.
They start an action list.
They send emails.
Everyone gets busy.
For a while, it can look as though the project is moving.
But activity isn't necessarily the same thing as control.
The project slowly becomes part of the day job
This is where many smaller projects start to struggle.
The project doesn't stop.
It just becomes absorbed into everybody's normal workload.
Meetings get moved because operational work is more urgent.
Actions slip.
Decisions take longer.
Nobody is completely sure who owns certain pieces of work.
The completion date stays exactly where it was.
Eventually somebody asks:
“Are we still on track?”
And that can be surprisingly difficult to answer.
The accidental project manager is often working extremely hard.
They simply haven't been given the basic structures that would allow them to see the project clearly.
They don't need a 200-page methodology
The answer isn't to give somebody a huge project management manual.
Nor does every small project need formal governance boards, complex reporting or specialist software.
That can create as much difficulty as having no structure at all.
Most smaller projects need something much simpler.
A clear outcome, a realistic plan, clear ownership, a way of tracking actions and decisions, visibility of the biggest risks and issues, regular conversations with the right people and somebody who knows when the project is beginning to drift.
That's project management.
It doesn't need to be complicated.
The day job is still the day job
There is another issue that organisations sometimes underestimate.
Being given responsibility for a project doesn't remove somebody's existing workload.
An operations manager still has an operation to run.
A finance manager still has month-end.
A sales manager still has customers and targets.
If the project is genuinely important, the organisation has to recognise that it requires time.
That might mean reducing other responsibilities temporarily.
It might mean giving the person additional support.
Or it might mean bringing in targeted project support at particular points.
Simply adding “run the project” to somebody's existing job description isn't a resource plan.
Build enough capability
The objective shouldn't necessarily be to turn accidental project managers into professional project managers.
Most of them don't want that.
They need enough capability to successfully deliver the projects they are being asked to lead.
That means understanding some core project principles and having practical tools they can actually use.
For organisations that want to build that capability internally, No Fluff Project Management training is designed around exactly that problem: practical project management without unnecessary methodology or bureaucracy.
Sometimes the project needs more
There is also a point where expecting somebody to manage the work alongside their day job stops being realistic.
The project might become too complex.
There might be several suppliers.
The financial or operational risk might become significant.
Or the organisation may simply not have enough management capacity.
Recognising that point matters.
Using an internal project lead doesn't mean the organisation has to manage everything internally.
Sometimes a little external support can help somebody remain in control without replacing them as project lead.
The important question
The next time somebody in the business says:
“Can you lead this?”
there is another question worth asking.
What does that person need in order to succeed?
Because accidental project managers can be extremely effective.
They already understand the organisation.
They often have the credibility needed to get things done.
Give them some practical project management capability, enough time and the right level of support, and they may be exactly the right person for the job.
Leave them to work it out while carrying their full-time role, and the outcome can be very different.
No Fluff Takeaway
Accidental project managers can be exactly the right people to lead smaller projects.
They already know the business, the people and the context.
What they need is not a heavyweight methodology.
They need:
a clear outcome
a realistic plan
clear ownership
simple ways to track actions, risks and decisions
enough time to do the job properly
support when the project becomes too complex
The right person + the right structure + enough time = a much better chance of project success.
Comments