Every Monday afternoon, on cycle only, the team reviews the week ahead. Each person shares their agenda, you schedule whatever the week needs scheduling, and you ask out loud what could go wrong. It takes about thirty minutes and it is the meeting that stops Thursday from being a surprise.
It is one half of a pair. Monday looks forward, and Friday's check-out looks back. Neither works nearly as well without the other.
How to run it
- Each person shares their weekly agenda. Straight off their own cycle sheet. Not a status report on last week, a walk through the days coming.
- Coordinate and schedule any required meetings or reviews. Do it in the room, while everyone's week is visible, rather than through five separate messages on Wednesday.
- Ask what problems could occur this week. Out loud, to everyone.
- Ask the team what tasks are important for management to focus on. This one inverts the usual direction of the meeting, deliberately.
- Review the improvements from the previous week. Whatever the group agreed to change at the last check-out, check whether it changed.
Question three is the one that earns the meeting
"What problems could occur this week" is a strange question to ask a group, because most weekly meetings ask the opposite: what did you finish.
Asking it forward has a specific effect. It surfaces the dependency somebody has been quietly worrying about since Thursday, the client who has not replied, the deploy that needs someone else's approval. All of it is cheap to solve on Monday and expensive to solve on Friday.
It also does something to the room. Naming a risk in front of everyone stops it from being a private problem that becomes a public failure later.
Question four inverts who the meeting is for
Asking the team what management should be focused on is uncomfortable the first few times, and then it becomes the most useful thirty seconds of the week.
Most teams have a running list of things only a manager can unblock. Budget approval, a decision that has been sitting for two weeks, a client who needs to hear it from you rather than from them. That list rarely gets raised unprompted, because raising it feels like complaining.
Ask directly and it stops feeling like complaining. It becomes an agenda item.
The plan will change, and that is not the point
Each person is responsible for adjusting their own schedule when things move, and things will move. I have watched a plan change the second we walked out of the meeting. It always does.
But at least there is a plan in place, something to measure against. Something you can track to understand how often tasks are not getting completed, and hopefully do better next time around.
A plan that survives contact with the week is not the goal. A plan that lets you notice what happened to the week is.
Keep it in the afternoon, and keep it on cycle
Two constraints that matter more than they look.
Afternoon, not first thing. Morning is when most people do their best work. Spending it in a meeting about work rather than on work is a bad trade, and it also means people arrive having already touched their week.
On cycle only. Both meetings run during the six working weeks and stop during the two weeks off. If you fill the break with recurring meetings you have deleted the break, which was the whole reason for the structure.
Why two meetings and not five
This pair replaces a lot of other things.
Because there are scheduled meetings on both ends of the week, I stopped dropping random tasks on people mid-week. My team was respectful of their own time, and that caused me to be respectful of it too. Work that used to arrive as an interruption on Tuesday now waits for Monday, or goes into the next cycle sheet.
If your calendar has no room for two meetings a week, the honest first step is deleting the ones that should have been emails. Most teams find the room immediately.
The whole method is in the guide to running your work in six-week cycles.