When a project fails, the problem usually shows up near the end. But in most cases, the cause was there from the first week.
I have seen this across disability services, community organisations and not-for-profits. A new system, a new service, a new site. Everyone is enthusiastic at the start. Then months later the project is late, over budget and not quite what anyone wanted. When you trace it back, the issue is rarely the people. It is that the project was never set up clearly in the first place.
Project management is the discipline of planning, organising and guiding work so it delivers what it was meant to. It does not need complicated software or thick documents. It needs a few basic things done well, early.
Agree what done looks like
The most important question in any project is also the one most often skipped: how will we know we are finished? If different people have different answers, the project will drift.
Write down what success looks like in plain language. Not "improve our intake process," but "new participants can complete intake in one visit, and staff no longer re-enter the same information twice." A clear finish line keeps everyone pointed in the same direction.
Give it one owner
Projects owned by everyone are owned by no one. Every project needs one person who is responsible for keeping it moving, making sure decisions get made and raising problems early. That person does not do all the work. They make sure the work comes together.
Be clear about scope
Scope is what the project includes, and just as importantly, what it does not. Without clear scope, projects grow quietly. Each extra request seems small, but together they stretch timelines and exhaust teams. Agree the scope at the start, and when new ideas come up, decide on purpose whether they come in now, later or not at all.
Break it into small steps
Large projects feel overwhelming and are hard to track. Breaking the work into smaller milestones, each with a clear outcome and date, makes progress visible and problems easier to spot. It is far easier to fix a two-week delay than to discover a six-month one.
Bring people with you
Most projects in our sector change how people work, which makes them change projects as much as delivery projects. The people affected need to understand why the change is happening, have a chance to shape it and know what it means for them. A project can be delivered on time and still fail if the team does not use what was built.
Close it out properly
When a project ends, take time to finish it well. Confirm that what was promised was delivered. Hand over clearly to whoever will look after it. And ask the team three honest questions: what went well, what did not and what would we do differently? Those lessons make the next project easier.
Good project management is not about control. It is about clarity: a clear goal, a clear owner, clear scope and clear communication. Get those right at the start, and most of the problems that sink projects at the finish never get the chance to grow.