If You’re Involved in a Difficult Project, Here’s How I Can Help
Projects do not have to be failing before they become difficult.
Sometimes the warning signs are obvious. Deadlines are being missed, costs are increasing and stakeholders are becoming frustrated.
More often, the position is less clear.
Progress is still being reported. Meetings are still taking place. Actions are being recorded and the project may even have a green or amber status. But confidence is beginning to slip.
The plan no longer feels entirely credible. Important decisions remain unresolved. Responsibilities are unclear. The team is working hard, but it is becoming difficult to tell whether the project is genuinely moving forward.
That is often the point when an independent project review can help.
It can be difficult to see the whole picture from inside the project
People working on a difficult project usually know that something is not right.
The challenge is agreeing what the real problem is.
One person may think the issue is a lack of resources. Another may blame unclear requirements. The supplier may be waiting for decisions from the client. The project team may believe that senior management keeps changing the priorities.
Each of those views may contain part of the truth.
When people have been dealing with the same issues for weeks or months, however, it becomes increasingly difficult to step back and look at the project as a whole. Attention naturally moves towards the latest problem, deadline or escalation.
An independent review creates the space to ask some more fundamental questions.
What is the project actually trying to deliver?
Is the scope sufficiently clear?
Is there a credible plan?
Are the right people making the right decisions?
Are risks and issues genuinely being managed?
Is the reported position supported by the evidence?
And, most importantly, what needs to happen next?
A project review is not an audit
The word “review” can make people defensive.
They may expect an investigation designed to find fault, assign blame or produce a long report that confirms what everybody already knows.
That is not how I approach it.
A useful project review should help the organisation understand the current position and make better decisions. It should identify what is working as well as what is not.
That requires honest conversations with the people involved, supported by a practical examination of the project information. Plans, risks, governance, resources, dependencies and delivery readiness all need to be considered together.
The purpose is not to judge the project against a theoretical version of perfection. It is to determine whether the arrangements are good enough for the project being delivered—and where the greatest risks sit.
What you should get from the review
A review shouldn't leave you with another list of problems.
You should have a clear and evidence-based view of where the project really stands, the main factors affecting delivery and the priorities that need attention.
That might mean clarifying the intended outcome before more work continues. It could involve rebuilding an unrealistic plan, resolving gaps in ownership or strengthening the way decisions are made.
In other cases, the immediate priority may be to reduce the scope, agree a realistic minimum viable product, address a difficult supplier relationship or prepare properly for testing and implementation.
Not every weakness needs to be fixed at once. Part of the value of the review is distinguishing between what is untidy, what is important and what could genuinely prevent successful delivery.
The recommendations therefore need to be practical, prioritised and appropriate to the organisation—not copied from a project management textbook.
Sometimes the project needs a reset, not a rescue
The review may show that the project remains fundamentally sound but needs tighter plans, clearer responsibilities or better control.
Sometimes a more substantial reset is required.
That does not necessarily mean replacing the team or starting again. It may mean pausing parts of the work, confirming the outcomes, agreeing what can realistically be delivered and rebuilding confidence around a credible way forward.
There are also occasions when the organisation needs some hands-on support after the review. Knowing what needs to change is not always the same as having the time or experience to make it happen.
That support can be proportionate. It might involve helping the existing team put the recommendations into practice, facilitating a project reset or providing an experienced sounding board while the organisation regains control.
You do not have to wait for the project to fail
The earlier concerns are examined, the more options the organisation is likely to have.
A review carried out before the project reaches crisis point can prevent wasted effort, expose unrealistic assumptions and help resolve difficult questions while there is still time to act.
If you are involved in a project that feels difficult, unclear or increasingly hard to control, the first step is not to pretend everything is fine—or to declare the whole project a failure.
It is to establish where things really stand.
That is where I can help.
Find out more about independent project reviews and practical project support at:
Comments