A lightweight project health check for busy project managers and engineering teams
Most project reviews take far too long, and often don’t achieve anything other than ticking a box. They need to be effective, and to be effective, they need to be done right.
There is no need to spend hours working through slide decks, status updates, and task-by-task discussions, which can still leave stakeholders walking away without a clear understanding of whether the project is actually in good shape.
If the project is properly structured and the right controls are in place, an experienced project manager should be able to assess the overall health of a project in around 20 minutes.
The purpose of the review is simple:
- Confirm the project is still under control
- Identify emerging risks early
- Make decisions
- Agree actions
Not to create more administration.
Here’s a lightweight structure I’ve used successfully across engineering and technical programmes.
1. Reconfirm the Objective (2 Minutes)
Start by grounding everyone in the same place.
- What are we delivering?
- What’s the next key milestone?
- Has anything changed since the last review?
Projects often drift gradually without anyone noticing. Spending two minutes reconnecting stakeholders to the objective can help prevent a lot of wasted effort later.
2. Review Overall Status (3 Minutes)
Keep this high level.
Review:
- Schedule position
- Milestone status
- Budget concerns
- Resource constraints
- Upcoming deliverables
Avoid reviewing every task individually. Instead, just focus on one question:
“What has changed since the last review?”
That question usually surfaces the important information very quickly.
3. Review Risks and Issues (5 Minutes)
This is where the real discussion normally sits.
Focus only on:
- Major risks
- Unresolved issues
- Blockers affecting delivery
For each item:
- What’s the impact?
- Who owns it?
- What’s being done about it?
- When will it be resolved?
It’s a fact of project life that things are always changing and evolving, so if your risk register never changes, the project probably lacks transparency.
4. Assess Delivery Confidence (5 Minutes)
This is often the most valuable part of the review.
Ask the team directly: “Are we still confident we can deliver successfully?”
Then actually listen to the answer, rather than hearing what you want to hear.
Most struggling projects show warning signs long before they formally turn red. Good project reviews create an environment where concerns can be raised early, before they become major problems.
5. Agree Actions and Decisions (3 Minutes)
Finish with clear actions:
- What needs doing
- Who owns it
- When it’s due
A review without clear actions is usually just a conversation. Make sure actions are recorded and shared following the review. It’s also worth reviewing previous actions at the start of the next session to maintain accountability and momentum.
Final Thoughts
The goal here isn’t to produce more reporting. The goal is to maintain visibility, support decision-making, and intervene early when delivery starts to drift.
In my experience, a focused 20-minute review is often far more effective than a two-hour marathon session full of slides where people’s attention drifts after the first half an hour.
And if a project can’t be reviewed in 20 minutes, the issue is usually not the review itself.
