Approval culture: how review rounds really go wrong

A review round is a decision with a deadline. That is the whole idea. In practice, most rounds drift into open-ended conversation: comments arrive over three days, half of them contradict each other, and nobody says the words 'this is approved'.

Three failure modes

1. The round with no edge

If a review does not say when it closes, it will not close. Feedback keeps arriving after the team has started revising, and every new comment reopens settled ground. A round needs a stated end — even a rough one — or it becomes a continuous stream.

2. The missing decision-maker

Reviews with five commenters and no named approver produce comments, not decisions. The work gets discussed from every angle and then stalls waiting for someone to say yes. Name the person whose sign-off counts, and let everyone else contribute to the thread.

3. The versionless file

A comment on 'the latest file' is a comment on nothing. Once two versions exist in circulation, feedback becomes archaeology. Every round should reference the exact version it reviewed — and approval should name that version explicitly.

What a healthy round looks like

One link. One current version. One named approver. A stated close date. And when the decision is made, a record of who approved what, when. That record is not bureaucracy — it is the difference between a project that moves and a project that re-litigates.

• State the round's close date when you send it
• Name the approver in the invitation, not the brief
• Anchor every comment to the current version
• Record the decision where the work lives