Your Weekly Review Shouldn’t Be a Courtroom

Somewhere between the second “what’s the status on this?” and the third “whose was this?”, the weekly review stops being a meeting and becomes a hearing. The manager is the investigator. The team are the witnesses. And the verdict, most weeks, is only this: now we know what happened.

That is the quiet problem with most status meetings. Their only output is information. An hour of skilled people reconstructs the recent past — what got done, what moved, who is waiting on whom — and when the reconstruction is finished, the meeting is over. Nothing was decided.

Listen to five minutes of it:

“What’s the status on the Sharma order?”

“Waiting for the drawing.”

“Since when?”

“Tuesday, I think. Maybe Wednesday.”

“Who has the drawing?”

“Design. Or it went to the customer already — the design office would know.”

That is not a discussion. It is cross-examination, conducted without records, over facts that were all known — separately, by different people — days ago.

Nobody wants the courtroom. It happens for a structural reason: the week’s facts live scattered across a group chat, an inbox, a stale spreadsheet and several memories, so the meeting is the only place the truth can be assembled.

When the facts have no home, reconstruction crowds out decision.

The past eats the hour. The future — choosing what to do about the week ahead — gets whatever minutes are left.

The usual fix treats the meeting: a better agenda, a timer, a rule that updates must be sent in advance. The problem is upstream of all three. An agenda cannot supply missing facts, and “send updates in advance” only moves the reconstruction into everyone’s Sunday evening.

The durable fix is to make status something that is read, not asked. Every task carries one owner, one written date and a current state, and that state updates where the work happens — not later, from memory, into a separate file. By Monday morning the facts are already there: who finished what, which dates moved and why, who is waiting on whom. Readable in minutes, before anyone sits down.

Then the meeting gets its hour back for the only things a meeting is good for — exceptions and decisions. Not “what happened to the Sharma order?” but “the Sharma order has been waiting on the drawing for three days. What do we do about it?”

Run this test in your next weekly review: how many minutes pass before the first real decision?

Not reported. Not clarified. Not reconstructed. Decided.

If that is more than half the meeting, you are not holding a review. You are holding a hearing.

The answer is not to cancel the meeting. It is to make the meeting unnecessary for status.

That is what TaskMIS is built for: the work and its record in one place, so the facts are current before anyone sits down. One owner. One deadline. One recorded reason when the date moves.

Less reconstruction. More decisions.