How to Run a Meeting That People Actually Want to Attend

Let me start with something honest. Most people don't want to be in most meetings.

I see it all the time. People join a call, switch their cameras off and quietly carry on with other work. Or they sit in a conference room nodding along while their mind is somewhere else. To be fair, I've done the same in meetings where I had no idea why I was there.

So whenever I run a meeting, I keep one goal in front of me. I want people to understand the message. If they walk out knowing what we discussed and what they need to do next, the meeting was worth it.

Over time I've learned that people don't switch off because they don't care. They switch off because the meeting didn't give them a reason to care. If I get their attention in the first few minutes, go straight to the main points and keep it simple, people stay with me. When I try to share everything I know in one go, I lose them.

I was reading Nehemiah recently and realised he's a very good example of this.

He prepared before he spoke

Nehemiah was working for the king of Persia when he heard that the walls of Jerusalem were broken down. He was heartbroken, but he didn't rush into action. He prayed about it for months (Nehemiah 1).

When he finally reached Jerusalem, he waited three days. Then he went out at night and checked the broken walls himself. He didn't tell anyone what he was planning yet (Nehemiah 2:11–16). Only after that did he gather the leaders.

Many of us do it the other way around. We send the meeting invite first and think about what to say later. Nehemiah had done his homework. He knew the problem well and he knew what he wanted from the people.

Now, before I set up a meeting, I ask myself one simple question: what is this meeting for? If I can't answer that in one line, I'm not ready.

He kept it short and clear

When Nehemiah spoke to the leaders, he didn't give a long speech. In a few lines he told them the problem, asked them to help rebuild the wall, and explained why it mattered. He also shared how God had helped him so far (Nehemiah 2:17–18).

The people responded straight away: "Let us start rebuilding."

That's what I want from my meetings too. I try to share the main point in the first couple of minutes: what the issue is, what I need from you and why it's important. The background can come later, if it's needed at all. Most of the time people don't need a big download. They need enough to understand and act.

Everyone knew their job

Nehemiah 3 is a long list of names, and it's easy to skip. But if you read it closely, you'll see that every family and group was given a specific part of the wall to repair. Many of them worked on the section right next to their own house. Nobody was confused about what they had to do.

I've been in so many meetings that end with "good discussion" and then nothing happens, because no one knows who's supposed to do what. So I've made it a habit to end every meeting by going over the next steps: who is doing what and by when. It takes a couple of minutes and saves a lot of follow-up later.

He kept people focused

As the work went on, problems came up. People mocked them, enemies threatened them, and some of the workers got discouraged (Nehemiah 4). Nehemiah listened to their fears and encouraged them. He also made practical changes, like having half the people work while the other half stood guard. But he kept everyone focused on finishing the wall, and it was completed in 52 days (Nehemiah 6:15).

Meetings go off track too. Someone brings up a different topic, or a discussion goes on too long. I don't want to shut people down, but I also don't want to waste everyone's time. So I'll usually say something like, "That's a good point, let's take it up separately," and bring the group back to the main topic.

He made sure people understood

Later in the book, when the people gathered to hear God's Law, the Levites read it and then explained it so everyone could understand (Nehemiah 8:8).

It's a small detail, but a very practical one. Just because I said something in a meeting doesn't mean people understood it. Before we close, I sometimes ask someone to quickly repeat the next steps. It's an easy way to catch confusion early.

Keep it simple

I don't get this right every time, but these are the things I try to do:

• Know the purpose of the meeting before sending the invite
• Start with the main point
• Share only what people need
• Bring the discussion back when it drifts
• End with clear next steps and owners

People will give you their attention when you respect their time. Nehemiah and the people of Jerusalem rebuilt a wall in less than two months because he prayed, planned well, spoke clearly and made sure everyone knew their part.

Your next meeting may not be that big. But the people in it are giving you their time, so make it worth it.