WEBVTT 00:00:09.609 --> 00:00:15.046 Let's face it: planning is important, but the reality is, priorities change. 00:00:15.399 --> 00:00:18.369 People who are successful at effectively managing priorities 00:00:18.370 --> 00:00:21.849 have one thing in common: they use a variety of techniques 00:00:21.850 --> 00:00:23.630 to help them stay on top. 00:00:23.996 --> 00:00:28.718 Let's take a look at seven quick examples of people dealing with shifting priorities. 00:00:28.860 --> 00:00:32.042 As you watch, notice how they ask questions to help determine 00:00:32.067 --> 00:00:36.183 what needs to be addressed first in constantly changing situations. 00:00:36.310 --> 00:00:40.355 Let's back up a minute. When exactly does this project need to be completed? 00:00:41.565 --> 00:00:45.998 Now, you said that supply and purchasing are having problems with each other. 00:00:46.091 --> 00:00:49.551 What did you see and hear when these problems were happening? 00:00:51.000 --> 00:00:54.217 It's got to go through legal and be proofed and printed all by the end of the month. 00:00:54.242 --> 00:00:56.502 Is the timeline overwhelming you? 00:00:57.791 --> 00:01:00.738 Look, I don't mind doing what it takes, but I'm really struggling 00:01:00.739 --> 00:01:02.714 with this particular situation. 00:01:04.397 --> 00:01:08.813 It's just that everybody on the team is coming from a different place on this one. 00:01:08.838 --> 00:01:11.435 Well, what if we got all of the key players from both 00:01:11.460 --> 00:01:15.058 departments around the table and worked until we had a clear agenda 00:01:15.083 --> 00:01:17.255 of what we need to deal with together? 00:01:18.769 --> 00:01:21.014 So the goal is to get the stock codes synced up. 00:01:21.039 --> 00:01:23.071 Do you see any problems with that? 00:01:24.680 --> 00:01:28.374 Okay, so the real issue isn't necessarily the timeline as it is getting 00:01:28.399 --> 00:01:31.105 everybody on the same page so that you can meet the deadline, right? 00:01:31.130 --> 00:01:32.361 Yeah, that's it. 00:01:39.079 --> 00:01:41.918 Now let's take a look at two examples of ways you can use 00:01:41.943 --> 00:01:45.942 effective communication to manage shifting priorities and interruptions. 00:01:45.967 --> 00:01:47.577 Greg? Yeah. 00:01:47.602 --> 00:01:49.889 I need you to do me a big favor. What's that? 00:01:49.914 --> 00:01:52.618 I just got off the phone with Maxwell's purchasing manager. 00:01:52.643 --> 00:01:54.450 They want a bid on their desk by tomorrow morning. 00:01:54.476 --> 00:01:55.563 Well, good for them. 00:01:55.672 --> 00:01:58.433 I know you're busy, but I could really use some help putting this thing together. 00:01:58.458 --> 00:02:02.103 I mean, I can do most of it, but I need somebody to review the specs. 00:02:02.227 --> 00:02:05.822 Well, I can't do it right now. But I've got some time later on. 00:02:05.847 --> 00:02:09.528 If you leave it with me, I can look at it, get it back to you by 4:00 if that's all right. 00:02:09.553 --> 00:02:11.854 Thanks, Greg. I owe you one. Yeah. 00:02:15.174 --> 00:02:18.113 You wanted to see me? Oh, yeah, come on in, Bruce. 00:02:18.138 --> 00:02:20.458 I know that you're swamped, but I need a favor. 00:02:20.483 --> 00:02:21.565 What's that? 00:02:21.622 --> 00:02:25.567 I need you to go through this and give me a breakdown on the reject rate by vendor. 00:02:25.668 --> 00:02:29.460 And I need it as soon as possible, by friday at the latest. 00:02:29.513 --> 00:02:32.794 Well, here's the situation: I've blocked off the next two days 00:02:32.819 --> 00:02:35.159 for getting matt trained on the new order entry system. 00:02:35.184 --> 00:02:37.975 That's right. I forgot that you were going to do that, but I remember. 00:02:38.050 --> 00:02:40.897 So what I can do is have it done by monday, 00:02:40.922 --> 00:02:42.530 unless you want me to reschedule matt. 00:02:42.557 --> 00:02:46.620 No, no, if he doesn't get those orders in right, everything wIll get screwed up. 00:02:46.708 --> 00:02:50.271 I'll live with monday. Thank you for your help. No problem.