Hey, welcome to the briefing. What I'm going to cover with you today in this DA briefing, navigate obstacles rapidly in logistics. You can stare at the river gauge all day. It is not going to negotiate with you. It does not care that the freight was booked three weeks ago. It does not care what the customer was promised, what the production schedule says, what the receiving team planned around, or how clean that transportation plan looked when everybody approved it. The water is going to be where the water is. The operating condition is going to be what the operating condition is. So the real question for the logistics leader is not whether you like the condition. The question is what happens to the objective when the path underneath that objective changes. That is the situation developing right now on the Mississippi River. Based on what is publicly known, American Commercial Barge Line placed its low water protocol into effect on August 3rd after the Memphis gauge reached zero feet. In its August 7th operating update, the company reported draft-related restrictions and reduced tow sizes. The Coast Guard also issued low water safety guidance across a significant portion of the Lower Mississippi, directing operators to account for reduced depths, loading conditions, route planning, docking conditions, and safe vessel movement. The river is not closed, that matters. Freight can still move. The system did not disappear, but the operating envelope tightened. And when the operating envelope tightens, the plan that protected the objective yesterday may stop protecting it today. That is where I want to start, because one of the easiest mistakes in logistics is confusing the path with the objective. We do it because the path is visible. The booking is visible, the lane is visible, the barge movement is visible, and the terminal is visible, the truck appointment is visible, the customer commitment is sitting in the TMS. The production requirement is sitting somewhere else. Inventory is sitting in another system. Everybody owns a piece of the plan, and after a while that plan becomes so familiar that people start treating it like it is the thing that actually matters. It is not. The path exists to serve the objective. The objective does not exist to preserve the path. That sounds obvious when I say it, but uh it gets a lot less obvious when changing the path costs money, introduces another handoff, creates uncertainty, forces somebody to revise an arrival commitment, burns alternate capacity, or turns what looked like a clean transport. Actually, forget the transportation plan for a second. It turns a clean operating assumption into something you can no longer trust the same way. Then staying with the original route starts to feel disciplined. Do not overreact, wait another day, watch the gauge, let the carrier work it, protect costs, do not move freight unless we have to. I understand every one of those thoughts. They can all be reasonable, and that is important because I do not want to manufacture some incompetent manager just so the tool looks smart, and that is not the lesson. The weak decision here can begin with a completely reasonable instinct. The problem starts when that instinct stays in place after the operating condition underneath it has changed. That is what I want you to watch. A logistics operation can keep protecting yesterday's answer after yesterday's answer, stop solving today's problem. Low water makes the distinction easy to see because nobody has to debate whether the physical constraint is real. You cannot call a meeting and make the Mississippi deeper. You cannot escalate the river to a vice president. You cannot send a more forceful email and recover draft. You cannot tell a vessel operator to ignore a safety condition because customer operations promised an arrival date. At some point, the river has officially declined the escalation request. The obstacle is real, the freight objective is also real. The mistake is assuming those two facts leave you with only one decision. So put yourself in this position. You are a regional transportation manager responsible for several inbound freight movements already planned through the Mississippi River system. This is an illustrative scenario built from the verified operating condition. I am not telling you what a specific company did. I am not inventing private shipments, customer conversations, cost decisions, or internal actions. I want to use the real condition to put a leader inside the decision. You have several movements already planned. Some of that freight supports normal replenishment, there is inventory downstream. The receiving operation has room. A delay is inconvenient, but it is not yet damaging the objective. Another movement has less tolerance. Maybe it supports a production requirement. Maybe it feeds an inventory position that is getting thin. Maybe there is a customer commitment sitting downstream that depends on it. And before I go any further, the exact business does not really matter for the pattern. What matters is this. The freight may be sitting inside the same transportation constraint without carrying the same operating consequence. That distinction is important. Now the river condition changes, tow capacity is constrained, loading decisions get tighter, the transportation team starts getting updates, operations wants arrival timing, procurement wants to know what material is exposed. Customer service wants to know what it can tell the customer. Receiving wants to know whether the dock and labor plan still makes sense. Finance can already see what happens if the team starts converting large amounts of freight to more expensive transportation. Leadership wants a clean answer, and um there may not be one yet. That is normal. You are working inside a constrained system. The first instinct is to hold the original plan. There are good reasons for that. Alternate transportation may cost more, rail capacity may not be available, truck capacity may be tight, a transload adds another handoff, another terminal can create another handoff. Moving one piece of freight can affect receiving sequence, inventory visibility, appointment timing, paperwork, carrier coordination, and the people responsible for the next step. So the team waits. That is not automatically wrong. I want to be clear about that. Waiting can be the right answer if the objective is still protected. Then one movement starts losing schedule tolerance faster, then the transportation condition is improving. Now something changed. The river did not suddenly become a different obstacle. The part that changed is the relationship between that obstacle and the business requirement sitting behind it. That freight objective is now being blocked in a way it was not being blocked before. That is where leadership judgment matters because the original decision can still feel responsible. Stay patient, protect cost, do not create churn, give the carrier time, do not destabilize everything because one part of the network is under pressure. Fine. But what is the objective? That is the question. If the objective is still protected, staying with the original route may make perfect sense. If the objective is no longer protected, loyalty to the original route has stopped being disciplined. Now the path is starting to control the objective. That is path captivity. And once you see it that way, the problem gets a lot cleaner. Nothing says you have to solve the river. You cannot. What you have to decide is whether the river still gets to control that specific freight requirement. Those are different problems, and this is where people will often swing immediately to the other side. Alright, the river is constrained. Get everything off the water, put it on trucks, find rail, find another terminal, expedite it, move it, do whatever we have to do. That sounds decisive. It can also be a complete mess. An alternate route written on a whiteboard is not capacity. A rail option on a network map is not a confirmed slot. Trucks existing in the market do not mean you have a truck assigned to your freight, and a terminal on a map does not mean it has the room, labor, equipment, storage, appointments, and downstream transportation to absorb what you're about to send there. Apparently the map has promoted itself to dispatch. That is why the evidence boundary matters here. The low water condition and restrictions are verified. What the public information does not establish is that every affected shipper has immediate truck, rail, transload, terminal, or alternate route capacity waiting. We cannot responsibly assume that. And from an operating standpoint, that unknown is part of the decision because redirection built on imaginary capacity is not that is not controlled redirection. It is an idea with a routing instruction attached to it. So now our transportation manager is sitting between two understandable responses. Stay with the river and preserve the existing plan, or move everything and protect the schedule. Neither one is automatically right. This is where the real work begins. The manager has to stop looking at the freight as one undifferentiated mass. Which movement is losing tolerance, and which still has room? Which consequence shows up first? Which requirement cannot absorb another delay? Which freight can stay where it is without losing the objective? And what alternate capacity is real, not assumed. Think about what just happened. We stop talking about the river as if the river were the whole problem. The physical obstacle is low water. The upper more precisely, the operational blockage is what that condition is doing to a specific freight objective. Those are not the same thing. That distinction is the center of this briefing. One barge movement may become slower and still protect the business requirement. Another may reach a point where the same delay is no longer acceptable. Same river, same physical condition, different consequence. That is why treating every shipment the same can become a bad decision. It looks consistent, it may not be controlled. The original transportation plan had a sequence. Freight enters the system. The barge movement carries it toward the next node. The next facility, customer, production line, terminal, warehouse, or receiving team is working from an expected arrival. Then one segment tightens. Every downstream assumption tied to that segment deserves another look. But the team can get hypnotized by the visible obstacle. What is the river doing? What is the gauge? What did the carrier say? Any update, any update, those are legitimate questions. They are just not the only questions. What is the freight doing? What is the inventory position doing? Which commitment is losing margin? What receiving window is harder to protect? What option disappears if you wait another 24 hours? That is where the leader has to keep attention on the objective instead of allowing the obstacle to become the entire operating picture. I have learned to respect this problem over time, because plans can become dangerous when people start defending them just because they are familiar. The plan was useful because it was supposed to create a result. Once the operating condition changes, the plan has to earn its place again. A good operator does not panic because the path changed. They also do not worship the original plan after the plan stops protecting the objective. And that is not flexibility for the sake of flexibility. That is discipline. You are holding the objective steady while reconsidering the path. Now follow the weak response a little further. Suppose the manager waits too long. At first, nothing dramatic happens. The freight is delayed. Customer operations updates an estimate. Receiving shifts the expectation. Everybody watches the river, then schedule margin starts disappearing. A procurement asks again because inventory is getting tighter. Receiving no longer knows whether to hold labor or shift it. Customer operations is working from an estimate with less confidence behind it. A production planner may start making protective adjustments. Again, those are illustrative operating effects. I am not claiming those outcomes happened to a specific company. The public information does not establish that. What I'm showing you is the consequence path. When decision space shrinks, options do not disappear evenly. Some get more expensive, some become unavailable, some require more handoffs, and some force faster commitments. You can create risks that might have been avoided by separating freight that could wait from freight that could not. So the manager who avoided an expensive transportation decision earlier may eventually be forced into a more expensive transportation decision later. That is one failure path. Now take the opposite response. The manager sees the constraint and redirects everything. Every affected shipment gets pushed toward road, rail, another terminal, another transfer point, another carrier, whatever can be found. Now alternate capacity starts filling. Costs rise. Appointments and documentation change. Receiving sequences move. Inventory visibility gets harder because the freight is no longer following the expected path. And now the freight with the highest consequence may be competing for the same alternate capacity as freight that never needed to move in the first place. If you redirect everything, congratulations, you may have just moved your bottleneck onto wheels. That is not control either. The organization did not clear the obstacle and it copied the obstacle into another part of the network. And this can feel like leadership because everybody gets busy. Phones are moving, loads are getting rebooked, carriers are being contacted, TMS records are changing, and customer updates are going out. A lot is happening, and this is the point where the operating plan becomes a cartoon. The transportation desk has 12 colored routes across the map. Three departments are celebrating because every shipment technically has a new destination, and somewhere in the middle of it, nobody can explain which freight actually needed to move. Take away the cartoon and the consequence remains. I do not care how much activity you created if the objective is now less protected than it was before. Activity is not the standard, movement is not the standard. The standard is whether the objective is better protected after the decision than it was before. Now we are getting somewhere. That is where obstacle redirection enters this conversation. Obstacle redirection is part of deepen. At the recognition level, it is useful when an obstacle is already interfering with progress. The issue cannot simply be ignored. Direct correction is not the best immediate move. And there may be a controlled way to move the obstacle's effect out of the path so the objective can continue. Notice what I did not say. The obstacle does not disappear. Everything does not get rerouted. Cheapest is not automatically right. Fastest is not automatically right. And every logistics disruption is definitely not an obstacle redirection problem. Different problems require different responses. In this situation, low water is active, the transportation path is constrained. The logistics leader cannot directly correct the physical condition. Waiting may still be appropriate for some freight. For other freight, the obstacle may now be controlling too much of the objective. That is the recognition point. You do not have to remove the obstacle to remove it from the shipment's path. Simple statement, not always a simple decision. Because once you move the obstacle's effect, you have to understand what the new path creates. Cost. Transit time. Another handoff, another terminal or carrier, another visibility issue, another appointment, another receiving sequence, another owner, another chance for the workaround to become the next problem. Every alternate path needs to work. Well, not every path, the path you actually choose has to work under control. That is the distinction. That is why obstacle redirection is not just another name for rerouting. Rerouting is an action. Obstacle. Redirection is a way of recognizing that the objective may need to be separated from the obstacle without pretending the obstacle has been solved. That part matters. Suppose one critical movement leaves the river path and the rest stays. Fine. The low water condition still exists. The remaining freight still needs visibility, the original route still needs monitoring, the alternate movement now has its own handoffs. Somebody owns what moved, somebody owns what did not. You do not get to throw the original problem over the fence and declare victory because the urgent freight is moving somewhere else. Responsibility does not disappear because the route changed. And that is why the better question is not simply can we get this freight moving? You can get freight moving in a lot of bad ways. The better question is whether you can protect the objective by moving the right part of the requirement away from the active obstacle without creating an uncontrolled second problem. That is a much stronger standard. And this is where it connects to the broader direct action system. CSA comes first because you need a clean read. What changed? What is verified? What is assumption? What still works? Which objective is exposed? If the CSA read is weak, deep and gets weak material and you can solve the wrong problem very efficiently. Maybe the river constraint is real, but one shipment still has tolerance. Maybe another looks routine in the transportation system, but supports something downstream with almost no margin. Maybe the TMS still shows a clean planned arrival after the physical condition has already moved. CSA helps expose that difference. Then Deepen helps determine what kind of problem you are actually navigating. Not every obstacle gets attacked, postponed, stabilized, or redirected. That is the value of a problem navigation structure instead of reaching for whichever response feels decisive. From there, ah, only the connections that actually matter should come forward. TMC matters once the route changes because a new path without ownership and communication can fail at the next handoff. Pace matters when the operation needs prepared alternatives instead of improvisation after every change. I am not going to turn this into a tour of the system because that is not the point. The point is that better execution depends on the quality of the read feeding the decision. In this episode, the read has to stay centered on the freight objective. Not your emotional attachment to the original plan, not your need to prove that everybody is taking action. The objective, that is the anchor. Bring this into your own operation. Maybe you do not move freight on the Mississippi. Fine. You still have paths, carrier lanes, dock doors, staging areas, routing guides, transloads, rail ramps, ports, warehouses, trailer pools, vendors, systems, equipment, customs processes, and receiving sequences. Somewhere in your operation, there is probably a path that works so consistently that your team has stopped distinguishing it from the objective. That is what I want you to inspect. What happens when that path becomes constrained? Does your team keep defending it because the plan is already built? And does everybody sit around waiting for normal to return? Or does the team immediately panic and shove everything toward the first available alternative? Those are opposite reactions to the same leadership problem. One gives the obstacle too much control, the other gives the workaround too much freedom. Neither one is what you want. You want discrimination. What is actually blocked? What consequence is approaching? What still has tolerance? What alternate path is confirmed? What will it put under pressure? Who owns the next handoff? What remains behind? That is enough for a field level check. You do not need a 20-page contingency plan to recognize that one constrained lane is starting to own too much of the business objective. You need to recognize when the relationship changed. The route was supposed to serve the freight objective, and the freight objective was never supposed to serve the route. That is the discipline. And uh there's another part of this that is easy to miss. You can make the right redirection decision and still create a mess if the rest of the organization keeps operating from the old plan. Transportation changes the route. Receiving still expects the old arrival. Customer service communicates the old date. Procurement carries the old inventory assumption. Finance sees the premium without the reason. The carrier sees one instruction, and the internal team sees another. The movement changed. Shared operating reality did not. And now you have another problem. The old ETA has apparently achieved diplomatic immunity. That is why a new path requires ownership. A workaround is not controlled just because it works once. It has to remain visible enough that the rest of the operation knows what changed and what that change means. I am not giving you the complete execution method here. I am showing you the failure pattern. The obstacle is not the only thing capable of taking control away from you. The workaround can do it too. Logistics is especially unforgiving because every change propagates. Move one load and you may change an appointment. Change the appointment and you may change receiving labor. Change the receiving sequence and you may change inventory availability. The new route can abs it can start carrying pressure the original route used to contain. And that can can become a second problem very quickly. So when I say move the freight path, I do not mean move it casually. I mean protect the objective with enough awareness to understand that the alternate path becomes part of the operating system the moment you commit to it. That is why the Mississippi situation is such a useful example. The obstacle is clean. Low water. Reduced operating flexibility, navigation restrictions. There is no reason to invent a villain. You do not have to blame the carrier. You do not have to blame the terminal. You do not have to blame the transportation manager. The physical condition changed. Now judgment matters. What does the organization do with the condition it actually has? That is where leadership shows up. Not in pretending you can control the river, not in acting like the original plan is sacred, not in paying any price just to preserve movement, not in freezing because you want perfect information before you decide anything. Leadership shows up in understanding which objective is actually threatened, and choosing a response that keeps that objective from becoming captive to the obstacle. That pattern transfers. A terminal goes down, a carrier loses capacity, a rail lane tightens, a road closure changes access, a warehouse loses a dock, a TMS feed becomes unreliable, the details change, the recognition question stays useful. Is the obstacle actually blocking the objective? And if it is, does the objective still need to stay behind that obstacle? Sometimes the answer is yes. There may be no responsible alternate path. Capacity may not exist. The workaround may create more risk than the delay. The freight may still be able to wait. That is a legitimate answer. Obstacle redirection does not mean every obstacle gets bypassed. The tool does not give you permission to become allergic to friction. More precisely, it helps you recognize when the original path no longer deserves automatic control over the objective. There is a difference. And that difference protects you from another mistake, which is turning urgency into fiction. I have seen versions of this all over operations. We need another option. Fine. Somebody names rail trucks, another facility, another terminal. Okay, can we actually do it? Not theoretically. Is capacity confirmed? Timing, ownership, receiving condition, new handoffs, cost understood well enough to decide? If not, then you do not have the alt you have an alternative idea. You do not have an operating path yet. At that point, the spreadsheet has hired a truck that does not exist. And that is okay. Ideas are where options begin. Just do not confuse an idea with operating capacity. That distinction gets critical under pressure because the team wants relief. The first plausible alternative feels like relief, but your job is not to create emotional relief. Your job is to protect the objective. So here is the field takeaway I want you to carry from this. When a transportation path becomes constrained, do not make the entire network react before you understand what is actually blocked. Ask which objective is losing movement. Ask what still has tolerance. Ask what consequence is approaching. Ask which alternate path is real. Then ask what that path could break. That is enough to improve the decision. You are not trying to redesign the entire network in one conversation. You are trying to keep a local obstacle from controlling more of the operation than it has to. That is obstacle redirection at the recognition level. The Mississippi does not care about your transportation plan. Neither does a closed terminal, a missed carrier, a blocked dock, or a constrained lane. The operation still has to decide what happens next. And that is why good logistics leadership is not measured by how faithfully the team protects the original route. It is measured by whether the objective keeps moving with control when the route stops working the way everybody expected it to. The river is the obstacle. It does not have to become the strategy. You do not have to remove the obstacle to remove it from the shipment's path. But you do have to know what you are protecting before you move anything. When you are ready to go deeper with this tool, go to www.direct action system.io slash course dash directory. Open the course directory. Find the course tied to obstacle redirection and deepen and start there. That is where the deeper application belongs. Thanks for listening to the briefing.