I mean the recurring Monday-morning status meeting. The one where everyone is expected to arrive with a polished account of last week and a confident plan for the next five days, before they've had time to reopen the work.
If production is down, people need a handover, or a decision is blocking the team, get together. Those meetings have a job to do. The weekly status round that exists because somebody once found an empty slot at 9 a.m. deserves more scrutiny.
Monday morning is for reloading context
Monday morning is a reasonable time to get back into context. Read what changed. Look at the work in progress. Check whether Friday's assumptions still hold. Remember why that pull request was more complicated than it looked.
That takes time, even when nothing dramatic happened over the weekend.
Put a status meeting at the very beginning of the day and you ask people to report before they've had a chance to understand. You'll hear what they remember from Friday, what they can safely promise without checking, or what they prepared in advance.
That last option deserves attention.
The hidden Sunday-evening deadline
A Monday-morning meeting can quietly create a Sunday-evening deadline. Nobody needs to explicitly ask people to work over the weekend. The expectation to arrive fully prepared can do the asking for them.
Some people will resist that pressure. Others will check their messages, update a slide, or rehearse an answer because they don't want to look unprepared in front of their manager.
If preparation is required, give it space during working hours. The calendar invitation should account for the work needed to make the meeting useful.
What the meeting displaces
The first clear block of the week could be used to investigate a problem, finish a piece of work, or think through an approach. Put a group update in the middle of it and you've made that block smaller before the week has properly started.
For an engineer holding a difficult problem in their head, even a short meeting can be an awkward interruption. And “just thirty minutes” becomes less persuasive when several people each have one small thing to add.
Most status doesn't need a meeting
The meeting may also produce surprisingly little that requires a meeting.
What changed? What's next? Where are you blocked?
Those are useful questions. A short written update can often answer them, particularly when the underlying work is already visible. Let people write it after they've had a chance to get oriented, during the working day.
Keep it genuinely lightweight. Requiring a carefully formatted report in three different systems would be an impressively thorough way to miss the point.
Save the room for real conversations
Then look at what actually needs a conversation.
Two teams disagree about a dependency. A delivery commitment needs to change. Someone needs help choosing between two approaches. Bring the relevant people together, with enough context to make progress. Finish with a decision, an owner, or a clear next step.
Sometimes that conversation should happen on Monday. Waiting until Tuesday while someone stays blocked would be ridiculous.
Moving every recurring meeting one day to the right would also achieve very little. Tuesday deserves a chance.
The useful question is whether the meeting happens when the team has enough context, and whether being together helps resolve something.
Try it for two weeks
If you manage a team, try protecting the start of Monday for a couple of weeks. Agree on how urgent issues get raised. Give people time to read, think, and update the work. Keep the conversations that genuinely help.
Then ask what you missed. Was something important overlooked? Did a decision happen too late? Or did the familiar status meeting turn out to be less necessary than its permanent place in the calendar suggested?
Monday already asks people to restart enough things.
Before booking everyone's first hour, have a better reason than “this is how we start the week.”