One question I ask project teams has changed how I think about weekly status meetings:

What became easier for the next person in the process this week?

It is a small change from asking what everyone completed, but it often produces a much more useful conversation. A team can finish several tasks without making the overall project easier to deliver. Work may be technically complete while the next person still lacks the context, permission, or material needed to continue.

In a fictional example from a design consultancy, a researcher finished twelve customer interviews and uploaded the recordings before Friday. The project tracker showed the research task as complete. On Monday, the designer still could not begin because the findings had not been organized around the decisions the design needed to support.

Nobody had failed to work hard. The handoff itself had not been defined.

We changed the review around three pieces of information: what had been learned, which decision it informed, and what the receiving colleague could now do. The researcher prepared a two-page summary with links to the relevant interview sections. The designer identified one unanswered question before work began, rather than discovering it during a later presentation.

This does not mean every task needs a formal handover document. It means completion should include a shared understanding of what happens next. Sometimes that requires a short note. Sometimes it requires a conversation. Occasionally it reveals that the next step has never been assigned to anyone.

When I advise teams, I encourage them to keep their existing status report and add this one question for a few weeks. Watch which dependencies become visible and which repeated explanations disappear.

The useful measure is not whether the meeting feels more energetic. It is whether people leave with less uncertainty about the work they need to do next. That is a much stronger basis for progress than a longer list of completed tasks.