Direct Action Briefings

Mikey K
  • 0.0 (0)
  • Management

Leadership, decision-making, and operational execution under pressure. 

  1. Aug 27

    DA Briefing 0060: Navigate Obstacles Rapidly in Manufacturing

    Stuck on a leadership, operations, or decision-making challenge? Have feedback, suggestions, or an idea you would like us to cover? Send it in. We may break it down in a future Direct Action Briefing. Submit your question or feedback here: https://podcast.direct-action-system.io/2623617/fan_mail Capability Focus: Navigate Obstacles Rapidly Industry Focus: Manufacturing Operations Tool Focus: In-Depth Analysis Episode Focus: Recognizing when an intermittent quality problem creates a critical unknown that must be understood before production can responsibly continue. The line can still run. Some units still pass. The shipment clock is still moving. But confidence in the process is getting weaker. In this Direct Action Briefing, Mikey K breaks down what happens when an intermittent manufacturing problem creates enough normal output to make continued production feel reasonable, while the operation still does not understand what is actually driving the failure. The episode uses Unusual Machines’ August 2026 disclosure of an intermittent quality issue involving one motor SKU as the current operating anchor. The company described cross-functional work to determine root cause, changes to production processes, and new quality-testing methods. The deeper leadership problem is not the failed motor by itself. It is what the failure may be telling you about a process whose affected boundary is still unclear. Under production pressure, the reasonable response is familiar. Increase inspection. Separate the units that fail. Watch the next run. Protect the shipment. Keep producing while the technical work continues. That response may eventually be correct. The leadership misread is assuming that several passing units prove the problem is contained before the team understands what those passing results actually mean. If the triggering condition is still unknown, every additional unit can increase the population the plant may later need to inspect, contain, rework, or reassess. Now quality confidence weakens. Planning starts rebuilding the schedule around assumptions. Customer-facing teams need better shipment information. And an issue that appeared small at the line can become a much larger operating problem. This episode examines where In-Depth Analysis becomes relevant. Not because every unknown should stop production. Not because analysis is automatically safer than action. The tool matters when one unresolved variable could materially change the correct move. The better decision is to recognize when the current read is no longer strong enough to support continued action, determine what evidence actually matters, and resist letting schedule pressure turn an assumption into operating fact. The schedule can create urgency. It cannot create evidence. If the missing variable can change the move, continuing is not decisiveness. It is guessing with production behind it. Read the companion article: https://www.direct-action-system.io/blog/it-only-showed-up-sometimes-the-line-had-to-stop-guessing Get the manufacturing-specific Direct Action starter resource: https://www.direct-action-system.io/manufacturing-starter Read practical leadership and operations articles on the Direct Action Blog: https://www.direct-action-system.io/blog This briefing is part of the Direct Action Briefings series, where Mikey K breaks down practical decision systems for leaders operating under pressure.

  2. Aug 26

    DA Briefing 0059: Navigate Obstacles Rapidly in Logistics

    Stuck on a leadership, operations, or decision-making challenge? Have feedback, suggestions, or an idea you would like us to cover? Send it in. We may break it down in a future Direct Action Briefing. Submit your question or feedback here: https://podcast.direct-action-system.io/2623617/fan_mail Capability Focus: Navigate Obstacles Rapidly Industry Focus: Logistics and Cold-Chain Operations Tool Focus: In-Depth Analysis Episode Focus: Stopping a receiving decision when a confirmed temperature-control failure has not yet established which product was actually exposed. The trailer is at the dock. The cold-chain failure is confirmed. Receiving needs the door. Inventory wants status. But nobody has established exactly what product was affected. In this Direct Action Briefing, Mikey K breaks down what happens when logistics pressure demands a yes-or-no decision before the evidence supports one. An August 2026 French recall involving smoked salmon and trout provides the operating proof. A transportation temperature failure occurred, but the official recall identified the affected scope as one pallet containing eighteen packages and specifically distinguished that pallet from the rest of the lot. The failure was real. The scope was not universal. That distinction matters at the receiving dock. One response is to treat the entire load as affected and stop everything. The other is to assume the problem is isolated and keep product moving because the trailer looks normal, another appointment is waiting, and customer demand is building downstream. Both responses can feel responsible. Both can create a second problem when the affected scope is still unknown. Move too early and questionable product can enter inventory, become available in the warehouse-management system, allocate against orders, and travel farther through the supply chain. React too broadly and usable inventory may remain unavailable, customer orders may be delayed, warehouse capacity may tighten, and the operation may build a large recovery effort around a much smaller confirmed problem. The leadership failure is not uncertainty. It is allowing dock pressure, customer demand, or confidence to substitute for the missing evidence that could change the decision. This episode introduces In-Depth Analysis at the recognition level: the point where continued action should halt because one critical unknown can make the next move wrong. Mikey K also separates operating ownership from technical authority. The receiving supervisor still owns the dock, labor, appointment pressure, inventory coordination, and downstream consequences. The qualified food-safety determination remains with the approved people and process responsible for making it. You do not need perfect information before every move. You do need the variable that can change the move. Read the companion article: https://www.direct-action-system.io/blog/the-cold-chain-broke-first-find-out-what-was-actually-exposed Get the logistics-specific Direct Action starter resource: https://www.direct-action-system.io/logistics-starter Read practical leadership and operations articles on the Direct Action Blog: https://www.direct-action-system.io/blog This briefing is part of the Direct Action Briefings series, where Mikey K breaks down practical decision systems for leaders operating under pressure.

  3. Aug 25

    DA Briefing 0058: Navigate Obstacles Rapidly in Healthcare

    Stuck on a leadership, operations, or decision-making challenge? Have feedback, suggestions, or an idea you would like us to cover? Send it in. We may break it down in a future Direct Action Briefing. Submit your question or feedback here: https://podcast.direct-action-system.io/2623617/fan_mail Capability Focus: Navigate Obstacles Rapidly Industry Focus: Healthcare Operations Tool Focus: In-Depth Analysis Episode Focus: Determining how far a serious medication error reached before corrective action becomes broader or narrower than the evidence supports. Four patients were affected. One medication error was identified. The pressure to fix it was immediate. But finding the error did not automatically establish where the failure stopped. In this Direct Action Briefing, Mikey K examines the August 2026 medication error at Ascension Saint Thomas Hospital Midtown in Nashville and the leadership problem that begins after a serious failure becomes visible. Ascension publicly stated that four joint-replacement patients received potassium phosphate instead of the intended anesthetic medication, mepivacaine. The hospital later said a comprehensive review confirmed that no additional patients were affected. That scope determination matters. Because under pressure, the reasonable response is to move. Stop the affected workflow. Move medications. Add another verification. Retrain staff. Issue new instructions. Those actions may ultimately be appropriate. But the leadership misread is assuming the visible error already tells you the full corrective boundary. Move too narrowly and part of the failure condition may remain. Move too broadly and new controls can create additional workload, handoffs, delays, and process variation in areas that were not part of the original problem. Move straight to blame and accountability can land on the person closest to the event before leadership understands what authority, safeguards, information, workload, and operating conditions actually shaped the failure. This episode breaks down why immediate protection and final correction are not the same decision. Mikey K also examines Ascension's publicly reported corrective actions, including separate medication storage, additional verification controls, second-pharmacist checks in the affected workflow, and independent outside review of the mitigation plans. The point is not to reverse-engineer Ascension's internal root cause from public information. The point is to recognize when a critical unknown can still change the next move. That is where In-Depth Analysis becomes relevant. Not because leaders need every possible answer. Because sometimes one missing variable determines whether the correction should stay narrow, expand, pause, or move in a different direction. The error tells you where to start looking. The analysis tells you when you know enough to move responsibly. Read the companion article: https://www.direct-action-system.io/blog/four-patients-one-error-where-did-the-failure-stop Get the healthcare-specific Direct Action starter resource: https://www.direct-action-system.io/healthcare-starter Read practical leadership and operations articles on the Direct Action Blog: https://www.direct-action-system.io/blog This briefing is part of the Direct Action Briefings series, where Mikey K breaks down practical decision systems for leaders operating under pressure.

  4. Aug 24

    DA Briefing 0057: Navigate Obstacles Rapidly in Retail, Restaurant, and Hospitality

    Stuck on a leadership, operations, or decision-making challenge? Have feedback, suggestions, or an idea you would like us to cover? Send it in. We may break it down in a future Direct Action Briefing. Submit your question or feedback here: https://podcast.direct-action-system.io/2623617/fan_mail Capability Focus: Navigate Obstacles Rapidly Industry Focus: Restaurant / Mixed-Use Hospitality Tool Focus: In-Depth Analysis Episode Focus: Knowing when the information already available can identify the problem, but cannot yet support the correction. Everyone smelled something. Everybody had a theory. Nobody could prove the source. In Washington, D.C., residents living above Gordon Ramsay Street Pizza and Street Burger have reported persistent grease odors and concerns about elevated fine-particle readings. Residents believe restaurant operations are contributing to the condition. The restaurant group and landlord dispute that conclusion. An engineering assessment found timing correlations between particulate spikes and restaurant operating activity, but it was not designed to establish where those particulates were actually coming from. That distinction creates the leadership problem. In this Direct Action Briefing, Mikey K breaks down what happens when a restaurant or property operations leader has enough information to know a problem is real, but not enough information to responsibly choose the correction. The temptation is to move. Clean the exhaust again. Modify ventilation. Change operating conditions. Blame the restaurant. Blame the building. Declare the issue resolved because an inspection did not identify a violation. Each response creates activity. None automatically proves the source. This episode separates C S A from In-Depth Analysis at the point where leaders often confuse them. C S A builds the strongest responsible read from information already accessible to the leader: complaints, operating hours, maintenance records, inspections, visible conditions, and current system information. But when that read exposes a critical variable that cannot be answered without new testing, technical expertise, additional access, sampling, or deeper evidence, the problem has changed. The leadership misread is treating the strongest theory as though it has already become fact. That can send money, attention, accountability, and corrective action toward the wrong system while the original problem continues. Mikey K also examines the other failure: allowing “we need more data” to become a comfortable excuse for avoiding a decision. In-Depth Analysis is not endless investigation. The missing variable has to matter enough that getting it wrong could change the move. A plausible explanation can justify investigation. It does not automatically justify the correction. Use the evidence for what it actually supports. When the next decision requires something you do not yet know, go get what the decision requires. Read the companion article: https://www.direct-action-system.io/blog/everyone-smelled-it-nobody-could-prove-who-dealt-it Get the retail / hospitality / restaurant-specific Direct Action starter resource: https://www.direct-action-system.io/retail-starter Read practical leadership and operations articles on the Direct Action Blog: https://www.direct-action-system.io/blog This briefing is part of the Direct Action Briefings series, where Mikey K breaks down practical decision systems for leaders operating under pressure.

  5. Aug 23

    DA Toolbox Brief 0007: In-Depth Analysis

    Stuck on a leadership, operations, or decision-making challenge? Have feedback, suggestions, or an idea you would like us to cover? Send it in. We may break it down in a future Direct Action Briefing. Submit your question or feedback here: https://podcast.direct-action-system.io/2623617/fan_mail Capability Focus: Navigate Obstacles Rapidly Industry Focus: Warehouse and Fulfillment Operations Tool Focus: In-Depth Analysis Episode Focus: Recognizing when the initial operating read is no longer sufficient and a staffing decision must stop until the missing variable is understood. The system says move the labor. The manager sees something different on the floor. Both reads may be reasonable. But only one staffing decision can be made. In this Direct Action Tool Brief, Mikey K breaks down Amazon’s current pilot of automated labor-management systems inside a small number of U.S. fulfillment and sortation facilities. The tools are designed to recommend where workers should move as workload and package volume change. Reporting has described some managers overriding or challenging recommendations when they believe the system is missing operating context. Amazon says the tools remain in pilot testing, managers retain decision authority, and feedback is being used to refine the systems. That creates a leadership problem larger than whether a manager or an algorithm is right. An area manager already has an initial operating read. They can see staffing. They can see queues. They can see work in process. They can see current volume and the automated recommendation. That is the C S A boundary. Use the accessible information already available to build the initial read. But what happens when that read exposes a conflict the available information cannot explain? Moving labor immediately may create a downstream bottleneck. Ignoring the recommendation because “I know my floor” may preserve an inefficient staffing decision. Neither confidence in software nor confidence in experience resolves the missing variable. That is where In-Depth Analysis begins. The leader stops only the exposed action long enough to obtain something the initial read did not provide. That may require additional data, technical review, deeper system visibility, specialized expertise, testing, or another resource capable of explaining the disagreement. The distinction matters. C S A is not incomplete because it identifies something the leader cannot yet answer. Sometimes a good initial assessment does exactly that. It shows you where the available read ends. In-Depth Analysis begins when the answer matters enough that acting without it could change the decision or create unacceptable consequences. More information is not automatically better leadership. The missing information must be capable of changing the move. Explore Direct Action training: https://www.direct-action-system.io/course-directory Choose the Starter Sheet that matches your operating environment: https://www.direct-action-system.io/starter-sheet-main Read practical leadership and operations articles on the Direct Action Blog: https://www.direct-action-system.io/blog This briefing is part of the Direct Action Briefings series, where Mikey K breaks down practical decision systems for leaders operating under pressure.

  6. Aug 22

    DA Mailbag 0010: There Is Nowhere to Promote Me. How Do I Keep Developing?

    Stuck on a leadership, operations, or decision-making challenge? Have feedback, suggestions, or an idea you would like us to cover? Send it in. We may break it down in a future Direct Action Briefing. Submit your question or feedback here: https://podcast.direct-action-system.io/2623617/fan_mail Capability Focus: Comprehensive Situation Assessment Industry Focus: Public Sector and Small Organization Leadership Tool Focus: Long-Range Observation Episode Focus: Building leadership capability before a supervisory vacancy forces the organization to start looking for someone who is ready. The position is filled. The next one may stay filled for years. And the people underneath it are still supposed to keep developing. In this Direct Action Mailbag, Mikey K breaks down what happens when a smaller organization has capable people, limited supervisory positions, and a development system that effectively waits for somebody to leave before leadership preparation begins. That structure creates a predictable response. Keep doing your job. Take another specialty assignment. Wait for the opening. Then, when a sergeant, manager, supervisor, or department lead finally retires or resigns, start asking who might be ready. The problem is that a vacancy is an event. Development is a system. This episode examines what large organizations like the military get right about progressive development, what smaller organizations should refuse to copy, and why promotion-first leadership development pushes the learning process into the live operation where employees, customers, officers, and the organization absorb the consequences. It also confronts one of the weakest defenses of a poor development model: “This is how we have always done it.” Some people surviving a system does not prove the system developed them well. And calling someone “not a good fit” does not automatically prove they lack leadership potential. Sometimes it exposes a leadership style, training method, or development structure that only knows how to produce one kind of leader. For police departments, staffing pressure makes the problem harder. Patrol coverage, calls for service, and immediate readiness can consume training time, specialty assignments, shadowing, and controlled leadership repetitions. For small businesses, the same problem appears when the strongest technician, operator, or customer-facing employee becomes the obvious promotion candidate simply because they are good at the work. Mikey K lays out the better read: define the capability before the vacancy, identify the bench, create legitimate repetitions before promotion, give direct feedback, protect technical and leadership paths, and review readiness before someone gives notice. The vacancy should reveal the bench. It should not be the first time leadership starts looking for one. Read the companion article: https://www.direct-action-system.io/blog/there-is-nowhere-to-promote-me-how-do-i-keep-developing Get the public-sector-specific Direct Action starter resource: https://www.direct-action-system.io/public-sector-starter Read practical leadership and operations articles on the Direct Action Blog: https://www.direct-action-system.io/blog This briefing is part of the Direct Action Briefings series, where Mikey K breaks down practical decision systems for leaders operating under pressure.

  7. Aug 21

    DA Briefing 0056: Navigate Obstacles Rapidly in Public Sector

    Stuck on a leadership, operations, or decision-making challenge? Have feedback, suggestions, or an idea you would like us to cover? Send it in. We may break it down in a future Direct Action Briefing. Submit your question or feedback here: https://podcast.direct-action-system.io/2623617/fan_mail Capability Focus: Navigate Obstacles Rapidly Industry Focus: Public Sector Operations Tool Focus: Manual Engagement Episode Focus: Recognizing when repeated referrals stop moving the resident’s problem and the blocker requires the right human capability. The resident was referred again. The request moved. The blocker did not. Los Angeles County’s newly designated Aging and Disability Resource Connection network is built around a No Wrong Door approach intended to reduce bureaucratic runaround and help residents reach coordinated services without having to navigate multiple organizations alone. That creates a practical leadership problem for the supervisors and team leads closest to the work. In this Direct Action Briefing, Mikey K breaks down what happens when a resident-services employee follows the normal process, provides the available information, makes a legitimate referral, and the resident still comes back with the same unresolved point. The first response feels reasonable. Send them to another program. Give them another number. Move the request to somebody else. The opposite response feels just as responsible. The supervisor takes over the entire case. Both can miss the real problem. Another referral may simply continue process cycling. A supervisor takeover can turn one difficult case into a permanent management bottleneck. The leadership decision is narrower. What is actually still stuck? Does the blocker require program knowledge, decision authority, system access, trust, judgment, or a specific relationship that the current path does not have? That is where Manual Engagement becomes relevant. The episode examines why the right person does not have to own the entire problem, why frontline employees should not be blamed for reaching legitimate limits in their authority or capability, and why activity inside a service queue should not be mistaken for progress. Repeated handoffs create repeated explanations. Repeated explanations consume staff capacity. Unclear ownership creates more escalations. And eventually the resident becomes responsible for carrying context between parts of the system that should be coordinating with each other. The better decision is not automatically another referral and not automatically leader takeover. It is recognizing when normal process has reached its limit and putting the right human capability onto the point that is actually stuck. The resident should not have to become the system integrator. The right person handles the blocker so the service objective can keep moving. Read the companion article: https://www.direct-action-system.io/blog/no-wrong-door-still-requires-the-right-person Get the public-sector-specific Direct Action starter resource: https://www.direct-action-system.io/public-sector-starter Read practical leadership and operations articles on the Direct Action Blog: https://www.direct-action-system.io/blog This briefing is part of the Direct Action Briefings series, where Mikey K breaks down practical decision systems for leaders operating under pressure.

  8. Aug 20

    DA Briefing 0055: Navigate Obstacles Rapidly in Manufacturing

    Stuck on a leadership, operations, or decision-making challenge? Have feedback, suggestions, or an idea you would like us to cover? Send it in. We may break it down in a future Direct Action Briefing. Submit your question or feedback here: https://podcast.direct-action-system.io/2623617/fan_mail Capability Focus: Navigate Obstacles Rapidly Industry Focus: Manufacturing Operations Tool Focus: Manual Engagement Episode Focus: Recognizing when a failed manufacturing signal requires the right technical capability instead of more general effort. The sensor said pass. The nut was still loose. Now the line has a problem, and the supervisor has a decision to make. In this Direct Action Briefing, Mikey K breaks down what happens when a normal manufacturing control produces a signal that no longer agrees with the physical condition on the floor. The episode uses General Motors’ 2026 Chevrolet Express and GMC Savana steering-gear recall as the real-world anchor. According to NHTSA, a malfunctioning supplier sensor allowed some steering gear assemblies with improperly tightened nuts to pass inspection, leading GM and its supplier to investigate the sensor condition and review torque trace data. (NHTSA) For the production supervisor, the leadership problem sits much closer to the floor. The inspection result says the work passed. The physical condition says something is wrong. Production wants movement. Quality wants confidence. Planning wants scope. Maintenance may already be involved. The schedule is still running while certainty is disappearing. The reasonable first response is to get involved. The leadership misread is believing responsibility means personally becoming the controls engineer, quality engineer, maintenance specialist, and manufacturing engineer at the same time. Pretty soon the supervisor is four departments in a polo shirt. The other weak response is just as familiar: everybody checks everything. Congratulations. The plant has reinvented panic with clipboards. Neither response automatically supplies the capability the blocker actually requires. This episode examines Manual Engagement, a Direct Action tool for recognizing when the obstacle has reached a point where the current path is missing specific human capability, authority, access, judgment, or technical skill. The operating consequence of missing that distinction spreads quickly. Production develops one version of the problem. Quality develops another. Maintenance sees something else. Planning starts protecting the schedule against assumptions. The plant develops a multiverse, and somehow every universe is behind schedule. The better decision is not to abandon ownership. It is to separate ownership of the operating problem from expertise over the technical blocker, engage the capability the blocker actually requires, and continue leading the rest of the operation. You do not have to become the expert. You have to recognize when the blocker requires one. Read the companion article: https://www.direct-action-system.io/blog/the-sensor-said-pass-the-nut-was-still-loose Get the manufacturing-specific Direct Action starter resource: https://www.direct-action-system.io/manufacturing-starter Read practical leadership and operations articles on the Direct Action Blog: https://www.direct-action-system.io/blog This briefing is part of the Direct Action Briefings series, where Mikey K breaks down practical decision systems for leaders operating under pressure.

See All (78)

About

Leadership, decision-making, and operational execution under pressure. 

Information

  • Creator
    Mikey K
  • Years Active
    2026
  • Episodes
    78
  • Rating
    Clean
  • Copyright
    © 2026 Direct Action System
  • Show Website
    Direct Action Briefings