How to Know If Your Meetings Are Actually Working
I spent years in rooms where nobody could answer that question.
Not because the teams were bad. I have worked with genuinely capable people across very different industries. Engineers, sales teams, research groups, ops functions. Talented people who cared about their work. And in almost every organisation, the same pattern appeared: meetings happened constantly, people left those meetings with a vague sense of whether they were useful, and nobody had a reliable way to tell the difference between a meeting that moved something forward and one that just consumed time.
That gap bothered me enough that I started building a framework to close it. What I am about to describe is what I learned, and it is the thinking that eventually became the measurement layer inside Minuteory.
The Feeling Is Not Enough
Most leaders know when something is wrong with their meetings. They feel it. The energy in the room is off, conversations circle without landing, the same topics resurface in the next meeting because nothing was resolved. The diagnosis is visceral and usually accurate.
The problem is that feelings do not produce change. When you tell a team their meetings are unproductive, the conversation almost immediately becomes subjective. People disagree about which meetings are the problem. They attribute the issue to specific individuals rather than to structure. Nobody has data to work from, so the discussion stays in the realm of opinion and the underlying pattern does not change.
I learned this the hard way. The first time I tried to fix a meeting culture problem, I had a lot of conviction and no numbers. The conversations were real but the diagnosis was contested at every turn. The second time, I came with measurement. That was a different conversation entirely.
What You Are Actually Measuring
When I started building the measurement framework, the first question was what a meeting is actually trying to produce. Strip away the formats and the agenda templates and the facilitation techniques, and a meeting has one job: to move something forward that cannot move forward any other way.
From that starting point, I landed on six dimensions that together determine whether a meeting is actually doing its job.
The first is Purpose Clarity. Did the meeting need to happen at all? Was there a clear agenda before it started, and did every person in the room understand what the meeting was trying to achieve? This sounds elementary and it is violated in the majority of meetings I have observed across very different organisations.
The second is Participant Engagement. Were the right people in the room? Were all voices being heard, or was one person carrying the conversation while everyone else waited for it to end? Was the discussion structured, or did it drift? The STATE principle applies here: meetings that produce good decisions tend to have structured, purposeful exchanges rather than open-ended discussion that mistakes activity for progress.
The third is Outcome Orientation. A meeting that ends without a decision has produced conversation, not output. The question is whether the decisions made were clear, whether the action items that came out of them were SMART (specific, measurable, assigned, realistic, time-bound), and whether the WWWF principle was applied: Who does What by When, and for what purpose. Most meetings fail on this dimension not because no one was trying but because the structure for capturing outcomes was not there.
The fourth is Personal Performance. For each participant, this asks how well they fulfilled their RACI role during the meeting. The person who is Responsible for a project should be driving the relevant discussion. The person who is Accountable should be making or confirming decisions. When those roles are not being played, the meeting structure is carrying people who are either in the wrong room or unclear on what they are supposed to be contributing.
The fifth is Meeting Analytics. This is where the data becomes visual: which topics consumed the most time, whether that time allocation matched the stated agenda, and how each participant showed up, their communication style, contribution patterns, and engagement signals across the session.
The sixth is the Overall Assessment. A numerical effectiveness score out of ten, with an explanatory narrative and a specific set of improvement steps for the next meeting based on what the data actually showed. Not generic advice. Steps drawn from the specific gaps that appeared in this meeting.
Why None of This Gets Measured
The honest reason is that measuring meetings manually is not worth the effort. To track these six dimensions across every meeting your team runs, you would need someone taking structured notes against a rubric during every call, and then someone else following up on task completion before the next meeting. For one meeting per week, that is a significant overhead. For a team running ten or twenty meetings per week, it is not remotely feasible.
So most organisations do not measure at all. They feel their way through, make occasional process changes based on subjective feedback, and the underlying pattern stays roughly the same.
The other reason is that most people do not know what they are looking for. The six dimensions above are not obvious. They came from years of observation and iteration across organisations with very different meeting cultures. Knowing what to measure is itself a body of knowledge that most leaders have not had reason to develop.
What Changes When You Have the Data
The shift that happens when you start measuring these dimensions is not subtle.
The first thing you see is patterns across meetings that look nothing like each other on the surface. A weekly leadership sync and a client delivery review might both show consistently low decision quality scores. That tells you something about how decisions are being made in the organisation that no individual meeting would reveal on its own.
The second thing you see is individual patterns. Who consistently generates clear tasks versus vague ones. Who dominates certain formats and goes quiet in others. Which facilitators run meetings that produce high follow-through and which ones produce lists of commitments that evaporate. This is not about blame. It is about knowing where to focus development attention.
The third thing you see is trend lines. Are your meetings getting better or worse over time? That question is unanswerable without longitudinal data. With it, you can see whether a process change you made three months ago is actually having an effect.
That last one matters most to me. The whole point of building a measurement framework is to know whether what you are doing is working. Without trend data, you are guessing. With it, you are managing.
How I Operationalised This in Minuteory
The six dimensions above are the conceptual framework. Turning them into something a team can actually use required building measurement into the meeting process itself rather than treating it as a separate administrative task.
Minuteory processes each meeting and produces an effectiveness score across these dimensions automatically. The score is not a judgment. It is a mirror. It shows you what actually happened in the meeting based on what was said, who said it, what was decided, and what was committed to.
Over time, the scores build into trend reports at the meeting group level. You can see whether your product reviews are consistently stronger than your client calls, or whether a specific team's meetings have been declining in quality over the past six weeks. That is the organisational intelligence that a feeling can never give you.
The score matters less than what you do with it. The teams I have seen get the most from this are the ones that treat the score as a conversation starter rather than a performance metric. Why did this meeting score low on decision quality? What would have needed to be different? That conversation, grounded in actual data, produces change that a general "let us have better meetings" discussion never does.
What to Do Before Your Next Meeting
If you have never measured your meetings against a structured framework, the fastest diagnostic is to do it manually for one week.
After each meeting, give it a score from one to five on each of the six dimensions. Clarity of purpose, decision quality, task generation, participation balance, information quality, follow-through rate. Do this honestly and without discussing it with anyone else first.
At the end of the week, look at the pattern. You will almost certainly see something you did not expect. A meeting type you thought was high quality will score low on follow-through. A short sync you thought was a waste of time will score well on decision quality.
That exercise takes about five minutes per meeting. It will tell you more about where your meeting culture actually stands than six months of instinct.
If you want the measurement to happen automatically across every meeting your team runs, that is what Minuteory is built for. Start at app.minuteory.com and run the first score against a real meeting this week.