WEBVTT - Fix the known bugs

0:00:03.440 --> 0:00:06.680
<v Speaker 1>Welcome to Before Breakfast, a production of I Heart Radio.

0:00:09.160 --> 0:00:15.120
<v Speaker 1>Good Morning, This is Laura. Welcome to the Before Breakfast podcast.

0:00:16.280 --> 0:00:21.759
<v Speaker 1>Today's tip is to fix the noon bugs. If something

0:00:21.880 --> 0:00:26.319
<v Speaker 1>is obviously wrong, stop what you are doing and fix it.

0:00:27.600 --> 0:00:33.400
<v Speaker 1>That way, you won't have to live with the annoyance anymore. So.

0:00:33.520 --> 0:00:35.680
<v Speaker 1>In the latest update to an app I use, a

0:00:35.720 --> 0:00:39.519
<v Speaker 1>certain glitch made it inefficient. A search to figure out

0:00:39.560 --> 0:00:42.200
<v Speaker 1>how to fix the issue revealed that the problem isn't

0:00:42.200 --> 0:00:46.040
<v Speaker 1>what the settings or that broad category known as operator error.

0:00:46.720 --> 0:00:49.000
<v Speaker 1>It is a problem with the latest version of the app,

0:00:49.720 --> 0:00:52.680
<v Speaker 1>and it appears the folks in charge know about it,

0:00:53.159 --> 0:00:55.800
<v Speaker 1>but are not in a rush to fix it. It

0:00:55.960 --> 0:01:00.880
<v Speaker 1>is a known bug. Sometimes we just have to decide

0:01:00.880 --> 0:01:03.720
<v Speaker 1>to live with these things or not. I guess there

0:01:03.720 --> 0:01:05.959
<v Speaker 1>are a lot of apps in this world, but it

0:01:06.000 --> 0:01:08.959
<v Speaker 1>can be really annoying to encounter the same problem again

0:01:09.000 --> 0:01:12.280
<v Speaker 1>and again. So if you find a bug in an

0:01:12.280 --> 0:01:15.640
<v Speaker 1>area where you can control things so that it becomes

0:01:15.680 --> 0:01:20.399
<v Speaker 1>a known bug to you do something about it, you

0:01:20.400 --> 0:01:25.840
<v Speaker 1>will probably save a lot of time and frustration. I

0:01:25.880 --> 0:01:28.240
<v Speaker 1>am sure if you think about it, you can identify

0:01:28.360 --> 0:01:32.160
<v Speaker 1>at least a few known bugs in your life. The

0:01:32.319 --> 0:01:37.039
<v Speaker 1>doorbells don't work in my new house. We are installing

0:01:37.080 --> 0:01:39.840
<v Speaker 1>a system, but in the meantime we missed deliveries and

0:01:39.880 --> 0:01:45.080
<v Speaker 1>had some folks just leave yikes. Now there are signs

0:01:45.120 --> 0:01:47.880
<v Speaker 1>on each of the broken doorbells with a note to

0:01:47.960 --> 0:01:51.760
<v Speaker 1>call my cell phone number. The known bug is getting fixed,

0:01:51.800 --> 0:01:56.040
<v Speaker 1>and in the meantime there's a workable patch. Maybe you

0:01:56.120 --> 0:01:58.840
<v Speaker 1>are part of a meeting that starts late every single

0:01:58.920 --> 0:02:03.920
<v Speaker 1>week because several participants have another meeting immediately beforehand that

0:02:04.200 --> 0:02:08.760
<v Speaker 1>always runs over. Maybe run a retail store where people

0:02:08.760 --> 0:02:12.120
<v Speaker 1>are constantly asking you to retrieve the petit pants from

0:02:12.120 --> 0:02:16.200
<v Speaker 1>the top shelf because no one stopped to realize that

0:02:16.360 --> 0:02:21.960
<v Speaker 1>anyone who is petite can't reach the top shelf. Many

0:02:22.000 --> 0:02:25.480
<v Speaker 1>of us have a strong tendency to make do I

0:02:25.520 --> 0:02:28.079
<v Speaker 1>will admit that I was standing by the window watching

0:02:28.120 --> 0:02:31.200
<v Speaker 1>for service people rather than realizing I should make a sign.

0:02:32.160 --> 0:02:34.000
<v Speaker 1>But this can waste a lot of time and make

0:02:34.000 --> 0:02:37.840
<v Speaker 1>people very frustrated. So if there is something that doesn't

0:02:37.880 --> 0:02:42.160
<v Speaker 1>work right in an area under your jurisdiction, fix it.

0:02:43.200 --> 0:02:45.680
<v Speaker 1>Maybe it will take a little time, maybe it will

0:02:45.680 --> 0:02:49.680
<v Speaker 1>take a little money, maybe it will take a little creativity,

0:02:49.880 --> 0:02:52.440
<v Speaker 1>but it's going to be worth it to solve the

0:02:52.520 --> 0:02:57.040
<v Speaker 1>known bug. So work with the meeting convener to move

0:02:57.080 --> 0:03:01.280
<v Speaker 1>the start time fifteen minutes. Move with the petites to

0:03:01.360 --> 0:03:04.800
<v Speaker 1>where petite people can reach them. If there is not

0:03:04.919 --> 0:03:07.720
<v Speaker 1>a clear fix to a non bug, ask colleagues and

0:03:07.760 --> 0:03:11.440
<v Speaker 1>customers for suggestions. What do you suppose we can do

0:03:11.520 --> 0:03:15.200
<v Speaker 1>to fix this? You may be surprised at the creativity

0:03:15.200 --> 0:03:19.680
<v Speaker 1>of the suggestions you hear. When we set the expectation

0:03:20.120 --> 0:03:23.800
<v Speaker 1>that we fix bugs, then things start to run more smoothly.

0:03:25.000 --> 0:03:29.880
<v Speaker 1>A culture of solving problems starts to spread. Instead of

0:03:29.880 --> 0:03:32.760
<v Speaker 1>accepting bugs, we start asking ourselves and others, what do

0:03:32.760 --> 0:03:36.240
<v Speaker 1>you think we can do to fix that? Now? I

0:03:36.280 --> 0:03:40.200
<v Speaker 1>am not suggesting that you go hunting for bugs. Some

0:03:40.280 --> 0:03:45.200
<v Speaker 1>people are experts at finding problems that aren't really problems.

0:03:46.360 --> 0:03:48.560
<v Speaker 1>What I am suggesting is that you deal with the

0:03:48.600 --> 0:03:52.800
<v Speaker 1>bugs that you can't avoid seeing. When a bug repeatedly

0:03:52.880 --> 0:03:56.560
<v Speaker 1>interferes with your team's productivity or mars your teams, or

0:03:56.560 --> 0:04:00.120
<v Speaker 1>your customers experience, or your personal life, deal with it.

0:04:01.280 --> 0:04:03.440
<v Speaker 1>The first time I didn't have to watch for a

0:04:03.480 --> 0:04:06.680
<v Speaker 1>truck because the person called me from the door. It

0:04:06.800 --> 0:04:10.400
<v Speaker 1>was incredibly relaxing. I was glad to have done something

0:04:10.400 --> 0:04:12.960
<v Speaker 1>about the problem, and I'm sure having a real doorbell

0:04:13.320 --> 0:04:18.320
<v Speaker 1>will be even better. In the meantime, this is Laura.

0:04:19.240 --> 0:04:23.320
<v Speaker 1>Thanks for listening, and here's to making the most of

0:04:23.400 --> 0:04:32.680
<v Speaker 1>our time. Hey, everybody, I'd love to hear from you.

0:04:32.680 --> 0:04:35.559
<v Speaker 1>You can send me your tips, your questions, or anything else.

0:04:36.320 --> 0:04:39.920
<v Speaker 1>Just connect with me on Twitter, Facebook, and Instagram at

0:04:39.920 --> 0:04:44.800
<v Speaker 1>Before Breakfast pod. That's b E the number four, then

0:04:44.839 --> 0:04:48.240
<v Speaker 1>Breakfast p o D. You can also shoot me an

0:04:48.279 --> 0:04:52.080
<v Speaker 1>email at Before Breakfast podcast at i heeart media dot

0:04:52.080 --> 0:04:55.040
<v Speaker 1>com that Before Breakfast is spelled out with all the letters.

0:04:55.640 --> 0:04:57.719
<v Speaker 1>Thanks so much, I look forward to staying in touch.

0:05:03.560 --> 0:05:06.640
<v Speaker 1>Before Breakfast is a production of I heart Radio. For

0:05:06.760 --> 0:05:09.800
<v Speaker 1>more podcasts from I heart Radio, visit the I heart

0:05:09.839 --> 0:05:13.200
<v Speaker 1>Radio app, Apple Podcasts, or wherever you listen to your

0:05:13.240 --> 0:05:15.000
<v Speaker 1>favorite shows. Yeah,