top of page

What a project health check should actually check

Oct 23
3 min read

Updated: Nov 4

A project health check should tell you whether the work still serves the purpose for which the project exists, not only whether the work is moving. Most health checks are status reports with a new name: they confirm the team is busy and the dates look fine, and they say nothing about whether the result will be what you meant.


If you lead product or engineering, you've seen a green report turn into a disappointing launch. Here are the four questions a real project health check asks, a worked example, and how to get one scored on your own project.


What does a status check miss?


A status check measures activity: tickets closed, milestones hit, budget burned against plan. Those numbers matter, but they answer "is the work moving?" They don't answer "is it still going where we meant?"


A project can hit every milestone and still drift.

A feature added after a customer call, a priority changed in planning, scope trimmed to hold a date: each change is reasonable, some get agreed, some nobody notices making. Together they move the project away from its purpose while every status indicator stays green.


A real project health check looks past activity to purpose...


What a project health check should actually check
What a project health check should actually check | Truvle

What are the questions of a real project health check?


  1. Why the project exists. Ask the people on the project separately, then compare. If the answers match, the why is set. If they differ, each person is building toward a different result, even if nobody has noticed yet.

  2. What will it deliver? Look for something specific enough that someone outside the team could check it. "A better onboarding experience" isn't checkable. "New teams finish their first project in their first week" is.

  3. What return do you expect? Name the benefit to the company and its customers. If this answer is blank, nobody will be able to prove the project paid off, because nobody agreed what paying off means.

  4. Where has it already drifted? List the scope changes since kickoff and who decided each one. A change nobody decided is drift. Any work that can't be connected to the why is extra weight the project is carrying.


Get these four questions scored on your own project: Book your free project audit.





What does a project health check look like in practice? [The 4 Answers]


An illustrative example, not a customer story.


  • Why does it exist? Product says "to raise activation." Customer success says "to cut support tickets from new accounts." Engineering says "to replace the old code." Three answers, three different projects.

  • What will it deliver? "A new onboarding flow." Nobody outside the team could check whether it's done well.

  • What return is expected? Blank. Everyone assumes it will help; nobody has said how they'll know.

  • Where has it drifted? Two features were added after a sales call, and nobody remembers deciding them.


If the health check says the why was never set, the fix is one conversation: agree on a single why, define a checkable result and an expected return, then decide on purpose whether those two features stay.


Caught now, that's a meeting. Caught after launch, it's rework.


Before your next steering meeting, find out where your project stands. Book your free project audit: an opportunity score on one of your projects.


Thanks for reading.

A quick breakdown from our blog.




Found this useful?

Save it for later or pass it along!




 
 
 

Comments


bottom of page