WEBVTT - Improve your conference calls

0:00:03.200 --> 0:00:06.400
<v Speaker 1>Welcome to Before Breakfast, a production of I Heart Radio.

0:00:09.119 --> 0:00:13.800
<v Speaker 1>Good Morning, This is Laura. Welcome to the Before Breakfast podcast.

0:00:14.560 --> 0:00:17.600
<v Speaker 1>Today's tip is about how to make your conference calls

0:00:17.880 --> 0:00:22.560
<v Speaker 1>more efficient and effective if you work with people located

0:00:22.600 --> 0:00:26.040
<v Speaker 1>in different places. Conference calls are just part of the

0:00:26.079 --> 0:00:29.800
<v Speaker 1>game these days. They definitely serve a purpose, but they

0:00:29.800 --> 0:00:33.520
<v Speaker 1>can also be frustrating for all involved. Here's a short

0:00:33.520 --> 0:00:38.600
<v Speaker 1>list of the frustrations. People have lousy reception or maybe worse.

0:00:38.680 --> 0:00:41.199
<v Speaker 1>Their reception is good and you pick up on the

0:00:41.200 --> 0:00:46.320
<v Speaker 1>background noise, people don't pay attention, the conversation meanders because

0:00:46.320 --> 0:00:49.120
<v Speaker 1>it's hard to read cues, and with too many people

0:00:49.120 --> 0:00:53.960
<v Speaker 1>on the call, tangential topics get introduced. And then there's

0:00:54.000 --> 0:00:57.400
<v Speaker 1>the matter of punctuality. I once got a note from

0:00:57.400 --> 0:01:00.520
<v Speaker 1>a young consultant who tracked her time and reported that

0:01:00.560 --> 0:01:04.440
<v Speaker 1>she wasted forty five minutes daily waiting for senior people

0:01:04.480 --> 0:01:08.279
<v Speaker 1>to join conference calls. It wasn't really a nefarious power

0:01:08.319 --> 0:01:10.280
<v Speaker 1>player or anything like that. It was really more of

0:01:10.280 --> 0:01:14.560
<v Speaker 1>a volume problem. People squeezed calls around flights, but then

0:01:14.560 --> 0:01:17.440
<v Speaker 1>if the flight landed fifteen minutes late, they'd be fifteen

0:01:17.480 --> 0:01:20.560
<v Speaker 1>minutes late to or a previous call would run over,

0:01:20.600 --> 0:01:23.400
<v Speaker 1>and because people were scheduled into so many calls, the

0:01:23.400 --> 0:01:27.319
<v Speaker 1>rest of the schedule would fall like dominoes. It's understandable,

0:01:27.360 --> 0:01:29.920
<v Speaker 1>but forty five minutes a day is a lot of

0:01:29.959 --> 0:01:33.840
<v Speaker 1>wasted time. So how can you keep conference calls from

0:01:33.880 --> 0:01:39.200
<v Speaker 1>being terrible? First, and probably the biggest breakthrough is committing

0:01:39.600 --> 0:01:45.000
<v Speaker 1>to quitting multitasking. Do not check email while you're on

0:01:45.040 --> 0:01:48.520
<v Speaker 1>a call. Do not serve the web, do not check

0:01:48.560 --> 0:01:53.040
<v Speaker 1>social media. Frankly, i'd say don't drive either, because it

0:01:53.120 --> 0:01:57.760
<v Speaker 1>isn't safe and distracted driving is a huge cause of accidents. Now,

0:01:57.800 --> 0:02:01.560
<v Speaker 1>I know this single tasking is incre credibly hard. We

0:02:01.640 --> 0:02:05.000
<v Speaker 1>all have so much to do. But the primary reason

0:02:05.080 --> 0:02:08.799
<v Speaker 1>single tasking is hard is that most conference calls are

0:02:08.880 --> 0:02:13.560
<v Speaker 1>so boring. I don't multitask if I'm being interviewed for

0:02:13.600 --> 0:02:15.560
<v Speaker 1>a podcast and the host and I are having an

0:02:15.560 --> 0:02:19.320
<v Speaker 1>incredible conversation, and that's because I'm engaged the whole time

0:02:19.840 --> 0:02:22.680
<v Speaker 1>I have to be. I really do believe that all

0:02:22.720 --> 0:02:26.400
<v Speaker 1>calls should rise to that level. If you bother to

0:02:26.440 --> 0:02:30.160
<v Speaker 1>take a call, you should be so engaged for the

0:02:30.360 --> 0:02:36.079
<v Speaker 1>entire time that you just can't multitask. If you can multitask, well,

0:02:36.120 --> 0:02:39.120
<v Speaker 1>you probably shouldn't have that call, or at least you

0:02:39.120 --> 0:02:41.919
<v Speaker 1>should have far fewer people on it. This is another

0:02:41.960 --> 0:02:45.760
<v Speaker 1>big breakthrough. Conference calls are incredibly easy to schedule, and

0:02:45.800 --> 0:02:47.840
<v Speaker 1>so we tend to have more of them and with

0:02:47.880 --> 0:02:52.359
<v Speaker 1>more people than are really necessary. So instead, pretend you're

0:02:52.400 --> 0:02:55.960
<v Speaker 1>doing something difficult. Pretend that you've got to fly everyone

0:02:55.960 --> 0:02:58.600
<v Speaker 1>on the call in for a meeting. You wouldn't want

0:02:58.600 --> 0:03:01.160
<v Speaker 1>to cover travel costs for any one who didn't absolutely

0:03:01.160 --> 0:03:03.639
<v Speaker 1>need to be there, and you'd also think about why

0:03:03.680 --> 0:03:05.760
<v Speaker 1>you were convening all these people and asking them to

0:03:05.760 --> 0:03:07.720
<v Speaker 1>fly in and what you hope to get out of

0:03:07.760 --> 0:03:11.480
<v Speaker 1>the meeting. Likewise, for any call, you need an agenda.

0:03:12.080 --> 0:03:14.880
<v Speaker 1>Just as if you were meeting in person, you also

0:03:14.919 --> 0:03:19.720
<v Speaker 1>need someone to definitively be in charge. Indeed, this is

0:03:19.760 --> 0:03:22.560
<v Speaker 1>even more important on the phone than it is for

0:03:22.600 --> 0:03:25.200
<v Speaker 1>an in person meeting, since you won't be able to

0:03:25.240 --> 0:03:27.239
<v Speaker 1>read each other's faces to see who would like to

0:03:27.280 --> 0:03:30.680
<v Speaker 1>speak or who has an objection. If you've got a

0:03:30.680 --> 0:03:33.880
<v Speaker 1>call coming up that doesn't have a clear leader, offer

0:03:33.960 --> 0:03:37.240
<v Speaker 1>to be this person. That way you can keep things

0:03:37.280 --> 0:03:41.120
<v Speaker 1>moving along. If you keep a focused agenda, you'll find

0:03:41.120 --> 0:03:44.200
<v Speaker 1>that the material won't naturally conform itself to thirty or

0:03:44.240 --> 0:03:48.160
<v Speaker 1>sixty minutes, and that's fine. Schedule the call for the

0:03:48.200 --> 0:03:52.480
<v Speaker 1>amount of time you actually need. Don't make it sixty

0:03:52.520 --> 0:03:55.000
<v Speaker 1>minutes just because that's an easy thing to block into

0:03:55.000 --> 0:03:59.440
<v Speaker 1>your calendar. Finally, as the person in charge, facilitate the

0:03:59.440 --> 0:04:05.240
<v Speaker 1>discussion by using people's names, Nancy, can you talk about

0:04:05.240 --> 0:04:08.040
<v Speaker 1>the problem the team is having with the deadline? Joe,

0:04:08.320 --> 0:04:10.880
<v Speaker 1>can you please report on what additional resources might be

0:04:10.880 --> 0:04:14.960
<v Speaker 1>available from other teams. There are several upsides to this. First,

0:04:15.000 --> 0:04:17.839
<v Speaker 1>it reminds everyone who's on the call, which is something

0:04:17.880 --> 0:04:21.839
<v Speaker 1>that's remarkably easy to forget when you can't see everyone. Second,

0:04:21.960 --> 0:04:24.840
<v Speaker 1>it keeps people from zoning out if they know they

0:04:24.880 --> 0:04:27.320
<v Speaker 1>are going to be called upon by name, and that

0:04:27.400 --> 0:04:30.479
<v Speaker 1>cuts down on the multitasking. And finally, when you call

0:04:30.600 --> 0:04:33.359
<v Speaker 1>people's names, you make sure that everyone does speak and

0:04:33.440 --> 0:04:36.240
<v Speaker 1>weighs in, and has done so with about the same frequency.

0:04:37.160 --> 0:04:39.560
<v Speaker 1>If your call is small and focused, it won't be

0:04:39.560 --> 0:04:41.240
<v Speaker 1>hard to keep track of who needs to weigh in

0:04:41.240 --> 0:04:44.119
<v Speaker 1>on what. You might even get done with your call early.

0:04:44.920 --> 0:04:47.800
<v Speaker 1>Just don't use that save time to schedule even more

0:04:47.880 --> 0:04:52.440
<v Speaker 1>conference calls in the meantime, this is Laura. Thanks for

0:04:52.520 --> 0:05:02.400
<v Speaker 1>listening and here's to making the most of our time. Hey, everybody,

0:05:02.640 --> 0:05:04.760
<v Speaker 1>I'd love to hear from you. You can send me

0:05:04.800 --> 0:05:08.440
<v Speaker 1>your tips, your questions, or anything else. Just connect with

0:05:08.480 --> 0:05:12.880
<v Speaker 1>me on Twitter, Facebook and Instagram at Before Breakfast pod.

0:05:13.560 --> 0:05:17.919
<v Speaker 1>That's B the number four, then Breakfast p o D.

0:05:18.760 --> 0:05:21.600
<v Speaker 1>You can also shoot me an email at Before Breakfast

0:05:21.680 --> 0:05:25.039
<v Speaker 1>podcast at i heeart media dot com that Before Breakfast

0:05:25.200 --> 0:05:27.760
<v Speaker 1>is spelled out with all the letters. Thanks so much,

0:05:27.960 --> 0:05:36.080
<v Speaker 1>I look forward to staying in touch. Before Breakfast is

0:05:36.080 --> 0:05:39.320
<v Speaker 1>a production of I heart Radio. For more podcasts from

0:05:39.320 --> 0:05:43.320
<v Speaker 1>I heart Radio, visit the I heart Radio app, Apple Podcasts,

0:05:43.600 --> 0:05:45.480
<v Speaker 1>or wherever you listen to your favorite shows.