The Four Types of Meetings (And Why You Can't Mix Them)

Meetings do one of four jobs: communication, brainstorming, problem solving, or relationship building. Each one produces something different, needs different people, and fails in a different way. Trying to do all four in one weekly meeting is the most common reason team meetings go off the rails. Communication can move to writing or video. Brainstorming needs a small room of the right people. Problem solving is the best use of a leadership team's time together and deserves the bulk of the meeting. Relationship building is too important to squeeze into ten minutes at the end.

Your weekly team meeting is trying to do four jobs at the same time.

It's supposed to get everyone on the same page. It's supposed to surface ideas. It's supposed to solve problems. And it's supposed to keep the team feeling like a team. Those are four different meetings that need four different rooms, and you've been asked to run all of them in the same ninety minutes on Tuesday.

No wonder it feels like a lot.

I don't gamble, but if I had to bet on one thing about your staff meeting, I'd bet it's trying to do too much. I've led staff meetings since I was eighteen, as a youth pastor, a church planter, and a lead pastor, and I've sat in plenty more. For years I would have told you mine were fine. Most of it was a report, with everyone waiting their turn. The parts I cared about most, the problems we needed to solve and the team I wanted to build, got whatever was left at the end. I wasn't running a bad meeting. I was asking one meeting to do too much.

If that sounds familiar, I'd like to make a case for doing less.

The four jobs a meeting can do. Each one wants different people, a different format, and a different length.

A meeting type is the single job a meeting exists to do, and it decides who should be in the room, how long it runs, and what counts as done.

Why Does One Meeting Struggle With Four Jobs?

Patrick Lencioni names this in Death by Meeting. He calls it meeting stew: announcements, tactical updates, strategic questions, and administrative details in one pot until nothing tastes like anything. Put four jobs in one room and you get a bad buffet. There's a lot on the table and none of it is what anyone came for.

Ninety minutes, four jobs. Half of it is people reading updates out loud. The thing the team came for gets what's left, and the thing that holds the team together gets nine minutes at the end.

Here's what makes the four hard to combine. Each one produces something different. Communication produces shared knowledge. Brainstorming produces ideas. Problem solving produces a decision. Relationship produces trust. And each one wants opposite conditions to get there. Very few people can switch between all four in one sitting, and the people you want in the room for one type are often the wrong people for the next.

There's one more thing. The commitment required rises as you move down that list. Communication asks almost nothing of anyone. Problem solving asks someone to name what's broken and own the fix. So when four jobs share a room, the meeting drifts toward the top of the list, where it's comfortable, and the work that would change something gets skipped. In a survey we ran of more than three hundred church leaders, thirty-nine percent said they never discuss their goals in any meeting. Not rarely. Never. They had the goals. The meeting just never got there.

Steven Rogelberg, who has studied meetings for decades, puts roughly half of meeting time in the not-well-spent category. That's not a verdict on you. You inherited a format and you've been carrying it well. You're allowed to put some of it down.

If you want the shorter diagnostic version of this, I've written about the five reasons meetings go unproductive.

Communication: Do You Need to Meet at All?

A communication meeting exists so everyone knows the same things. Announcements, what's coming up, the calendar, what each department did this week. The information flows one direction, from whoever has it to everyone who doesn't.

Here's how it usually goes. We've got stuff to say, so we get everybody together and say it, because that's the most efficient thing for the person talking. It's not the most efficient thing for the room. Somebody says "let's go around the table," and the first person gives their update. You're mildly interested. The second person goes, and you're less interested. By the third person, phones are out, because most of the room already knew what happened. It's efficient for the presenter and disengaging for the participants, and everyone leaves mildly annoyed. Not annoyed enough to say anything. Just annoyed enough to sit through it again next week because it's on the calendar.

You know the phrase. This could have been an email. When I asked a room of pastors to finish that sentence, they went further: could have been a video, could have been a Slack message, could have been a nap.

So the question to ask is simple: do you need to meet at all?

Usually not, and that's good news. Record a Loom on Monday morning. Write it in Slack. Send one email that covers everything the go-around would have covered. Everybody can read the calendar, as long as somebody maintains it and everyone is expected to read it. People read it when they have a minute, questions come back in writing, and your meeting gets to start where the interesting part is. We built the weekly check-in in Alignify around exactly this: each person takes sixty seconds before the meeting to update their goals and what they worked on, it lands in the agenda, and nobody has to say it twice.

I know why the go-around survives, and it isn't about information. Saying it in the room means you know they heard it. Going around the table makes everyone's week visible. And for a lot of teams, this is the only hour when everyone is in one place. Those are real needs. Written updates handle the first two better than a room does, and I'd gently push back on the worry that people won't read what you send. We expect college students to read a syllabus. We can expect the same of the adults on our staff. The third need, being together, deserves its own answer, and it's coming in a minute.

Brainstorming: Do You Have the Right People?

A brainstorming meeting exists to produce ideas. We need an idea for a sermon series, an outreach event, a way to get more people into groups. You're not communicating information and you're not building the full solution. You're thinking out loud with a whiteboard, and it's one of the most valuable things a team can do together.

Here's how it usually goes when it's stapled onto the staff meeting. Everyone is in the room, because everyone is always in the room. Someone floats a big idea for spring. Before the second idea gets out, someone else has asked what it's going to cost. That throws water on the fire. The person asking isn't being difficult. They're doing their job in the wrong meeting.

I've written before about WOW people and HOW people. The WOW people say "we could do this, we could do that." They bring optimism and ideas, and they're exactly who you want in a brainstorm. The HOW people hear an idea as a task before it's finished being an idea. You need them. You need them later. A brainstorm needs more WOW people than accountants, and it needs the accountants afterward, with the shortlist, where their questions make everything better.

It cuts the other way too. Put a room full of WOW people on a problem-solving meeting and they'll propose a family life center while the practical people are trying to figure out how to pay the electric bill. Neither group is wrong. They're built for different meetings, and the problem solvers get frustrated with the brainstormers when they're forced into the same one.

So the question is: do you have the right people? And the answer is usually a smaller room. Take brainstorming out of the weekly meeting. Book thirty minutes with the three or four people who generate, tell them the goal, and let the ideas run without pricing them. Then hand the best two or three to the people who know what things cost. You'll get better ideas and a more honest budget, in that order.

Problem Solving: Is Everyone Prepared to Decide?

A problem-solving meeting exists to fix something. We've got an issue, a challenge, an opportunity, and we're not just coming up with ideas about it. We're deciding what to do. It ends with a decision, a name, and a date.

If your leadership team only did one thing in a room together, this is the one I'd keep. I'd give it almost half the meeting. It's the best use of the hour, and it's the one that gets starved when the meeting is full of everything else.

Here's how it usually goes. Nothing gets decided, so everything comes back. The same item shows up on three consecutive agendas. We talk about it each week, the conversation feels productive, and next week we spend the first five minutes going "okay, where did we land?" and pick the cycle back up. We are talking things to death and never solving them. That's disheartening for the people in the room who came hoping to see something move. It's not a lazy team. It's a team that never got the time to finish, and often a team that's a little too nice. Naming what's broken and owning the fix costs something. Kind cultures tend to disagree in the hallway instead of the room, so the problem stays on the list and the list gets longer.

Two things help, and both happen before the meeting starts. Keep a written issues list that anyone on the team can add to, in one place, that carries forward week to week. When your youth pastor notices at ten o'clock at night that the website is slow, they need somewhere to put that. A problem that's written down stops being whispered about. And rank the list before you work it. Ask which one would matter most if it were solved in ninety days, and start there. You don't have to solve all of them. You have to solve one.

This is my favorite part of a staff meeting now, and it's the part we spent the most time building in Alignify. Anyone in the church can add an issue and it lands in an inbox. You drag the one you want to work over to active, and it shows up on the staff meeting agenda automatically. When you work it, the decision and the action item are captured with a name and a date, and the issue closes. Next week starts on the next one, and nobody has to hold the list in their head.

In the room, I use IDS, from Gino Wickman's Traction: identify, discuss, solve. The identify step matters more than it looks. Sometimes the issue isn't what's being said. "Our website is slow" might really be "nobody is responsible for the website," because if somebody were, they'd know it was slow. Ask why three or four times and you'll usually find it. Then discuss it once, and solve it. Solved doesn't always mean finished. It might mean you handed it to someone, they'll build a plan, and they'll bring it back for a yes. But it's decided, and it comes off the list. If the time runs out and it isn't solved, it's on the agenda next week. You stay on it until it's fixed. I've written about borrowing that from EOS without adopting the whole system.

Imagine what your staff meeting would be if you only solved one thing a week. That's fifty things a year. Right now you're probably talking about four hundred things a year and solving very few of them. Fifty solved problems is a different organization twelve months from now, and it comes from doing less in the room, not more.

Relationship: Have You Given It Its Own Time?

A relationship meeting exists to build trust, culture, and a team. It's the biggest catch-all bucket of the four, and we reach for words like culture and doing life together. Prayer, devotion, celebration, the story from someone's weekend, the conversation that has nothing to do with the agenda. This is the one type where efficiency advice is wrong. You cannot Loom a prayer meeting.

Here's where you might push back, and I'd want to hear it. "This sounds like a business. We're not a business. Part of why we meet is so people who work in different corners remember they're on the same team." You're right on both counts. Parts of this should sound like a business. And the being-together part is the best reason the go-around survives. It's also exactly why the relational part deserves better than the last ten minutes of a task meeting.

Because here's how it usually goes. The devotion is supposed to take five minutes and takes fifteen, and now you're behind from the start. Or kudos and prayer and "let's each share a win" sit at the end of the agenda, which makes them the first thing a long meeting eats. When the issues run over, the human part gets skipped. When it does happen, it's hurried, and everyone can feel that it's the item before the exit. Nobody planned it either way. It's just what an overloaded hour does to the thing you care about most.

Please hear what I'm not saying. I'm not saying cut prayer, cut leadership development, cut celebrating wins, or cut the reason to be in a room at all. The most pastoral thing you can do with all the hours you're asking of your team is to not waste them. So you may need to double down on culture. You're just not going to force it into the staff meeting.

So give it its own time and no agenda. Instead of ten minutes of team building, have everybody over to your house for dinner. Cook something. Sit at a table with nothing to decide. Go to Topgolf. Have an actual prayer meeting where you're not trying to do anything else. That's not staff meeting. That's team building, and it deserves to be its own thing. One evening like that will do more for trust than a year of icebreakers, and it frees your weekly meeting from a job it was never going to do well. Put it on the calendar on purpose, and don't apologize for it.

Draw Your Own Pie Chart

Before you change anything, get an honest picture of what you have.

Take a blank page and draw a circle. Think back to your last team meeting and divide the circle by where the time actually went. How much of it was people reading updates out loud? How much was somebody floating an idea that got priced before it got heard? How much went to a problem the team actually decided? And how much was left for the part where people felt like a team?

Don't draw the meeting you wish you'd run. Draw the one you ran.

For most leaders, the biggest slice is communication and the smallest is relationship, and the problem the team came to solve sits somewhere in the middle, half finished. That's not a failure. That's what happens when four jobs share one plate. You've been feeding everyone from the same dish and wondering why nobody's full.

Now draw the meeting you want. Communication gone to a Monday email. Brainstorming pulled out into its own half hour with the right people. Relationship moved to your dinner table. What's left is a whole circle with one job in it, and it's the job that changes your organization.

Frequently Asked Questions

What Are the Four Types of Meetings?

Communication, brainstorming, problem solving, and relationship building. Communication transfers information. Brainstorming generates options. Problem solving produces decisions with an owner and a date. Relationship building strengthens trust between people. Each needs different people, a different format, and a different length.

Can a Meeting Ever Do More Than One Job?

Briefly, and only if one job is clearly primary. A five-minute win at the top of a problem-solving meeting is fine. A thirty-minute go-around inside the same meeting is not, because it changes what the meeting is and crowds out the job you kept it for.

Which Type Should a Small Team Protect First?

Problem solving. It's the one that needs everyone in the room at the same time, and it's the one that quietly loses its hour to everything else. Move communication to writing first, because that's where the time comes from.

How Do I Move Communication Out of the Meeting?

Pick one place and one deadline. A written check-in each person completes before the meeting, or a Monday morning recap from you. It only works if it's reliable, so people stop saving updates for the room.

Change One Thing This Week

You don't get there by working harder in the meeting. You get there by asking the meeting to do less.

Your team gives you that hour every week whether it's good or not. Ten people and ninety minutes is 780 hours a year. Give those hours back to the one thing that needs everyone in the room, and give the other three the homes they deserve. Your team will feel the difference the first week. You'll feel it the first Tuesday you don't dread.

If you'd like company while you make the change, the Staff Meeting Challenge walks a team through one change a week, and the homework happens inside the meeting you already have. Prefer to watch first? The on-demand staff meeting training covers the same ground in one sitting.