Blog

The 15-minute Monday planning meeting

It is 9:47 on Monday and the planning meeting is still going. Two people are reading their task lists aloud. One is renegotiating a deadline in a side conversation. Half the room has quietly opened email, and a meeting meant to plan the week is eating the week's best morning.

The fix has three parts: the drafting happens before the meeting, the meeting walks a grid, and the grid stands as the minutes afterwards. Done that way, fifteen minutes is enough for a team of twelve.

Before: everyone drafts their own week

Planning meetings run long when people plan inside them, so move the drafting out. Before the meeting (Friday afternoon works, so does Monday over coffee), each person lays out their own five days: which tasks, on which days, roughly in order. In ToDoing that means filling in My Week, the personal planner. Anything unfinished moves forward to today by itself each working morning, so a draft made on Monday starts from what is actually left rather than from memory, and anything that cannot earn a day goes to the Someday list until it can.

That takes each person about ten minutes on their own, and it means the meeting reviews plans instead of producing them.

During the meeting: walk the team grid

Open the Overview, which puts the whole team's week on one grid with people as rows and days as columns. My Week and the Overview are the same data seen two ways, so every draft is already on screen when the meeting starts. Then run three passes.

First, people. Walk the rows from top to bottom, about thirty seconds each: here is my week, and here is the one thing that could knock it over. An overloaded Wednesday shows as a crowded cell, so nobody has to confess to being buried, because the grid already says it.

Second, milestones. Deadlines sit on the same calendar as the tasks, so a milestone with too little work scheduled in front of it shows the gap on Monday, while there is still time to act. Look at this week's milestones and next week's. If Thursday's delivery has one task ahead of it and that task needs three days, you have found the conversation the meeting is really for.

Third, trade-offs. Repair what the first two passes turned up, live in the grid, with whoever runs the meeting (an admin, since only admins can move other people's work) driving. Drag a task to a different day or a different person, or drag a milestone if a date has genuinely moved. Pull work out of Someday when someone's week is light, and push work into it when someone's week is fiction. Changes reach everyone's screen in under a second, so the plan gets fixed in the room, with the people it affects watching.

After: the grid is the minutes

Write nothing up. The grid you just edited shows who is on what this week, where each milestone now sits and what went to Someday. Anyone who missed the meeting can read the week in thirty seconds, and anyone who forgets a decision on Wednesday can look at the grid, which changed the moment the room made it.

This is where most weekly meetings leak. Someone writes the minutes from memory, they drift from reality by Tuesday, and by Thursday two people are working from two different versions of the plan. When the thing you edit in the meeting is the thing everyone plans their day from, there is nothing left to reconcile.

The longer argument for running a small team on weeks is in plan the week, not the backlog. If you want a longer, fuller version of this meeting, with time to clear last week's leftovers and talk through the trade-offs, the weekly review for a whole team sets out a thirty-minute shape. The fifteen-minute version works best once everyone has the habit of drafting their week before they walk in.

Keep reading

ToDoing is the simple work planner these notes come from. It's free to try, and it never asks for a card.