Pro free for 30 days.No card.Start free →

Running meetings people don't dread: a simple guide for small teams

How to run meetings people don't dread: use a five-question filter to cancel the ones you do not need, design the ones you keep with question-style agendas, run them in a tight structure and audit your meeting load every few weeks.

By WorkBOS Content Desk7 min read
Empty meeting room with a white table, dark chairs and glass whiteboards (Photo by Pexels on Pixabay)
Photo: Pexels / Pixabay

Ask any team what they would change about work, and meetings come up quickly. Not because people dislike talking to each other, but because so many meetings have no clear purpose, include people who do not need to be there, and end without a decision. In a small business, where everyone wears several hats, a wasted hour is felt by the whole company.

This guide shows you how to question whether a meeting should happen at all, how to run the ones that should, and how to build a simple rhythm that gives people their time back. Everything here is cheap to try and needs nothing more than a shared calendar and a habit of writing things down.

Why meetings get a bad reputation

The research is more nuanced than "meetings are bad". A piece from the Wharton School's Knowledge at Wharton argues that the problem is bad meetings, meaning unclear purpose, vague goals and poor preparation, rather than meetings themselves. It also notes that live conversation is the richest form of communication, which is why it suits complex or ambiguous issues better than email.

Other findings are sobering. A team including a Boston University lecturer, working with Harvard Business School researchers, surveyed 182 executives. As described in BU Research, a majority of senior managers said too many meetings were unproductive, kept them from their own work and did not bring teams closer together. And an article in SHRM discusses researcher Steven Rogelberg's idea of "meeting recovery syndrome": the time people spend getting over a frustrating meeting. Note that the SHRM piece draws on cost estimates and surveys rather than a controlled experiment, so treat the productivity claim as reasoned, not proven.

The practical lesson: fix the cause, not the symptom. A shorter useless meeting is still useless.

Step 1: Ask whether the meeting should exist

The BU researchers recommend questioning whether a meeting is needed at all, who must attend and how many are needed, before worrying about agendas. Use this quick test.

The five-question filter

  1. What decision or outcome do we need? If you cannot state it in one sentence, do not schedule it.
  2. Could this be an update? Wharton's piece notes that meetings that only share information can usually be replaced with an email. A written update or a recorded video works for status.
  3. Do these people depend on each other for this task? If not, invite fewer people.
  4. Does it need live discussion? Conflict, complex trade-offs and brainstorming with real back-and-forth do. Routine approvals do not.
  5. Is today the right time? Sometimes a decision needs a day of thinking first.

If a meeting fails the filter, replace it with a written message and a deadline for replies. Our guide to asynchronous communication shows how.

Step 2: Design the meetings you keep

Pick the right type

Wharton's article describes four formats attributed to author Patrick Lencioni, which fit small teams well:

| Format | Length | Purpose | |---|---|---| | Daily check-in | 5 to 10 minutes, standing | Quick coordination, flag blockers | | Weekly staff meeting | About an hour | Tactical topics the team agrees on | | Strategic session | About two hours | One big issue, in depth | | Quarterly review | Half a day | Step back, assess how the team is doing |

You may not need all four. A team of five might use a weekly meeting and a quarterly review only. The same article suggests well-run meetings should add up to no more than about 15% of staff time, which is a handy budget to check against your calendar.

Prepare in writing

  • Send the agenda in advance, phrased as questions rather than topics. For example, "Do we take the Henderson project?" rather than "Henderson." Wharton's piece notes that a question tells the room when it is finished: when it is answered.
  • State the desired outcome at the top: decide, discuss or inform.
  • Ask everyone to prepare. The article points out that if only some attendees prepare, the prepared ones become frustrated.
  • Share documents ahead of time, so the meeting is for discussion, not reading aloud.

Invite the right people

Invite only people who depend on each other for the task. Offer everyone else the notes. Make it fine to decline: a "no, send me the summary" is a sign of a healthy culture.

Step 3: Run the meeting well

A simple structure keeps meetings short.

  1. Open (1 minute): restate the purpose and the outcome you need.
  2. Work through the questions in order, with a rough time for each.
  3. Hear from everyone on important decisions. Ask quieter people first, or collect written input beforehand.
  4. Close (3 minutes): read back the decisions, then name owners and due dates for actions.
  5. Send notes within a day: decisions, actions, owners, dates. Keep them short.

Make hybrid meetings fairer

  • Everyone joins on their own device if some people are remote, so no one is a small face on a conference-room screen.
  • Use a shared document or chat for notes and questions.
  • Ask for remote voices first, since they are easiest to overlook.

Step 4: Fix the system, not just individual meetings

The BU researchers suggest auditing your meeting load, analyzing patterns together, setting concrete goals people can see benefiting them, and checking progress weekly at first, then monthly. They say vague aims like "fewer meetings" do not stick, while specific rules such as a meeting-free day do. They also report that at one company using the plan, employees reported a 42% rise in collaboration and satisfaction with work-life balance rose from 62% to over 90%. That is one company's result, not a guarantee.

A two-week meeting audit

  1. Each person lists every meeting for two weeks, with its length and whether it was useful.
  2. Total the hours and attendees.
  3. Cancel or shrink anything most people rated low value.
  4. Agree one new rule, such as no meetings on Wednesdays, or a 25-minute default length.
  5. Review after a month.

People often will not volunteer that their calendar is overwhelming, so collecting the data privately and sharing patterns avoids blame.

Common mistakes

  • Scheduling by habit. Recurring meetings outlive their purpose. Review each one quarterly.
  • No decision-maker. If nobody can say yes, the meeting will end with "let us follow up."
  • Agenda as topic list. Topics invite wandering, questions invite answers.
  • Meeting to feel in control. The SHRM piece notes managers sometimes call meetings for that reason.
  • Skipping the follow-up. A decision without an owner and date does not happen.
  • Ignoring the cost. Multiply attendees by hourly cost to see what an hour really costs.

Where WorkBOS fits

WorkBOS includes a shared calendar, team chat and tasks, so meeting actions can become tasks with owners and due dates instead of living in someone's notebook. Documents and agendas can sit in the drives, and surveys let you ask the team how meetings are going. See the features page, the docs and pricing; the Free plan covers up to 5 users. It will not make a pointless meeting purposeful, but it makes follow-through easier. For related reading, see building team accountability without micromanaging and managing a remote or hybrid small team.

Frequently asked questions

Q: How many meetings is too many? A: There is no fixed number, but one article suggests all meetings combined should take no more than about 15% of staff time. Count yours over two weeks and compare.

Q: Should every meeting have an agenda? A: Yes, if the meeting is necessary. A BU lecturer says agendas matter, though deciding whether to meet at all matters more. Write agenda items as questions.

Q: How long should a meeting be? A: Match length to purpose: 5 to 10 minutes for a daily check-in, about an hour for a weekly tactical meeting. Shorter calendar blocks also help by forcing focus.

Q: How do I stop people from multitasking in meetings? A: Keep meetings small, make them relevant to everyone present and ask for preparation. Multitasking is usually a symptom of people not needing to be there.

Q: Are meeting-free days worth trying? A: Many teams find them helpful, and the BU researchers cite a meeting-free day as an example of a concrete rule that works better than a vague goal. Try one day for a month and measure how people feel.

Sources are linked in the text above: Knowledge at Wharton, BU Research, SHRM.

Run it all from one place

Projects, clients, finance, people and AI employees in one system. Start free, no card needed.

Start free →