Why Meetings Feel Like A Trap

SPEAKER_00 0:00

Don't you just love meetings? Sitting through long-winded conversations of the same thing over and over, and leaving an hour or two later thinking, what a gigantic waste of my time. You live with no real decision made on pending or at-risk projects and no clear next step. Your team is so busy talking about work that the work itself feels behind, and it is behind, and things are still falling through the cracks. The good news is that this is a problem that can be solved. Hello and welcome back to the Systemized Business Podcast where we talk about simple systems, confident delegation, and predictable execution in your business. I am your host, BK. I'm a business manager and operations strategist, and I am on a mission to elevate small business systems. And today we are talking about what meetings your small team actually needs and which ones to cut out completely. Meetings are supposed to create clarity, accountability, and momentum. But in a lot of small businesses, meetings are doing just the opposite. They are interrupting work, they're blurring priorities, and they create the illusion of progress without actually moving anything forward. So by the end of this episode, you will know how to build a lean meeting rhythm for your team. You will assess what meeting types you actually need in your business and what every agenda needs. And also what to stop doing so meetings support execution instead of slow it down. Let's get started. And so

Small Teams Are Not Corporate

SPEAKER_00 2:10

we just adopted some of what we saw being done in those companies that we were in. But a small team in a small business with four, five, or even eight people doesn't need layers of recurring meetings just because that's what corporate teams do. Small teams need clarity, they need fast decisions, they need alignment. And of course, they need accountability. There are a lot of moving parts, and they need room to actually do the work, not just talk about it. So meetings are only useful if they help create those things. But what often happens is that meetings become this default response to uncertainty. If you feel, hmm, I need an update, you call a meeting. Or you need to talk through a problem, you call a meeting. Or you need to feel like things are under control, you call a meeting. And before long, you find that the calendar is full, but this business is still feeling reactive. On the other hand, I'll I've also seen teams that swing so far the other way, they avoid structured meetings completely because they want to stay agile and flexible and fast. And yes, okay, fine, that sounds good in theory, but in practice, that often means that nobody is fully aligned. Priorities are shifting, and important issues only come up when something has already gone wrong. So the answer isn't just to have more meetings or just to have no meetings, it's to have the right meetings with the right purpose at the right rhythm. And this is what we are aiming for.

Why Most Meetings Fail

SPEAKER_00 4:00

So before we talk about what meetings you actually need, we need to talk about why meetings so often fail. Because meetings are not automatically useful just because they happen. Most bad meetings fail for a few predictable reasons. The first is that there's no clear purpose. People show up, they talk, they update each other, maybe a few issues come up, and then the meeting ends. But nobody's quite sure what the point was or what was supposed to happen by the end. A second reason is that the wrong things are being discussed live in the meeting. Not everything needs to be discussed in real time. Simple updates, simple updates, status reports, and information sharing can often be handled asynchronously in a project management tool, in your business chat tool like Slack, through email. Even with a short Loom video, nothing or not everything needs to be uh said or discussed in a meeting. So if people are spending 30 minutes verbally repeating what could have been read in three minutes, that meeting is already too expensive. The third reasons meetings fail is that there are too many people in the room. When everybody gets invited just in case, the conversation gets slower, it gets less focused and more performative. The more people in a meeting, the more likely it is that clarity will get diluted. The fourth reason is that there's no agenda. And or or there is an agenda, but it's too vague. Having things like team update or team check-in or general discussion is not really an agenda item. These are just placeholders for drifting and going down unnecessarily unnecessary rabbit holes. And the fifth reason is that there's no decision, no action, no ownership. A lot of meetings will end with a nice conversation and absolutely no movement. Nobody knows who owns what, no deadlines are set, no follow-up is being captured, and the same issues are gonna resurface next week. And the final reason that meetings fail is because they have become a habit rather than a tool. And this is such an important point because meetings should exist to serve a purpose, not because there's all it has always been on the calendar. And this is why I think every meeting should justify itself, and a useful meeting should do one or more of these four things. It should help the team decide, it should help the team solve, it should help the team align, or it should help the team review progress and move forward. If it does none of these things, then you probably don't need it. So, okay, so now let's answer the main question. What

The Four Meetings Worth Keeping

SPEAKER_00 7:21

meetings do you need? Well, in most cases, a small business does not need a complicated meeting structure, it simply needs a lean operating rhythm. And I would say that there are four core meeting types to think about, and not everybody not every business will need all four right away, but these are the are the main ones. So the first one is the weekly team meeting, and this is really the backbone of your meeting rhythm. The purpose of this meeting is really simple. It's to align priorities, is to review the progress, review progress, troubleshoot any blockers that have surfaced, and clarify ownership and to make sure that everybody knows what matters this week. So it's not meant to be a long meeting, it's not meant to become this giant discussion forum, and it's definitely not meant to be a performative meeting where everyone reports everything they did kind of meeting. So a good weekly meeting, a good weekly team meeting is focused and it's practical, and it could include things like the top priorities for the week, the review uh on the progress of the key deliverables, any blockers or dependencies that are in the red right now, any decisions that need to be made this week. And it needs to really be clear on who owns what next. And that's it. And for some small teams, 30 to 45 minutes is really enough. If it's running longer than that, regularly over an hour, then you probably have one of the problems that we talked about earlier. The agenda is too broad, too many people are there, and you're probably trying to solve deep issues that should be handled separately. So the weekly team meeting is for visibility and execution, not for processing every issue in depth. The second meeting small teams may need is a monthly meeting or review meeting, and this one is more strategic. It's more strategic than the weekly meeting. The weekly meeting keeps work moving, the monthly meeting helps you step back and to ask bigger questions. For example, you ask yourself at the monthly meeting what is working? What keeps getting delayed? Where are we overcommitted? What projects are need attention next month? What bottlenecks are slowing us down? And what should we stop, simplify, or change? So this is where you lift your eyes from the week-to-week rush and assess whether the team is actually moving in the right direction. So a monthly meeting is helpful because execution problems often show patterns over time. And if you only ever look at one week at a time, you might miss the fact that a project, for example, is consistently under-resourced, or that one process is creating repeated confusion, or that the team is overloaded in one area and underused in another. So this meeting can be used to review all of that. It can also be used to review your goals, your capacity, your timelines, priorities for the month ahead. And for small teams, this can be this meeting can take 60 to 90 minutes. Again, the purpose is not to have a long abstract discussion, it's to make those practical adjustments that improve execution. The third type is a project-specific meeting, and this is one of those that is not always needed. It depends on what the business is actively working on. If you have a launch or a campaign or a client delivery project, a website build, a new offer, things like that. Any initiative involving multiple moving parts and multiple people, having a project meeting might make sense for you right now. But this is where I have to really stress something important. Project meetings should exist because the project needs coordination, not because every project deserves a standing meeting forever. The purpose of a project meeting is to coordinate work, is to manage dependencies, resolve bottlenecks, track milestones, keep the project moving, basically. It should be tied to real body to a real body of work. And once that work is complete, the meeting should disappear. And a lot of calendar clatter happens because teams create project meetings and then they never shut them down. So if you have project meetings, keep them tied to a specific purpose, specific team members, and a specific time frame. Just as projects don't go on forever, the meetings about them should not go on forever, right? The fourth meeting is a quarterly strategy meeting. And for every small business, then this may simply be a founder and operations review. This is not about the day-to-day. This is where you step back and you ask yourself, what is the business prioritizing right now? What has changed? What is putting pressure on the team? What systems are breaking down? What do we need to stop doing? What do we need to build before the next stage of growth? We have a weekly meeting about execution, the monthly meeting is about adjustment, making adjustments, and the quarterly meeting is about setting direction. And this is often where you make the biggest decisions about preventing or with regard to preventing future operational chaos. So some of the questions you might ask yourself during the quarterly strategy meeting is do we need clearer workflows? Where do we need to improve our handovers? Where are we overloading the team with too many priorities? Are roles clear? Are we using meetings to come compensate for missing systems? And that last question is so powerful because sometimes the real issue isn't the meeting. The real issue is that the business has not documented processes, it hasn't clarified ownership, and it hasn't built a reliable communication rhythm. So meetings are doing the job that systems should be doing. So a quarterly strategy session helps you catch those things.

Meetings To Cut Or Replace

SPEAKER_00 14:45

Alright, so we know now the types of meetings that we need. What meetings should we cut? Yeah, let's talk about the other side of this. What meetings should we eliminate? And here is my rule: if a meeting does not create clarity, decisions, movement, or accountability, then it should be questioned. And here are some common meetings that small teams should seriously consider cutting, reducing or replacing. Firstly, meetings that exist only for updates. If an update can be written or recorded or tracked somewhere, it's probably it probably doesn't need a live meeting. Second, meetings with no agenda. No agenda usually means no filter, and no filter means the meeting expands to fill the time available. Third, recurring meetings nobody can explain anymore. If you ask yourself, why do we still have this meeting and nobody has a strong answer? That is a signal for that meeting to be cut. Fourth type, meetings with too many attendees. If somebody does not need to decide, contribute, or own a follow-up, then they probably do not need to be there. Fifth, brainstorming meetings with no decision maker. And these are tricky because they often feel productive in the moment because there's a lot of talking, a lot of ideas being exchanged, a lot of notes being taken. But if nobody owns the next step or decides what happens after this the discussion, then that energy just goes nowhere, right? The sixth meetings that should have been a process. We talked a little bit about this before. Sometimes people are in meetings repeatedly because a workflow is unclear, a handover is messy, or responsibilities are fuzzy. And in those cases, the answer is not another meeting, the answer is to fix the system. So

The Agenda Framework That Works

SPEAKER_00 17:01

let's think about what should be in the agenda because this is where so many meetings really live or die. A good agenda is not just a list of talking points, it's a structure for decision making and for action. So, what are the must-have items on a meeting agenda? And here is a an eight-point framework that I use. Firstly, there needs to be a purpose. Why are we here? And this should be specific. It shouldn't be a weekly catch-up. It should be more like we are here to align priorities, review blockers, and confirm actions for this week. And this gives the meeting the shape. The next thing that needs to be in your agenda is the desired outcome. What should be true by the end of this meeting? For example, at the end of this meeting, everybody is clear on the week's priorities, blockers have been surfaced, decisions have been made on key issues, actions have owners and deadlines. And this matters because meetings will drift and go down rabbit holes if there's no defined endpoint. The third thing that needs to be in the agenda is priority discussion items only. Not everything needs live discussion. So only include items that require input, decision, coordinating, or problem solving. Simple updates should be moved out of the meeting if possible. Fourth thing that should be in the meeting metrics, progress, or status snapshot. What do we need to review before discussing next steps? This should be project status, campaign performance, deadlines that are at risk, outstanding tasks, client delivery updates. And we need to keep this part really tight because given enough ground, the discussion could this these items could swallow up the meeting. So we need to keep this really strict to high-level snapshots only. We also need to have on our agenda blockers and risks. What's slowing work down or what's creating fiction? This is one of the most important parts of a good agenda because blockers are where momentum really gets lost. Tied to that are decisions that need to be made. What decisions need to be decided today? And this part forces clarity. It stops meetings from becoming this vague, open-ended conversations. We need in our agenda action, owners, and deadlines. What is happening next, who owns it, and by when? And this is one of those non-negotiables of your agenda. A meeting that ends without clear next steps is unfinished. And then you have to come back, sit through this meeting again, and that is a gigantic waste of time. And you can in the your agenda just note down important things that come up but that don't belong to this meeting. So you could have a parking lot section in your agenda. And this is one of the easy this is one of the ways you can protect your agenda to stop it from drifting. Not every useful idea needs to be discussed right now. And so

Turn Talk Into Decisions And Owners

SPEAKER_00 21:07

if we go uh just one level deeper about how agendas actually drive action, because yes, the agenda is there to organize the meeting, it is also there to organize the execution. So just a few practical shifts can make this huge difference here. If you first start with outcomes, not just themes or topics. So instead of saying marketing, say decide launch date and confirm content owner. Instead of saying client updates, say review delivery risks and assign follow up. You see what I mean? So one invites the conversation, the other one invites movement. It it it's it's already pointing to the outcome. That you want. Right? Secondly, put decision items near the top. Don't wait until the end of the meeting to address the thing that actually matters most. Have those, make those decisions at the top of the meeting and then work your way down. Third, capture actions live. Don't assume somebody will remember. Don't leave it vague. Write it down during the meeting. Yeah, this could probably be the responsibility of the person taking minutes or whatever, but it's important to in your capacity to know what the action items that are decided in the meeting are. So write those down during the meeting. And then fourth, assign one owner per action. Don't just write, oh, we will do XYZ or the team will handle it. No, one owner. Put one person's name down. And this doesn't mean that one person does all the work. It just means that one person owns, making sure it happens. And then fifth, put deadlines in there. Not soon or next week, maybe. Put a real deadline, a real date that everybody knows and can work towards. And review previous actions at the meeting. And so this is what turns meetings then into accountability loops instead of just isolated conversations. A good meeting agenda creates that continuity. It links one meeting to the next and keeps moving it in between. So if you are listening and you're wondering, what does this look like in practice? So here's an example of a lean meeting rhythm for a small team. You might have one weekly team meeting for 30 minutes, a monthly planning or review meeting for 60 minutes, project meetings only when needed for active work that's going on. And a quarterly strategy session for deeper strategy reset. And usually that might be 90 minutes to a two-hour thing, depending on what is going on in your business and the goals that you are reviewing and setting. And this is enough really for a small, for many small businesses. The point is we don't want to fill our calendar. We want to create just enough rhythm to support visibility, decision making, and follow-through. And I want to emphasize this too, because not every team needs every meeting. A meeting with three people, a team with three people with simple workflows does not need the same rhythm as a 10-person team handling multiple offers and launches and client projects. So start start lean, start simple. And only with what serves a real purpose. And review your meetings regularly because the rhythm that served your business six months ago might not be the rhythm you need right now. And that might not also be the rhythm you need six months from now. So keep reviewing your meetings. The key thing is to respect the purpose of the meeting. Don't try to solve everything in one meeting. A weekly meeting is not the place to have very deep operational issue discussions. It's not the time to have every, you know, very deep brainstorming or process redesign or you know emotional check-in. That's not the time to do that.

Audit Your Calendar And Close

SPEAKER_00 26:07

So I encourage you to take time this week to audit your meetings. They should earn their place on your calendar. So here's the big takeaway from this episode. Your team does not need more meetings, it just needs the right meetings. Meetings should support execution, not replace it. They should be creating clarity, decisions, accountability, and momentum. So a lean meeting rhythm usually works better than a crowded calendar. And the agenda, a strong agenda, should do more than organize conversations. It should drive the action. So this week I want to challenge you to look at every recurring meeting on your calendar and ask yourself, why does this meeting exist? What purpose does it serve? What would break if we removed it? Could this be handled asynchronously? And does this meeting end with action, ownership, and deadlines? Those questions alone could save your team a lot of wasted time. And more importantly, they could help you build a rhythm that could actually support the way your business runs. All right. Thank you so much for listening to this episode of the systemized business. If this episode helped you, it might help somebody else in your world. Share it with a founder, a team member, a business owner, friend who is tired of wasting time in meetings that go nowhere. Talk to you again real soon. Bye for now.