When I joined Halden (fictional) in March 2025, the product and engineering teams had four status meetings a week: a Monday planning sync, a Tuesday cross-team stand-up, a Thursday leadership update and a Friday demo that had turned into a progress report. Together they took 31 hours of people's time every week.

By week three there was one written update and one review. Releases went from every six weeks to every two over the quarter.¹ The meetings were not the only reason, but they were the easiest one to fix.

Why status meetings fail

A status meeting is a broadcast pretending to be a conversation. Each person reads out what they did while everyone else waits for their turn. Information goes one way, decisions get deferred to 'take it offline', and the people who need the update most are often not in the room.

The written update

Every team lead writes one update by Thursday noon, in the same five headings, in one shared document. It takes fifteen minutes to write and five to read. Anyone can comment. The CEO reads all of them on Thursday afternoon instead of attending three meetings.

Weekly update template: TEAM: Payouts WEEK: 2025-W14 · Shipped: same-day payout status (week 2 item) · Next: retry logic for failed bank files · At risk: bank sandbox access, waiting since Tue · Decision needed: drop SEPA Instant from Now? (owner: Ines, by Fri) · Metric: payout status tickets 212 -> 140 / week

The heading that does the work is 'Decision needed'. It turns the update from a report into a request, with an owner and a date.

The review

On Friday we hold one 45-minute product review. There is no round of updates, because everyone has read them. The agenda is the list of 'Decision needed' items, plus anything a commenter flagged. If the list is empty, the meeting is cancelled. At Halden that happened three times in the first quarter, and people noticed.

If the meeting exists to share information, it should be a document. If it exists to make decisions, it should have a list of them.

From my Halden notes, 2025

A two-week experiment: Count the hours your team spends in status meetings this week, then ask each lead for a five-heading written update instead, for two weeks. Keep one review for decisions only. Bring the meetings back only if someone can name what was lost.

What I would do differently

I cancelled the Friday demo along with the rest, and that was a mistake. It had been a progress report, but under that it was the one place engineers showed their work to the whole company. Morale dipped for a month until we brought it back as a monthly show-and-tell with no status in it at all.

Notes

Production releases per month went from 0.7 to 2.2 between April and June 2025. See the Halden case study for the full numbers.