Listen to Direct Action Briefings on Spotify, Apple Podcasts, Amazon Music, or YouTube.

When one operating path goes down, the objective does not automatically have to go down with it. 

A production facility loses power.

That is real.

The line cannot operate normally.

That is real too.

But manufacturing leaders can create a second problem when they allow one blocked operating path to define every resource connected to it.

The building is down, so the people wait.

The equipment is unavailable, so the schedule freezes.

One path stops, so the whole objective is treated as stopped.

Sometimes that is necessary.

Sometimes it is not.

That difference matters.

On July 27, 2026, severe storms moved through eastern Wisconsin. The National Weather Service confirmed an EF-3 tornado developed in the Appleton area with estimated peak winds around 140 mph before moving through Fox Crossing and Menasha. Wisconsin declared a state of emergency the next day after the storms caused significant damage, including power outages across the affected area.  

Pierce Manufacturing was caught inside that operating pressure.

What the company did next gives manufacturing leaders a strong example of what it looks like when an obstacle remains in place but the operation refuses to let that obstacle define every available path.

The Leadership Trap

Manufacturing naturally creates dependencies.

A person works at a station.

A station belongs to a line.

The line belongs to a building.

The building depends on power, compressed air, network connectivity, material delivery, maintenance support, inspection capability, tooling, and dozens of other operating conditions.

That structure is necessary.

The problem begins when dependency turns into captivity.

If the building cannot operate, leaders can start thinking as though every person, every skill, every useful hour, and every available option connected to that building has become unusable too.

That is not always true.

The physical obstacle may be fixed.

The resources attached to it may not be.

The danger is confusing the current path with the objective.

Obstacle Redirection exists for exactly that kind of condition. The tool is designed for an active obstacle that is already interfering with progress, when direct correction is not the best immediate move and another controlled path can keep the objective moving. The failure pattern it is designed to prevent is path captivity.  

What Usually Happens Under Pressure

When a plant loses power, the first instinct is obvious.

Restore power.

Get the equipment back.

Get the line running.

Recover the schedule.

None of that is wrong.

The problem is treating restoration as though it is the only useful action available while the obstacle remains active.

That creates waiting.

People wait on utilities.

Production waits on facilities.

Planning waits on production.

Customer commitments start absorbing the delay.

Leadership spends all of its attention staring at the blocked point because that is where the failure occurred.

The harder question is different:

What part of the objective actually has to remain behind that obstacle?

That question changes the read.

Field Note

A blocked facility does not automatically mean every usable resource connected to that facility is blocked.

The obstacle may still be real.

The damaged path may still need repair.

The operation may still lose output.

But leaders should separate three things:

What is physically unavailable.

What remains usable.

What can move.

That distinction can preserve options while the original problem is still being resolved.

Real-World Scenario: Pierce Manufacturing

Pierce Manufacturing produces custom fire apparatus and operates as an Oshkosh Corporation business. Its broader manufacturing network includes facilities in multiple states, and Pierce has invested heavily in expanding production capacity and manufacturing flow.  

Then severe weather struck the Appleton area on July 27.

Pierce publicly reported that a power outage temporarily interrupted operations at one manufacturing facility. The company then said production team members were redirected to other Pierce facilities until power was restored.  

That distinction is the entire reason this case matters.

Pierce did not publicly say it moved complete production orders.

It did not say specific work cells were transferred.

It did not identify which employees went where.

It did not disclose how much output the personnel movement recovered.

We should not fill in those blanks.

What the evidence establishes is narrower and more useful:

One manufacturing path became unavailable, but Pierce did not leave production team members automatically captive to that unavailable path.

The company also reported roof damage at its aftermarket parts warehouse. At the time of its July 27 statement, Pierce said it expected no effect on parts availability, expected shipments to resume the next day, and expected full production operations to return July 28.  

Those were expectations reported during the response. I did not find a later public Pierce statement that separately verifies every element of that anticipated July 28 restoration, so this article does not treat the forecast as a confirmed final outcome.

That evidence boundary matters.

The value of this case is not proving that the redirection restored a certain number of production hours.

The public information does not tell us that.

The value is seeing the operating decision clearly:

The obstacle remained active, but at least one resource tied to the affected path was redirected elsewhere.

The Problem Path

The original operating path was straightforward:

People.

Facility.

Power.

Production.

Then the power dependency failed.

The weakest read says:

Facility unavailable equals workforce unavailable.

The better read separates the pieces.

The facility had a constraint.

The production team still represented capability.

The question became whether some of that capability could be useful somewhere else while the facility problem remained under restoration.

Pierce's statement shows that it could be redirected.  

The Blockage

This was not a small inconvenience.

The National Weather Service documented significant storm damage across the Appleton and Menasha area, and Wisconsin's emergency declaration specifically cited tornado damage, high winds, hail, power outages, and disruptions to public water systems.  

That matters because the obstacle was not simply an internal production scheduling problem.

Pierce could respond to its operation.

It could not simply order the regional recovery environment back to normal.

Its own statement thanked utility crews and emergency-response personnel as work continued to return operations to normal.  

So manufacturing leadership had to operate while an external dependency was still being restored.

That is where path captivity becomes dangerous.

If the only acceptable operating plan is:

Wait until the original path returns,

then an external obstacle owns the timetable.

The Decision Point

Obstacle Redirection does not mean moving everything simply because something went wrong.

That would create another form of chaos.

Not every operator can work at every facility.

Not every line can absorb additional people.

Not every work order can shift.

Not every process is interchangeable.

And the Pierce public statement does not tell us how those questions were handled.

The recognition point is simpler:

Do not assume the blocked path has authority over resources that may still have another legitimate use.

That is where a manufacturing leader needs to stop looking only at the failed point and start looking at what can still move under control.

The Next Movement

This is what makes the Pierce case stronger than a generic business-continuity story.

The public action was specific:

Production team members were redirected to other Pierce facilities while power restoration continued.  

The obstacle was not declared solved.

The powerless facility was not magically operational.

The original path remained under recovery.

Another resource moved.

That is the principle.

The objective was no longer treated as completely captive to one unavailable location.

Consequence Chain

When leaders fail to separate the obstacle from the objective, the consequences can spread quickly.

A facility constraint becomes idle capability.

Idle capability becomes lost productive time.

Lost productive time adds schedule pressure.

Schedule pressure creates recovery pressure later.

Recovery pressure can drive overtime, rushed sequencing, overloaded downstream processes, maintenance compression, and quality exposure.

Not every consequence will happen every time.

But the chain begins the same way:

One obstacle is allowed to control more of the operation than it actually has to control.

The opposite mistake is just as dangerous.

Redirection without control can move the problem somewhere else.

Send people into a facility that cannot productively absorb them, and you have not protected the objective.

You have relocated congestion.

Move work without the right tooling, quality controls, materials, instructions, authorization, or capacity, and you have not cleared the path.

You have created a second obstacle.

Obstacle Redirection is not dumping the problem onto somebody else's floor.

The tool specifically requires the remaining issue to stay owned and the new path to stay controlled.  

The Better Read

The better read is not:

The plant is down. Move everybody somewhere else.

That is not discipline.

The better read is:

What exactly did this obstacle block, what remains usable, and what does not need to remain trapped behind the same constraint?

That creates a very different leadership posture.

You can respect the severity of the outage without surrendering every available option to it.

You can continue restoration without confusing restoration with the entire operating objective.

You can protect movement without pretending the obstacle disappeared.

How This Fits the Direct Action System

Obstacle Redirection sits inside Decision Execution and Problem Navigation, or DEPN.

CSA helps clarify what is actually happening.

DEPN then helps determine how the problem should be navigated instead of treating every obstacle the same way.

In this case, the critical distinction is that the obstacle is already active. This is not about avoiding something that might happen later. It is about recognizing that the current path is blocked and determining whether the objective can continue through another controlled path.

From there, risk still matters. Moving people, work, material, or sequence can expose another operation if the consequences are not considered.

The goal is not movement for movement's sake.

The goal is controlled progress.

The Point

The power outage mattered.

The facility mattered.

Restoration mattered.

But the unavailable building did not automatically have to define every productive option associated with it.

That is the operating lesson.

The obstacle can remain real without being allowed to own the entire objective.

That is what Obstacle Redirection is designed to help leaders recognize.

A Practical Field Exercise

The next time one manufacturing path becomes unavailable, do not begin by designing the workaround.

Start by improving the read.

1. Name What Is Actually Blocked

Do not say, “Production is down,” unless all production is actually down.

Ask:

What equipment is unavailable?

What facility or work center is affected?

What process dependency failed?

What specific objective can no longer move through that path?

Precision matters.

2. Separate the Resource From the Location

Ask:

What people remain available?

What skills remain available?

What material remains usable?

What capacity exists elsewhere?

What is truly location-dependent?

The goal is not to move anything yet.

The goal is to stop treating every connected resource as equally blocked.

3. Challenge the Single-Path Assumption

Ask:

Are we waiting because waiting is required?

Or are we waiting because the original path is the path we are used to?

Those are not the same thing.

4. Keep the Original Problem Visible

If another path exists, the original obstacle still needs ownership.

Do not let a successful workaround become permission to forget the problem that created it.

Redirection protects the objective. It does not erase responsibility for the obstacle.

What Leaders Should Watch For

“We cannot do anything until this is fixed.”
Sometimes true. Sometimes an assumption. Find out which.

Every resource is being treated as part of the failed path.
A building, line, machine, person, material lot, schedule, and customer commitment are connected, but they are not the same thing.

The workaround is creating another bottleneck.
A redirected resource that overwhelms another work center is not a clean redirection.

The alternate path has no clear limit.
Temporary routes have a habit of becoming permanent when nobody defines when they stop.

The original obstacle has lost ownership.
If everyone celebrates the workaround and nobody owns restoration, redirection has become avoidance.

Why This Matters for Manufacturing

Manufacturing is full of fixed infrastructure.

Machines are bolted down.

Utilities feed defined areas.

Tooling belongs to processes.

People develop specialized skills.

Quality controls attach to specific operations.

Material moves through defined sequences.

That physical structure makes manufacturing powerful.

It can also make leaders mentally rigid.

When one piece of the structure fails, the temptation is to see the entire structure attached to it as unavailable.

Sometimes it is.

Sometimes the better operating question is:

What still has another path?

That question can apply to labor, material, inspection, tooling, production sequence, staging, maintenance support, or customer-critical work.

The answer will be different every time.

The discipline is remembering to ask.

Where Obstacle Redirection Fits

This is where Obstacle Redirection fits.

It is a path-clearing strategy for an obstacle that is already interfering with the objective when direct correction is not the best immediate move and another controlled path exists.  

It does not mean ignoring the obstacle.

It does not mean improvising without controls.

It does not mean transferring a problem to another department and calling it progress.

It means recognizing when the obstacle and the objective have become unnecessarily tied together.

The full application goes further into redirection paths, ownership, reassessment, failure points, and how to determine when Obstacle Redirection is the wrong DEPN strategy.

That belongs inside the paid DEPN training path. The blog stays at recognition level by design.  

What to Practice This Week

Look at the next manufacturing constraint that stops movement.

Before accepting the stop, ask:

• What exactly is blocked?
• What remains usable?
• What resource am I treating as unavailable only because it is connected to the blocked path?
• If another path exists, what problem would still remain after we use it?

Do not force an alternate path.

Just make sure you can see one before declaring that none exists.

Final Thought

Manufacturing leaders spend a lot of time removing obstacles.

Sometimes that is exactly the job.

Repair the machine.

Restore the utility.

Correct the defect.

Fix the process.

But leadership discipline also means recognizing when the operation does not need to stand still while the obstacle is being resolved.

Pierce's July 27 response gives us a clean real-world example.

A facility lost power.

The facility problem remained active.

Production team members were redirected to other Pierce facilities while restoration continued.  

The outage owned the building.

It did not automatically have to own every productive option connected to it.

That is the read.

---

Keep the Objective Moving Without Letting the Obstacle Choose the Path 

When a production path becomes blocked, the first move is not always to attack the obstacle.

Start with the Manufacturing Direct Action Starter Sheet.

Use it to slow the read, identify what is actually blocking the objective, separate what has truly become unavailable from what can still move, and get clearer before deciding how to respond.

When the situation is clearer and you need a structured way to determine what kind of response the problem requires, move into Decision Execution and Problem Navigation.

Obstacle Redirection is one strategy inside DEPN.

DEPN is built for the decision that comes after the situation is clearer:

What kind of problem am I facing, and how should I move through it without creating the next one?

DEPN Fast Track provides the compressed starting point for learning how to recognize different obstacle conditions, select the appropriate DEPN strategy, and keep the objective moving under pressure.