WEBVTT 00:00.638 --> 00:01.666 [SPEAKER_00]: I'm Jamie Cochran. 00:01.767 --> 00:02.735 [SPEAKER_02]: I'm Lake Babin. 00:02.755 --> 00:03.461 [SPEAKER_00]: Weed wind. 00:03.643 --> 00:05.417 [SPEAKER_02]: I'm extreme watershed podcast. 00:06.798 --> 00:14.289 [SPEAKER_00]: back with another episode of the lead win podcast, and we have, back with us today, J.P. to know one of our leadership instructors at Eshelon front. 00:14.349 --> 00:21.800 [SPEAKER_00]: And the topic for today is simple, specifically simple plans, and simple communication. 00:21.880 --> 00:28.430 [SPEAKER_00]: How do we as leaders ensure there's alignment across our teams, and they can go and execute on the things that we're asking them to do? 00:28.930 --> 00:30.713 [SPEAKER_00]: And it's all about this principle of simple. 00:31.073 --> 00:33.497 [SPEAKER_00]: So what do we mean when we say simple leave? 00:33.646 --> 00:35.730 [SPEAKER_02]: we all have a tendency to overcomplicate things. 00:36.411 --> 00:42.902 [SPEAKER_02]: I mean, and I think the scary thing about this is everyone knows that you should simplify stuff. 00:42.983 --> 00:57.949 [SPEAKER_02]: Everyone knows that, I mean, the kiss principle keep it simple stupid was that had been taught to me by veterans and my community and certainly by the not commission officers at the Naval Academy when I was there. 00:57.929 --> 01:06.259 [SPEAKER_02]: And yet the first time that I'm put in charge of coming up with a plan as a young junior officer in the seal teams, I come up with a super complex plan that nobody can understand. 01:06.879 --> 01:15.669 [SPEAKER_02]: And even though I think I'm actually keeping an example, and we used to see this in training, we're running training the seal teams where you tell people, hey, come up with a simple plan. 01:15.689 --> 01:17.151 [SPEAKER_02]: You don't want to make sure everybody understands it. 01:17.732 --> 01:27.463 [SPEAKER_02]: And so you'd have a 40 plus man seal task unit that decides to split each of their guys up 01:27.443 --> 01:42.005 [SPEAKER_02]: So you've got dozens of two-man shooter pairs running around instead of having a squad, you know, of eight guys or a fire team of four guys, and and in their mind like, oh, yeah, it is I, I remember talking to that particular task, you said, hey, you know, you feel like they're playing a simple. 01:42.025 --> 01:42.887 [SPEAKER_02]: Oh, yeah, it's totally simple. 01:42.867 --> 01:48.096 [SPEAKER_02]: But it's the reality, in their mind, they thought it was simple, the reality is it's highly complex. 01:48.397 --> 01:56.652 [SPEAKER_02]: Because now you have all these different units out there that are running around doing their own thing, talking on the radio, and it was absolute disaster. 01:56.732 --> 02:01.821 [SPEAKER_02]: So we actually had to come back from that debrief and talk about what keeping it simple actually meant. 02:01.801 --> 02:17.515 [SPEAKER_02]: And that's really the trap because, you know, we come out of meeting, I've done a bunch of talking, and I feel like, hey, yeah, Jamie and JP know exactly what I said, because I'm the perfect communicator, and I communicate in a manner that's simple care concise because I teach these principles. 02:17.495 --> 02:33.838 [SPEAKER_02]: And the reality is, you guys are like, I don't know what you're talking about, that was super complex, I took something away, but maybe that wasn't when I actually meant, are you misinterpreted something, or you misunderstood something, then I said, or I poorly communicated, even though it was simply, it was clear in my mind, it wasn't clear to you. 02:34.498 --> 02:44.232 [SPEAKER_02]: And so that's really the danger is that we think it's simple, and the only test that really matters is that the people you're trying to communicate with actually get it. 02:44.652 --> 02:45.814 [SPEAKER_02]: That's the only test that matters. 02:46.115 --> 02:52.988 [SPEAKER_00]: Yeah, and the measurement of your success is a leader as to whether or not you're communicating effectively is whether or not your team is executing. 02:53.008 --> 03:00.623 [SPEAKER_00]: If our team is an executing, it's our instinct as leaders to look at them and question what they are doing wrong. 03:00.703 --> 03:06.655 [SPEAKER_00]: Why are they not able to execute on this task or we've assigned them as opposed to looking inward and thinking, 03:06.635 --> 03:10.921 [SPEAKER_00]: Oh, this is a this is a function of me not being able to communicate effectively. 03:11.341 --> 03:18.712 [SPEAKER_00]: If I was communicating in a simple clearing concise manner, my team has a much higher potential of actually executing on the task. 03:18.732 --> 03:19.573 [SPEAKER_00]: That should be our measure. 03:19.633 --> 03:25.220 [SPEAKER_00]: If our team isn't doing what we're asking them to do, it's because we're not communicating in a way that they can actually go and execute. 03:26.002 --> 03:33.672 [SPEAKER_01]: I remember just, especially for my time in the sealed teams and then in business 03:34.613 --> 03:57.136 [SPEAKER_01]: saying that life says all the time and I remember when I first started working at echelon front, getting to do, you know, keynotes and workshops with life in Jaco and, you know, listening to them and, you know, helping assist on Q and A's at the beginning and then actually getting to do like the workshops and keynotes with them whenever we would talk about our second law combat simple and it came to communication. 03:57.856 --> 04:03.642 [SPEAKER_01]: Life has always said there's only two measures 04:03.622 --> 04:08.351 [SPEAKER_01]: There's no gray zone, it's black or white, either it works or it doesn't work. 04:09.052 --> 04:14.963 [SPEAKER_01]: And that's hard because as leaders, like you guys are saying, we feel like our communication is effective and it's good. 04:14.983 --> 04:25.883 [SPEAKER_01]: And the mistake that we make when we're communicating with people on our team and our family or just anybody in general is we ask a question, did that make sense? 04:25.863 --> 04:40.779 [SPEAKER_01]: or hey does anybody have any questions and people don't ask questions and most of time it's not because they're afraid to ask questions it's in their mind they legitimately don't have any questions because what they heard communicated made sense to them. 04:40.799 --> 04:42.443 [SPEAKER_01]: So when we say hey does anybody have any questions? 04:42.644 --> 04:43.686 [SPEAKER_01]: Nobody ask questions. 04:43.666 --> 05:09.825 [SPEAKER_01]: and then we just put it like for our own little like cherry on top to solidify how good our communication was we say all right so did that make sense and then my team's not in their heads they go off they do the work or the task and clearly it did not make sense because whatever they were doing was wrong or it wasn't done the right way and you know we get frustrated and who do we get frustrated with primarily? 05:10.177 --> 05:13.441 [SPEAKER_01]: Initially, it's them, you know, that was joking. 05:13.461 --> 05:14.763 [SPEAKER_01]: I don't do workshops at echelon front. 05:14.783 --> 05:20.491 [SPEAKER_01]: I'm like, hey, you know, if you have kids, you know exactly what I'm talking about because you'll be communicating with your kids. 05:20.511 --> 05:23.635 [SPEAKER_01]: I'm like, all right, hey, you know, and then they go do something the wrong way. 05:23.875 --> 05:32.847 [SPEAKER_01]: And it's easy for us to get frustrated with other people, not doing things properly after our brief or our communication with them. 05:32.867 --> 05:34.429 [SPEAKER_01]: But what we're missing is alignment. 05:35.236 --> 05:42.867 [SPEAKER_00]: Yeah, and I think what a lot of leaders don't realize is that most mistakes come from unclear directions and expectations, not incompetence. 05:43.608 --> 05:48.936 [SPEAKER_00]: And that's something we as leaders need to recognize that our control in the situation is how we're communicating with our team. 05:49.397 --> 05:56.367 [SPEAKER_00]: We do an exercise that actually on front, and without giving too much away, essentially we give two teams, two different sets of instructions. 05:56.347 --> 06:04.997 [SPEAKER_00]: And on one hand, there is a, let's just call it Shakespearean explanation of what the team is supposed to do. 06:05.037 --> 06:08.402 [SPEAKER_00]: And on the other one, it is broken down into three bullet points. 06:08.882 --> 06:11.105 [SPEAKER_00]: And in bulls scenarios, they have the same amount of time. 06:11.425 --> 06:18.914 [SPEAKER_00]: One group has the most simple set of instructions and tasks, but it's communicated in this very complicated Shakespeare language. 06:19.375 --> 06:21.778 [SPEAKER_00]: The other group has a much more complicated task. 06:21.798 --> 06:25.442 [SPEAKER_00]: They have to complete actually several tasks within their minute. 06:25.422 --> 06:31.352 [SPEAKER_00]: And what we see every time is the group with the simple clear and concise instructions execute efficiently. 06:31.412 --> 06:33.896 [SPEAKER_00]: And at the end of it, they feel like, yeah, we accomplished that. 06:33.956 --> 06:35.379 [SPEAKER_00]: We did what we were asked to do. 06:36.020 --> 06:43.212 [SPEAKER_00]: While the other group who's dealing with the Shakespeare takes almost a whole minute just to read it and try to decipher what the instructions are saying. 06:43.192 --> 06:48.861 [SPEAKER_00]: Most of the time they end up completing the task, but the end result is when you ask them, hey, did you complete your task? 06:48.881 --> 06:51.666 [SPEAKER_00]: There's always a sense of uncertainty, like, I think we did. 06:51.706 --> 06:52.588 [SPEAKER_00]: I'm not really sure. 06:52.608 --> 07:00.120 [SPEAKER_00]: And my message to leaders when we talk about this is hey, listen, you don't realize it, but you are overestimating. 07:00.100 --> 07:02.344 [SPEAKER_00]: your ability to communicate effectively with your team. 07:02.825 --> 07:20.016 [SPEAKER_00]: You are speaking to them in Shakespeare, and they are trying their best execute on what you're asking of them, and they're not able to do it because they can't understand the directions, and they can't understand the expectations, because you're speaking to them in some version of your own way of Shakespeare. 07:20.249 --> 07:27.435 [SPEAKER_02]: that's an outstanding exercise and it just points out like how how can you say yes we could put it to the task with confidence when you don't even know what the task was. 07:27.996 --> 07:50.256 [SPEAKER_02]: I mean it's just it's just it seems obvious and yet we do this stuff all the time right and yet we might not be writing in Shakespeare but we're sending out you know a three page email and thinking that I communicate effectively and you know J. P. pulled out from you know paragraph seven sentenced three exactly the information that I wanted him to to see when J. P. 07:50.236 --> 07:52.119 [SPEAKER_02]: 250 emails that morning. 07:52.359 --> 07:54.042 [SPEAKER_02]: Maybe he's not even in front of his email right now. 07:54.102 --> 07:58.929 [SPEAKER_02]: He's out, you know, away from his desk doing some stuff in the field, running training, whatever it is. 07:59.009 --> 08:03.837 [SPEAKER_02]: So, and then in my mind, like, I've communicated perfectly what I want him to do and why his knee falling up with me. 08:04.518 --> 08:07.202 [SPEAKER_02]: It's one of the hardest places to apply extreme ownership. 08:07.482 --> 08:09.325 [SPEAKER_02]: It really is because. 08:09.305 --> 08:10.127 [SPEAKER_02]: I get frustrated. 08:10.187 --> 08:15.116 [SPEAKER_02]: I told Jamie exactly what, you know, I wanted to have happened and she's doing something entirely different. 08:15.717 --> 08:21.428 [SPEAKER_02]: And instead of actually like, okay, why is Jamie doing something different than I thought I clearly communicated to her to do? 08:22.150 --> 08:23.613 [SPEAKER_02]: Obviously, I wasn't clear, right? 08:23.633 --> 08:26.959 [SPEAKER_02]: It's it's back to the effective or ineffective and the only way you're going to know that is. 08:26.939 --> 08:28.041 [SPEAKER_02]: if you use the readback, right? 08:28.061 --> 08:33.148 [SPEAKER_02]: The tool that we teach of asking not, hey, are there any questions? 08:33.168 --> 08:39.838 [SPEAKER_02]: Like you said, JP, or even do you understand, because people will kind of fake it, tell they make it, nobody wants to admit, they don't understand what's going on. 08:40.620 --> 08:48.812 [SPEAKER_02]: And so you actually have to use the readback, which is just asking a question of, can you talk me back through what we just talked about? 08:48.792 --> 08:50.334 [SPEAKER_02]: And that is not a test for those people. 08:50.394 --> 08:54.859 [SPEAKER_02]: It's a test for yourself and how you communicated and whether or not you were effective. 08:55.439 --> 08:57.782 [SPEAKER_02]: And what's interesting about it is it's different for different people. 08:57.822 --> 09:04.309 [SPEAKER_02]: Because I might say something and Jamie, you clearly understood what I was trying to get across. 09:04.349 --> 09:06.832 [SPEAKER_02]: You were able to drive out and execute with confidence. 09:06.852 --> 09:10.296 [SPEAKER_02]: And JP just didn't process that at all for whatever reason. 09:11.037 --> 09:18.765 [SPEAKER_02]: And our vice versa, I sent an army mail, but JP got the email and he's making it happen, but you didn't happen to see the email or you got my party with a bunch of other stuff. 09:18.745 --> 09:29.540 [SPEAKER_02]: And so it's different for different people, and but that readback to is powerful as a task for whether or not our communications are simple, clear, good size, and that and we can make adjustments. 09:30.261 --> 09:36.730 [SPEAKER_02]: And again, it's not a task for whether or not people are paying attention to the tests for you and whether or not you communicated clearly. 09:37.130 --> 09:42.778 [SPEAKER_02]: And it's one of the simplest things that we encourage leaders to implement, and it makes a massive difference in communication. 09:43.045 --> 09:45.847 [SPEAKER_00]: We teach a lot of practical things in echelon front. 09:45.867 --> 09:46.888 [SPEAKER_00]: A lot of practical things. 09:47.189 --> 09:55.956 [SPEAKER_00]: I would argue the readback is one of the most effective practical tools, teams and leaders can implement within their organizations. 09:56.096 --> 09:58.819 [SPEAKER_00]: And within their families, hey, I used to read back all the time with my kids. 09:58.879 --> 10:01.781 [SPEAKER_00]: It's an amazing tool to ensure that alignment. 10:02.622 --> 10:05.244 [SPEAKER_00]: And you guys work with clients all the time as do I. 10:05.284 --> 10:06.686 [SPEAKER_00]: And I think we would all agree. 10:06.726 --> 10:11.770 [SPEAKER_00]: The readback is a tool that is allowed teams to correct 10:11.750 --> 10:16.761 [SPEAKER_00]: for communication at every level in the organization and ensure alignment up down across the chain of command. 10:17.263 --> 10:17.824 [SPEAKER_01]: Absolutely. 10:18.084 --> 10:22.755 [SPEAKER_01]: And when these organizations start implementing the rebound, 10:23.596 --> 10:25.980 [SPEAKER_01]: the return on that investment is immediate. 10:27.022 --> 10:30.667 [SPEAKER_01]: It doesn't take anything other than a little bit of extra time. 10:31.288 --> 10:36.777 [SPEAKER_01]: And I think, you know, some people, they're a little hesitant to do in the rebound because it's something new. 10:37.318 --> 10:38.540 [SPEAKER_01]: They're not comfortable with it. 10:38.861 --> 10:42.887 [SPEAKER_01]: They don't know how to structure it properly and, you know, when we're working with clients, 10:42.867 --> 10:43.609 [SPEAKER_01]: Welcome through that. 10:43.649 --> 10:56.036 [SPEAKER_01]: We coach and we might even do role plays with them of how to implement a readback and there's there's definitely a right way to do it and there's a wrong way to do it and the best way to do it is to introduce it to your team before you're going to implement it. 10:56.076 --> 10:57.940 [SPEAKER_01]: So if I'm going to sit down with my team. 10:57.920 --> 11:03.968 [SPEAKER_01]: And I want to implement the Reback before I start that meeting or that brief or the plan of the day or the safety brief. 11:04.108 --> 11:11.778 [SPEAKER_01]: I want to tell my team ahead of time about the Reback, what it is, the purpose of the Reback is for alignment and let them know. 11:12.318 --> 11:15.603 [SPEAKER_01]: And you know, I would say, hey, Jane, I could use your help when we get down with the safety brief. 11:15.923 --> 11:19.067 [SPEAKER_01]: I'm going to have you live in a few other people. 11:19.047 --> 11:29.563 [SPEAKER_01]: brief back to me what we talked about so that I can make sure my communication was simple clearing concise and I also want to know what I need to do to to best support you guys throughout the day. 11:30.304 --> 11:34.771 [SPEAKER_01]: What's the likelihood of you and I have just a somewhat decent working relationship? 11:34.931 --> 11:35.993 [SPEAKER_01]: You say no to that. 11:36.563 --> 11:37.204 [SPEAKER_00]: very low. 11:37.404 --> 11:40.188 [SPEAKER_01]: Yeah, and if you do, okay, cool, no factor. 11:40.569 --> 11:43.693 [SPEAKER_00]: Well, and if you're framing it as like, hey, this is a test for me. 11:43.874 --> 11:44.094 [SPEAKER_00]: Yes. 11:44.134 --> 11:48.721 [SPEAKER_00]: Not as like a test for, I think that's where people screw up, which is that they use the readback. 11:49.021 --> 11:51.405 [SPEAKER_00]: And instead, they say, hey, JP, can you give me a readback? 11:51.765 --> 11:53.728 [SPEAKER_00]: But they don't caveat with the reason why. 11:53.748 --> 11:54.109 [SPEAKER_00]: Yes. 11:54.129 --> 11:58.695 [SPEAKER_00]: So it can feel like, hey, so I made sure that you were listening and you understand. 11:58.916 --> 11:59.076 [SPEAKER_00]: Yeah. 11:59.096 --> 11:59.196 [SPEAKER_00]: Yeah. 11:59.176 --> 12:02.706 [SPEAKER_00]: You have to frame it as, hey, I don't always communicate effectively. 12:02.766 --> 12:03.769 [SPEAKER_00]: I've got a lot going on. 12:04.050 --> 12:04.852 [SPEAKER_00]: Can you give me a readback? 12:04.873 --> 12:07.259 [SPEAKER_00]: I want to make sure I didn't miss anything of importance. 12:07.520 --> 12:08.423 [SPEAKER_01]: Yes, absolutely. 12:09.025 --> 12:11.953 [SPEAKER_01]: And I know that 12:12.119 --> 12:18.911 [SPEAKER_01]: If I'm asking you in life and a few other people to brief it back to me, I know that you're going to be paying more attention, but that's a byproduct. 12:19.372 --> 12:24.301 [SPEAKER_01]: The intent behind the Reback is not to test if you're listening or taking proper notes. 12:24.742 --> 12:28.208 [SPEAKER_01]: The intent for the Reback is my communicator. 12:28.288 --> 12:30.051 [SPEAKER_01]: It's a test of my communication. 12:30.372 --> 12:31.093 [SPEAKER_01]: Was it effective? 12:31.133 --> 12:33.958 [SPEAKER_01]: Yes or no. 12:33.938 --> 12:44.145 [SPEAKER_01]: You know, and then I just, you know, ask a few people, let them know, you know, and I might even say, like, hey, we're, you know, we're going to get started in a few minutes if you guys want to go grab some notebooks to take notes for free. 12:44.185 --> 12:44.906 [SPEAKER_01]: We have that time. 12:44.967 --> 12:48.977 [SPEAKER_01]: And you know, when we get down with it, we do the rebound. 12:48.957 --> 12:54.487 [SPEAKER_01]: And if you brief back to me something that is wrong, I don't say, hey, why weren't you paying attention and why didn't you take notes? 12:54.828 --> 13:01.340 [SPEAKER_01]: It's an opportunity for me to take ownership over my communication that clearly was not simple, clear and concise. 13:01.400 --> 13:07.551 [SPEAKER_01]: And when you do that, you build trust with your people, you have a little more influence, which is how we lead people. 13:08.132 --> 13:09.835 [SPEAKER_01]: And that time, 13:09.815 --> 13:17.623 [SPEAKER_01]: that I know everyone's limited on on the back end is always going to be less time than what it would take to go fix a mistake. 13:17.644 --> 13:37.425 [SPEAKER_01]: You know, I had a construction company two years ago, one of the superintendents after the half day workshop I did with them that evening sent me a message on Instagram and he said, hey, that that rebound that we talked about that you that you taught us today, I implemented it and it saved us a couple hundred thousand dollars today of 13:37.557 --> 14:03.075 [SPEAKER_01]: That's incredible, and so we talked, we went back and forth, and he said he implemented it with his team, and he explained the purpose of alignment, him wanting to make sure his communication was clear and concise, and one of his foremen, you know, when he was briefing him back with the information, he told me that if that foreman who was a square of a foreman would have went and started doing the work, that he thought they needed to be doing, because it was such a large 14:03.055 --> 14:12.677 [SPEAKER_01]: decentralized project that by time he would have figured out what was going on, it would have cost them a couple hundred thousand dollars in rework. 14:12.927 --> 14:14.649 [SPEAKER_01]: And he just wanted to say, thank you for that. 14:14.689 --> 14:22.958 [SPEAKER_01]: But the cool thing is this superintendent also reached out to all the other superintendents that had been in that training and said, hey, I implemented the re-backed this morning. 14:24.319 --> 14:25.841 [SPEAKER_01]: It's a non-negotiable for our team now. 14:26.041 --> 14:26.542 [SPEAKER_01]: Here's why. 14:26.802 --> 14:27.803 [SPEAKER_01]: This is what it saved us. 14:27.843 --> 14:30.266 [SPEAKER_01]: We're doing re-backs and debriefs every day. 14:30.306 --> 14:33.149 [SPEAKER_01]: The other superintendents, they recognized the value. 14:33.189 --> 14:34.931 [SPEAKER_01]: They did the same thing. 14:35.091 --> 14:38.935 [SPEAKER_01]: And when this company got done with this very large project, 14:38.915 --> 14:44.180 [SPEAKER_01]: They were a head of schedule under budget and safety scores looked better than they had ever looked before. 14:44.661 --> 14:48.024 [SPEAKER_01]: Moral was, you know, was better than it had ever been. 14:48.124 --> 14:55.992 [SPEAKER_01]: And to your point, the rebound is something that you can implement right now that will have an immediate effect on your on your team. 14:56.232 --> 14:57.934 [SPEAKER_00]: Yeah, and it works up the chain of came in, too. 14:58.475 --> 15:08.905 [SPEAKER_00]: You know, we're talking about how you might implement this as a leader with your team, but at echelon front, when you build a culture of using the rebound, it works in 15:09.205 --> 15:10.388 [SPEAKER_00]: Give me information. 15:10.448 --> 15:15.739 [SPEAKER_00]: I'm quick to say, hey, real quick, if I want to give you a readback piece, I want to make sure I understand what you're asking of me. 15:16.200 --> 15:18.505 [SPEAKER_00]: So if you're on the front lines, you can use a readback, too. 15:18.906 --> 15:21.271 [SPEAKER_00]: And by doing that, it shows your boss that you've listened to him. 15:21.311 --> 15:22.594 [SPEAKER_00]: You care about what he has to say. 15:22.935 --> 15:25.541 [SPEAKER_00]: You care about the plan that he's put in place. 15:25.781 --> 15:26.683 [SPEAKER_00]: And you want to get it right. 15:26.984 --> 15:28.547 [SPEAKER_00]: Even if your boss isn't, 15:28.527 --> 15:39.201 [SPEAKER_00]: implementing the readback in that way, you can start to build that culture of the readback by doing it yourself with your peers and up the chain with your leadership that creates that sense of alignment by me saying, hey, late, can I give you a quick readback? 15:39.221 --> 15:40.823 [SPEAKER_00]: I want to make sure I understand what you need of me. 15:41.063 --> 15:41.664 [SPEAKER_02]: No question. 15:41.744 --> 15:44.247 [SPEAKER_02]: It goes up down and across the chain of command. 15:44.488 --> 15:47.832 [SPEAKER_02]: And I think that's this is something that the team does so well. 15:48.052 --> 15:56.543 [SPEAKER_02]: You know, at echelon front is we're talking about a bunch of stuff and we're throwing out a bunch of different ideas, but to capture that, you know, hey, life, I just 15:56.523 --> 16:01.169 [SPEAKER_02]: You know, that these are the five things we should be focused on right for the next month or the next quarter. 16:01.770 --> 16:02.731 [SPEAKER_02]: And that works really well. 16:02.771 --> 16:10.221 [SPEAKER_02]: I think a practical way to implement this is using an alternative form of communication. 16:10.262 --> 16:13.786 [SPEAKER_02]: If we're talking in person, then I can send an email, right? 16:13.866 --> 16:18.152 [SPEAKER_02]: If we're having a phone call, I can send an email to fall from a feedback. 16:18.593 --> 16:23.239 [SPEAKER_02]: If I'm sending an email, that's got a bunch of information in it. 16:23.219 --> 16:29.488 [SPEAKER_02]: then how often Jamie, you'll pick up the phone and call me and say, hey, I just want to make sure I'm tracking on this and that I understand what your intent is here. 16:30.029 --> 16:35.577 [SPEAKER_02]: And that's that's a form of a readback just to clarify to make sure that you're pulling out the most important information. 16:35.597 --> 16:38.742 [SPEAKER_02]: So you're using a phone call to do that to clarify an email. 16:39.282 --> 16:41.025 [SPEAKER_02]: If you're sending out an important email, 16:41.461 --> 16:43.523 [SPEAKER_02]: You ought to follow up with a text message or a phone call. 16:43.543 --> 16:54.455 [SPEAKER_02]: Like it's just the idea that someone's going to read that and understand perfectly what you're meaning and how important it is in, you know, it just gets buried in all the other stuff that's there. 16:54.535 --> 16:59.080 [SPEAKER_02]: So, you know, some people get pretty upset if you don't have an immediate response to an email. 16:59.801 --> 17:07.249 [SPEAKER_02]: And yet, when people are actually practically just outdoing things and engaged in life for work, a lot of people aren't sitting in front of their desk. 17:07.229 --> 17:13.158 [SPEAKER_02]: which other people that are sitting in front of a desk most of the day have sometimes have a hard time understanding that. 17:13.178 --> 17:16.103 [SPEAKER_02]: So I think just seeing other people's perspectives is really important. 17:16.784 --> 17:20.570 [SPEAKER_02]: And really, at the end of the day, what would we talk about here for communication? 17:21.091 --> 17:22.433 [SPEAKER_02]: How do you keep things simple, clear, concise? 17:22.493 --> 17:23.955 [SPEAKER_02]: It's really just, 17:23.935 --> 17:25.316 [SPEAKER_02]: theory versus reality, right? 17:25.416 --> 17:30.621 [SPEAKER_02]: In theory, I should be able to send you a three-page email and you should process all that perfectly, right? 17:30.661 --> 17:42.633 [SPEAKER_02]: I should, JP, I should be able to stand up in front of the, you know, of the, of the, the, the platoon in a mission planning space and talk about what we're going to do and everyone should process that perfectly and understand what we're going to do. 17:43.134 --> 17:44.515 [SPEAKER_02]: It, it doesn't work that way, right? 17:44.535 --> 17:46.176 [SPEAKER_02]: People are thinking about other things. 17:46.757 --> 17:47.097 [SPEAKER_02]: We used it. 17:47.117 --> 17:52.963 [SPEAKER_02]: We had instructors going through Buds and an SKTJP, you remember they, they would 17:53.146 --> 18:15.366 [SPEAKER_02]: I'm putting out the word you guys right now and this is pretty important and you're thinking what you're hearing right now is blah, blah, blah, blah, blah, blah, blah, what am I doing on Friday night right and that's that is actually the reality of a bunch of bug students that are tired you know or and particularly when people are hungry, people are tired, people are thinking about the things that they want to do. 18:15.606 --> 18:20.571 [SPEAKER_02]: If you're trying to give an important presentation to people at 5 p.m. on Friday, 18:20.551 --> 18:23.674 [SPEAKER_02]: When they're trying to get out for the weekend, they're not paying attention to what's going on. 18:23.694 --> 18:26.758 [SPEAKER_02]: If they've been up all night, they're probably not paying attention to what's going on. 18:26.778 --> 18:27.739 [SPEAKER_02]: They're thinking about other things. 18:28.079 --> 18:29.781 [SPEAKER_02]: And so that's just the reality. 18:30.081 --> 18:40.592 [SPEAKER_02]: What we're trying to do, that's all front is provide practical tools that people can implement immediately in the realities of their lives, of their worlds, and that's what this is. 18:40.692 --> 18:41.894 [SPEAKER_02]: It's theory versus reality. 18:42.234 --> 18:45.057 [SPEAKER_02]: In theory, everyone should process all of the information. 18:45.037 --> 18:51.365 [SPEAKER_02]: My wife will tell me, hey, I need you to pick up the kids at 330 after school and take them to the their dental appointments. 18:52.065 --> 18:53.848 [SPEAKER_02]: She says that to me, but guess what? 18:53.868 --> 18:54.909 [SPEAKER_02]: I was thinking about something else. 18:55.289 --> 19:02.718 [SPEAKER_02]: I was dealing with something else, or I lost track of it, and I might actually need a fall, but I'm like, hey, this is a reminder, what time am I picking them up again? 19:02.858 --> 19:05.061 [SPEAKER_02]: If I have that in a text message, I can reference it. 19:05.361 --> 19:12.630 [SPEAKER_02]: So, it's theory versus reality, deal with reality so that you can be successful because theory is not going to work. 19:12.965 --> 19:19.499 [SPEAKER_00]: Yeah, and the key to all of this and communicating in a simple clear and concise manner is that it takes a lot of effort. 19:19.559 --> 19:20.501 [SPEAKER_00]: That's why people don't do it. 19:20.561 --> 19:31.986 [SPEAKER_00]: It's a whole lot easier for me to just give you a running stream of what's going on in my mind as opposed to taking the time to simplify and ensure that the way I'm communicating is clear and concise. 19:31.966 --> 19:33.928 [SPEAKER_00]: And that, there's a bunch of tools we can use. 19:34.229 --> 19:38.634 [SPEAKER_00]: If you're sending emails, don't send the seven paragraph email, there's seven page email. 19:38.654 --> 19:45.862 [SPEAKER_00]: And in certain situations where yes, you might need to provide a little more information, start with the tool of using the bluff bottom line up front. 19:46.302 --> 19:52.429 [SPEAKER_00]: Give the person or the people that you're sending this message to and understanding of what the real goal is right up front. 19:52.830 --> 19:55.252 [SPEAKER_00]: Then you can backfill with some of the more detailed information. 19:55.673 --> 19:59.357 [SPEAKER_00]: In the same way, if I'm going to go put out word to my team, I'm going to take 19:59.337 --> 20:17.168 [SPEAKER_00]: time to write that out to have a plan to make sure that I've got some bullet points of how I'm going to go through this so I can be as simple clear and concise as possible or in certain situations when I might be putting out word that is going to be maybe potentially misconstrued or have emotions around it. 20:17.469 --> 20:19.472 [SPEAKER_00]: I'm going to take that chance to 20:19.452 --> 20:22.115 [SPEAKER_00]: role play with a trusted agent and get feedback on that. 20:22.135 --> 20:23.137 [SPEAKER_00]: Hey, did this make sense? 20:23.557 --> 20:25.940 [SPEAKER_00]: How can I anticipate the team to react? 20:26.261 --> 20:33.710 [SPEAKER_00]: There's all these different tools that we can implement, but the key here is as leaders, we have to do the work to be more simple. 20:33.890 --> 20:40.659 [SPEAKER_00]: It's a lot more work, but the outcome is so much better when we can communicate in a way that allows our team to actually go and execute. 20:41.260 --> 20:41.460 [SPEAKER_01]: I love it. 20:41.440 --> 20:45.646 [SPEAKER_00]: immediate action drill for this week is to implement the readback. 20:45.686 --> 20:51.614 [SPEAKER_00]: We have likely talked about using the readback in other episodes because this is a very practical tool. 20:51.994 --> 20:59.745 [SPEAKER_00]: So what I want you to do this week is look for something that you need to communicate with a team, take the time to simplify it to the best of your ability. 21:00.045 --> 21:04.552 [SPEAKER_00]: And at the end of that, ask for that readback, not as a test for them, but as a test for you. 21:04.652 --> 21:07.836 [SPEAKER_00]: So you can ensure your 21:07.900 --> 21:13.694 [SPEAKER_02]: any time that you're frustrated with somebody for not doing what you think you clearly told them to do. 21:13.734 --> 21:14.617 [SPEAKER_02]: Don't look at them. 21:14.637 --> 21:15.699 [SPEAKER_02]: Don't point fingers at them. 21:15.880 --> 21:16.501 [SPEAKER_02]: Look at yourself. 21:16.561 --> 21:19.068 [SPEAKER_02]: Take ownership of keeping it simple. 21:19.428 --> 21:22.095 [SPEAKER_02]: And if you do that, you'll lead and win.