What is project management — and why does it matter?
- 5 days ago
- 9 min read
Project management is more than keeping a plan up to date. It is about helping an organisation turn an important idea into a real outcome.
IN THIS INSIGHT…
Projects are how organisations turn plans, opportunities and ambitions into action. But successful delivery requires more than assigning tasks and monitoring deadlines.
In this Insight, you'll discover:
What project management actually involves
Why project management is about outcomes, not just tasks
The difference between managing a project and simply coordinating activity
Why good Project Managers cannot deliver successfully in isolation
How organisations can think about the project management capability they actually need
PROJECTS TURN INTENTIONS INTO ACTION
Most organisations have more ideas than they have capacity to deliver.
A new service.
A digital system.
A building improvement.
A new funding programme.
An organisational restructure.
A major piece of research.
A change to the way services are delivered.
At the beginning, these initiatives often feel straightforward. There is a reason for doing them. People are enthusiastic. The desired outcome seems clear.
Then the work begins. Different people become involved. Decisions need to be made. Resources have to be allocated. Risks emerge. Priorities change. Deadlines approach. Dependencies appear. Stakeholders ask questions.
What looked like a relatively simple idea becomes a project. This is where project management matters.
Project management provides the structure, coordination and leadership needed to move from an intention to a defined outcome.
Project management is not:
simply about creating a project plan
about arranging meetings
about maintaining a spreadsheet
And it certainly isn't about making work look more complicated than it needs to be!
Good project management helps an organisation answer some fundamental questions:
What are we trying to achieve?
How are we going to achieve it?
Who needs to be involved?
What could prevent us from succeeding?
What decisions need to be made?
Are we still moving towards the outcome we originally agreed?
Those questions sound simple. In practice, answering them consistently throughout a project can be surprisingly difficult.
PROJECT MANAGEMENT IS ABOUT MORE THAN TASKS
One of the easiest ways to misunderstand project management is to think of it as a collection of tasks. Create a plan. Set some deadlines. Arrange meetings. Update the tracker. Send a report. Follow up actions. These activities can all form part of project management. But they aren't the purpose of it.
The purpose is to help the organisation achieve the outcome the project exists to deliver. That distinction matters. A project can have a beautifully maintained spreadsheet and still be failing.
Every task might have an owner.
Every meeting might have minutes.
Every milestone might be colour-coded.
Yet the project could still be moving in the wrong direction.
Perhaps the original objective is no longer aligned with organisational priorities.
Perhaps a key assumption has changed.
Perhaps the project team doesn't have enough capacity.
Perhaps an important decision has been delayed.
Perhaps the people who need to adopt the eventual change haven't been sufficiently involved.
Good project management creates the visibility to recognise these things early. It connects the day-to-day work with the reason the project exists in the first place.
REFLECTION:
If you looked beyond your current project plans and trackers, could everyone involved clearly explain what the project is ultimately trying to achieve?
And are the activities taking place today still contributing to that outcome?
A PROJECT MANAGER PROVIDES LEADERSHIP WITHIN THE PROJECT
A Project Manager is sometimes viewed as the person who keeps everyone organised. That is part of the role, but experienced project management goes considerably further.
A Project Manager provides leadership within the project environment. They bring together people who may have different responsibilities, priorities and perspectives.
They:
create a shared understanding of what needs to happen
establish a realistic route towards the desired outcome
identify risks and dependencies
keep decisions moving
challenge assumptions when necessary
communicate progress
make problems visible
And, importantly, they help the organisation respond when circumstances change.
That last point is particularly important. Projects rarely happen exactly as originally planned.
A funder may change its requirements.
A supplier may experience delays.
A key member of staff may leave.
A new organisational priority may emerge.
A budget may be reduced.
A technical problem may appear.
A stakeholder may raise an issue that had not previously been considered.
Project management does not prevent these things from happening. It helps the organisation understand their implications and respond deliberately rather than reactively.
This is one reason good Project Managers can make such a difference. They don't simply manage the plan, they help manage the reality around the plan.
PROJECT MANAGEMENT IS AN ORGANISATIONAL CAPABILITY
This also leads to an important distinction - a Project Manager may be responsible for managing a project, but successful project delivery is not the sole responsibility of the Project Manager.
Leadership still needs to provide direction.
Decision-makers still need to make timely decisions.
Teams still need to contribute their expertise.
Stakeholders still need to engage.
Resources still need to be available.
People still need to make space for the project alongside operational responsibilities.
In other words, a Project Manager can provide strong project leadership without having complete control over the environment in which the project operates.
This is something leaders should recognise when assessing project performance. If a project is struggling, the first question should not automatically be:
"Is the Project Manager doing their job properly?"
The more useful questions might be:
Are priorities clear?
Are decisions being made quickly enough?
Does the project have the capacity it needs?
Are risks being escalated appropriately?
Does the Project Manager have sufficient authority and access to leadership?
Is the organisation creating the conditions in which good project management can succeed?
This broader perspective is important because project delivery is a shared organisational responsibility. It is also why replacing a Project Manager isn't necessarily the answer when a project is struggling - sometimes the problem sits elsewhere.
As we've explored previously, projects can drift because priorities change, resources become stretched, decisions are delayed and organisational visibility becomes harder to maintain. Good project management helps identify and respond to those pressures, but it cannot remove every organisational obstacle.
REFLECTION:
When a project isn't progressing as expected, do you look first at the Project Manager — or at the wider conditions in which the project is being delivered?
NOT EVERY PROJECT NEEDS THE SAME LEVEL OF PROJECT MANAGEMENT
Another important consideration is proportion. A small, well-defined project involving three people probably doesn't require the same project management structure as a major organisational transformation involving multiple teams, suppliers and stakeholders.
That sounds obvious. Yet organisations can sometimes fall into one of two traps:
The first is under-managing the project.
People assume everyone knows what is happening. Responsibilities remain informal. Decisions happen in conversations. Risks aren't recorded. Progress is discussed rather than measured. This can work for a while. Until it doesn't.
The second is over-managing the project.
Too many meetings. Too many templates. Too much reporting. Too much process for the scale of the work. The project begins spending more time demonstrating that it is being managed than actually moving forward.
Neither approach is particularly helpful. The right level of project management should reflect the project's size, complexity, risk, importance and organisational context.
A relatively contained project may need straightforward planning, coordination and reporting. A more complex project may need dedicated project leadership, formal governance, structured risk management, stakeholder management and more regular leadership oversight.
The principle is simple: The project should determine the level of project management it needs. Not the other way around.
REFLECTION:
Are your projects receiving enough project management to give people clarity and confidence?
Or are you applying more process than the project genuinely needs?
WHO SHOULD MANAGE YOUR PROJECT?
Once an organisation recognises the importance of project management, another question naturally follows: Who should provide it?
There isn't one universal answer.
Some organisations need a permanent Project Manager because they have a sustained pipeline of projects and require that capability continuously.
Others may need a Project Manager for a defined period while a particular initiative is delivered.
Some may benefit from part-time or fractional project management.
A contractor may be appropriate for a specific project or specialist requirement.
In other circumstances, an external Project Manager may provide the experience and delivery capacity required without creating a permanent role.
Remote or hybrid support may work well where physical presence isn't essential. For some projects, however, being on site may genuinely add value.
The important point is that the employment arrangement or physical location should come after understanding the capability the project actually requires.
The starting question shouldn't necessarily be: "Do we need to recruit a Project Manager?"
It might be: "What project management capability do we need, for how long, and why?"
That shift in thinking can open up more proportionate options. It also helps organisations avoid creating permanent structures around temporary needs.
The objective isn't to make external support sound better than internal employment. Sometimes a permanent Project Manager is exactly the right answer. The objective is simply to make sure the organisation chooses deliberately rather than assuming that one model is automatically appropriate.
GOOD PROJECT MANAGEMENT CREATES CONFIDENCE
Ultimately, project management matters because projects matter. Organisations don't undertake projects for the sake of producing plans and reports. They undertake them because they want something to change.
They want to improve a service.
Reach more people.
Introduce something new.
Respond to an opportunity.
Solve a problem.
Meet a commitment.
Strengthen the organisation.
Deliver a strategic priority.
Project management helps turn that intention into controlled, visible action.
It gives people clarity about what needs to happen.
It gives leadership greater visibility of progress, risks and decisions.
It gives project teams a structure within which they can work.
And it creates a mechanism for responding when reality inevitably differs from the original plan.
That doesn't mean every project will succeed. Good project management cannot guarantee that.
It does, however, make it much easier to understand where a project stands, what needs attention and what decisions are required. That is valuable in any organisation. It is particularly valuable in charities and other purpose-driven organisations where resources are often limited and projects sit alongside significant operational responsibilities.
REFLECTION:
If your organisation's most important projects were being managed exceptionally well, what would leadership notice first?
Greater visibility? Faster decisions? Better use of resources? More confidence that strategic priorities were actually being delivered?
THE RIGHT PROJECT MANAGEMENT CAPABILITY FOR THE PROJECT
There is a tendency to think about project management as a job title.
Project Manager.
Senior Project Manager.
Programme Manager.
But the more useful way to think about it is as a capability.
Your organisation needs someone — or several people — with the experience, authority and capacity to help a project move from intention to outcome. How that capability is provided is a separate question.
It might sit within the organisation.
It might be provided on a part-time basis.
It might be brought in for a defined project.
It might be supplemented by external expertise.
It might eventually develop into a broader project delivery function as the organisation grows.
The answer should reflect the work that needs to be done. This matters because organisations change.
A project that requires significant external support today may not need it in a year.
An organisation with informal project management today may eventually need permanent internal capability.
A team with an experienced Project Manager may later need broader oversight as the number of projects increases.
There is no single model that fits every organisation. The important thing is to recognise the capability required and provide it at the right level.
REFLECTION:
If you started with the project rather than the job description, what would you actually need from your project management capability?
And would that need be permanent?
PROJECT MANAGEMENT IS ABOUT MAKING CHANGE HAPPEN
Project management can sometimes appear administrative from the outside.
Plans. Reports. Meetings. Actions. Milestones. Risk registers.
But at its best, project management is about something much more important.
It is about helping an organisation make change happen.
It connects strategic intention with practical delivery.
It gives people clarity.
It creates accountability.
It makes problems visible.
It supports better decisions.
And it keeps attention focused on the outcome that matters.
The strongest project management isn't necessarily the most complicated. It is the project management that gives an organisation enough structure to move forward confidently without creating unnecessary bureaucracy around the work.
That means the right question isn't simply whether your organisation has a Project Manager. It is whether your organisation has the project management capability it needs to deliver the changes that matter.
And as the number and complexity of projects grows, that question may eventually become broader still: how does leadership maintain visibility, consistency and oversight across everything being delivered? That's where the conversation about wider project governance and PMO capability begins.
CONCLUSION
Projects are how organisations turn ambition into action. Good project management helps make that transition possible. It provides leadership within the project, creates visibility, coordinates people and activity, manages uncertainty and keeps attention on the outcomes that matter.
But project management isn't a one-size-fits-all structure. The right level of capability depends on the project, the organisation and what needs to be achieved.
Sometimes that means a permanent Project Manager.
Sometimes it means part-time, fractional, contract or external support.
Sometimes physical presence is valuable.
Sometimes it isn't.
The important thing is to start with the project and organisational capability you actually need — then choose the most appropriate way to provide it.
At RootRise, we help charities, non-profits and purpose-driven organisations strengthen project delivery through practical Project Management and flexible delivery support. Whether you need someone to lead a specific project, provide additional delivery capacity or help get a project back on track, the right approach should reflect your organisation's needs rather than a predetermined model.
If you're considering a project or have one that isn't progressing as you expected, we'd be happy to have an initial conversation about what support would make sense for your organisation.
