WEBVTT - How long will this take?

0:00:03.200 --> 0:00:06.400
<v Speaker 1>Welcome to Before Breakfast, a production of I Heart Radio.

0:00:09.200 --> 0:00:13.800
<v Speaker 1>Good Morning. This is Laura. Welcome to the Before Breakfast podcast.

0:00:14.280 --> 0:00:18.119
<v Speaker 1>Today's tip is to figure out how long things will take.

0:00:18.840 --> 0:00:21.840
<v Speaker 1>This way you can make wise choices about how to

0:00:21.880 --> 0:00:25.479
<v Speaker 1>plan your life. I decided to do an episode on

0:00:25.520 --> 0:00:28.840
<v Speaker 1>this topic after getting a note from Before Breakfast listeners Zoe,

0:00:29.280 --> 0:00:33.080
<v Speaker 1>who has learned how useful time estimates can be. Zoe

0:00:33.159 --> 0:00:35.279
<v Speaker 1>wrote in that I once heard a rule that if

0:00:35.320 --> 0:00:38.440
<v Speaker 1>a task takes under five minutes, don't add it to

0:00:38.479 --> 0:00:42.280
<v Speaker 1>your to do list, just do it. She says that

0:00:42.520 --> 0:00:44.560
<v Speaker 1>I lived by this for quite a while, but found

0:00:44.560 --> 0:00:47.680
<v Speaker 1>that it didn't always work. For example, when I'm grocery

0:00:47.680 --> 0:00:50.680
<v Speaker 1>shopping and I randomly remember that I need to reschedule

0:00:50.720 --> 0:00:53.440
<v Speaker 1>an appointment, I wasn't going to call the office in

0:00:53.479 --> 0:00:56.120
<v Speaker 1>the middle of the cereal aisle, so I adapted the

0:00:56.160 --> 0:00:59.840
<v Speaker 1>rule just a bit. She says that my trick is

0:01:00.080 --> 0:01:02.320
<v Speaker 1>when I write things on my to do list, I

0:01:02.360 --> 0:01:07.280
<v Speaker 1>include a time estimate in minutes next to the task. Then,

0:01:07.440 --> 0:01:09.480
<v Speaker 1>when I am ready to tackle my to do list

0:01:09.800 --> 0:01:12.720
<v Speaker 1>and I become overwhelmed by the length and don't know

0:01:12.760 --> 0:01:15.880
<v Speaker 1>where to start, I knock off the tasks that are

0:01:15.959 --> 0:01:20.679
<v Speaker 1>under five minutes. First. This boosts my motivation because I

0:01:20.720 --> 0:01:23.360
<v Speaker 1>can cross off some quick winds and my list is

0:01:23.400 --> 0:01:27.440
<v Speaker 1>already shorter. She also says that the other benefit of

0:01:27.480 --> 0:01:30.160
<v Speaker 1>the time estimate is that when I have free time,

0:01:30.720 --> 0:01:33.920
<v Speaker 1>I can pick which task fits the time frame I have.

0:01:35.280 --> 0:01:38.520
<v Speaker 1>I think that this idea of including time estimates on

0:01:38.600 --> 0:01:42.600
<v Speaker 1>a to do list is wise. In general, having an

0:01:42.640 --> 0:01:45.720
<v Speaker 1>accurate sense of how long things will take is what

0:01:45.880 --> 0:01:50.200
<v Speaker 1>separates time management masters from everyone else. It is a

0:01:50.320 --> 0:01:54.200
<v Speaker 1>very useful skill. I also know that it is a

0:01:54.320 --> 0:02:01.680
<v Speaker 1>rare skill. Time estimation is really really hard. It's challenging

0:02:01.720 --> 0:02:06.120
<v Speaker 1>for a number of reasons. Sometimes people are just oblivious.

0:02:06.600 --> 0:02:08.880
<v Speaker 1>There are people who think it takes thirty minutes to

0:02:08.919 --> 0:02:11.560
<v Speaker 1>get to work, even though it takes forty five minutes

0:02:11.600 --> 0:02:14.400
<v Speaker 1>every day and has for the past week. I don't know,

0:02:14.560 --> 0:02:17.919
<v Speaker 1>Maybe the last five days have all been atypical. Maybe

0:02:17.919 --> 0:02:20.600
<v Speaker 1>in this person's fantasy world, no one else should be

0:02:20.600 --> 0:02:23.520
<v Speaker 1>on the road at eight am. In any case, the

0:02:23.720 --> 0:02:29.280
<v Speaker 1>estimate is wildly optimistic. Other times, we're dealing with complex

0:02:29.400 --> 0:02:33.480
<v Speaker 1>or highly variable tasks. If you've never done something before,

0:02:34.000 --> 0:02:36.440
<v Speaker 1>it's hard to know how long it will take. Or

0:02:36.520 --> 0:02:40.120
<v Speaker 1>maybe there are a lot of what ifs. This past spring,

0:02:40.639 --> 0:02:42.720
<v Speaker 1>I learned that the length of my nine year olds

0:02:42.720 --> 0:02:46.920
<v Speaker 1>little league games varied widely based on the skills of

0:02:46.960 --> 0:02:50.760
<v Speaker 1>the other team's pitchers. Nine year olds are still figuring

0:02:50.760 --> 0:02:53.560
<v Speaker 1>out the pitching thing, and sometimes there would be long

0:02:53.639 --> 0:02:57.240
<v Speaker 1>innings with lots of walks, and then some really good

0:02:57.240 --> 0:03:00.360
<v Speaker 1>pitchers would strike out three batters in a row, appelling

0:03:00.400 --> 0:03:04.720
<v Speaker 1>the game forward with rather ferocious velocity. So time estimation

0:03:04.840 --> 0:03:09.320
<v Speaker 1>is hard, but it's also really important. As Zoe pointed out,

0:03:09.800 --> 0:03:12.240
<v Speaker 1>it helps you figure out what you can fit in

0:03:12.360 --> 0:03:15.840
<v Speaker 1>any given unit of time. If you've got an hour,

0:03:16.680 --> 0:03:21.880
<v Speaker 1>you can't do four tasks requiring twenty minutes apiece. Frankly,

0:03:21.960 --> 0:03:25.680
<v Speaker 1>you'll probably have trouble getting through three because switching between

0:03:25.720 --> 0:03:29.560
<v Speaker 1>tasks takes time. But maybe you could do to twenty

0:03:29.560 --> 0:03:33.119
<v Speaker 1>minute ones and then to five minute ones and emerge

0:03:33.160 --> 0:03:37.120
<v Speaker 1>on the other side of the hour feeling accomplished. Or

0:03:37.200 --> 0:03:40.960
<v Speaker 1>you could skip this estimation step and just hope Superman

0:03:41.040 --> 0:03:44.160
<v Speaker 1>will reverse the Earth and turn back time. I'm always

0:03:44.200 --> 0:03:48.280
<v Speaker 1>amazed by how persistently hopeful people can be, and by

0:03:48.320 --> 0:03:52.680
<v Speaker 1>hopeful I mean delusional. People will create to do lists

0:03:52.760 --> 0:03:56.240
<v Speaker 1>that are completely unrelated to the amount of time available.

0:03:57.120 --> 0:04:00.560
<v Speaker 1>You cannot fit fourteen hours of tasks into an eight

0:04:00.600 --> 0:04:03.880
<v Speaker 1>hour work day. This is what leads to people feeling

0:04:03.920 --> 0:04:08.840
<v Speaker 1>incredibly behind. But it's not about discipline, it's not about talent,

0:04:09.520 --> 0:04:14.360
<v Speaker 1>it's about physics. In any case, accurate time estimates can

0:04:14.400 --> 0:04:18.120
<v Speaker 1>help you make more reasonable task lists. They can also

0:04:18.160 --> 0:04:20.440
<v Speaker 1>help you figure out when to say no or to

0:04:20.480 --> 0:04:23.840
<v Speaker 1>ask for help. Ten hours of tasks that are due

0:04:23.880 --> 0:04:27.840
<v Speaker 1>in six hours must be spread over more than one person,

0:04:28.920 --> 0:04:32.359
<v Speaker 1>and as Zoe points out, accurate time estimates can also

0:04:32.400 --> 0:04:35.679
<v Speaker 1>help you use bits of time. I have ten minutes

0:04:35.720 --> 0:04:38.520
<v Speaker 1>before this call, and I estimate that calling to move

0:04:38.560 --> 0:04:42.719
<v Speaker 1>an appointment will take five minutes. Bingo, we have a winner.

0:04:43.839 --> 0:04:45.960
<v Speaker 1>Of course, this raises the question of how we can

0:04:46.040 --> 0:04:49.360
<v Speaker 1>learn to estimate tasks correctly, or at least get better

0:04:49.400 --> 0:04:52.559
<v Speaker 1>at this skill. This is one reason I suggest people

0:04:52.560 --> 0:04:55.680
<v Speaker 1>try tracking their time. You can start to see there

0:04:55.680 --> 0:04:58.760
<v Speaker 1>in black and white how long things take. It is

0:04:58.800 --> 0:05:02.520
<v Speaker 1>hard to write down day after day that a drive

0:05:02.600 --> 0:05:07.159
<v Speaker 1>takes forty five minutes and persist in believing it takes thirty.

0:05:07.400 --> 0:05:11.040
<v Speaker 1>You can try, but hopefully rational sorts will respond to

0:05:11.080 --> 0:05:15.320
<v Speaker 1>a preponderance of evidence. You can also start to see ranges.

0:05:16.040 --> 0:05:19.120
<v Speaker 1>We do this naturally for some things. For instance, the

0:05:19.240 --> 0:05:21.719
<v Speaker 1>drive to the airport is forty five to sixty minutes,

0:05:22.000 --> 0:05:25.080
<v Speaker 1>depending on traffic. You can come up with a range

0:05:25.080 --> 0:05:28.960
<v Speaker 1>for any variable task, then budget your time based on

0:05:29.000 --> 0:05:33.000
<v Speaker 1>the upper limit. If you get lucky, great you can

0:05:33.000 --> 0:05:35.360
<v Speaker 1>go find some other stuff to do. But if you

0:05:35.440 --> 0:05:38.880
<v Speaker 1>hit the top of the range, you're still okay. You

0:05:38.920 --> 0:05:43.040
<v Speaker 1>can break big tasks down into constituent parts. Preparing a

0:05:43.160 --> 0:05:46.560
<v Speaker 1>presentation is vague, but you could budget thirty minutes for outlining,

0:05:46.960 --> 0:05:49.200
<v Speaker 1>another thirty for finding the stats that will help make

0:05:49.240 --> 0:05:51.839
<v Speaker 1>your case. In an hour or so to make the slides,

0:05:52.440 --> 0:05:56.000
<v Speaker 1>build in another hour to practice twice. You can also

0:05:56.080 --> 0:06:00.200
<v Speaker 1>ask other people. Maybe you've never written this sort of report,

0:05:59.839 --> 0:06:02.560
<v Speaker 1>but Pete, who used to be on your team, has

0:06:03.120 --> 0:06:06.400
<v Speaker 1>budget ten minutes to call Pete see what he says.

0:06:07.200 --> 0:06:09.719
<v Speaker 1>Of course, Pete might be wrong, because, as we've noted,

0:06:09.960 --> 0:06:13.400
<v Speaker 1>many people are bad at estimation, but his estimate gives

0:06:13.440 --> 0:06:16.040
<v Speaker 1>you a starting point that you can then revise as

0:06:16.080 --> 0:06:22.320
<v Speaker 1>you go, and finally, when all else fails, bid high.

0:06:22.560 --> 0:06:24.839
<v Speaker 1>If Zoe puts down that it will take five minutes

0:06:24.880 --> 0:06:27.719
<v Speaker 1>to move an appointment, but she calls and the receptionist

0:06:27.720 --> 0:06:30.160
<v Speaker 1>solves her problem in thirty seconds. She's not going to

0:06:30.240 --> 0:06:33.320
<v Speaker 1>be unhappy, whereas if she tells herself it will take

0:06:33.360 --> 0:06:35.920
<v Speaker 1>one minute and she tries to slip it in between

0:06:35.920 --> 0:06:38.839
<v Speaker 1>other things, and then she starts hearing that hold music

0:06:39.120 --> 0:06:41.039
<v Speaker 1>and then her manager is calling right at the time

0:06:41.080 --> 0:06:44.960
<v Speaker 1>she said she would. Well, that sounds stressful. So when

0:06:44.960 --> 0:06:48.159
<v Speaker 1>you're making your to do lists, be sure to include

0:06:48.400 --> 0:06:53.799
<v Speaker 1>time estimates and then, just for fun, add up the estimates.

0:06:54.600 --> 0:06:57.159
<v Speaker 1>Does this number look like less than the amount you

0:06:57.200 --> 0:07:02.679
<v Speaker 1>plan to work today? If so, right, If not, time

0:07:02.720 --> 0:07:05.920
<v Speaker 1>to go back and change something. I promise this will

0:07:05.960 --> 0:07:09.840
<v Speaker 1>help you feel less busy while getting more done in

0:07:09.880 --> 0:07:14.200
<v Speaker 1>the meantime. This is Laura. Thanks for listening, and here's

0:07:14.240 --> 0:07:23.320
<v Speaker 1>to making the most of our time. Hey, everybody, I'd

0:07:23.360 --> 0:07:25.800
<v Speaker 1>love to hear from you. You can send me your tips,

0:07:25.880 --> 0:07:29.560
<v Speaker 1>your questions, or anything else. Just connect with me on Twitter,

0:07:29.920 --> 0:07:35.360
<v Speaker 1>Facebook and Instagram at Before Breakfast Pod that's B the

0:07:35.480 --> 0:07:39.720
<v Speaker 1>number four, then Breakfast p o D. You can also

0:07:39.720 --> 0:07:43.120
<v Speaker 1>shoot me an email at Before Breakfast Podcast at i

0:07:43.240 --> 0:07:46.240
<v Speaker 1>heeart media dot com That Before Breakfast is spelled out

0:07:46.240 --> 0:07:48.960
<v Speaker 1>with all the letters. Thanks so much, I look forward

0:07:49.000 --> 0:07:57.200
<v Speaker 1>to staying in touch. Before Breakfast is a production of

0:07:57.240 --> 0:08:01.280
<v Speaker 1>I heart Radio. For more podcasts from heart Radio, visit

0:08:01.320 --> 0:08:04.720
<v Speaker 1>the i heart Radio app, Apple Podcasts, or wherever you

0:08:04.760 --> 0:08:08.360
<v Speaker 1>listen to your favorite shows. H