[Eps 72] Are You Using Meetings To Hide Broken Systems?

WEBVTT
00:00:00.320 --> 00:00:02.000
Don't you just love meetings?
00:00:02.319 --> 00:00:13.359
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.
00:00:13.839 --> 00:00:21.039
You live with no real decision made on pending or at-risk projects and no clear next step.
00:00:21.359 --> 00:00:33.200
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.
00:00:33.759 --> 00:00:38.399
The good news is that this is a problem that can be solved.
00:00:38.880 --> 00:00:49.759
Hello and welcome back to the Systemized Business Podcast where we talk about simple systems, confident delegation, and predictable execution in your business.
00:00:50.000 --> 00:00:51.520
I am your host, BK.
00:00:51.679 --> 00:00:58.320
I'm a business manager and operations strategist, and I am on a mission to elevate small business systems.
00:00:58.560 --> 00:01:08.000
And today we are talking about what meetings your small team actually needs and which ones to cut out completely.
00:01:08.640 --> 00:01:14.159
Meetings are supposed to create clarity, accountability, and momentum.
00:01:14.480 --> 00:01:19.120
But in a lot of small businesses, meetings are doing just the opposite.
00:01:19.280 --> 00:01:28.959
They are interrupting work, they're blurring priorities, and they create the illusion of progress without actually moving anything forward.
00:01:29.359 --> 00:01:36.000
So by the end of this episode, you will know how to build a lean meeting rhythm for your team.
00:01:36.319 --> 00:01:45.680
You will assess what meeting types you actually need in your business and what every agenda needs.
00:01:46.000 --> 00:01:52.640
And also what to stop doing so meetings support execution instead of slow it down.
00:01:53.200 --> 00:01:54.799
Let's get started.
00:02:09.599 --> 00:02:15.919
And so we just adopted some of what we saw being done in those companies that we were in.
00:02:16.400 --> 00:02:27.759
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.
00:02:28.080 --> 00:02:33.439
Small teams need clarity, they need fast decisions, they need alignment.
00:02:34.000 --> 00:02:36.240
And of course, they need accountability.
00:02:36.400 --> 00:02:43.680
There are a lot of moving parts, and they need room to actually do the work, not just talk about it.
00:02:43.840 --> 00:02:48.639
So meetings are only useful if they help create those things.
00:02:48.879 --> 00:02:55.360
But what often happens is that meetings become this default response to uncertainty.
00:02:55.599 --> 00:02:59.439
If you feel, hmm, I need an update, you call a meeting.
00:02:59.680 --> 00:03:03.599
Or you need to talk through a problem, you call a meeting.
00:03:03.919 --> 00:03:08.560
Or you need to feel like things are under control, you call a meeting.
00:03:08.879 --> 00:03:17.280
And before long, you find that the calendar is full, but this business is still feeling reactive.
00:03:17.919 --> 00:03:30.800
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.
00:03:30.960 --> 00:03:39.520
And yes, okay, fine, that sounds good in theory, but in practice, that often means that nobody is fully aligned.
00:03:39.919 --> 00:03:46.879
Priorities are shifting, and important issues only come up when something has already gone wrong.
00:03:47.120 --> 00:03:57.360
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.
00:03:57.439 --> 00:04:00.159
And this is what we are aiming for.
00:04:00.479 --> 00:04:08.719
So before we talk about what meetings you actually need, we need to talk about why meetings so often fail.
00:04:09.520 --> 00:04:14.639
Because meetings are not automatically useful just because they happen.
00:04:15.039 --> 00:04:20.240
Most bad meetings fail for a few predictable reasons.
00:04:20.399 --> 00:04:23.360
The first is that there's no clear purpose.
00:04:23.680 --> 00:04:30.639
People show up, they talk, they update each other, maybe a few issues come up, and then the meeting ends.
00:04:30.800 --> 00:04:36.800
But nobody's quite sure what the point was or what was supposed to happen by the end.
00:04:37.439 --> 00:04:43.120
A second reason is that the wrong things are being discussed live in the meeting.
00:04:43.279 --> 00:04:46.160
Not everything needs to be discussed in real time.
00:04:47.040 --> 00:05:03.519
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.
00:05:04.879 --> 00:05:13.120
Even with a short Loom video, nothing or not everything needs to be uh said or discussed in a meeting.
00:05:13.199 --> 00:05:22.720
So if people are spending 30 minutes verbally repeating what could have been read in three minutes, that meeting is already too expensive.
00:05:23.439 --> 00:05:29.040
The third reasons meetings fail is that there are too many people in the room.
00:05:29.279 --> 00:05:37.920
When everybody gets invited just in case, the conversation gets slower, it gets less focused and more performative.
00:05:38.240 --> 00:05:43.680
The more people in a meeting, the more likely it is that clarity will get diluted.
00:05:44.079 --> 00:05:47.120
The fourth reason is that there's no agenda.
00:05:47.920 --> 00:05:53.199
And or or there is an agenda, but it's too vague.
00:05:53.439 --> 00:06:00.959
Having things like team update or team check-in or general discussion is not really an agenda item.
00:06:01.120 --> 00:06:08.079
These are just placeholders for drifting and going down unnecessarily unnecessary rabbit holes.
00:06:08.720 --> 00:06:14.160
And the fifth reason is that there's no decision, no action, no ownership.
00:06:14.480 --> 00:06:20.800
A lot of meetings will end with a nice conversation and absolutely no movement.
00:06:21.120 --> 00:06:32.639
Nobody knows who owns what, no deadlines are set, no follow-up is being captured, and the same issues are gonna resurface next week.
00:06:32.879 --> 00:06:38.959
And the final reason that meetings fail is because they have become a habit rather than a tool.
00:06:39.120 --> 00:06:50.639
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.
00:06:50.879 --> 00:07:00.639
And this is why I think every meeting should justify itself, and a useful meeting should do one or more of these four things.
00:07:00.800 --> 00:07:10.959
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.
00:07:11.199 --> 00:07:15.680
If it does none of these things, then you probably don't need it.
00:07:17.439 --> 00:07:20.720
So, okay, so now let's answer the main question.
00:07:20.959 --> 00:07:23.120
What meetings do you need?
00:07:23.839 --> 00:07:33.439
Well, in most cases, a small business does not need a complicated meeting structure, it simply needs a lean operating rhythm.
00:07:33.680 --> 00:07:45.680
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.
00:07:46.079 --> 00:07:55.759
So the first one is the weekly team meeting, and this is really the backbone of your meeting rhythm.
00:07:56.000 --> 00:07:58.319
The purpose of this meeting is really simple.
00:07:58.399 --> 00:08:12.319
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.
00:08:12.560 --> 00:08:26.720
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.
00:08:27.040 --> 00:08:53.279
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.
00:08:53.600 --> 00:08:59.840
And it needs to really be clear on who owns what next.
00:09:00.480 --> 00:09:01.279
And that's it.
00:09:01.360 --> 00:09:05.600
And for some small teams, 30 to 45 minutes is really enough.
00:09:05.919 --> 00:09:13.120
If it's running longer than that, regularly over an hour, then you probably have one of the problems that we talked about earlier.
00:09:13.360 --> 00:09:22.159
The agenda is too broad, too many people are there, and you're probably trying to solve deep issues that should be handled separately.
00:09:22.480 --> 00:09:30.080
So the weekly team meeting is for visibility and execution, not for processing every issue in depth.
00:09:30.639 --> 00:09:39.279
The second meeting small teams may need is a monthly meeting or review meeting, and this one is more strategic.
00:09:39.600 --> 00:09:42.080
It's more strategic than the weekly meeting.
00:09:42.320 --> 00:09:49.919
The weekly meeting keeps work moving, the monthly meeting helps you step back and to ask bigger questions.
00:09:50.159 --> 00:09:54.159
For example, you ask yourself at the monthly meeting what is working?
00:09:54.399 --> 00:09:56.240
What keeps getting delayed?
00:09:56.559 --> 00:09:58.799
Where are we overcommitted?
00:09:59.039 --> 00:10:02.960
What projects are need attention next month?
00:10:03.200 --> 00:10:05.759
What bottlenecks are slowing us down?
00:10:05.840 --> 00:10:09.679
And what should we stop, simplify, or change?
00:10:10.559 --> 00:10:18.960
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.
00:10:19.200 --> 00:10:25.039
So a monthly meeting is helpful because execution problems often show patterns over time.
00:10:25.200 --> 00:10:46.080
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.
00:10:46.320 --> 00:10:50.960
So this meeting can be used to review all of that.
00:10:51.200 --> 00:11:01.120
It can also be used to review your goals, your capacity, your timelines, priorities for the month ahead.
00:11:01.360 --> 00:11:07.440
And for small teams, this can be this meeting can take 60 to 90 minutes.
00:11:07.600 --> 00:11:18.399
Again, the purpose is not to have a long abstract discussion, it's to make those practical adjustments that improve execution.
00:11:19.679 --> 00:11:27.440
The third type is a project-specific meeting, and this is one of those that is not always needed.
00:11:27.600 --> 00:11:31.759
It depends on what the business is actively working on.
00:11:32.080 --> 00:11:40.879
If you have a launch or a campaign or a client delivery project, a website build, a new offer, things like that.
00:11:41.120 --> 00:11:50.559
Any initiative involving multiple moving parts and multiple people, having a project meeting might make sense for you right now.
00:11:50.960 --> 00:11:54.720
But this is where I have to really stress something important.
00:11:55.759 --> 00:12:06.080
Project meetings should exist because the project needs coordination, not because every project deserves a standing meeting forever.
00:12:06.399 --> 00:12:18.159
The purpose of a project meeting is to coordinate work, is to manage dependencies, resolve bottlenecks, track milestones, keep the project moving, basically.
00:12:18.399 --> 00:12:23.600
It should be tied to real body to a real body of work.
00:12:23.919 --> 00:12:28.320
And once that work is complete, the meeting should disappear.
00:12:28.639 --> 00:12:37.360
And a lot of calendar clatter happens because teams create project meetings and then they never shut them down.
00:12:37.840 --> 00:12:49.039
So if you have project meetings, keep them tied to a specific purpose, specific team members, and a specific time frame.
00:12:49.200 --> 00:12:54.639
Just as projects don't go on forever, the meetings about them should not go on forever, right?
00:12:56.240 --> 00:13:00.480
The fourth meeting is a quarterly strategy meeting.
00:13:00.720 --> 00:13:07.279
And for every small business, then this may simply be a founder and operations review.
00:13:07.600 --> 00:13:10.480
This is not about the day-to-day.
00:13:10.720 --> 00:13:17.600
This is where you step back and you ask yourself, what is the business prioritizing right now?
00:13:17.840 --> 00:13:19.200
What has changed?
00:13:19.519 --> 00:13:22.480
What is putting pressure on the team?
00:13:23.679 --> 00:13:25.600
What systems are breaking down?
00:13:25.840 --> 00:13:27.519
What do we need to stop doing?
00:13:27.679 --> 00:13:31.600
What do we need to build before the next stage of growth?
00:13:31.840 --> 00:13:42.399
We have a weekly meeting about execution, the monthly meeting is about adjustment, making adjustments, and the quarterly meeting is about setting direction.
00:13:43.279 --> 00:13:51.759
And this is often where you make the biggest decisions about preventing or with regard to preventing future operational chaos.
00:13:52.000 --> 00:14:02.799
So some of the questions you might ask yourself during the quarterly strategy meeting is do we need clearer workflows?
00:14:03.120 --> 00:14:06.879
Where do we need to improve our handovers?
00:14:07.200 --> 00:14:10.480
Where are we overloading the team with too many priorities?
00:14:10.639 --> 00:14:11.919
Are roles clear?
00:14:12.159 --> 00:14:16.159
Are we using meetings to come compensate for missing systems?
00:14:16.720 --> 00:14:22.960
And that last question is so powerful because sometimes the real issue isn't the meeting.
00:14:23.440 --> 00:14:34.480
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.
00:14:34.720 --> 00:14:38.559
So meetings are doing the job that systems should be doing.
00:14:38.799 --> 00:14:44.159
So a quarterly strategy session helps you catch those things.
00:14:45.279 --> 00:14:49.840
Alright, so we know now the types of meetings that we need.
00:14:50.320 --> 00:14:52.799
What meetings should we cut?
00:14:53.039 --> 00:14:55.360
Yeah, let's talk about the other side of this.
00:14:55.519 --> 00:14:58.639
What meetings should we eliminate?
00:14:58.879 --> 00:15:08.320
And here is my rule: if a meeting does not create clarity, decisions, movement, or accountability, then it should be questioned.
00:15:08.480 --> 00:15:16.559
And here are some common meetings that small teams should seriously consider cutting, reducing or replacing.
00:15:16.879 --> 00:15:20.639
Firstly, meetings that exist only for updates.
00:15:20.879 --> 00:15:29.440
If an update can be written or recorded or tracked somewhere, it's probably it probably doesn't need a live meeting.
00:15:30.000 --> 00:15:32.720
Second, meetings with no agenda.
00:15:33.120 --> 00:15:40.639
No agenda usually means no filter, and no filter means the meeting expands to fill the time available.
00:15:41.120 --> 00:15:45.519
Third, recurring meetings nobody can explain anymore.
00:15:45.759 --> 00:15:51.120
If you ask yourself, why do we still have this meeting and nobody has a strong answer?
00:15:51.360 --> 00:15:54.799
That is a signal for that meeting to be cut.
00:15:55.120 --> 00:15:59.360
Fourth type, meetings with too many attendees.
00:15:59.679 --> 00:16:08.879
If somebody does not need to decide, contribute, or own a follow-up, then they probably do not need to be there.
00:16:10.000 --> 00:16:14.399
Fifth, brainstorming meetings with no decision maker.
00:16:14.639 --> 00:16:24.000
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.
00:16:24.240 --> 00:16:34.720
But if nobody owns the next step or decides what happens after this the discussion, then that energy just goes nowhere, right?
00:16:35.679 --> 00:16:39.519
The sixth meetings that should have been a process.
00:16:39.759 --> 00:16:41.600
We talked a little bit about this before.
00:16:41.759 --> 00:16:51.679
Sometimes people are in meetings repeatedly because a workflow is unclear, a handover is messy, or responsibilities are fuzzy.
00:16:51.919 --> 00:16:59.120
And in those cases, the answer is not another meeting, the answer is to fix the system.
00:17:00.799 --> 00:17:13.920
So let's think about what should be in the agenda because this is where so many meetings really live or die.
00:17:14.799 --> 00:17:23.839
A good agenda is not just a list of talking points, it's a structure for decision making and for action.
00:17:24.400 --> 00:17:28.720
So, what are the must-have items on a meeting agenda?
00:17:29.200 --> 00:17:34.319
And here is a an eight-point framework that I use.
00:17:35.759 --> 00:17:38.000
Firstly, there needs to be a purpose.
00:17:38.160 --> 00:17:39.200
Why are we here?
00:17:39.440 --> 00:17:40.960
And this should be specific.
00:17:41.119 --> 00:17:44.240
It shouldn't be a weekly catch-up.
00:17:44.960 --> 00:17:53.759
It should be more like we are here to align priorities, review blockers, and confirm actions for this week.
00:17:54.000 --> 00:17:56.880
And this gives the meeting the shape.
00:17:57.279 --> 00:18:01.759
The next thing that needs to be in your agenda is the desired outcome.
00:18:02.000 --> 00:18:04.799
What should be true by the end of this meeting?
00:18:04.960 --> 00:18:19.200
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.
00:18:19.519 --> 00:18:27.279
And this matters because meetings will drift and go down rabbit holes if there's no defined endpoint.
00:18:27.599 --> 00:18:34.640
The third thing that needs to be in the agenda is priority discussion items only.
00:18:35.440 --> 00:18:38.960
Not everything needs live discussion.
00:18:40.799 --> 00:18:47.519
So only include items that require input, decision, coordinating, or problem solving.
00:18:47.839 --> 00:18:52.480
Simple updates should be moved out of the meeting if possible.
00:18:53.359 --> 00:18:59.200
Fourth thing that should be in the meeting metrics, progress, or status snapshot.
00:18:59.440 --> 00:19:03.279
What do we need to review before discussing next steps?
00:19:03.440 --> 00:19:12.400
This should be project status, campaign performance, deadlines that are at risk, outstanding tasks, client delivery updates.
00:19:12.640 --> 00:19:24.799
And we need to keep this part really tight because given enough ground, the discussion could this these items could swallow up the meeting.
00:19:25.039 --> 00:19:31.599
So we need to keep this really strict to high-level snapshots only.
00:19:33.359 --> 00:19:37.359
We also need to have on our agenda blockers and risks.
00:19:37.599 --> 00:19:41.119
What's slowing work down or what's creating fiction?
00:19:41.359 --> 00:19:48.640
This is one of the most important parts of a good agenda because blockers are where momentum really gets lost.
00:19:50.240 --> 00:19:54.000
Tied to that are decisions that need to be made.
00:19:54.240 --> 00:19:57.359
What decisions need to be decided today?
00:19:58.240 --> 00:20:02.079
And this part forces clarity.
00:20:02.240 --> 00:20:07.119
It stops meetings from becoming this vague, open-ended conversations.
00:20:08.240 --> 00:20:12.880
We need in our agenda action, owners, and deadlines.
00:20:13.839 --> 00:20:17.599
What is happening next, who owns it, and by when?
00:20:18.000 --> 00:20:21.759
And this is one of those non-negotiables of your agenda.
00:20:22.000 --> 00:20:27.759
A meeting that ends without clear next steps is unfinished.
00:20:28.079 --> 00:20:38.000
And then you have to come back, sit through this meeting again, and that is a gigantic waste of time.
00:20:38.880 --> 00:20:49.680
And you can in the your agenda just note down important things that come up but that don't belong to this meeting.
00:20:49.839 --> 00:20:53.680
So you could have a parking lot section in your agenda.
00:20:53.839 --> 00:21:00.240
And this is one of the easy this is one of the ways you can protect your agenda to stop it from drifting.
00:21:00.400 --> 00:21:04.880
Not every useful idea needs to be discussed right now.
00:21:06.559 --> 00:21:21.039
And so 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.
00:21:21.279 --> 00:21:27.519
So just a few practical shifts can make this huge difference here.
00:21:28.079 --> 00:21:33.839
If you first start with outcomes, not just themes or topics.
00:21:34.079 --> 00:21:42.160
So instead of saying marketing, say decide launch date and confirm content owner.
00:21:42.400 --> 00:21:48.400
Instead of saying client updates, say review delivery risks and assign follow up.
00:21:48.640 --> 00:21:49.599
You see what I mean?
00:21:49.759 --> 00:21:54.880
So one invites the conversation, the other one invites movement.
00:21:55.680 --> 00:21:59.759
It it it's it's already pointing to the outcome.
00:22:00.240 --> 00:22:01.119
That you want.
00:22:01.519 --> 00:22:02.160
Right?
00:22:02.559 --> 00:22:06.240
Secondly, put decision items near the top.
00:22:06.480 --> 00:22:11.680
Don't wait until the end of the meeting to address the thing that actually matters most.
00:22:12.720 --> 00:22:18.079
Have those, make those decisions at the top of the meeting and then work your way down.
00:22:18.799 --> 00:22:21.519
Third, capture actions live.
00:22:21.680 --> 00:22:23.920
Don't assume somebody will remember.
00:22:24.079 --> 00:22:26.640
Don't leave it vague.
00:22:26.880 --> 00:22:28.720
Write it down during the meeting.
00:22:28.880 --> 00:22:46.160
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.
00:22:46.480 --> 00:22:49.200
So write those down during the meeting.
00:22:49.440 --> 00:22:53.200
And then fourth, assign one owner per action.
00:22:54.319 --> 00:23:01.200
Don't just write, oh, we will do XYZ or the team will handle it.
00:23:01.839 --> 00:23:03.920
No, one owner.
00:23:04.160 --> 00:23:06.319
Put one person's name down.
00:23:06.400 --> 00:23:09.039
And this doesn't mean that one person does all the work.
00:23:09.200 --> 00:23:14.480
It just means that one person owns, making sure it happens.
00:23:14.720 --> 00:23:17.839
And then fifth, put deadlines in there.
00:23:18.079 --> 00:23:20.640
Not soon or next week, maybe.
00:23:20.880 --> 00:23:28.079
Put a real deadline, a real date that everybody knows and can work towards.
00:23:28.480 --> 00:23:33.279
And review previous actions at the meeting.
00:23:33.519 --> 00:23:40.880
And so this is what turns meetings then into accountability loops instead of just isolated conversations.
00:23:41.440 --> 00:23:45.440
A good meeting agenda creates that continuity.
00:23:45.680 --> 00:23:51.200
It links one meeting to the next and keeps moving it in between.
00:23:53.279 --> 00:23:58.400
So if you are listening and you're wondering, what does this look like in practice?
00:23:58.640 --> 00:24:03.920
So here's an example of a lean meeting rhythm for a small team.
00:24:04.240 --> 00:24:19.039
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.
00:24:19.359 --> 00:24:24.000
And a quarterly strategy session for deeper strategy reset.
00:24:24.079 --> 00:24:35.200
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.
00:24:35.440 --> 00:24:40.720
And this is enough really for a small, for many small businesses.
00:24:40.960 --> 00:24:44.000
The point is we don't want to fill our calendar.
00:24:44.240 --> 00:24:51.279
We want to create just enough rhythm to support visibility, decision making, and follow-through.
00:24:51.599 --> 00:24:56.640
And I want to emphasize this too, because not every team needs every meeting.
00:24:56.880 --> 00:25:12.640
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.
00:25:12.880 --> 00:25:16.640
So start start lean, start simple.
00:25:17.039 --> 00:25:20.880
And only with what serves a real purpose.
00:25:21.279 --> 00:25:31.200
And review your meetings regularly because the rhythm that served your business six months ago might not be the rhythm you need right now.
00:25:31.440 --> 00:25:35.839
And that might not also be the rhythm you need six months from now.
00:25:36.319 --> 00:25:38.720
So keep reviewing your meetings.
00:25:38.960 --> 00:25:42.480
The key thing is to respect the purpose of the meeting.
00:25:42.640 --> 00:25:45.279
Don't try to solve everything in one meeting.
00:25:45.440 --> 00:25:52.480
A weekly meeting is not the place to have very deep operational issue discussions.
00:25:52.720 --> 00:26:04.559
It's not the time to have every, you know, very deep brainstorming or process redesign or you know emotional check-in.
00:26:04.880 --> 00:26:06.880
That's not the time to do that.
00:26:07.359 --> 00:26:12.400
So I encourage you to take time this week to audit your meetings.
00:26:12.640 --> 00:26:16.640
They should earn their place on your calendar.
00:26:17.039 --> 00:26:20.319
So here's the big takeaway from this episode.
00:26:20.640 --> 00:26:26.160
Your team does not need more meetings, it just needs the right meetings.
00:26:26.400 --> 00:26:30.400
Meetings should support execution, not replace it.
00:26:30.559 --> 00:26:36.480
They should be creating clarity, decisions, accountability, and momentum.
00:26:36.799 --> 00:26:43.599
So a lean meeting rhythm usually works better than a crowded calendar.
00:26:44.240 --> 00:26:50.079
And the agenda, a strong agenda, should do more than organize conversations.
00:26:50.240 --> 00:26:52.480
It should drive the action.
00:26:52.960 --> 00:27:01.680
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?
00:27:02.079 --> 00:27:04.319
What purpose does it serve?
00:27:04.559 --> 00:27:07.119
What would break if we removed it?
00:27:07.440 --> 00:27:10.319
Could this be handled asynchronously?
00:27:10.720 --> 00:27:15.920
And does this meeting end with action, ownership, and deadlines?
00:27:16.480 --> 00:27:20.880
Those questions alone could save your team a lot of wasted time.
00:27:21.279 --> 00:27:27.920
And more importantly, they could help you build a rhythm that could actually support the way your business runs.
00:27:28.640 --> 00:27:29.200
All right.
00:27:29.359 --> 00:27:33.279
Thank you so much for listening to this episode of the systemized business.
00:27:33.519 --> 00:27:38.240
If this episode helped you, it might help somebody else in your world.
00:27:38.480 --> 00:27:47.200
Share it with a founder, a team member, a business owner, friend who is tired of wasting time in meetings that go nowhere.
00:27:47.440 --> 00:27:49.519
Talk to you again real soon.
00:27:49.759 --> 00:27:50.960
Bye for now.