A meeting effectiveness survey asks the people who were in a meeting whether it achieved what it was called for. Good questions cover eight things: purpose, preparation, participation, decisions, duration, attendees, follow-up and overall worth. Bad questions ask about satisfaction, and satisfaction is the one thing that does not predict whether the meeting was useful.
That distinction is not academic. In the classic HBR survey on the subject, 71 % of senior managers said meetings are unproductive and inefficient, most often because a meeting meant for a decision is used for status sharing instead. A satisfaction question cannot see that. A decision question can.
Below are the eight questions, what a low score on each actually means, and the three questions that are worse than asking nothing.
The eight questions, and what a low score means
Rate each on a five-point scale. The right-hand column is the part most question lists leave out: the same low score means a different problem depending on which question produced it, and the fix differs accordingly.
| Question | Measures | A low score means |
|---|---|---|
| I knew what this meeting was supposed to achieve before it started. | Purpose clarity | The invitation names a topic, not a goal. Cheapest fix on the list. |
| The meeting was prepared well enough that we could start straight away. | Preparation | The first fifteen minutes are spent rebuilding context. Send material ahead, not an agenda. |
| The people who had something relevant to say got to say it. | Airtime for the relevant knowledge | A facilitation problem, or a safety problem. Look at the spread: if it splits, it is safety. |
| We made the decisions this meeting was there to make. | Decision output | The most diagnostic item. Low three rounds running means a status update wearing a decision label. |
| The length of the meeting matched what we had to do. | Duration fit | Reads in both directions. Ending early and overrunning are different problems with the same score. |
| The right people were in the room, and no one was there without reason. | Attendee fit | The invite list has never been revisited since the first invitation. Usually the largest hidden cost. |
| I know what happens next and who is doing it. | Follow-up clarity | A documentation problem, not a meeting problem. The topic will come back next time. |
| This meeting was a good use of my time. | Overall judgement | Only meaningful against the other seven. High here plus low on decisions means it is pleasant and pointless. |
Send these eight after your next meeting
The meeting feedback survey template has all eight questions, answers anonymously in about two minutes, and returns an AI analysis naming the two dimensions that explain the score. Free.
Three questions that do more harm than good
Retrospective or survey: which one when
A live retrospective fits when
The team is small and already speaks openly
You want the discussion, not the number
The topic is the work, not the people
There is time to act on it in the same session
An anonymous survey fits when
The meeting has a clear hierarchy in the room
You suspect that not everyone is saying what they think
You need a trend across several rounds
The group is larger than about eight people
The two are not alternatives. The survey produces the numbers, the retrospective is where you talk about them. Sending the survey and never discussing the result is the most common way this ends in nothing.
Running it: five steps
Pick one recurring meeting, not all of them
Surveying every meeting produces survey fatigue and a flat line. Pick the one people complain about and measure that.
Send it within an hour
Memory of a meeting decays fast and turns into a general opinion about meetings. Same day is the outer limit.
Keep it anonymous, and say so
The participation and worth questions are exactly the ones people soften when their name is attached. Saying it out loud matters as much as the setting does.
Repeat twice more before changing anything
One round is a mood, three is a pattern. Changing the meeting after one round means you will never know whether it worked.
Read the result to the group in five minutes
Sharing it is the intervention. A result that only the organiser sees changes the organiser's opinion and nothing else.
Reading the result without fooling yourself
Read the spread before the average. A 3.5 built from fives and twos is a different meeting from a 3.5 built from threes and fours, and only the first one has a participation problem. That split usually means some people in the room are having a good meeting and others are attending one.
Then read pairs rather than single numbers. Decisions against follow-up tells you whether you decide well and forget quickly. Participation against overall worth tells you whether the people who stayed quiet also found it pointless. If participation is consistently low, the underlying question is not about meetings at all: it is whether people expect speaking up to be worth the risk, which is what psychological safety measures and what Google identified as the top factor in team effectiveness.
And watch the calendar, not only the scores. HBR's work on managers holding too many meetings makes the point that meeting load is a decision someone made, usually years ago, and never revisited. A team mood check or a running pulse survey will show the load effect before any individual meeting score does.
When the numbers are not enough
Eight ratings tell you that something is wrong and roughly where. They do not tell you how the group actually talks: who picks up whose idea, where a decision was made and then quietly reopened, which objection was raised once and never again.
That needs the words, not the scores. If a transcript of the meeting already exists, reading it against a framework is the next step, and it adds no new recording and no new consent question. We wrote up which tools produce those transcripts, where they store and process them, and the German and Austrian legal steps involved, in AI meeting notes and GDPR. For the reading itself, the C&C meeting analysis examines an uploaded transcript for atmosphere, decisions and feedback loops. Where the issue is the leadership circle rather than the meeting format, the manager effectiveness guide is the better next read.
The transcript exists. What is in it?
Upload a meeting transcript and read the meeting against the KI©K framework: atmosphere, climate radar, values, feedback loops. Free, and it records nothing.
The short version
• Ask about the job the meeting had, never about satisfaction. The friendliest recurring meeting is often the least useful one.
• Eight questions: purpose, preparation, participation, decisions, duration, attendees, follow-up, worth.
• A low score means something different per question. Decisions low for three rounds is a status update with a decision label.
• Drop how satisfied were you
, what could the facilitator do better
and a bare any other comments
.
• Read the spread before the average, and read pairs: decisions against follow-up, participation against worth.
• One round is a mood, three is a pattern. Share the result with the group or nothing changes.






![Psychological Safety in Teams: How to Measure What Google Found Matters Most [2026]](https://www.teamazing.com/wp-content/uploads/2026/04/psychological-safety-analysis.jpg)

![Remote & Hybrid Teams: The Data-Driven Guide to Leading Distributed Teams [2026]](https://www.teamazing.com/wp-content/uploads/2026/04/remote-work-analysis.jpg)