Meeting agenda for a small team: build the weekly agenda from open items the day before, one owner per topic, and a Slack thread that drafts it

A good weekly meeting agenda for a small team is a short list of questions, each with one owner, gathered the day before from three places: last week's open action items, the overdue tasks in your project tool, and the topics people posted during the week. Harvard Business Review's agenda advice adds the test: only topics that affect everyone present, written as questions, with who leads each.

The gathering is where most small teams fail. The agenda gets typed five minutes before the call, or last week's copy is reused, so open items from the previous meeting are never checked and the hour fills with status updates. With six people in the room, every hour of updates costs six hours of paid time, spent hearing news that could have been read. A day-before build gives you a 30 minute meeting that ends with decisions, and a list of open items that cannot quietly disappear between Mondays.

What should a weekly meeting agenda include?

A weekly team meeting agenda needs four parts: the open items from last time, the topics that need the group, decisions, and new action items with owners. The current templates agree on this skeleton. Less Meeting's agenda templates give recurring meetings three standing slots: last time's open action items, the numbers, and the current issues list. Otter's team meeting template puts a review of previous action items near the start of a 45 minute weekly sync, and Rolebase's staff meeting format gives open actions a short standing slot of their own.

Here is a copyable version sized for a team of 5 to 15 people. Treat the times as a budget, not a schedule.

That is 30 minutes. If the topics slot keeps running over, the fix is fewer topics, not a longer meeting. tinyteam's agenda guide makes the same point in its build steps: list topics, then cut them, time-box what remains, and give each item an owner.

Try Kipwise Agent free in Slack: mention it once in a thread and it does the repetitive work, with your permissions.

Where should the agenda items come from?

A weekly meeting agenda should be gathered from three places the day before: last week's open action items, the overdue tasks in your project tool, and the topics people posted during the week. Each source catches something the others miss.

1. Last week's open action items. These come from last week's meeting notes, or from the transcript if the meeting was recorded. They are the promises the group made to itself, and they are the items most likely to vanish, because nobody owns the list between meetings. If your team already turns Slack discussions into tasks, the action items workflow in Slack is the same list, seen from the other end.
2. Overdue tasks in the project tool. Asana, Jira, Linear, ClickUp or monday.com already know which tasks are past their date. An overdue task is not automatically a topic, but it is a question someone should be asked: is this blocked, or did it stop mattering?
3. Topics posted during the week. Give the team one place to drop topics, such as a thread in the meeting channel, and tell people that a topic not posted by the day before waits a week. This is where the agenda gets real input instead of the organiser's guesses, which is the first piece of HBR's advice: seek input from the team so the agenda reflects what they need.

Why the day before? Because the agenda has to reach people early enough to prepare. Less Meeting suggests sending it the day before so people arrive with an opinion, and tinyteam says to share it at least 24 hours early. A day-before build also gives topic owners one working day to gather what they need, which a five-minute-before agenda never does.

The rule has a blunt practitioner version. In a Hacker News thread on how tech leads work, one commenter writes that recurring weekly meetings are fine, but a meeting without an agenda sent a day or so before should be cancelled. Another commenter, a manager of a large department, reports that "no agenda, no meeting" became a running joke and then a habit across the whole team. These are one person's reports each, not a study, but they show the rule can stick when the person who runs the meeting holds to it.

Which topics deserve a slot in the meeting?

A topic earns a slot only if it affects everyone in the room, is written as a question, names one owner and says whether it informs, asks for input or decides; everything else goes in a written update. Each part of that test comes from Roger Schwarz's HBR piece on agenda design, which says the issues discussed should affect everyone present, topics work better as questions, the agenda should say whether a discussion shares information, seeks input or makes a decision, and it should name who leads each one.

Use the test as a checklist when you read the gathered list:

• Does it affect everyone present? A pricing question for two account leads is a side conversation, not a team topic.
• Is it a question? "Client onboarding" is a heading. "Should new clients get the kickoff call in week one or week two?" is a topic someone can prepare for and the group can close.
• Does it have one owner? The owner brings the facts and leads the discussion. "The team" is not an owner.
• Is the purpose stated? Inform, input or decide. People argue less when they know a topic is for input only and the owner will decide after.

Here is a made-up example of the test at work. The gathered list for a 9 person agency has eight items. Three are status updates on client projects, so they move to the written update. One affects only the two designers, so it becomes a thread between them. That leaves four: one open action item from last week that is still blocked, one overdue task that needs a decision on whether to drop it, and two posted questions. Four topics fit the 15 minute slot.

Why should status updates leave the meeting first?

Status updates are the first thing to remove from a small team's weekly meeting, because they are the one item that loses nothing when it is read instead of heard. A status update has no question in it, so it fails the second part of the topic test. It also rarely affects everyone present, so it often fails the first part as well.

Moving them out of the meeting keeps them in writing. Ask each person to post a short written update before the meeting, then give the numbers slot five minutes to discuss only what someone wants to question. For a team that already works in Slack, an async status digest does this without anyone chasing the updates by hand. The meeting keeps the work a written update cannot do, which is deciding together.

This is a recommendation, not a measured rule. Some teams use the weekly meeting partly to stay connected, and a round of updates is how they do it. If that is your team, keep the round, but time-box it and move it to the end so the topics get the fresh minutes.

How do you run the day-before build in Slack?

You can run the day-before build by hand in about 20 minutes, or let an agent in Slack draft it from the same three sources. The manual version works for most teams, and it is worth doing by hand for a few weeks so you know what a good agenda looks like before you hand the job over.

The manual version

1. The day before, open last week's notes and copy every action item that is not marked done.
2. Open the project tool and filter for overdue tasks assigned to anyone in the meeting.
3. Read the topics thread in the meeting channel.
4. Run each item through the topic test. Move status items to the written update and side conversations to their own thread.
5. Write each surviving topic as a question with its owner, its purpose and a time.
6. Post the agenda in the meeting channel and in the calendar event, at least a day ahead.

With the agent in Slack

The Kipwise Agent works in Slack threads: a teammate mentions it once, and plain replies in the same thread continue the conversation. It can run a request on a schedule in plain language and post the result in the channel, so a request such as "every Monday at 2pm, draft tomorrow's team meeting agenda in this thread" becomes a weekly job. Creating a scheduled task needs approval once; later runs do not ask again. Scheduling recurring agent jobs in Slack covers how a scheduled request runs and what to watch for.

For each run, the agent reads what the asker's own connected tools allow:

• Last week's action items. If last week's call ran on Google Meet with transcription or Gemini notes turned on, the agent can read the transcript or notes from the calendar event, with Google Calendar and Google Drive connected (Meet transcripts need Google Workspace Business Standard or higher). It can also read the transcript of a Zoom meeting the person hosted. It quotes what was said and does not fill gaps; when there is no transcript, it says so.
• Overdue tasks. Asana, Jira, Linear, ClickUp, monday.com and the other connected project tools each use the asker's own access.
• Posted topics. The topics teammates replied with in the meeting thread.

It drafts the agenda as a reply in the thread, and teammates reply to add or drop a topic. If you want the agenda copied into the meeting notes Doc, the agent shows an Approve or Deny card before it edits the Doc, and only the person who asked can approve it; the card expires after 30 minutes. The agent does not join or record meetings and does not transcribe audio, and it does not invite anyone to a calendar event unless explicitly asked.

What stays with a person: cutting the topics, running the meeting, making the decisions and anything that goes to a client. The agent does the gathering, which is the step that usually gets skipped.

What goes wrong, and how do you check it worked?

Five failures come up again and again, and each has a simple fix.

To check the new agenda is working, look at three things after four weeks. Do meetings end on time? Does the open items slot shrink, or at least stop growing? Can someone who missed a meeting find what was decided in the thread? If all three hold, keep the build as it is. MeisterTask's agenda examples end their simple template with decisions and action items for the same reason, so the agenda doubles as the record.

Monthly meetings follow a different pattern. A monthly business review for a small team has its own pre-read and a longer agenda built around numbers, and it should not be squeezed into the weekly slot. For the notes that follow your weekly meeting, the meeting minutes template gives you a place to record decisions and action items.

What to do next

Before your next weekly team meeting, post one message in the meeting channel asking people to reply with any topic they want covered, written as a question, by the day before. Then build that week's meeting agenda from the three sources above, run every item through the four part test, and post it a day ahead. If you want the gathering done for you, add the Kipwise Agent to that channel and ask it once to draft next week's agenda in the thread the day before; it costs $10 per user per month, and there is a trial with no card.