10/13/2026
The project is 80% complete.”
As a client or agency owner, what can you do with that information?
The screens might be designed, while payments are still untested. The main journey might work, while permissions and error handling are unfinished.
A percentage needs context.
I find a project update more useful when it answers four questions:
1. What is ready to review?
A specific feature, page or workflow, ideally with a working demonstration.
2. What has been tested?
There is a difference between something being built and being checked against agreed requirements.
3. What is blocked?
Missing content, access, an integration issue or a decision that needs attention.
4. What happens next?
The next deliverable, who is responsible and when it is expected.
For example:
“Customers can now submit a booking request on the test site. Confirmation emails have been tested. Payment integration is waiting for account access. Next, we’ll complete cancellations.”
That gives everyone something concrete to discuss.
If you manage development projects, ask for updates built around demonstrable progress and outstanding decisions. It becomes much easier to spot problems while there is still time to address them.
