Boost Your Productivity with ClickUp

The all-in-one workspace for teams. Try it free for 30 days!

Meeting Agenda: How to Write One That Gets Decisions, Not Just Discussion

Small studio team working through a meeting agenda around a table in a bright workspace
A step-by-step way to write a meeting agenda that ends in decisions, with a copy-ready template and a worked example for small studios and service teams.

A meeting agenda is more than a list of topics. Written well, it tells everyone why the meeting exists, what each item is for, and what should be decided before people leave. Written loosely, it can invite a long conversation that ends with “let’s pick this up next week.” This guide shows how to write a meeting agenda that steers the group toward decisions, with a template you can copy and a worked example from a small studio.

Who this guide is for

This guide is for small business owners, studio founders and small-team leads who run weekly team meetings, client check-ins or planning sessions. It suits design studios, agencies and service businesses where meeting time comes straight out of billable or creative hours. No special software is needed; a shared document works fine.

Why discussion-only agendas stall

Consider a typical agenda line: “Website redesign.” It names a subject but says nothing about what the group should do with it. As a result, people can arrive with different expectations. One person wants to share an update, another wants feedback, and a third assumes a decision is due. The conversation drifts, and the meeting ends without a clear outcome.

The fix is to make each item answer three questions before the meeting starts: what exactly are we discussing, why are we discussing it, and who is leading it. The steps below build on advice from Roger Schwarz in a Harvard Business Review article on agenda design and Asana’s guide to agendas.

How to write a meeting agenda in seven steps

1. State the goal in one sentence

Asana’s guide recommends stating the primary purpose of the meeting in a single sentence. For example: “Agree the launch date and budget for the Harbour Café rebrand.” If you cannot write that sentence, the meeting may not be needed yet, or an email might do instead.

2. Ask the team for input

Schwarz’s HBR article suggests seeking input from team members so the agenda reflects their needs. In practice, share a draft a day or two ahead and ask, “Is there anything you need from this group that isn’t here?” Consequently, people arrive with fewer surprise topics.

3. Include only topics that need this group

The same HBR article advises that when the whole team meets, topics should affect everyone present and need the whole team to resolve. Therefore, anything that concerns two people can move to a separate conversation. This one filter can shorten an agenda noticeably.

4. Phrase each topic as a question

In HBR, Schwarz gives the example of turning “office space reallocation” into “Under what conditions should we reallocate office space?” A question tells people what kind of answer is needed. Compare these versions:

Topic as a label Topic as a question
Website redesign Which of the two homepage concepts do we present to the client on Friday?
Hiring Do we hire a freelance developer for Q1 or extend current hours?
Client feedback process What is the one change we make to how we collect client feedback next month?
Holiday schedule Who covers client emails during the last two weeks of December?

5. Label the purpose of each item

Next, the HBR article recommends telling the team whether each discussion is to share information, seek input on a decision, or make a decision. Add a simple tag to each line: Inform, Input or Decide. In addition, name who makes the call on “Decide” items, so nobody assumes the decision is by consensus when it is not.

6. Give each item a time and a lead

Asana’s guide suggests assigning a realistic amount of time to each topic and adding buffer time. Schwarz’s HBR article also recommends showing who leads each discussion so they can prepare. Put “Decide” items early so they get full attention, and keep “Inform” items short or move them to a written update.

7. Share it with pre-reading in advance

Finally, attach any documents people should read beforehand. Asana’s guide suggests sharing the agenda as early as possible and, at the very latest, an hour before the meeting. For decision items, a day ahead gives people time to form a view.

A meeting agenda template you can copy

Copy this into your shared document and fill in the brackets:

  • Meeting: [name], [date], [start and end time]
  • Goal: [one sentence describing the outcome]
  • Attendees and roles: [facilitator], [note-taker], [decision-maker for each Decide item]
  • Pre-reading: [links]
# Question Type Lead Time
1 [Decision question] Decide [Name] [mins]
2 [Input question] Input [Name] [mins]
3 [Update] Inform [Name] [mins]
4 Recap decisions, owners and deadlines Close Facilitator 5 mins

The closing recap matters. Before anyone leaves, read back each decision, who owns the next step, and when it is due. Then paste that recap into the agenda document so the agenda becomes the record.

Worked example: a weekly studio meeting agenda

Consider a hypothetical six-person brand studio. Its Monday meeting used to be a 60-minute round of updates. The founder rewrote the meeting agenda using the template above:

  • Goal: Confirm this week’s priorities and settle the two open questions blocking client work.
  • 1. Decide (founder, 15 mins): Do we accept the Harbour Café request to add a menu redesign within the current fee, or quote it separately?
  • 2. Decide (design lead, 10 mins): Which of the two packaging directions goes to the client on Thursday?
  • 3. Input (account manager, 10 mins): What should we change in our project handover checklist?
  • 4. Inform (written): Project status updates, posted in the shared document before the meeting.
  • 5. Close (5 mins): Recap decisions, owners and deadlines.

Because updates moved to writing, the meeting now runs to about 40 minutes. More importantly, each item has a clear finish line. The menu question ends with “quote separately, account manager sends quote by Wednesday.” Similarly, the packaging question ends with a chosen direction and a named designer to prepare the presentation.

Adapting the meeting agenda for client meetings

The same structure works with clients, with a few adjustments. Share the agenda with the client contact ahead of time and invite them to add items, so the session covers what they need as well as what you need. Be explicit about who decides each item. For example, the client might sign off on creative direction, while your team decides on production approach and scheduling.

It also helps to separate feedback from decisions. A line such as “Input: what feels off-brand in the second concept?” invites open comments. In contrast, “Decide: do we proceed with concept two, with the agreed changes?” asks for a clear yes or no. Keeping both on the agenda, in that order, gives the client room to react before they are asked to commit.

After the meeting, send the recap of decisions, owners and dates within a day. That message becomes the shared reference if questions come up later in the project.

Running the meeting so the agenda holds

A strong meeting agenda still needs a facilitator who sticks to it. A few habits help:

  • Open by reading the goal aloud and confirming the end time.
  • Keep a visible timer for each item and give a two-minute warning.
  • When a new topic appears, add it to a “next meeting” list instead of discussing it now.
  • If a decision item cannot be settled, agree what information is missing, who will get it, and when the decision will be made.
  • End on time, even if the last item has to move.

For more ways to protect your team’s time, browse our time management articles.

Meeting agenda checklist

Before you send the agenda, check that:

  • The goal fits in one sentence.
  • Every item is phrased as a question.
  • Every item is tagged Inform, Input or Decide.
  • Every Decide item names the decision-maker.
  • Every item has a lead and a time.
  • Updates that need no discussion have moved to writing.
  • Pre-reading is linked, and the agenda goes out with enough notice.
  • A recap slot is booked at the end.

Key takeaways

A meeting agenda is more likely to produce decisions when each item is a clear question with a stated purpose, a named lead and a time limit. Ask the team for input, keep only topics that need the whole group, put decisions first, and move pure updates to writing. Close every meeting by recapping decisions, owners and deadlines in the agenda itself, so the next meeting starts from what was agreed rather than from scratch.

Written by the Design Productive Editorial desk. Disclosure: this guide contains no affiliate or sponsored links.

Share this article

Facebook
Twitter
LinkedIn
WhatsApp

Search Articles

WRITTEN BY

Weekly Productivity Tips

Get the latest AI tools and productivity hacks delivered to your inbox.

Analytics Made Simple

Track your productivity metrics with Mixpanel. Get insights that matter.

Boost Your Focus

Block distractions and stay in flow state with Freedom app.