Most planning meetings run long for the same reason: the team uses the meeting to find out what is going on. If everyone arrives already knowing the state of the work, the meeting only has to answer one question, which is what matters most this week.
Here is the format we settled on after a lot of trial and error. It works for teams of three to about ten people. Beyond that, split into smaller groups.
Before the meeting: update the board
By Monday morning, every person moves their own cards to the right column and adds a one-line comment to anything that is stuck. This takes each person about five minutes, and it is the reason the meeting can be short.
- Move finished work to Done, even if it shipped late.
- Flag blocked cards with the reason and who can unblock them.
- Add anything new you know is coming this week.
The agenda
We use the same three questions every week, in the same order, with a timer on the screen.
- What shipped? Two minutes. Read the Done column out loud, and say thank you.
- What is stuck? Five minutes. Only flagged cards. Agree on one next step and one owner for each.
- What matters most this week? Eight minutes. Each person names their top one or two tasks. Nobody names more than two.
If a topic needs more than two minutes of discussion, it gets its own meeting with only the people who need to be there.
Keep a parking lot
Good ideas come up in planning meetings, and they are rarely urgent. Keep a column called Later on the board. Anything that is not about this week goes there, and you review it once a month.
Weekly planning — 15 minutes
1. What shipped? (2 min)
2. What is stuck? (5 min)
3. Top 1–2 tasks per person (8 min)
Parking lot → "Later" column
After the meeting
The facilitator posts a short summary in the team channel: what we agreed, who owns each blocked item, and anything moved to Later. In Stackly, the Monday digest does this automatically from the board.
What to do when the meeting runs over
It will, at first. Resist making the meeting longer. Instead, look at which question overran. If it is the second one, blocked work needs a separate conversation. If it is the third, people are bringing too many priorities.