Fewer Meetings, Better Decisions: Rules for Meetings at Work

Why do many meetings lead to few decisions?

In small companies, meetings rarely come about through planning. A problem crops up, someone sends an invitation, and the meeting stays. After a year, every week has five recurring meetings, and most of them report what is already known. Questions that need a decision get postponed because time runs out or the right people are missing.

The obvious response is to cut meetings radically. That saves time but shifts coordination into hallway conversations and message threads nobody can keep track of. The guiding question of this article is therefore: Which meetings does a small company need, and how must they be built to produce better decisions?

To answer it, we first distinguish three purposes of meetings. Then we introduce a thinking model from group research, the hidden profile, that explains why groups decide worse than they could. After that come findings on the burden of meetings and three rules for clearing up your week.

A meeting is good when someone does something different afterward than before.

Informing, coordinating, deciding: what is a meeting for?

A meeting is an appointment in which several people work on a shared question at the same time. It is a company’s most expensive means of communication, because it ties up the time of all participants simultaneously. It is only worthwhile for purposes that truly require this simultaneity.

Most meetings mix all three purposes. Then informing eats up the time, and the decision comes at the end under time pressure or not at all. The article on the weekly sales meeting describes the exception rule for this: the meeting only discusses what needs a decision or help. Everything that is going to plan is in the overview and is not read aloud. The rule applies equally to every other meeting in the company.

The hidden profile: why groups decide worse than they could

The hope behind every decision meeting is that several heads know more than one. That is true, but only if the knowledge is actually voiced. This is exactly where a thinking model comes in that group research calls the hidden profile, going back to Stasser and Titus (1985).

It describes the following situation: part of the information is known to everyone, another part only to individual members. The shared information favors a weaker solution. Only when the scattered individual pieces are brought together does the better one emerge. An example from a small business: everyone knows the price and delivery time of two suppliers, and both favor supplier A. Only the employee in goods receiving knows about repeated quality defects at A, and only the service technician knows that B delivers spare parts overnight.

Lightle, Kagel, and Arkes (2009) studied this in experiments with clear financial incentives for the right choice. In the second experiment, based on what their members remembered, the groups could have uncovered a little over three quarters of the hidden profiles. In fact, they succeeded in 35 percent of cases. The authors found a sober reason: recall errors about shared information are corrected in discussion because others know it too. Recall errors about individual information cannot be corrected by anyone. This also explains why groups spend so much time on what everyone already knows.

Written tools help, but not by themselves. Dennis (1996) compared groups discussing verbally with groups using an electronic support system. The latter exchanged about half as much information again, enough to identify the best solution. Nevertheless, only one of these groups actually chose it. Exchanging information and incorporating it into your own assessment are two different steps. A small preliminary study by Xiao and Witherspoon (2015) points in the same direction: what participants had noted before the discussion came up in the discussion more often.

For a small company, two things follow. First, individual knowledge must be recorded before the discussion, or it gets lost in conversation. Second, the meeting needs a step in which this knowledge is explicitly tested against the preferred solution. The studies are laboratory experiments with students, but the situation is an everyday one in every company.

What do too many meetings cost? Two perspectives

One perspective says: meetings are coordination, and there can never be enough coordination. The other: meetings are a waste of time, the fewer the better. Research does not fully side with either, but it shows where the costs lie.

Standaert, Ulm, Castro, and a further author (2025) analyzed survey data from 1,137 employees. A higher meeting load was associated with more exhaustion, but not generally with more or less engagement. Kreamer and Rogelberg (2026), in two studies with 109 and 222 employees, presented fictitious daily schedules that differed in the number, length, and spread of meetings. Days with many, long meetings scattered across the day led respondents to expect a worse mood and lower productivity, especially when the actual work of the day was demanding.

On the other side are the findings of Leach, Rogelberg, Warr, and Burnfield (2009), presented in detail in the article on the sales meeting. In two studies with 958 and 292 employees, an agenda and good rooms were associated with more effective meetings, mediated by stronger participation. Larger meetings went along with lower participation. So meetings are not bad in themselves. What is bad is many, large, and poorly built ones.

I therefore consider not the number of meetings the most important lever, but their design and their place in the calendar. A single well-prepared decision meeting replaces three meetings in which the same question is touched on anew each time. The studies cited mostly measure respondents’ assessments rather than business results. Their direction is nonetheless clear enough for a rule.

How does a decision meeting work?

1. Phrase the question beforehand

   Whoever raises the item writes the decision down as a question and names two or three options. “Do we switch suppliers for small parts next quarter, yes or no?”

2. Collect a pre-meeting note from everyone

   By the day before, each participant writes three sentences on what they know about the question that the others may not know. No opinions, only facts and experience.

3. Read the notes first

   The meeting starts with five minutes of silent reading. That way, individual knowledge is on the table before anyone argues for their own solution.

4. Counter-check

   The person leading the meeting asks explicitly: which information from the notes speaks against the preferred solution?

5. Decide and record

   One person decides, or the group does so according to a rule agreed beforehand. The decision, rationale, owners, and review date are recorded.

The pre-meeting note is the antidote to the hidden profile. It forces individual knowledge out of people’s heads before the group settles on what is shared. The counter-check is the antidote to the finding by Dennis (1996): exchanged information only becomes effective when someone holds it up against the majority view.

If you are making a decision under uncertainty, you will find further help in the essay on deciding under uncertainty. And how to record the decision and rationale so that you can learn from it later is described in the article on the decision journal.

Worked example: how much time is in your meeting week?

A company with 22 employees has five recurring meetings. The owner calculates the person-hours, meaning duration times number of participants, and tests each meeting with the three-question rule. The figures are a worked example.

The 15 person-hours saved equal almost two working days every week. More important is what the remaining meetings gain. They are smaller, have a clear question, and take place on fixed days instead of chopping up the calendar. This matches the finding by Kreamer and Rogelberg (2026) that scattered meetings lower a day’s expected productivity.

Which rules keep a meeting culture in place over time?

A cleaned-up week fills up again if nobody pays attention. A few fixed rules are enough to prevent that.

• Every recurring meeting has an owner who tests it once a quarter with the three-question rule.
• New recurring meetings are only created if an existing one is dropped or shortened in return.
• Meetings start on time and end on time, even if someone is missing.
• Every meeting ends with agreements: what, who, by when.
• Information that is only being passed on goes to everyone in writing.

For weekly coordination in the team, the article on weekly team planning offers a proven agenda. For teams that do not work in the same place, additional agreements on availability and channels apply, described in the article on organizing distributed teams. And if it is regularly unclear in a meeting who actually decides, the RACI matrix helps.

Conclusion: which meetings a company needs

The opening question was
meetings a small company needs and how they must be built to decide better. The answer is: only meetings for coordination and decisions deserve the simultaneous time of several people. Informing belongs in writing. Decision meetings need a question phrased in advance, a pre-meeting note from every participant, and an explicit counter-check.

As shown, groups prefer to discuss what is known, and knowledge held by individuals gets lost in the process. Many scattered meetings also burden those involved. Neither speaks against meetings, but against unplanned ones. The consequence is simple: fewer meetings are not the goal but the result of every remaining meeting having a clear purpose.

What you can do this week

1. List all recurring meetings with duration, number of participants, and person-hours.
2. Test each with the three-question rule and cancel or replace pure information meetings.
3. Move the remaining meetings to as few fixed days as possible.
4. Introduce the pre-meeting note for the next important decision: three sentences from each participant by the day before.
5. End every meeting this week with agreements: what, who, by when.

After a month, a short review is worthwhile: which decisions were made, and which meeting did nobody miss?