The 10-minute project health check: a self-assessment for stuck projects

lorenaflorian0
May 1
4 min read

You know the feeling. The project feels 'off'. The team is quiet in meetings; the status reports are suspiciously green, and you have a nagging suspicion that the deadline is a fantasy. You don't have time for a full-blown audit, and you certainly don't need another consultant telling you to 're-align your stakeholders' without giving you a concrete starting point.

Sometimes you just need a quick, sharp diagnosis.

At PMLogic, we've seen projects die not because of a lack of effort, but because the warning signs were ignored until it was too late. We've developed a 10 Minute project health check - a self-assessment framework that strips away the politeness and gets straight to the point.

This isn't about finding a silver bullet. It's about identifying whether your project is suffering from scope bleed, leadership paralysis, or a broken feedback loop.

Grab a coffee, set a timer for 10 minutes, and run through these seven questions. Be honest. If you hesitate on an answer, that's your first red flag.

The 7-point diagnostic

Rate your project on a scale of 1 (critical failure) to 5 (healthy and on track) for each of the following.

1. The 'why' clarity test

If you asked a random team member today, 'what is the single most important business benefit of this project?', could they answer in one sentence without checking their notes?

1: They would give you three different answers, or say 'I think it's the dashboard?'
5: They can recite the primary value proposition instantly.
The verdict: If you scored below 3, your project lacks a north star. You are building features, not solving problems.

2. The 'green report' reality check

Look at your last status report. If everything is 'green', does that match the gut feeling of the team in the hallway (or slack channel)?

1: The report is all green, but the team is stressed, possibly working overtime, and hiding issues.
5: The report reflects reality, including the red flags, and the team feels safe raising them.
The verdict: A discrepancy here means you have a culture of fear. Your governance is patchy at best, and you might be flying blind.

3. The decision latency audit

Think of the last major blocker your team hit. How long did it sit waiting for a decision from leadership and stakeholders?

1: Days or weeks. The team is idle or working on guesswork.
5: Decisions were made within 24 hours, or the escalation path is clear and used.
The verdict: If you scored low, your bottleneck isn't the work; it's the governance. You need to tighten the decision loop or delegate authority.

4. The scope creep - o - meter

Can you point to a change request added in the last month that was not formally approved against a trade-off (time, cost, or quality, or other)?

1: Yes, and there are five others. The scope is a moving target.
5: Every change is logged, assessed, and approved (or rejected) via a formal process.
The verdict: Low scores indicate scope bleed. You are trying to boil the ocean. You need to freeze the scope immediately.

5. The resource reality check

Are your key resources doing the work they were hired for, or are they constantly putting out fires in other departments?

1: They are over allocated, context - switching hourly, possibly even burning out.
5: They have protected time for deep work and clear capacity planning.
The verdict: If this is low, your resource plan is fiction. You are over - promising and under - delivering on capacity.

6. The stakeholder engagement score

Who is the most vocal stakeholder? Are they engaged in the solution, or just complaining about the process?

1: They are disengaged until the last minute, then demand changes.
5: They are involved in regular demos and reviews and provide constructive feedback early.
The verdict: Low engagement means misaligned expectations. You are building in a vacuum.

7. The 'next step' certainty

Does the team know exactly what they need to do tomorrow morning to move the needle?

1: No. Everyone is waiting for direction or clarification.
5: Yes. The backlog is prioritised, and the next sprint or phase is clear.
The verdict: If you scored low, you have a planning failure. You are reacting, not leading.

Interpreting your score

Add up your scores. Here is what the number tells you:

Total Score	Diagnosis	Immediate Action Required
7 - 14	Critical failure	Stop. Pause new work. Call an emergency 'Reset' meeting. Re - baseline the scope, re - engage stakeholders, and fix the culture of fear. Do not proceed until the 'Why' is clear.
15 - 24	Stuck in the mud	Slow Down. You have systemic issues (likely scope or decision latency). Freeze scope changes for 2 weeks. Implement a daily 15-minute stand-up focused only on blockers.
25 - 35	Healthy but fragile	Optimise. You are functional, but complacency is setting in. Focus on tightening feedback loops and automating status reporting to free up time for strategic thinking.

The 'so what?' (your takeaway)

If you scored low, don't panic. The goal of this check isn't to shame you; it's to give you a diagnosis so you can prescribe the cure.

If your 'why' was low: Re-write your project charter. Get it signed off again.
If your 'green report' was low: Hold a 'red flag' session. Ask the team: 'what are we hiding, or not seeing?'
If your 'decision latency' was low: Create a RASCI matrix to identify roles and responsibilities. Who decides? Who advises? Who executes?

The bottom line: A project that feels 'off' is rarely saved by working harder. It's saved by stopping, looking in the mirror, and fixing the root cause.

Don't wait for the quarterly review to find out your project is failing. Run this check today.