Look beyond the schedule
Imagine a project that delivers every document on time. Its schedule is green, yet the receiving team still cannot perform the task that prompted the project. This hypothetical example invites us to distinguish delivery from outcome. Both matter: we need to control the work we have committed to and check that it remains appropriate for the need we are trying to address.
First conversation: what change do we expect?
A progress meeting can begin with a simple question: what should someone be able to do when we finish? The answer connects activities with their purpose. Naming a deliverable is not enough; describe the expected change for its users. If different people give incompatible answers, that disagreement deserves attention before the project moves further ahead.
Separate delivery from achievement
A useful exercise is to create two columns. List the committed products or services in the first, and the capability or improvement each should support in the second. This does not mean holding the project accountable for every later outcome: some will depend on external factors. It does help identify those conditions and agree who should take responsibility for them.
Second conversation: what evidence do we have?
The percentage of completed tasks describes activity, but it cannot answer every question about usefulness. Complement it with demonstrations, user reviews or acceptance tests suited to the setting. Agree in advance what you want to check. If a review reveals that a deliverable does not fit operations, that information needs to arrive early enough to support a decision.
Third conversation: what needs a decision?
A progress report becomes more useful when it separates facts, risks and outstanding decisions. For each decision, identify who can make it and what information they need. Not every deviation requires a new plan. Some call for a clearer requirement, others for a revised priority or an acknowledged dependency. Making the distinction explicit prevents the meeting from becoming a report-reading exercise.
Protect scope without losing the purpose
Revisiting objectives does not mean accepting uncontrolled change. When a new need appears, assess its impact on scope, time and resources, and use the agreed decision process. Purpose guides the discussion; change management makes the consequences visible. Keeping both in view helps avoid rigidity as well as the informal expansion of work.
For your next meeting
Set aside ten minutes for three questions: what change do we expect, what evidence do we have and what decision is missing? Record owners and next steps. This is a simple way to enrich existing progress reviews without replacing the controls the project requires.