WEBVTT - 50 not 60

0:00:03.440 --> 0:00:07.560
<v Speaker 1>Welcome to Before Breakfast, a production of I Heart Radio.

0:00:09.080 --> 0:00:15.160
<v Speaker 1>Good Morning. This is Laura. Welcome to the Before Breakfast podcast.

0:00:16.480 --> 0:00:21.760
<v Speaker 1>Today's tip is to schedule meetings for fifty minutes, not sixty.

0:00:23.320 --> 0:00:26.560
<v Speaker 1>That way, people can get where they're going and more

0:00:26.600 --> 0:00:31.800
<v Speaker 1>meetings can start on time. As I have studied corporate

0:00:31.800 --> 0:00:34.720
<v Speaker 1>schedules over the years, I have been fascinated to see

0:00:34.720 --> 0:00:39.239
<v Speaker 1>how most organizations, or at least most individual people, have

0:00:39.520 --> 0:00:44.280
<v Speaker 1>some sort of default length for their meetings. Some places

0:00:44.320 --> 0:00:48.160
<v Speaker 1>set the default at thirty minutes, but sixty minutes tends

0:00:48.200 --> 0:00:51.559
<v Speaker 1>to be the most common. Because people wind up in

0:00:51.600 --> 0:00:55.280
<v Speaker 1>a lot of meetings, many of these meetings get scheduled

0:00:55.280 --> 0:01:00.240
<v Speaker 1>back to back. This is a problem because if you

0:01:00.280 --> 0:01:03.080
<v Speaker 1>are in a meeting that runs from nine to ten

0:01:03.920 --> 0:01:07.840
<v Speaker 1>and another one that runs from ten to eleven, you

0:01:07.880 --> 0:01:11.920
<v Speaker 1>are expected to be in two different meetings at precisely

0:01:12.000 --> 0:01:15.920
<v Speaker 1>ten am. If the meetings are in different places, this

0:01:16.000 --> 0:01:20.160
<v Speaker 1>is a physical impossibility. But even if both meetings are

0:01:20.160 --> 0:01:23.520
<v Speaker 1>by video conference, and even if the first ends precisely

0:01:23.680 --> 0:01:26.760
<v Speaker 1>on time, you will still be a minute late to

0:01:26.880 --> 0:01:30.160
<v Speaker 1>the second because it takes a non zero amount of

0:01:30.200 --> 0:01:33.880
<v Speaker 1>time to log in. You also won't have time to

0:01:34.280 --> 0:01:37.119
<v Speaker 1>use the restroom or make any notes about follow ups

0:01:37.120 --> 0:01:40.720
<v Speaker 1>from the first meeting, which means those two dous may

0:01:40.880 --> 0:01:43.920
<v Speaker 1>fade to the back of your mind until they urgently

0:01:44.319 --> 0:01:48.480
<v Speaker 1>boil back up. And of course, many meetings do not

0:01:49.120 --> 0:01:52.920
<v Speaker 1>end on time. That makes people even later for all

0:01:52.960 --> 0:01:57.280
<v Speaker 1>subsequent meetings, so all meetings after the first starting a

0:01:57.440 --> 0:02:01.400
<v Speaker 1>discombobulated way, as you just side whether to wait for

0:02:01.440 --> 0:02:08.560
<v Speaker 1>the latecomers or shift the agenda accordingly. Fortunately, this is

0:02:08.600 --> 0:02:13.840
<v Speaker 1>a comparatively easy problem to solve. Indeed, it is a

0:02:13.880 --> 0:02:18.480
<v Speaker 1>problem that most high schools have solved. You need to

0:02:18.560 --> 0:02:23.400
<v Speaker 1>create a passing period between scheduled events so people can

0:02:23.440 --> 0:02:28.040
<v Speaker 1>get from one commitment to another. If you are in

0:02:28.040 --> 0:02:32.000
<v Speaker 1>a leadership role at your organization, one obvious way to

0:02:32.120 --> 0:02:35.000
<v Speaker 1>do this is to set the norm of having meetings

0:02:35.240 --> 0:02:38.760
<v Speaker 1>start on the hour and end at ten minutes until

0:02:38.840 --> 0:02:42.919
<v Speaker 1>the hour. That is, they are all fifty minutes long

0:02:43.280 --> 0:02:47.640
<v Speaker 1>instead of sixty minutes long. That way, even participants with

0:02:47.840 --> 0:02:51.640
<v Speaker 1>back to back meetings aren't inevitably late for all of

0:02:51.680 --> 0:02:55.480
<v Speaker 1>their meetings of the day except the first. You can

0:02:55.560 --> 0:02:58.760
<v Speaker 1>even encourage staff to adjust their outlook settings to shorten

0:02:58.800 --> 0:03:01.880
<v Speaker 1>the duration of all events so that meetings default to

0:03:02.000 --> 0:03:06.160
<v Speaker 1>a specific amount of time before the hour. A few

0:03:06.240 --> 0:03:09.880
<v Speaker 1>organizations choose a corollary to this idea, that is, all

0:03:09.960 --> 0:03:13.880
<v Speaker 1>meetings start ten minutes after the hour and end on

0:03:14.000 --> 0:03:17.840
<v Speaker 1>the hour. That can also work, but it is slightly

0:03:17.919 --> 0:03:23.079
<v Speaker 1>less intuitive to explain to people outside the organization. So

0:03:23.560 --> 0:03:29.240
<v Speaker 1>I like on the hour and ending ten minutes till now.

0:03:29.280 --> 0:03:33.919
<v Speaker 1>It is true that fifty minutes is less than sixty minutes,

0:03:34.960 --> 0:03:38.560
<v Speaker 1>and if you were accustomed to filling every single one

0:03:38.680 --> 0:03:42.480
<v Speaker 1>of those sixty minutes efficiently in all of your meetings,

0:03:43.240 --> 0:03:47.200
<v Speaker 1>then you may have to rethink things. But in my experience,

0:03:47.880 --> 0:03:51.720
<v Speaker 1>there are very few corporate meetings that were scheduled for

0:03:51.760 --> 0:03:56.960
<v Speaker 1>sixty minutes but that could not take fifty Indeed, since

0:03:57.000 --> 0:04:00.600
<v Speaker 1>many meetings start late because of latecomers from previous as meetings,

0:04:01.320 --> 0:04:05.440
<v Speaker 1>the material may often be taken closer to fifty minutes. Anyway,

0:04:05.560 --> 0:04:08.920
<v Speaker 1>as people get antsy once the clock strikes the hour

0:04:09.640 --> 0:04:11.560
<v Speaker 1>and they know they need to go to the next thing.

0:04:12.880 --> 0:04:17.080
<v Speaker 1>Best to acknowledge this now. If you are not in

0:04:17.120 --> 0:04:19.799
<v Speaker 1>a leadership role, this might be a bit harder to establish,

0:04:20.560 --> 0:04:22.720
<v Speaker 1>but you can certainly make it happen for any meetings

0:04:22.720 --> 0:04:25.960
<v Speaker 1>that are under your control. If you know people are

0:04:26.000 --> 0:04:29.360
<v Speaker 1>going to be late, plan on starting at five minutes

0:04:29.440 --> 0:04:35.279
<v Speaker 1>after the hour and then end ten minutes before. Yep,

0:04:35.400 --> 0:04:38.679
<v Speaker 1>that means turning your sixty minute meetings into forty five

0:04:38.760 --> 0:04:43.880
<v Speaker 1>minute ones. But hey, you listen to this podcast. You

0:04:44.080 --> 0:04:48.279
<v Speaker 1>thrive on doing things effectively. I am betting that you

0:04:48.279 --> 0:04:52.120
<v Speaker 1>could figure it out. Of course, in the grand scheme

0:04:52.120 --> 0:04:57.880
<v Speaker 1>of things, it would be better to just have fewer meetings. Ideally,

0:04:58.480 --> 0:05:02.159
<v Speaker 1>when a meeting happens, it is because something needs to

0:05:02.400 --> 0:05:06.480
<v Speaker 1>change in the world that can only result from bringing

0:05:06.520 --> 0:05:11.120
<v Speaker 1>those people together. The length of the meeting is determined

0:05:11.160 --> 0:05:15.600
<v Speaker 1>by what needs to happen, and not by some arbitrary

0:05:15.640 --> 0:05:20.400
<v Speaker 1>clock time. If you need twenty minutes, you set the

0:05:20.440 --> 0:05:24.600
<v Speaker 1>meeting for twenty minutes. If you need thirty seven point

0:05:24.680 --> 0:05:28.040
<v Speaker 1>five minutes, you ask for that, and everyone is going

0:05:28.080 --> 0:05:32.919
<v Speaker 1>to assume your agenda is incredibly well thought through. But

0:05:33.120 --> 0:05:35.920
<v Speaker 1>if that is not going to happen, the next best

0:05:36.000 --> 0:05:40.560
<v Speaker 1>solution is to shorten all meetings just a little. People

0:05:40.560 --> 0:05:45.000
<v Speaker 1>won't be late, they can catch their breath, they can

0:05:45.080 --> 0:05:49.559
<v Speaker 1>think about what just happened, and then they can start

0:05:49.560 --> 0:05:54.400
<v Speaker 1>the next thing. This is a fairly simple fix that

0:05:54.480 --> 0:05:58.960
<v Speaker 1>can have a big impact in terms of increasing focus

0:05:59.080 --> 0:06:04.640
<v Speaker 1>and avoiding a sense of being overwhelmed. In the meantime.

0:06:05.880 --> 0:06:10.840
<v Speaker 1>This is Laura. Thanks for listening, and here's to making

0:06:10.880 --> 0:06:20.719
<v Speaker 1>the most of our time. Hey, everybody, I'd love to

0:06:20.760 --> 0:06:23.719
<v Speaker 1>hear from you. You can send me your tips, your questions,

0:06:23.800 --> 0:06:27.560
<v Speaker 1>or anything else. Just connect with me on Twitter, Facebook

0:06:27.680 --> 0:06:33.160
<v Speaker 1>and Instagram at Before Breakfast pod. That's B the number four,

0:06:33.680 --> 0:06:37.200
<v Speaker 1>then Breakfast p o D. You can also shoot me

0:06:37.240 --> 0:06:40.880
<v Speaker 1>an email at Before Breakfast podcast at i heeart media

0:06:40.960 --> 0:06:43.560
<v Speaker 1>dot com that Before Breakfast is spelled out with all

0:06:43.600 --> 0:06:46.440
<v Speaker 1>the letters. Thanks so much, I look forward to staying

0:06:46.440 --> 0:06:55.080
<v Speaker 1>in touch. Before Breakfast is a production of I Heart Radio.

0:06:55.680 --> 0:06:58.599
<v Speaker 1>For more podcasts from my heart Radio, visit the I

0:06:58.680 --> 0:07:02.120
<v Speaker 1>heart Radio app, Apple Podcasts, or wherever you listen to

0:07:02.200 --> 0:07:11.960
<v Speaker 1>your favorite shows. Yeah m hm