A weekly team meeting agenda template that fits in 20 minutes

Most weekly meetings in small businesses run for an hour and consist of people reading out what they did last week, to colleagues who could have read it themselves. This weekly team meeting agenda template does the opposite: it takes 15 to 20 minutes, skips the updates nobody needs, and spends most of its time on the two or three things that are stuck.

It’s written for teams of roughly 3 to 15 people who meet once a week, in a room or on a call. Bigger teams can use it too, but they’ll probably want one per department.

The weekly team meeting agenda template

Copy this into whatever you use. The times are a guide; the order matters more than the minutes.

WEEKLY TEAM MEETING (15-20 minutes)
Same day, same time, every week. Starts on time even if someone's late.

0:00  Numbers (2 min)
      One or two figures the whole team cares about this week.
      Orders in, jobs booked, overdue invoices. Not a report.

0:02  Last week's commitments (4 min)
      Walk the board. Each one is done, or not done and why.

0:06  Stuck or late (6 min)
      Only cards that are blocked or past their due date.
      For each: who unblocks it, and by when?

0:12  This week (4 min)
      Each person names what they'll finish, not what they'll "work on".

0:16  Notices (2 min)
      Holidays, rota changes, a new client, the boiler engineer on Thursday.

0:18  Read back (2 min)
      New tasks created in this meeting: owner and due date, out loud.
      Then stop.

What each part is for

The numbers slot is short on purpose. A bakery might look at wholesale orders for the week and how many custom cakes are booked. An agency might look at hours left on two retainers. Pick figures people can do something about. If nobody in the room can change a number, it belongs in a monthly review.

Last week’s commitments is where the meeting earns its keep. Last Monday people said what they’d finish, and now you check. Keep it to done or not done, and when it’s not done, one sentence on why. It’s also why the last slot asks people what they’ll finish rather than what they’ll work on, because a finish can be checked a week later.

Stuck or late gets the longest slot because it’s the only part of the meeting where the whole team is needed. A card is stuck when whoever owns it is waiting on something they can’t hurry, usually a supplier or somebody else’s decision. The job in the meeting is to name who unblocks it and by when, and nothing more. You don’t solve it there. If fixing it needs more than a minute of discussion, the two people involved stay behind afterwards and everyone else goes back to work.

This week is quick: each person says one to three things they’ll finish. People who say five are usually going to finish two, and it’s kinder to say so now than next Monday.

Notices are one-way, and nobody debates the rota in the notices slot.

The read-back feels a bit school-assembly, and it’s the part teams drop first. Please don’t. Two minutes of “Kasia, supplier quote, Wednesday; Tom, new starter’s laptop, Friday” is what turns a chat into work that someone owns. If a job gets mentioned in the meeting and nobody’s name goes on it, it didn’t really get agreed.

What we’d cut

Round-the-table updates go first. They’re the reason weekly meetings take an hour. Each person talks for four minutes about things that are going fine, and the other nine people wait for their turn. If the board is up to date, the updates are already written down.

Problem-solving between two people goes next. If a conversation only involves Marco and the accounts person, the rest of the room is just waiting. Park it, and they sort it straight after.

“Any other business” is a trap. It invites a 20-minute tangent at minute 17. If something matters enough to raise, it goes on the board or in the notices before the meeting starts.

Reading the board aloud card by card also goes. The board is there so you don’t have to. Filter it to what’s late or stuck and look only at that.

And the minutes. A small team doesn’t need a written record of the meeting if every decision became a task with a name and a date. The tasks are the minutes.

Running it from a board

A board makes this agenda easier because it shows most of what you’d otherwise say out loud. Put it on the big screen or share your screen, and work from left to right.

The setup we’d suggest is simple. One project for the team’s ongoing work, a handful of columns (To do, Doing, Waiting, Done works for most people), and a due date on every card. If you’re new to boards, our guide to kanban boards for small teams covers columns and what a good card needs.

In Klusko you’d run the meeting in Board view and save two views beforehand, for example one sorted by due date and one filtered to cards tagged “waiting”. A saved view keeps your filter and sort under a name, so next Monday it’s one click rather than rebuilding the filter while nine people watch. The Workload view (on the Team plan) is worth a glance during “this week”: it shows capacity bars per person against the team average, which makes it obvious when one person has signed up for twice what everyone else has. There’s more on planning views on the planning page.

Make the meeting itself a recurring task, weekly, assigned to whoever chairs. When they tick it off, next week’s appears. It’s a small thing, but it means the meeting has an owner too. We wrote up how recurring work fits in Klusko if you want other examples.

Klusko doesn’t do video or voice calls. If your team is remote or split across sites, run the call in whatever you already use and share the board on screen. It works fine, and there are a few more tips for remote teams on that page.

When the owner does all the talking

If you own the business, this section is probably about you. It was about us.

Owners talk more in meetings for understandable reasons: they usually know the most, and everyone waits for them to speak before committing to anything. The result is a meeting where the owner reads out their own to-do list while the team nods, and the problems the team could have raised never come up.

So what helps? Take whichever of these suit you.

Let someone else chair, and rotate it weekly through the team. The chair keeps time and moves the agenda on, and that includes moving the owner on.

Owner goes last in “this week”. Once the boss has said “I think we should focus on the Harrow job”, nobody says their own priority is something else. Hearing everyone else first also tells you what the team thinks matters, which is useful information in its own right.

Put a visible timer on each slot. A phone on the table showing 4:00 counting down does more than any amount of good intentions.

Owner’s ideas go on the board like everyone else’s. “We should redo the website” becomes a card, with a name and a date, or it doesn’t happen. That one habit tends to cut the owner’s airtime by half, because a lot of what bosses say in meetings is thinking out loud, and thinking out loud looks different once someone asks who’s doing it and when.

If you only try one thing

Try the read-back. Two minutes at the end, every task, every name, every date. Most teams find that the week after, “last week’s commitments” suddenly has something to check against, and the meeting gets shorter on its own. For the days between meetings, the same rule works in chat; our piece on stopping tasks getting lost in chat covers it.

Questions