The Missing Step Between Your Mission and What Actually Gets Done

Craig Coyle: Everyone loves a good mission. Leadership gets in a room, they wrestle with the language, they land on something that actually means something. Not corporate wallpaper, but a real statement of what the team is trying to accomplish and why it matters. And when it gets shared, it lands. Heads nod. A few people actually feel something. But almost nobody knows what's supposed to happen next. Monday morning comes, the floor opens the same way it always has. Same meetings, same handoffs. Same list of what's on fire. Nothing about how the work actually gets done has changed. Because a mission everybody loves and a mission that changes what people do and how they act are completely different things. And nobody has ever been shown how to close that gap. Welcome back to the Frontline Leadership Podcast where we help organizations strengthen and empower the leaders their operations depend on. I'm your host, Craig Coyle, former Apache helicopter pilot, aerospace leader, and founder of Operation Lead. And today, we're closing a loop we opened a couple months ago and taking it one step further than most organizations ever go. Let's dive in. In episode nineteen, we made the case for how your leaders should be communicating, making the people they lead the hero of the story instead of a passive recipient of instructions. Then in episode twenty we went a step further. We gave that communication a structural home, a properly nested mission. Task and purpose translated level by level, all the way to the floor. If you've done that work genuinely, good. That's not nothing. Most organizations will never get that far. But here's what I want you to sit with today. A leader's job is roughly 80% planning and communication. Not motivating, not inspiring. Planning and communicating that plan clearly enough so that it actually moves. A mission statement on its own, even well built one, is neither one of those things. It's not a plan, it's the input to one. The military never stops at the mission. The commander doesn't write the mission, hand it down, and consider the job done. The mission is where planning starts, it's the first dominant. Not the last one. So today we go a layer deeper. To the layer that takes here's where we're headed and why and turns it into here's exactly what has to happen and here's what winning looks like when it does. In the army, once a mission is issued, the next thing every leader has to build is something called Commander's Intent. Commander's Intent is built from three components. The first one, purpose, you already know. That's the why from the task and purpose structure we covered in episode 20. The other two are new and they're the whole point of today's conversation. Key tasks. These are the specific essential actions that must happen for the mission to succeed. Not everything that could happen on the way to the mission, not a full task list, the handful of things that if they don't happen, the mission fails, no matter what else goes right around them. Here's a simple filter for telling a real key task apart from just another item on a list. If this one thing failed, does the mission fail with it? If the answer is no, if the mission still succeeds even without it, it's not a key task. It might be worth doing, it's just not essential. If the answer is yes, you've found one. The second is end state, not a task list either, a picture. What do conditions actually look like once this is done? Not we completed the checklist, but what does done look like or feel like or produce? Here's why this layer exists, and it's the most important thing I'm gonna say today. Commander's intent exists so that people underneath a leader can exercise disciplined initiative. Now, what does that mean? Disciplined initiative means that when conditions change mid-mission, and they always do, a soldier who understands the intent doesn't need to radio back for new orders. They understand what has to happen and what success looks like well enough. To make the right call themselves in real time inside the intent, even when the plan on paper no longer fits the situation in front of them. That's not chaos. That's not figure it out. That's the product of extremely deliberate planning. Planning good enough that it survives contact with changing situation because the people executing it understand the intent behind it and not just the instructions. And there's a second thing Commander's Intent does. That's just as important as the first. It shows every individual exactly where the responsibilities fit inside the larger mission. Think about the difference between being handed a task and understanding your task. Here's what you're doing today as an instruction. Here's what you're doing today, and here's exactly how it connects to what all of us are working toward. That's a completely different experience for the person doing the work. One is a to-do list item that makes you feel like a means to an end. The other is your piece of something bigger, and you could see the shape of it. One clarification because it's easy to get this backwards. Commander's intent is not itself handing out tasks. No, it's the bridge. It's the connective tissue between the mission everyone shares and the individual assignments each person eventually. Receives. It's what makes those individual assignments make sense as part of something bigger instead of landing as a disconnected to-do list from a supervisor who's just trying to get through the day. The task list comes later. Commander's intent is what makes that task list make sense when it arrives. And here's what makes Commander's intent more than just a nice idea. It's the hinge. It's the thing that allows a mission to cascade into real, detailed, executable planning at every single level underneath it. Without it, a mission dead ends. It gets announced, it gets nods, and then everyone underneath is left to guess what it actually requires of them. When that void exists, people don't go out of their way to fill it themselves. They either make an opportunistic guess with minimal effort, or they just write the mission off as another lofty, detached leadership move. But with it, every level down the chain can build their own detailed plan. And that plan still nests perfectly inside the intent above it. Let's go back to the nested example from episode 20 and take it one step further. Remember, we had an executive mission, a plant manager mission, and a frontline supervisor mission. Each one translated down and nested within the level above. At the executive level, the mission was ninety-nine percent on time delivery and a fifteen percent defect reduction by Q4. Now the key tasks underneath that mission, remember that's two or three things that must absolutely happen for it to be possible, might be things like stabilize the top three chronic late order categories, or cut rework time in half at the two highest volume plants, or close the on time delivery gap with the largest customer account. The end state The organization is positioned as a timely and reliable partner with its customers leading into the next fiscal year. Now at the plant manager level, that mission got translated into something specific for one plant. Reduce late to start orders by 5% and cut rework production time by 10% by the end of Q3. The key task that might make that real might be identify and fix the two most common causes of late starts. Get every supervisor trained on the new rework escalation process. Or hit a specific weekly checkpoint on defect rates. The end state, a plant reliably positioned. To expand its production volume without sacrificing speed or quality. And then at the supervisor level, the most concrete layer of all, the key tasks are things a supervisor can point to this week or today. Every planned order starts on time. Every quality flag gets escalated immediately, not ignored until a QC specialist catches the defect in the review. The end state a shift that ends with nothing carried over that shouldn't have been, and a handoff to the next crew that's clean. Here's the major distinction. A supervisor who only has the mission has information. A supervisor who has key tasks and an end state has the beginnings of a plan. Information tells you where things are headed. A plan tells you what you're doing about it today. Those are not the same thing, and an organization that stops at the first one has done real work, but it hasn't finished the job. In episode twenty we said most corporate mission statements fail because they try to do three jobs at once, inspire like a vision, energize like a purpose, and direct like a mission. And they end up doing none of them particularly well. They're heavy on purpose, thin on task. That's why they don't translate into action. But now we can take that a step further. See, adding tasks to a mission is a huge step forward, but it isn't enough. That's where the mission stops, but it isn't where the mission planning process ends. Even after you fix that, after you've built a genuine mission with real task and real purpose, properly nested from top to bottom, there's still a gap between the mission and its execution. A team level mission, even a good one, is still a team level statement. We will start and complete all planned production orders this week. Tells a supervisor what the team is aiming at. But it doesn't yet tell them the two or three things that Absolutely have to happen today for that to be true. It hasn't been broken down into key tasks. It hasn't been connected to what lands on any individual person's plate. Something that a specific person can act on. That's the gap commander's intent begins to close. This isn't a correction of mission work. It's the next required step after you've done that work correctly. And here's what it looks like when this step gets skipped. And I bet almost every senior leader listening has lived some version of it. Leadership does the real work. They build a mission that has genuine task and purpose behind it. People feel something in the room when it's shared. And then Monday comes, and the floor runs exactly like it did the week before. Not because anyone rejected the mission. But because the mission, even a well-built one, was never translated one layer further into what specifically has to happen and who specifically owns it. That has real costs. If a military unit stopped at the mission, you'd have a chaotic effort of subordinate units all attempting to seize a single objective instead of a synchronized and choreographed sequence of events organized in time and space to seize that objective. And just like in the military, Ineffective or inefficient mission planning can have real consequences. Real time and real effort building a strong, actionable mission that produces no visible operational change doesn't just limit your forward movement. It's also corrosive. Leadership starts to lose faith in the exercise itself. We did the mission thing, nothing changed. That's not a failure of the mission framework. It's a failure to take the next step. Before you know it, Supervisors default back to pure task management because managing what's directly in front of them is the only layer they were ever actually equipped to operating. The mission exists somewhere above them, technically true, yet operationally irrelevant to how their day actually runs. The senior leader stays the ceiling, and results only come when the senior leader personally forces them. Decisions keep landing back on their desk and production targets or routine end of month sprint, not because their people are incapable, but because nobody ever handed them the translation work that would have equipped them with the intrinsic ownership that elevates organizations. And here's the worst part it's nobody's fault. It doesn't sit with your supervisors and doesn't sit with a badly written mission. This is a missing skill and a missing process. Translating a mission into key tasks and an end state is not instinctive. Almost nobody is ever taught how to do it. That's not a character problem or a talent problem. It's a training and development gap. One I hope we've helped you start to close today. If you've already done the work from episodes 19 and 20, if you've built out the mission details section of the leader's pre-flight checklist and your supervisors are working with real nested missions, here's the next test. It's not whether they can repeat the mission back to you. That's necessary, but it's not sufficient anymore. The real test is this. Can your supervisors name the two or three key tasks that have to happen this week? And describe what the end state looks like when they do. If the answer stops at recitation, the translation work hasn't happened yet. That's not failure. That's just where the next step of the work is waiting. Start with the leader's preflight checklist. It's free. Operationlead.com slash checklist. The mission details section is exactly where this framework lives. And look, if you're a senior leader looking at your operation, realizing this gap runs deeper than one team or one mission statement. But your organization has never built the muscle to translate intent into execution at scale, that's exactly what we're here to help you install. Head to operationlead.com to learn about our system and process. Here's the through line of everything we've talked about when it comes to the mission. Strategic, story-driven communication makes your team the hero instead of a passive audience. Then a properly nested mission gives that communication a structure to run on. Commander's intent, key tasks, and then state, is what takes that mission and starts to make it actionable, all the way down to what one person does today and how they know it matters. That's the 80%. That's planning and communication done right all the way to the floor. Next week we're shifting gears to talk about what leaders need to protect their own capacity to do the very work we talked through today. Because a supervisor who can't say no to anything eventually can't say yes to what actually matters. We're getting into boundaries, why your best supervisors are afraid to set them, and what it quietly costs your team when they don't. Until then, I'm Craig Coyle, and this is the Frontline Leadership Podcast. Let's lead.