WEBVTT - Second Cup: 50 not 60

0:00:03.520 --> 0:00:08.200
<v Speaker 1>Welcome to Before Breakfast, a production of iHeartRadio.

0:00:09.160 --> 0:00:09.720
<v Speaker 2>Good Morning.

0:00:11.080 --> 0:00:13.120
<v Speaker 1>This is Laura.

0:00:13.240 --> 0:00:15.200
<v Speaker 2>Welcome to the Before Breakfast podcast.

0:00:16.560 --> 0:00:21.840
<v Speaker 1>Today's tip is to schedule meetings for fifty minutes, not sixty.

0:00:23.360 --> 0:00:26.640
<v Speaker 1>That way, people can get where they're going and more

0:00:26.680 --> 0:00:31.840
<v Speaker 1>meetings can start on time. As I have studied corporate

0:00:31.880 --> 0:00:34.800
<v Speaker 1>schedules over the years, I have been fascinated to see

0:00:34.840 --> 0:00:39.400
<v Speaker 1>how most organizations, or at least most individual people, have

0:00:39.560 --> 0:00:44.360
<v Speaker 1>some sort of default length for their meetings. Some places

0:00:44.400 --> 0:00:48.240
<v Speaker 1>set the default at thirty minutes, but sixty minutes tends

0:00:48.240 --> 0:00:51.640
<v Speaker 1>to be the most common. Because people wind up in

0:00:51.720 --> 0:00:55.360
<v Speaker 1>a lot of meetings, many of these meetings get scheduled

0:00:55.360 --> 0:01:00.360
<v Speaker 1>back to back. This is a problem because if you

0:01:00.400 --> 0:01:03.160
<v Speaker 1>are in a meeting that runs from nine to ten

0:01:04.000 --> 0:01:07.920
<v Speaker 1>and another one that runs from ten to eleven, you

0:01:07.959 --> 0:01:12.040
<v Speaker 1>are expected to be in two different meetings at precisely

0:01:12.040 --> 0:01:15.800
<v Speaker 1>ten am, and if the meetings are in different places,

0:01:15.840 --> 0:01:20.080
<v Speaker 1>this is a physical impossibility. But even if both meetings

0:01:20.120 --> 0:01:22.800
<v Speaker 1>are by video conference, and even if the first ends

0:01:22.920 --> 0:01:26.679
<v Speaker 1>precisely on time, you will still be a minute late

0:01:26.800 --> 0:01:30.119
<v Speaker 1>to the second because it takes a non zero amount

0:01:30.160 --> 0:01:33.839
<v Speaker 1>of time to log in. You also won't have time

0:01:33.880 --> 0:01:36.880
<v Speaker 1>to use the restroom or make any notes about follow

0:01:36.959 --> 0:01:40.520
<v Speaker 1>ups from the first meeting, which means those to dos

0:01:40.640 --> 0:01:43.200
<v Speaker 1>may fade to the back of your mind until they

0:01:43.560 --> 0:01:48.400
<v Speaker 1>urgently boil back up. And of course, mini meetings do

0:01:48.520 --> 0:01:52.760
<v Speaker 1>not end on time. That makes people even later for

0:01:52.840 --> 0:01:57.120
<v Speaker 1>all subsequent meetings, so all meetings after the first start

0:01:57.160 --> 0:02:00.880
<v Speaker 1>in a discombobulated way, as you do decide whether to

0:02:01.080 --> 0:02:07.240
<v Speaker 1>wait for the late comers or shift the agenda accordingly. Fortunately,

0:02:08.120 --> 0:02:13.640
<v Speaker 1>this is a comparatively easy problem to solve. Indeed, it

0:02:13.720 --> 0:02:18.040
<v Speaker 1>is a problem that most high schools have solved. You

0:02:18.160 --> 0:02:22.840
<v Speaker 1>need to create a passing period between scheduled events so

0:02:22.960 --> 0:02:27.720
<v Speaker 1>people can get from one commitment to another. If you

0:02:27.840 --> 0:02:31.800
<v Speaker 1>are in a leadership role at your organization, one obvious

0:02:31.840 --> 0:02:34.240
<v Speaker 1>way to do this is to set the norm of

0:02:34.280 --> 0:02:38.760
<v Speaker 1>having meetings start on the hour and end at ten minutes.

0:02:38.560 --> 0:02:41.680
<v Speaker 2>Until the hour. That is, they are.

0:02:41.560 --> 0:02:46.480
<v Speaker 1>All fifty minutes long instead of sixty minutes long. That way,

0:02:46.600 --> 0:02:51.040
<v Speaker 1>even participants with back to back meetings aren't inevitably late

0:02:51.240 --> 0:02:52.959
<v Speaker 1>for all of their meetings of the day.

0:02:53.040 --> 0:02:53.880
<v Speaker 2>Except the first.

0:02:55.240 --> 0:02:58.360
<v Speaker 1>You can even encourage staff to adjust their outlook settings

0:02:58.360 --> 0:03:01.440
<v Speaker 1>to shorten the duration of all events. So that meetings

0:03:01.440 --> 0:03:04.640
<v Speaker 1>default to a specific amount of time before the hour.

0:03:05.919 --> 0:03:09.520
<v Speaker 1>A few organizations choose a corollary to this idea, that is,

0:03:09.800 --> 0:03:13.480
<v Speaker 1>all meetings start ten minutes after the hour and end

0:03:13.880 --> 0:03:17.359
<v Speaker 1>on the hour. That can also work, but it is

0:03:17.480 --> 0:03:21.640
<v Speaker 1>slightly less intuitive to explain to people outside the organization.

0:03:23.000 --> 0:03:27.280
<v Speaker 1>So I like on the hour and ending ten minutes

0:03:27.360 --> 0:03:32.760
<v Speaker 1>till now. It is true that fifty minutes is less

0:03:33.040 --> 0:03:37.240
<v Speaker 1>than sixty minutes, and if you were accustomed to filling

0:03:37.480 --> 0:03:41.680
<v Speaker 1>every single one of those sixty minutes efficiently in all

0:03:41.760 --> 0:03:45.000
<v Speaker 1>of your meetings, then you may have to rethink things.

0:03:46.120 --> 0:03:50.240
<v Speaker 1>But in my experience, there are very few corporate meetings

0:03:50.840 --> 0:03:53.760
<v Speaker 1>that were scheduled for sixty minutes but that could not

0:03:53.800 --> 0:03:58.760
<v Speaker 1>take fifty Indeed, since many meetings start late because of

0:03:58.880 --> 0:04:03.120
<v Speaker 1>latecomers from previs meetings, the material may often be taking

0:04:03.200 --> 0:04:07.840
<v Speaker 1>closer to fifty minutes. Anyway, as people get antsy once

0:04:07.880 --> 0:04:10.600
<v Speaker 1>the clock strikes the hour and they know they need

0:04:10.640 --> 0:04:16.240
<v Speaker 1>to go to the next thing. Best to acknowledge this now.

0:04:16.240 --> 0:04:18.440
<v Speaker 1>If you are not in a leadership role, this might

0:04:18.480 --> 0:04:21.400
<v Speaker 1>be a bit harder to establish, but you can certainly

0:04:21.400 --> 0:04:24.000
<v Speaker 1>make it happen for any meetings that are under your control.

0:04:25.000 --> 0:04:27.839
<v Speaker 1>If you know people are going to be late, plan

0:04:27.920 --> 0:04:32.039
<v Speaker 1>on starting at five minutes after the hour and then

0:04:32.279 --> 0:04:36.960
<v Speaker 1>end ten minutes before. Yep, that means turning your sixty

0:04:37.000 --> 0:04:41.680
<v Speaker 1>minute meetings into forty five minute ones. But hey, you

0:04:41.760 --> 0:04:45.800
<v Speaker 1>listen to this podcast. You thrive on doing things effectively.

0:04:46.839 --> 0:04:51.239
<v Speaker 1>I am betting that you could figure it out. Of course,

0:04:51.279 --> 0:04:53.200
<v Speaker 1>in the grand scheme of things, it.

0:04:53.160 --> 0:04:56.240
<v Speaker 2>Would be better to just have fewer meetings.

0:04:57.400 --> 0:05:02.120
<v Speaker 1>Ideally, when a meeting happens, it is because something needs

0:05:02.200 --> 0:05:06.200
<v Speaker 1>to change in the world that can only result from

0:05:06.240 --> 0:05:10.560
<v Speaker 1>bringing those people together. The length of the meeting is

0:05:10.640 --> 0:05:14.880
<v Speaker 1>determined by what needs to happen, and not by some

0:05:15.120 --> 0:05:20.400
<v Speaker 1>arbitrary clock time. If you need twenty minutes, you set

0:05:20.400 --> 0:05:24.359
<v Speaker 1>the meeting for twenty minutes. If you need thirty seven

0:05:24.400 --> 0:05:27.919
<v Speaker 1>point five minutes, you ask for that, and everyone is

0:05:27.960 --> 0:05:31.360
<v Speaker 1>going to assume your agenda is incredibly well thought through.

0:05:32.920 --> 0:05:35.719
<v Speaker 1>But if that is not going to happen, the next

0:05:35.760 --> 0:05:39.360
<v Speaker 1>best solution is to shorten all meetings just a little.

0:05:40.320 --> 0:05:44.840
<v Speaker 1>People won't be late, they can catch their breath, they

0:05:44.839 --> 0:05:49.320
<v Speaker 1>can think about what just happened, and then they can

0:05:49.360 --> 0:05:53.560
<v Speaker 1>start the next thing. This is a fairly simple fix

0:05:54.400 --> 0:05:57.719
<v Speaker 1>that can have a big impact in terms of increasing

0:05:57.760 --> 0:06:04.760
<v Speaker 1>focus and avoiding a sense of being overwhelmed. In the meantime,

0:06:05.960 --> 0:06:10.800
<v Speaker 1>This is Laura. Thanks for listening and here's.

0:06:10.520 --> 0:06:12.839
<v Speaker 2>To making the most of our time.

0:06:19.320 --> 0:06:22.080
<v Speaker 1>Hey, everybody, I'd love to hear from you. You can

0:06:22.120 --> 0:06:25.599
<v Speaker 1>send me your tips, your questions, or anything else. Just

0:06:25.640 --> 0:06:29.520
<v Speaker 1>connect with me on Twitter, Facebook and Instagram at Before

0:06:29.640 --> 0:06:35.520
<v Speaker 1>Breakfast Pod. That's b E the number four then Breakfast pod.

0:06:36.400 --> 0:06:39.240
<v Speaker 1>You can also shoot me an email at Before Breakfast

0:06:39.320 --> 0:06:43.240
<v Speaker 1>podcast at iHeartMedia dot com that Before Breakfast is spelled

0:06:43.240 --> 0:06:44.200
<v Speaker 1>out with all the letters.

0:06:44.800 --> 0:06:46.880
<v Speaker 2>Thanks so much, should I look forward to staying in touch.

0:06:52.720 --> 0:06:56.760
<v Speaker 1>Before Breakfast is a production of iHeartRadio. For more podcasts

0:06:56.800 --> 0:07:01.719
<v Speaker 1>from iHeartRadio, visit the iHeartRadio app, Apple Podcasts, or wherever

0:07:01.760 --> 0:07:03.120
<v Speaker 1>you listen to your favorite shows.