You Are the Worst Judge of Your Own Staff Meeting

Leaders consistently rate the staff meetings they run higher than the people attending them do, and the cause is structural rather than personal. The more you talk in a meeting, the better you think the meeting was, and the leader talks the most. That makes your own read the least reliable measure in the room. In most organizations it is also the only measure anyone collects. Before you change anything about your staff meeting, go get a number you did not produce yourself.

You are the least reliable person in the room to judge your own staff meeting.

Not because you aren't paying attention. Because of where you sit. You set the agenda, so the agenda gets met. You talk whenever you want, so you never sit through a stretch that has nothing to do with you. You called the meeting, so you were already invested in it going well before it started.

Steven Rogelberg has studied meetings for thirty years. Across multiple studies, he found that leaders consistently rate the meetings they run more favorably than the people attending them. Same room. Same hour. Two different experiences, and only one of them gets written down.

Yours.

The meeting blind spot is the distance between how the person running a meeting experiences it and how everyone else in the room does.

Why the Person Running the Meeting Always Has the Best Seat

None of this is about ego.

The finding underneath it is about talk time. The more you talk in a meeting, the better you think the meeting was.

So think about who talks the most in your staff meeting. You open it. You transition between sections. You ask the follow-up questions. You decide when something has been discussed enough.

Everyone else talks for a few minutes and listens for fifty.

Add the other two advantages you have. Your agenda gets covered, because you wrote it. And you scheduled the meeting in the first place, which means you had a reason to want it to go well.

So you walk out thinking something like, that ran eight minutes long, but we got through everything. Your children's director walks out thinking about the forty minutes of updates that had nothing to do with her.

Both of you are describing the same hour honestly.

Here's where that leaves you. If you think the meeting is basically fine, then the problem must be the people who seem checked out. So you don't change the meeting. You get quietly frustrated with your team instead.

I've watched good leaders sit in that loop for years.

Your read isn't worthless. You're the only person holding every thread that meeting is tying together, and that perspective is real. It's just partial. And you're the one deciding whether anything changes.

What Your Team Pays for That Hour

When I was pastoring, I ran the staff meeting and I would have told you it was fine.

It really wasn't. Most of it was a report, with everyone waiting their turn to say what they were working on. I'd been in ministry two decades by then and had sat through and led more meetings than I could count. Some were great. Most were not, and mine were in the second group.

I never did the math on what that hour was costing us. If I had, I'd have changed it years earlier.

Ten people, ninety minutes, fifty-two weeks. That's 780 hours a year, which is most of a full-time position, spent in one room.

But time is the smaller cost.

A 2010 study in Human Resource Management surveyed nearly a thousand working adults across two samples. How satisfied people were with their meetings predicted how satisfied they were with their jobs overall. That held after controlling for pay, advancement, coworkers, their supervisor, and the work itself.

The researchers checked whether meeting satisfaction was just standing in for one of those. It wasn't.

So your team carries that meeting into how they feel about the job itself. That's separate from how they feel about you.

And nobody in that room is going to tell you. The person running the meeting usually signs off on the reviews. That makes honest feedback a small act of career risk. Your team has done that math too.

The Signals You Can Read Before Anyone Says Anything

You don't have to wait for a survey to get information. Six things happen in a room when a meeting isn't working. Every one of them is a reflection on whoever is running it. Watch for them next week:

1. Phones out and laptops open. Not one person catching an urgent message. A pattern, in the same stretch of the meeting, week after week. Note which stretch. That part isn't earning the room.
2. Side conversations. Two people are holding a second meeting inside your meeting because it's more useful than the first one. Find out what they're talking about.
3. One or two people carrying the discussion while everyone else waits it out. Usually the agenda isn't relevant to all of them, or nobody feels safe enough to disagree with the person running the room.
4. You doing most of the talking. Easiest to check, hardest to accept. Have someone time it for one meeting and tell you the split.
5. The same item on three straight agendas. You're counting the discussion as progress. Everyone else stopped expecting a decision weeks ago.
6. Nobody asks a question when you finish. Silence at the end reads like agreement and usually isn't. It more often means the room decided the conversation wasn't worth having.

There's one thing most leaders treat as evidence that isn't.

Every author who writes about meetings will tell you to have an agenda, so leaders who have one assume they've cleared the bar. Writing an agenda means somebody typed something before the meeting started. It doesn't mean anyone decided anything in the room.

I'd still argue for a standing agenda in any organization. But you only get something out of it if you put the right things on it. And if you end with decisions that have names attached. Those signals map closely onto the five reasons meetings go unproductive.

But You Already Know What They'd Say

Most leaders I talk to have a reason not to ask. They're all reasonable, and I've used two of them myself.

"My team is six people and we're close. They'd tell me." They probably would tell you about the budget, the building, or a bad hire. The staff meeting is different. It's the one topic where the person with the complaint has the least to gain and the most to lose. Nobody's career ever improved by critiquing the boss's meeting.

"Asking just invites complaining." That's a real risk if you ask a vague question. "Any feedback for me?" gets you either silence or a list of grievances about everything. A narrow question about one specific hour gets you narrow, specific answers. And the complaining you hear is cheaper than the complaining you don't.

"I've asked before and got nothing." Almost always because it was asked out loud, in the meeting, by the person running it, with everyone watching. That isn't a question. It's a test, and your team passed it by saying the meeting was fine.

None of those three people are wrong to be cautious. They're just describing a hard version of the question rather than an easier one.

Go Get a Number You Didn't Produce

Ask your team three questions in writing, and ask for written answers back:

1. What's going well in our staff meeting?
2. What isn't going well?
3. What could I do differently?

Three questions, asked once, will tell you more than another year of assuming.

Four things make the difference between useful answers and polite ones.

• Ask in writing. Asking out loud in the meeting gets you agreement, not information.
• Make it anonymous if you can. If your team is small enough that anonymity is a fiction, say so, and ask anyway.
• Add the sharpest question. What is the one thing we do in staff meeting that you would cancel?
• Read the answers without defending anything. Not out loud, not in your head. This is the whole exercise, and it's the part most leaders skip.

Some of what comes back will sting. You've been grading your own work with every advantage a grader could have, and the grade came back fine every time.

Then Change One Thing

Read for the answer that shows up most, not the one that stings most. In my experience the answers cluster in four places: too much reporting, no decisions, the wrong people in the room, or the wrong length. Pick whichever one your team named most and change only that.

I want to be honest about how I finally fixed mine, because it matters for the argument.

I didn't figure it out from inside my own meeting. Years into running a bad one, I sat in a coaching room with a group of entrepreneurs and business leaders. One of them walked through the meeting system his company had been running for years. It was new to me and it made immediate sense. We went home and put our own version in place. We got better at it, and it became part of how we worked. A couple of years later I could point to that one change as one of the biggest reasons we grew.

The fix didn't come from trying harder inside the room. It came from information I didn't have.

That's the whole point of asking. You've been the only source of data on this hour, and you're a compromised one. Three questions and one honest read will tell you more than another year of running the meeting on instinct.

The hour is already on your calendar either way.

Common Questions About Meeting Feedback

How Do I Ask for Feedback Without Sounding Defensive?

Ask in writing, ask about the meeting rather than about you, and say what you'll do with the answers. "I'm looking at how we spend our Tuesday hour and I want three honest answers before I change anything" gives your team a job instead of a loyalty test.

What If Only Two People Respond?

Two honest answers beat zero. Read them, change one thing, and tell the room which answer drove the change. People answer the second survey when they see the first one mattered.

How Often Should I Ask?

Twice a year is plenty for the full three questions. In between, a one-question rating at the end of each meeting keeps a running signal without turning feedback into another agenda item.

Should I Ask If I'm Not Willing to Change the Meeting?

No. Asking and doing nothing costs you more credibility than never asking. Wait until you're ready to change one thing.

Free Live Training: Why Staff Meetings Stink (And How to Fix Yours)

Three questions will tell you which part of your staff meeting to fix. They won't tell you what to put in its place.

Wednesday, September 9 at 2:00 PM Eastern. Forty minutes, plus time for your questions at the end. Here's what we work through:

• The five reasons staff meetings go bad, and how to tell which one is yours
• STAFF, a five-part framework for spending the same hour differently
• A standing agenda you can run without rebuilding it every week
• IDS, a three-step method for taking one problem to a real decision in the room, with a name and a date on it

Everyone who attends gets the templates too: the STAFF cheat sheet and the standing agenda, ready to use in your next meeting. You won't need a new tool, a new budget, or anyone's permission to run any of it. And if you register and something comes up that day, I'll send you the recording and the templates anyway.

Reserve your seat for the September 9 training →

This particular training is built for church leaders, so the examples and the demo are church-shaped. If you lead a team somewhere else, the STAFF framework works the same way and you're welcome in the room. If you'd rather see the software side first, watch the demo.