Standing on the inbound dock after unburying an underperforming receiving process, I looked up from my time study to see multiple forklifts moving simultaneously with freedom of navigation. It literally took my breath away, as I witnessed flow in its purest, most beautiful form return to the space.

One of my problems in explaining my work is that most language for continuous improvement belongs to business. Labor hours. Cycle time. Productivity. Throughput. Waste. Rework. I know and use those words because they matter. A company must make profits to exist. A warehouse needs to move product. A process that burns time, space, and motion costs somebody something, even when the cost is hidden in the daily rhythm that looks normal.

That CI language has given me access for most of my career. It gives leaders a reason to allow me near the system. It lets me explain why something matters in terms the business can recognize. When the work starts moving better, savings almost always appear. Sometimes obvious, other times those savings must be excavated out of extra touches, excess travel, hidden rework, or the daily cost of people interpreting a process. I am grateful for the savings that results from my work because it’s real, and because it creates the permission to keep doing the work.

It’s more difficult to explain that the savings is not what makes me come alive. Savings is just the receipt for my work. They prove something valuable happened, and the business is right to care about them. But the thing I am really drawn to is the living motion of the floor itself. That is my artistic medium. A musician works in sound. A sculptor works in stone. I work in motion and patterns. I work in the space between what the process claims to be and what the floor is doing to keep it alive.

I do not experience an operation as a list of tasks, rather a field of relationships in motion. People, equipment, product, space, timing, information, and purpose are all moving together. Sometimes they cooperate. Often, they fight. Sometimes the whole operation is absorbing the cost of a system that has drifted away from its intended shape. Cases still move. Orders still ship. Up close, I see the loss of flow to constraints and ambiguity.

That is usually where my attention goes first. I notice the small places where the next move is not obvious. Or when an experienced operator must make an unnecessary judgment the process should prevent. I notice when space forces equipment into awkward negotiation and product shows up in a form the building cannot cleanly absorb. Those are places where money disappears and human intelligence is spent holding together something broken.

I am different from most who are placed under the same general heading of continuous improvement. Like most, I use the tools, build the case and measure the work. Each is useful, and I do not dismiss them. But I do not begin with the spreadsheet. I begin with the motion. In order to access my gifts of clear seeing, I must witness how the system behaves. I see exactly where the workaround is the process.

A process usually has a truer shape than the one the organization is living with. The work knows, in a practical sense, what it is trying to become, but ambiguity covers it. Workarounds grow around the unclear places. Tribal knowledge fills the gaps. People invent small ways to survive the day: extra checks, local rules, little decisions that never appear in the documented process. Because the work keeps moving, the organization begins mistaking the survival pattern for the process.

That is where I usually start. I am trying to find the original shape underneath everything people added to keep the work moving. The first material I carve away is ambiguity. Unclear versions of sequence, ownership, handoffs and expectation must be chipped away. Ambiguity forces workers to interpret while they are doing, and once that starts, compensation grows around it. Experienced people learn the hidden rules. New people step on the hidden mines. Supervisors spend their day translating exceptions. The system survives by hiding how much of its stability depends on people carrying what the process failed to make clear.

When ambiguity is removed, motion appears first. That is the part I love. The explanation for the improvement may still be incomplete, but the floor starts to move differently. Next, handoffs clean up and the lurching eases. The room finds its pulse. People no longer must burn attention to follow the system, so their attention returns to the work itself.

That is the beginning of flow. Not speed. Not busyness. The first sign is cleaner motion. The work starts taking its proper shape, and the floor begins to show what it had been trying to become all along.

I have seen this happen in both large and small ways. A path opens. A staging point moves. A sequence becomes clearer. The handoff is changed so the next person receives usable work instead of a problem to interpret. The effect can look almost ordinary from a conference room because conference rooms flatten motion. On the floor, the change is like lightning striking. Equipment stops negotiating with space. Workers no longer must pausing to solve the same preventable question. The room can be busy, but also becomes calm.

That is the moment I stop and watch. To someone else, it may look like forklifts, carts, pallets, cases, people, and equipment moving through a building. To me, it looks like a sculpture coming alive. Everyone is moving differently, in different directions, with different tasks and timing, yet the movements belong to a single unspoken purpose. That is the part that brings me joy before I have words for it. The analysis comes later. The savings come later. First the floor moves, and something in me recognizes that the system is more honest.

That is why I compare it to music. When a band locks in, it becomes greater than any individual instrument or performer. You feel it. Each person is still playing a separate part, yet the parts belong together. A warehouse can do that, also. A good floor has a pulse. A great floor finds a groove. When it happens, the room becomes more awake. The energy rises without turning frantic. Possibility returns because the system has stopped spending all of its strength surviving itself.

The operators change in those moments too. Their competence stops being trapped inside rescue. Their intelligence returns to circulation. You see it in timing, coordination, anticipation, and economy of motion. They move at the right moment instead of the urgent moment. They fit into the field around them without forcing the whole room to make space. They start using their knowledge as craft instead of as shock absorption for bad design. That is indescribably beautiful to me because it is precise and purposeful. Every movement has a reason. The work lands exactly where it belongs.

This is also the place where cost savings is present. The company saves money because the floor stops paying hidden taxes. Less wasted motion, rework, searching, and all the other wastes. Workers spend less human intelligence managing ambiguity. The business gets real value because the work is closer to its intended shape. The people inside the process get relief because the system asks less of them in the wrong places and allows more of their actual skill to show up in the right places.

That alignment is the part I care about most. Serving the floor and serving the business can be the same act when the system is restored instead of merely pressured. Many organizations try to pull money out of operations by squeezing the people closest to the work. That creates motion, effort, compliance, and a great deal of hidden compensation. Real flow does something different. It removes what should not have been there, lets the work take a cleaner shape, and allows the savings to appear because the system is no longer wasting itself.

This is what I want a senior leader to understand about me. I am not animated by the performance of continuous improvement nor interested in dressing up obvious observations in corporate language. I am useful because I can stand inside a living system and see where it has become untrue. I can see where the represented process and the real process have separated. I can see where the workaround has become the process.

Then I can usually help remove enough of that burden for the real process to start showing itself again. That is where the money is. That is where the dignity is. That is where the craft is. It is all connected. The same change that saves labor can also release operator competence and restore rhythm. A cleaner handoff reduces friction, increase trust, and makes the work easier to teach. The financial value and the human value are often coming from the same source: the system has stopped forcing people to compensate for what it should have made clear.

That is why I keep returning to the floor. It is the only place where the system tells the absolute truth. A dashboard is useful, but it can also be too clean. The floor has less patience for fiction. It shows where the burden went, where the rhythm broke. It shows when the room is holding its breath. And sometimes, if you remove the right ambiguity and give the work enough room to take its proper shape, it shows you something beautiful.

Being present the moment the floor comes alive. That is the medium I work in. Motion with purpose. Relationship made visible. Sequence becoming clear enough that the next move feels natural. People, equipment, product, space, and timing moving in a way that finally belongs to the work. The savings matter, and I know how to find them. But the reason I do this, the reason I can stay with a system long enough to see what others miss, is because every once in a while the hidden form appears, the room finds its rhythm, and the work shows what it had been trying to become all along.

Moving sculpture.

-30-

Subscribe now

Author’s Note

This piece is the companion to The Workaround Became the Process. That essay is about drift. This piece is about the other side of that same reality: what I see when the burden starts to lift.

I have spent most of my career using the language of continuous improvement because it gives organizations a way to understand the value of the work. But that is not what first pulls me to the floor. Motion pulls me in.

I experience a working floor as a living field of relationships and purpose all moving together. When ambiguity is removed and the work takes its proper shape, motion becomes cleaner. The next move becomes obvious. Operators stop using their intelligence to compensate for confusion and begin using it as craft.

That is the part that feels like art to me.

The savings are the receipt. The art is the moment the floor comes alive.

Most leaders think a warehouse receives product.

That’s true in the most superficial sense. Trucks do arrive. Trailer doors are opened and pallets are unloaded. Receivers receive. Putaway puts away. If you sketch the process on a whiteboard, it looks like clean and organized: Unload, Receive, Putaway. A neat sequence of control.

But that is not what I see when I stand on a dock. I witness the exact moment where burden changes hands.

When a pallet comes off a truck, for a brief second, the written process works. Then the real system introduces itself quietly. Mixed SKU pallets land, and instead of flowing forward, they stall. A worker must rework it, to make the next process possible. Cases are downstacked to a seperate pallet. Weight gets shifted. Layers get examined. The pallet that was supposed to be moving now has to be translated by hand into something the building can tolerate.

That moment matters in ways dashboards cannot typically illuminate.

It reveals a failure by someone in the supply chain to satisfy the downstream putaway requirements of one SKU/one pallet per location in a warehouse. In order for a mixed SKU pallet or floor loaded freight to work here, it must be stable enough to travel safely, sorted enough to separate by SKU, identified clearly enough to be received accurately, and built in a form the putaway and replenishment process can actually absorb. If it arrives built in a way that violates those downstream requirements, the missing work cannot be avoided. Someone on the dock must convert it by hand into something the building can use. That is why the work appears there. The requirement never went away. It simply arrived on the inbound dock and became manual labor.

That is the kind of activity most leaders never really see.

They see activity and people working. They see forklifts and receivers moving and assume the operation is functioning. But a warehouse can lie to you all day long if you do not know how to see what is really happening. Motion is not the same as flow. A team can be working heroically while the system quietly steals life from them one adjustment at a time.

The written process almost never tells you this.

That process assumes readiness. It assumes that what arrives can enter the building’s flow more or less as is. It assumes that what is coming into the facility meets the condition the downstream process can absorb. But that assumption is wrong more often than leaders realize.

Shippers optimize for their own realities centered around cost, cube and trailer utilization. Loads are build for order profiles, labor convenience, local workarounds, or whatever pressure their shipping department is under that day. The freight arrives at the downstream facility in a condition that violates what the receiving and putaway system actually requires.

At that point, the requirement does not vanish. It cannot vanish. The pallet still has to become something the building can store. If it cannot do that in the condition it arrived in, then a local worker must do the missing work. Not because anyone chose it. Because the system leaves no alternative.

That is the hidden theft.

One part of the network gets the convenience and savings. Another part gets the burden and cost. And when that burden lands on the dock, it spreads fast.

A pallet that should flow now becomes WIP until a receiver, who should be verifying, now must rebuild. Space that was supposed to support movement now has to absorb correction work. A forklift path tightens. A staging area starts to do the work it isn’t funded to do. The whole facility begins paying, in real time, for an upstream decision it did not make and cannot refuse.

This moment is a transfer of burden across organizations.

Freight that does not arrive in a form the building can process occurs when an upstream actors fails to satisfy that requirement. The burden slides downhill until it reaches the point where physical reality forces honesty. That point is often the dock. The dock is where abstract decisions translate into one company’s convenience becomes another company’s labor.

That is why I stand there.

I am not standing there to admire activity, rather to observe where the written process loses contact with physical reality. I am standing there to find the hidden constraints that create dwell and cost long before anyone has language for them. I am standing there to see the points where the system is being quietly asked to do work it was never designed to do.

That work is often invisible to the untrained eye precisely because it does not announce itself dramatically. There is usually no siren, it just quietly happens and hidden costs accrue.

A little more attention here or a second touch there. A pallet set down “for now” in a place that was meant to stay open. A receiver shifting from formal work to translation work. A lift driver negotiating with the aisle instead of moving cleanly through it. A building that still appears to function, but now functions like a body carrying tension everywhere.

That is the cost.

Not just labor. Not just time. Not just dwell.

Burden.

Burden dropped into the system one pallet at a time until the whole operation starts compensating in ways that no standard work document ever mentions.

This is why I have become so sensitive to hidden constraints. I know the written SOP is never the whole story. The real story is in the conditions required to make that path possible. If those conditions are absent, the missing pieces do not stay abstract. They are supplied manually by the people inside the system. The warehouse becomes the translator of other people’s unfinished work.

And once you learn to see that, you start seeing much more than a receiving issue.

What looked like a bad pallet becomes an upstream design failure. What looked like a local delay becomes a cross-company burden transfer. What looked like “the team handled it” becomes “the team absorbed a cost leadership never saw.”

That last one matters.

Because there is a moral dimension to this. Moral in the sense that systems can be arranged in ways that place unnecessary burden on human beings and then normalize it so thoroughly that no one even thinks to question it. A person spends part of their day compensating for distortion that never should have reached them, and because they are competent and conscientious, the organization calls that normal work.

It is not normal work. It is forced accommodation.

And the more capable the people are, the easier it is for leadership to miss. Good operators can hide enormous design failure simply by absorbing it. They keep things moving. They save the day in small ways, over and over, and the system repays them by making their extra effort invisible.

That is one of the reasons standing still matters so much.

If you move too quickly, all you will see is motion. And motion will lie to you.

If you stand there long enough, though, the pattern is unmistakable. You begin to see which pallets move cleanly and which ones arrive with a debt attached to them. You begin to see where space is being borrowed from flow and where degrees of freedom are being lost. The warehouse is not merely processing freight. It is correcting for upstream realities, often at significant hidden cost.

That kind of seeing is not automatic.

It takes a skilled set of eyes to see it clearly.

It takes someone who can hold the written process in one hand and the physical truth of the building in the other, and feel the gap between them. It takes someone who can watch a pallet and understand not only what is happening to it, but what had to be true for it to flow cleanly, what is missing, where that missing condition is now being supplied by hand, and how the cost of that burden will propagate outward through the facility. It takes someone who can look at a dock and see not just work, but the invisible negotiations the system is demanding from people every minute.

That is what I do.

I stand at the seam where burden changes hands, and I make that transfer visible.

I can see when one part of the network is surviving by forcing another part to compensate. I can see when a pallet arrives carrying hidden labor inside it. I can see when the building has stopped flowing and started negotiating. I can see when the team is doing work the official process never admitted existed. And because I can see it clearly, I can help others see it too.

That clarity matters because once the hidden burden is visible, the conversation changes. You stop blaming the nearest operator and begin asking the better question: what requirement exists downstream that is not being satisfied upstream, and why are we paying for that failure here?

That is the doorway to real improvement.

Not more effort. Not more pressure. Not another speech about accountability.

Truth.

Every once in a while, you remove enough distortion that the building tells you the truth back. That moment is not just operationally satisfying. It is beautiful.

Because what you are seeing is not people working harder. You are seeing unnecessary burden removed. You are seeing right relationship restored. You are seeing a system stop lying about what it requires and begin to move truthfully again.

Most people will never notice that moment for what it is.

I will.

Because seeing hidden burden clearly is a skill.

And it is mine.

-30-

Author’s note: I write longer-form essays at Chasing Omniscience and shorter field observations at Seeing Systems Clearly. If you are interested in hidden drift, burden transfer, and the patterns most systems teach themselves not to see, that is where to find me.

Author’s pre-note: Last year, I wrote You Can't Fix What You Don't Understand and The Death Cult of the Operational Dashboard to call out that many of today’s leaders have lost touch with the actual work they manage. This is a modest proposal to begin addressing that problem. Baby steps.

Dashboards tend to hide and oversimplify complexity. In predictable times, they functioned. Steps identified and taken in one process would bring predicable improvements without unintended consequences. This wasn’t alchemy, the people making those changes were almost always in the same space as the work. Presence allowed feedback and better outcomes.

Then the process owners were told to work from home. Alignment calls, excel action trackers and monthly review decks kept us connected to a now-distant process. It worked but the world and work environment we live in changed dramatically in the meantime. And a lot of the people that own processes never really visit them. Those processes naturally drifted, since presence gave way to managing KPIs. The handoffs between the processes, it often turns out, weren’t owned by anyone.

What prompted me to write this is a renewed call for people to walk their processes again by thought leaders in the business leadership space. Mine is an effort to open eyes and return respect to the place where the work is done. This is an open request to the folks that conduct monthly operational review calls with slides, action items, a safety minute, and all the bells and whistles.

When you schedule the next one, tell everyone invited to show up in person and bring PPE. Create the slides as usual, if you must, but don’t waste time going through them. Instead, take them on a field trip to relearn the value stream. Literally, skip the meeting and take the entire team to the floor, the place where the actual work is done.

• Divide into teams and have each group follow a different workstream from end to end. Start at the beginning and stand there long enough to witness and understand the flow. Pay attention to where things slow down or seem unclear.

• Follow the value stream step-by-step, down the aisle and around the corners. Notice each handoff along the way. Stay where it stays until it is touched, checked, moved, or delayed. Stand in place and dwell with it. Feel the delay.

• Most of what is wrong in a system doesn’t show up when things are moving cleanly. It shows up in the form waiting, confusion from lack of clear standards, and tiny adjustments people must make to keep things going. You will feel it when you are standing there with nothing happening and no clear reason why.

• When your target reaches its final destination, start again and follow it a second time. The first pass shows you motion, the second shows you pattern. Keep going until you understand it and can explain it to others.

• Talk to the workers. Pay attention to the number of steps, the extra touches, the distance traveled, and where things slow down or don’t line up as you thought they did.

• At the end, bring everyone back together and ask them to explain the steps in the process they observed. Have them explain every step in the sequence. Listen for explanations that are vague or inconsistent. That is usually where the system is not understood as well as people think.

• Ask what surprised them and what they would change. The result might surprise even the most jaded operational executive.

The COVID era and its work-from-home shift didn’t create this lack of clarity, but it certainly accelerated it in a way that most organizations haven’t fully accounted for. Work environments, previously siloed, became fragmented pockets of knowledge about segments of the system. People became very good at managing their part, but fewer and fewer can describe how the system actually fits together from end to end.

The dashboard, already a star for simplification through aggregation, became the field of play. Leaders manage KPIs through actions, instead of through the work itself, not because they’re wrong, but because that is what the system now asks of them.

But the work never moved.

It is still on the floor, and it still depends on sequence, timing, space, and touch to function. When it’s leaders are not close enough, they risk managing outcomes without fully understanding how those outcomes are created. Over time, that gap shows up not as failure, but as friction or waste. The system still runs, but it runs heavier and slower than it could if tuned properly.

So take one meeting and give it back to the work.

Don’t make it a tour or view this as a grand symbolic gesture. Be deliberate about it. Stay in the system long enough to understand how it actually functions.

Because if no one in the room can walk it end to end and explain how it works, then no one owns the system. And systems without ownership don’t fail all at once. They drift.

Drift is your system under decay. And that monthly meeting is where it’s aggregated and explained away. Better you see it clearly.

Author’s Note

I may seem anti-dashboard. I’m a quantitative analyst at heart and appreciate the rich analysis one gets for what is really happening in well-aggregated data. But dashboards are not the system, just snapshots of a system that lives somewhere else.

My call is not to abandon structure, but rebalance it by getting close enough to the work that your understanding is grounded again, and by making sure that someone can still walk it, explain it, and improve it without relying on abstraction.

Uncontrolled systems lead to bad outcomes. Systems in control make sense and this is a call to return systems to control state. To read more of my essays, subscribe to my Substack, Chasing Omniscience.

Subscribe now

Early in my career, a mentor told me a story that stayed with me. Bringing Lean thinking to his company was his project deliverable, and he was knee-deep in Who-Moved-My-Cheese-style management unwilling and unable to accept any suggestion. No matter the move, red tape slowed his process as fear led to consistently hard pushback.

The system was telling on itself.

Rather than continue an asymmetric battle with site leaders, he reframed his idea around worker safety. The two overlap more than most people realize. When he visited a new site he didn’t begin with charts or presentations. Instead he gathered a few workers and asked them a simple question.

“Please take me to the place in this building that nobody wants to work,” he’d instruct. “Show me the job everyone tries to avoid.” The workers always knew without prompting; they always had a place in mind.

Every building has at least one, usually many more. A corner, a cage, or a rack where problems go to dwell in plain sight. When my mentor walked to that spot the workers suggested, he was almost always standing over a big target.

The idea stayed with me. I don’t usually ask it out loud, but I start looking for the answer the moment I walk into any operation. I was built for this kind of observation, since I see systems in motion in my mind. I notice the flow and when it drags, the hidden friction and sloppy handoffs that occur when nobody owns a process. Years of walking operations has sharpened that instinct, but the core of it is simple curiosity about how work actually moves.

A pallet or many sitting where pallets usually don’t or should not sit, or tools scattered because nobody returned them. Dust caking on flat surfaces in a stuffed but abandoned corner that suggest nobody is really responsible for that space anymore. Areas that quietly absorb labor and attention because the system never fully accounted for their existence in the first place. Each almost always tells the tale of hidden inefficiency or even risk.

These are not housekeeping problems. They are signals. They tell you the operation is being led as a series of individual tasks rather than a complete in-dwell-out system. Strong operations run as systems. Work moves forward with a purpose and preplanned rhythm and cadence. Ownership is clear and problems get corrected before they have time to spread.

Conversely, weak operations slowly become a collection of activities. Each group of workers performs its work and then hands the result to the next group without regard to the dwell, flow, or number of touches. Small disruptions accumulate in the spaces between those activities. Workarounds appear so the day can keep moving. Eventually those workarounds become the process.

The most dangerous part is that the people inside the building stop seeing the drift. What started as temporary becomes normal. The pallet in the corner stops looking strange, and soon more join it. The extra touch in the process starts to feel necessary.

I’ve walked through buildings where operators were working incredibly hard while the system quietly worked against them. None of it showed up clearly in the reports, dashboards or trackers but the building itself told the story.

This is where leadership matters most.

In strong operations leaders stay close to the work. They walk the building. They see the signals early and correct them while the problems still are small. The goal isn’t about cleanliness it’s sustaining operational continuity. When a system loses continuity, flow begins to break down.

What I see more often now is leadership trying to understand operations from a distance. Dashboards and trackers begin to be the source of truth. Meetings form around explaining what the numbers might mean and how to make them turn green. When the explanations don’t settle the conversation, another tracker is added so leadership can stay informed. It feels like control, but it’s just activity.

No action list can replace an understanding of the nature of the system and how it works. Action without understanding is just motion.

Put plainly, you cannot fix what you don’t understand. How it runs, and stops and struggles and flows. That is earned knowledge by those close to the work who look and listen to the real work being done. Dashboards and trackers are a way to manage the conversation about the numbers while the real system continues doing what it is doing.

Meanwhile the building is still there telling the truth.

The corner nobody wants to go to still exists. The signals are still visible to anyone willing to walk the floor and look at the work with fresh eyes.

Operations are physical systems. Work moves through space. When that movement begins to break down, the evidence shows up in the building long before it shows up in the reports. That’s why my mentor’s question still works.

If you want to understand a system, start by asking the people who work there one simple thing.

Where is the place in this building that nobody wants to go?

Start there. The system will tell you the rest.

-30-

Share

Author’s note: I see operations as systems in motion. Flow, breakdown, and recovery show up to me before metrics do. Once you see it that way, it’s hard to walk a building without noticing where the system is telling on itself.

Author’s Note

If system flow matters to you, this work isn’t optional. Volatility grows exponentially in unstable markets and it will reveal itself whether your leadership architecture is sound or not. Designing Supervisory Authority in Unstable Systems.

Volatility is a part of life as an operations supervisor. So is vagueness. But unlike customer-driven volume forecast volatility, institutional vagueness is squarely a leadership choice. For a supervisor, the vagueness arises in practical ways.

• They are expected to control labor costs without a clear understanding of shift’s throughput capacity.

• They are measured against productivity targets without a universally shared understanding of the system’s natural operating range or even a defined preferred method to instruct toward.

• They are told to “own their shift,” without the boundaries of that ownership defined and resourced properly.

• When targets miss, they are accountable for the outcome but not always empowered to manage it deliberately.

From the senior leader’s vantage point, the supervisor role and performance can appear inconsistent or haphazard. From the supervisor’s vantage point, they often feel like they are navigating movement blindfolded and without a map. Why such a big and growing disconnect? Economic volatility is causing a change in system flow, and the front lines is where volatility outpaces organizational readiness for most in the warehouse space.

Many of today’s leaders built their early and mid careers in a more stable economic time period. Labor performance ranges remained generally steady during the past 15 years as has employment and wages. Operational imprecision on a day-to-day basis did not compound into greater volatility quickly before now. A little vagueness could be absorbed by a site at minimal cost. That is no longer the case.

When capacity is undefined and volatility unpredictable, supervisors are left to interpret weekly swings in labor need without structural clarity. This is when the system begins to oscillate toward uncontrolled variability, lower productivity and higher costs. Those oscillations are often blamed on the floor leadership, but make no mistake, they are architectural and the result of leadership decisions.

In most organizations, supervisors are thought of as reactive to problems. They are labeled firefighters. They are criticized for inconsistency. Yet firefighting is the predictable outcome when leadership tolerates and often facilitates ambiguity around what stable performance actually looks like at an enterprise level.

If supervisors do not know the true capacity of their shift at multiple staffing levels, they cannot manage flow with precision. Noise often is confused with signal. Accountability looms as a real, personal risk in places where authority is restricted. Supervisors in those environments choose the lowest-risk path. They will escalate rather than act, not because they lack judgment, but because the system does not accommodate for its lack of clarity. It adds complexity and cost without value.

Volatility did not create that condition. It exposed it.

I spent decades inside systems where vagueness was not tolerated because it was not survivable. In thin-margin 3PL environments, understanding capacity is the key to the operation. Labor mix was deliberate. Customer forecasts were viewed as directional inputs, a starting point for labor use. Rolling averages and seasonal patterns were used to calibrate staffing decisions. Voluntary time off and a clear, overtime methodology were structured tools deployed against signal, that the front line supervisors could rely upon.

Supervisors were expected to run their shift like a business because they were equipped to do so. They understood cost per unit, throughput capacity, and where the system normally operated. They adjusted deliberately within defined guardrails. That architecture absorbed volatility locally by ensuring the supervisors had the skills and authority to lead effectively.

You can tell almost everything about the health of an organization by watching its supervisors.

In strong systems, supervisors understand flow. They can describe capacity without guessing. They know what a normal day feels like and can articulate when something has actually changed or degraded. Their presence changes the outcome of a day.

In weaker systems, supervisors are present but not influential. They relay information. They manage tasks as independent actions. They attend meetings. Rarely do they alter the trajectory of their shift because the system, built by their leaders, fails to define clearly what good looks and feels like.

The difference is not personality. It is design.

I coached baseball for years, and there is a simple lesson in that wonderful sport. A player can take the field every inning and step to the plate several times during a game and never meaningfully touch the ball or impact the game. They are present, but the game would unfold the same without them. Supervisors are no different.

If your supervisors can be swapped out and the system behaves no differently, the problem is not personnel. It is system design. Leadership must stop managing symptoms and change its methods. Supervisors treated primarily as controllable expense lines will act accordingly. They will protect themselves before they protect flow. That is not character flaw. It is design outcome.

Most supervisors take their role seriously. They want to run something well. They want clarity. When leadership defaults to suspicion instead of structure, initiative naturally contracts. Decisions move upward away from their point of occurence. Volatility intensifies and challenges control. It is at moments like this, that I often see leadership conclude that supervisors cannot handle more authority.

That conclusion is convenient. It is also often wrong.

If you are cutting heads, reducing bonuses, and tightening work hours while leaving the architecture vague, you are leaving instability in your operation. Cost pressure does not justify structural ambiguity. It makes clarity more necessary and vagueness more expensive.

A practical first step does not require a transformation program. Start with your supervisor pass-down process.

• Make it disciplined. Require supervisors to articulate what was planned, what actually occurred, where performance sat within the system’s natural range, and what represented true signal.

• Sit in on those conversations. Listen for whether capacity is clearly understood or loosely assumed.

• Listen for whether supervisors are making decisions within guardrails or asking permission to act.

You will learn quickly whether your issue is people or design. If your supervisors cannot describe shift capacity and natural variation without looking at their chart or slides from a passdown, the system isn’t properly defined for them. That is not their failure.

Volatility will continue. Whether it is absorbed at the shift level or amplified across the organization depends on leadership discipline. Supervisors can change the game. Or they can stand in position while it happens around them.

The architecture decides.

-30-

Author’s Post Note

This is not theory for me. Supervisors can stabilize volatile operations when they are given clarity and authority. I have seen them blamed for instability when that clarity was absent; and how they bring flow when they live within it. That difference is leadership.

Several years ago I wrote a short piece called “Standing in a Chalk Circle…at 400 feet”. At the time, I thought I was describing an operational insight.

I reread that piece recently and now I understand it differently. Differently, because I experience it in a most different way today. What I thought, at the time. was a story about improving a trailer yard was also a story about how I think.

The yard in question bothered me from the first moment I saw it. Hundreds of trailers, frenetic movement in every direction, tight corners. And trailers were filling the rows between the neat aisles. I felt it in my gut.

The first time I walked into that facility, I matter-of-factly mentioned that the yard must be a problem. It was a pattern I recognized without fully understanding why. When the yard ran at or over capacity, dwell rose. Others saw it too. But the yard was too complex and there were easier problems to solve, so attention went there first. That made sense.

But one metric kept pulling me back upstream: Stem time.

Stem time begins when a yard move is assigned to a hostler, and it ends once the trailer is physically in the door. It varied by trailer and door at this massive site, but it was consistently higher here than at comparable facilities. Not occasionally high. Consistently high. And worse, stem time was hiding a part of the site’s biggest metric: Gate to close dwell time. That is the number the customer paid attention to.

The equipment was the same as other sites. The control systems were solid. Site leadership was disciplined. This was not people being slow. It was systemic slowness that people acknowledged but didn’t understand.

Before I ever bought the drone, I opened Google Earth. From the satellite view, I could see rows of trailers packed tightly, stacked deep. Units clearly buried behind others. The yard was saturated.

There was a quiet certainty in that moment. I had seen enough systems to know this pattern mattered. When you observe flow long enough, you learn to distinguish noise from structure. This wasn’t noise.

If I wanted to understand how three hundred inbound trucks a day actually moved through that site, I had to understand what was happening in the yard. That wasn’t optional. It was foundational.

Google Earth showed congestion. It didn’t show sequence. It didn’t show how many moves it took to retrieve a trailer or how arrival variability fed burial. For that, I needed motion.

I tried to understand it from the ground first. I walked it with a clipboard and stopwatch. Every yard horse looked the same. Trailer numbers blurred together at distance. I couldn’t see the far side of the building. I was watching pieces and trying to infer the whole.

I could feel the pattern, but I couldn’t demonstrate it.

When I work on problems, I look for similar solutions in other contexts. I didn’t need a helicopter. I needed something that functioned like one. Drones were just becoming usable at the time. The one I bought was large and heavy by today’s standards. It could stay in the air for about twenty-eight minutes and return automatically to its takeoff point using GPS.

Subscribe now

The first day I flew it, the hostlers saw it go up. By mid-afternoon I got a call saying it was the best day the yard had ever had. Productivity was up. Everything was moving. That told me I wasn’t looking at the system. I was looking at its participants typical response to being observed.

So I adjusted. I launched from a distance and kept the flights less visible. I varied the timing. The yard returned to its usual rhythm. The extra repositioning moves were there again.

What I kept seeing was simple. To get one trailer to a door, several others had to be moved first. Not because anyone was careless. Because the yard was too full and sequencing broke down. From the ground it looked like constant motion. From above it was a chain reaction.

Trailers arrived in uneven bursts. Space tightened. The right trailer got buried. Drivers moved multiple inbound loads just to retrieve the right one. The cost wasn’t obvious in a single place. It was distributed across dozens of small, repeated moves.

When I could finally see that sequence clearly, the system made sense. The irregular arrivals, the crowded yard, the extra repositioning, the dwell time. It connected. That is when a physical shift locked in. The restlessness I had been carrying dropped. I wasn’t guessing anymore.

The first thing that happened was clarity. Once I could see the system without guessing, the rest followed. We quantified the hidden cost. We built a surcharge model tied to dwell. We explained it to the client. None of that felt complicated after the pattern was legible.

Years later, I recognized that same quiet certainty in myself.

There were situations where something in me signaled that I was too close to the pressure to see clearly. I didn’t name it at the time. I worked harder. Looking back, the signal wasn’t anxiety. It was pattern recognition.

When I ignore it, I narrow. When I respect it, I widen.

In the yard, following that signal led to altitude and clear seeing. In my own life, following it led to distance from the pressure behind unsolvable and misunderstood problems. In both cases, the work improved.

I didn’t learn to think differently. I learned to trust how I think. When I can see flow, I follow it. When I can’t see enough, I change vantage instead of forcing a conclusion. The drone was a tool. The pattern recognition was already there.

The drone exposed more than $1 million in wasted labor and the critical minutes that were quietly murdering Gate-to-Close. But the deeper lesson was this: the system wasn’t mysterious. We were just too close to it. From the wrong vantage point, you mistake motion for progress and noise for explanation. Clear seeing is not a personality trait. It’s a practice. It’s refusing to guess, refusing to blame, and refusing to stop looking until the pattern is unearthed for all to see.

-30-

Leave a comment

Reader’s Note

This began as an operational case study that grew into a lesson in diagnostic discipline. When performance lags and the obvious explanations fail, the problem often is not effort or personnel. It’s perspective. Most systems don’t hide their constraints. We simply examine them from the wrong perspective. Until the pattern is visible, analysis is guesswork.

The drone didn’t solve the problem. It made the system legible. Clear seeing is not intuition. It’s a method to align flow.

— Todd Andrew Owings

It usually shows up on Sunday night as you emotionally prepare for the week ahead. Not as a thought. It feels like physical pressure. Nothing happening, simply your body already dealing with the daily stresses at work.

For me it lived in my chest. There was a tightness that didn’t hurt but wouldn’t let go. Shallow breathing that felt normal, even when I tried to take a deep breath and couldn’t. You feel it to. In your clenched jaw or tight shoulders.

Sitting on the couch with my family, I’d be half-listening, half elsewhere. Running simulations of conversations that hadn’t happened yet. Replaying ones that already had looking for clues. Solving complex problems no one had asked me to solve in order to be prepared. I was donating attention to a system that wasn’t paying me for it in my off hours. And the worse part, I couldn’t see what I was trading away. My peace.

I assured myself this was responsibility and professionalism. That this was what it meant to care. It wasn’t. It was the system living in my body. Not metaphorically. Literally. I could feel it in how my shoulders never quite relaxed. Or how my jaw stayed set unless I consciously let go.

Most of us made a deal early on. We sell a portion of our life for pay. Time, attention, energy, skill. That part was explicit when we joined the workforce. It seemed fair, even. You show up, you work, you get paid. You go home.

I understood that deal. I honored it.

What wasn’t in the contract is how completely the system evolved to follow us home and embed itself as a priority role in our personal lives. It now sits alongside our children’s dance recitals, school plays, vacations, and birthdays as a standing condition. Work no longer competes with life; it carries the assumed right of way. In each of us, there is a reflex built by the system that allows it to take precedence at any moment, often without asking. Over time, we’ve learned to stop ourselves on its behalf.

Phones in our pockets with work email on them. Slack pings during dinner. A low-grade vigilance for the office that never quite shuts off fully. When COVID arrived with work-from-home rules, the system finished normalizing what had already been creeping in.

• Home became an extension of work.

• Constant presence became a condition of employment.

• Availability became assumed.

For years, I didn’t question this. I adapted. I answered messages quickly. I thought ahead. I stayed one step in front of problems so they wouldn’t surprise me. I told myself this was professionalism. I told myself this was leadership. What I didn’t realize was that I was never actually off.

Even on vacation, I wasn’t fully present. Part of me stayed vigilant, rehearsing work concerns in the background. In prayer, my attention slipped. In rest, my body remained on watch.

Then something changed. I healed enough that the vigilance stopped feeling necessary. Not all at once. Gradually. But enough that the background fear softened and that’s when the vigilance stopped feeling useful.

I began to notice that the constant mental rehearsal wasn’t producing insight. The tension wasn’t making me more ethical or more effective. The fear wasn’t protecting anything. It was just there, taking up energy and emotional space.

It also was burning my attention, consuming all sense of presence and occupying space in my life with permission explicitly asked for or granted. That’s when I could finally name it.

This isn’t burnout. It’s earlier than that. It’s the slow occupation of your inner life by a system that is never satisfied. It no longer needs to demand anything of you because it has already moved in and runs alongside your life.

The Deal We Made — and the Deal That Changed

The original bargain was simple. You sell hours. You get paid. Work ends. Life resumes.

The new bargain is quieter and more invasive. The system doesn’t just buy your time. It rents space in your mind. It occupies your nervous system with vigilance you were never compensated for.

Nothing in your offer letter mentioned this.

Yet here we are.

Always available. Always partially on. Always carrying tomorrow’s work problems unless we explicitly give ourselves permission to avoid it. The system didn’t ask you for your permission. It didn’t need to. It just waited until technology made it easy and then normalized it.

At some point I realized something that now feels obvious but didn’t then. I did agree to sell my labor. My fears, those are not for hire anymore. That distinction took me years to see.

Why Fear Felt Normal to Me

Here’s the part that mattered most, and the part I didn’t understand for most of my life.

I grew up hypervigilant, shaped by a chaotic and abusive childhood. Complex trauma wires the body to stay alert as a survival strategy. I learned early that safety is conditional — that it can be withdrawn, that it has to be monitored, protected, and earned. Staying ahead of danger becomes the only reliable way to stay intact.

In that state, vigilance doesn’t register as fear. It registers as responsibility. As attentiveness. As care. Over time, it even comes to feel like maturity. So when work demanded constant alertness, it didn’t feel imposed. It felt familiar.

The system didn’t create my fear. It found it already installed.

Because it felt normal, I never questioned it. I assumed everyone lived this way. I assumed the tension was the price of competence.

It isn’t.

There’s a well-documented pattern hiding in plain sight: people with early trauma are overrepresented among high performers. Not because trauma creates talent, but because it creates adaptations.

• Hypervigilance becomes “attention to detail.”

• Anxiety becomes “urgency.”

• People-pleasing becomes “stakeholder management.”

• Fear of abandonment becomes “commitment.”

These are the raw adaptions of childhood trauma survival strategies. Yet in adulthood, systems value, appreciate and leverage those adaptions.

Healing Changed the Equation

Healing did something I didn’t expect.

As the trauma loop softened, the Sunday-night, before-work vigilance sessions stopped paying dividends. The fear isn’t making me more ethical, smarter or competent. It just burned attention.

I remember the first time I saw this clearly. I was lying in bed, my mind cycling through work as always, when I realized nothing bad would happen if I stopped. No failure would be made more likely nor prevented. No one would be protected. The fear wasn’t doing anything useful. It wasn’t serving the work, and it wasn’t serving me. It was simply there because it had always been there.

That was the moment it became impossible to ignore what was actually happening. The system wasn’t demanding fear. It didn’t need to. It was accepting it. And I had been supplying it automatically, faithfully, without ever stopping to ask whether it was required.

Gabor Maté names this pattern with uncomfortable clarity.

Trauma is not what happens to you.
Trauma is what happens inside you.
And our society is built to exploit it.

That line landed hard because it explained something I could feel but had never articulated.

Hypervigilance often looks like commitment. Anxiety can pass for urgency. Fear can resemble drive to an untrained eye. These states don’t announce themselves as distress; they present as engagement, care, and effort. Systems don’t have to create them. They only have to reward and incentivize them.

I didn’t understand that intellectually at first. I recognized it by watching myself. I noticed how often I stayed mentally engaged when nothing was being asked of me. How easily I volunteered attention, anticipation, and concern long before it was required. Once I saw that pattern clearly, something else became obvious: I wasn’t being pressured to give more of myself.

I was offering it.

In the end, I gave it away for nothing.

Where Gabor Maté shows how fear is installed and exploited inside the individual, W. Edwards Deming warned that the same fear, left unchecked, eventually destroys a system’s ability to see the truth at all.

That was the pivot.

I stopped treating fear as a moral issue and started treating it as a quality defect.

Seeing What My Body Already Knew

There was a moment at work when my body reacted before my language did. This wasn’t a moral revelation or a crisis. It was an example of what happens when you stop ignoring somatic signals and start treating them as valuable information.

I was walking a bottle-pick line in a warehouse. Among the rows, I can across pint liquor bottles. Ordinary, single-serve units. And yet my stomach turned slightly. Not disgust. Not judgment. Just a quiet recognition by my senses that these formats often are associated with maintaining dependence, not occasional recreational use. That association registered in my body before it took shape as a thought.

I didn’t dramatize it. I didn’t condemn anyone. I didn’t pretend I could fix a system that would exist with or without me. I did what I know how to do.

I observed the process. I mapped incentives. I looked for where cost, damage, and waste already lived in the system. I found a small, legitimate lever that aligned with existing priorities, and I acted there. The change was modest. Boring, even.

And it worked.

I didn’t fix the system. I fixed my relationship to it. I reduced the distance between what I noticed and how I acted, using the system toward an end it already recognized as valid.

And something important happened.

The internal noise dropped.

What I Reverse-Engineered

I didn’t set out to build a philosophy. I simply noticed a change in myself and worked backward to understand why it held. What I learned is simple, and it’s not aspirational.

• When something feels off, I no longer rush to explain it away or convert it into judgment. I treat the bodily signal as early data. Not emotion. Information.

• I slow myself down long enough to see what the system is actually doing. What it rewards. What it tolerates. What it quietly punishes. Most of the time, the problem isn’t malevolence. It’s misalignment reinforced by incentives no one is naming.

• I don’t look for permission to redesign the system. I look for a place where my authority is real and the lever already exists. Waste. Risk. Cost. Friction. Delay. Those are the only moves that stick.

Then I act. Small. Clean. Defensible. Afterward, I pay attention to MY system response. If the action is aligned, my nervous system settles. The background vigilance drops. The noise fades. If it isn’t in alignment, the noise stays.

That’s how I know whether I acted truthfully.

That’s the loop I trust.

What I No Longer Do

What I no longer do is carry work where it doesn’t belong.

I don’t run unpaid simulations in my body. I don’t stay alert to problems that haven’t arrived. I don’t pre-emptively brace for conversations that haven’t been scheduled. I don’t confuse constant readiness with responsibility, or anxiety with care.

I don’t let a system that compensates me for output quietly claim my nervous system as part of the deal. That habit cost more than it ever returned, and I stopped paying it.

Reclaiming Yourself from the System

If you want to do this work yourself, start smaller than you think.

Don’t take on the whole system, and don’t start with the parts you hate or fear most. Respect what you cannot change, and learn where your influence is real.

You’ll feel it in your body before you think it. The places in the system that make your body tighten are often inflection points—areas where incentives and your sense of well-being are quietly in conflict.

Notice where something feels off, but not dramatic. A meeting. A report. A process you touch regularly that asks you, subtly, to look away from something you can feel but haven’t named yet. That’s your signal. Not outrage. Information.

Resist the urge to judge it or fix it all at once. Judgment burns energy and collapses options. Instead, study incentives. Ask what this part of the system actually rewards, what it tolerates, and what it quietly ignores.

Then look for a lever that already exists. Waste. Risk. Cost. Friction. Delay. Exposure. Every system has them. You’re not inventing morality; you’re working with gravity.

Act there. Small. Clean. Defensible. In a way that still makes sense to someone who doesn’t share your inner conflict.

That’s your version of the pint bottle.

You’re not trying to redeem the system. You’re reducing the distance between what you notice and how you behave. You’re giving your nervous system evidence that you don’t have to stay on alert just to remain intact.

Then pay attention to what happens next.

If the move is aligned, the noise drops.
If it isn’t, it won’t.

That’s how you know whether you’ve reclaimed something real.

This isn’t rebellion. It isn’t virtue. It isn’t withdrawal.

It’s maintenance.

And if enough people start here—quietly, locally, without spectacle—the system will still exist.

But it will no longer live in quite so many bodies.

-30-

Subscribe now

Author’s Note

For most of my life, fear lived in my body as vigilance. It kept me safe. It also made me very good at seeing systems, anticipating failure, and carrying responsibility early and often. For a long time, I couldn’t tell where trauma ended and competence began. The system didn’t care. It rewarded the output.

Healing didn’t take away my edge. It brought crystalized intelligence forward. What changed wasn’t my work, but how much of my nervous system the work was allowed to occupy.

This essay is a record of that shift. Of learning how to stay inside systems without being colonized by them. Of discovering that integration doesn’t look like withdrawal or softness, but like precision, restraint, and quieter participation.

I’m not offering a theory. I’m naming a lived transition. If it resonates, it’s likely because your body already knows what I’m describing.

There was a moment I didn’t understand at the time.

We had just enough money. Not enough to relax or feel safe—just enough to get by. Then the brakes went out on one of the cars.

I remember standing there, doing the math in my head, and the first feeling wasn’t panic.

It was shame.

That detail matters, because the shame didn’t belong to the car, the timing of the emergency, or even the math. It landed squarely on me.

Somewhere deep inside, a voice said, “You failed.”

At the time, that didn’t make sense.

I was working hard. I was educated. I was married. I was in a real career. I was doing exactly what responsible adults are told to do.

And still, one ordinary, predictable expense was enough to make me feel weak, dependent, and exposed.

That wasn’t bad luck.

That was the system doing exactly what it was designed to do.

For decades, worker productivity rose while wages didn’t. Costs didn’t pause. Housing, healthcare, education, and transportation all kept climbing.

What disappeared wasn’t your effort, intelligence, or work ethic. Those were never the problem. In fact, entire systems exist to ensure you keep giving those—consistently, reliably, and at full intensity. That’s part of the bargain.

What disappeared from your life was margin.

Your margin.

The extra financial breathing room you once had was identified as excess. The system decided it was paying you too much of it, and then quietly took it back—slowly, methodically, and without ceremony. It was optimized away from you and redeployed where it produced a higher return for itself.

To you, it wasn’t just money.

It was your buffer.
Your sense of safety.
Your ability to absorb life without feeling like one bad week could undo you.

That’s what the system removed. And once it did, you quietly assumed more of the financial risk of living. The pressure didn’t disappear. It simply became all yours.

This is the part that matters most.

People don’t break under this pressure because they are weak or careless. They break because they are trying to live like adults inside a system that no longer budgets for adulthood.

The old bargain included margin. There was room for error, illness, care, and the occasional bad week without it becoming an existential threat.

That margin wasn’t generosity. It was realism—an acknowledgment that you are human, with needs beyond what you produce.

That deal has changed.

The system didn’t simply tighten budgets or respond to market forces. It rewrote the terms while pretending nothing had changed. Pressure increased. Risk was shifted. Margin disappeared. Responsibility expanded. Authority and compensation did not.

That is an ethical failure.

Any system that increases the burden of participation owes honesty and protection in return. Shifting pressure without consent or compensation is not efficiency. It is exploitation.

This wasn’t done blindly. It was done with models that showed exactly where the pressure would land. The system knew families would absorb it. That workers would stretch. That people would stay quiet. And it proceeded anyway.

Pressure didn’t disappear. It was reassigned.

And pressure does not reliably make people stronger.
It makes them quieter. More cautious. More compliant.

That silence is not consent. It is the predictable result of a system that has decided human stability is expendable so long as performance continues.

Once you see that clearly, neutrality is no longer an option. Silence stops being professionalism. It becomes participation.

This is why certain behaviors become so common.

When you see people pulling back from speaking up, or you notice judgment fade as someone looks the other way, understand what you are observing. You are not witnessing disengagement, it’s the force of pressure.

Pressure created by living inside a system that only functions if nothing goes wrong, and quietly penalizes anyone who introduces uncertainty, friction, or risk back into the process.

When good people stop raising concerns early, when issues are delayed or softened, and when everything appears stable right up until it suddenly isn’t, that pattern is not accidental.

It is adaptive.

People learn that telling the truth early carries a cost, and that being silent is often safer than being correct at the wrong moment. Judgment doesn’t disappear because people stop caring. It disappears because caring without protection becomes dangerous.

So people manage their exposure. They conserve what little margin they have left. They learn when to speak, when to soften, and when to look the other way.

Not because they lack integrity or courage, but because the system has made it unmistakably clear where risk is assigned—and it is no longer absorbed upstream.

In that environment, people are not failing.

They are adapting. They are doing exactly what the system has trained them to do.

This is the moment where you decide what kind of adult you are going to be inside it.

Not a hero.
Not a martyr.
Not someone who burns their life down on principle.

An adult who sees clearly.

• If you run a process, you are responsible for where the risk goes. If it has been pushed downward or outward onto people with no authority to refuse it, don’t call that efficiency. Own the decision. Humanize the process.

• If you manage people, pay attention to what they are absorbing on your behalf. Every unplanned hour, every softened truth, every unspoken concern is being carried somewhere—often in their bodies, their families, and their sleep.

• And if you are being asked to carry weight without power, stop normalizing it. That arrangement is not professionalism. It is risk transfer. Pretending otherwise is how harm becomes routine.

You don’t have to fix the entire system. But you do owe it to yourself to stop participating in the lie that this is neutral or unavoidable.

Seeing clearly comes with responsibility. Noblesse oblige. Once you recognize where the risk is placed, you are accountable for what you do next.

Once you really see it, you can no longer confuse shame with truth. It changes how you stand in the world, the choices that you make, and even how well you sleep at night.

This isn’t about opting out.

It’s about opting back in—with your eyes wide open, your dignity intact, and your humanity no longer treated as an error term.

That’s where this begins.

Share

Writer’s Note

This isn’t theory. It’s lived experience, translated into clarity.

I wrote this for people who feel something is off but have been taught to doubt their intuition. For people who are quietly carrying more than they are allowed to name. For people whose competence has been used against them.

If this landed for you, trust that recognition. That feeling isn’t cynicism.

It’s orientation.

And orientation is where real agency starts.

For most of my life, I experienced the world as complex.

Not complicated in an abstract way, but layered and full of moving parts, hidden dynamics, and second- and third-order effects that all needed to be watched carefully. I didn’t question that experience. I assumed everyone saw the world this way. Being responsible meant staying attentive to everything all at once.

Ease felt suspect and risky. It ignored too many variables I couldn’t unsee or turn off.

What I didn’t understand at the time was how much that sense of complexity was shaped both by how I think and how my nervous system learned to survive a chaotic childhood. That way of seeing the world wasn’t theoretical for me. It shaped how I lived.

It showed up in how I worked, how I provided, how I solved problems, how I showed up for the people around me. I became steady. Dependable. Someone others could rely on. That mattered to me. I liked that about myself. I still do.

I can see it now in a hundred ordinary ways—being the one who planned, fixed, anticipated, or stepped in before anyone else had to ask.

The life I built during those years wasn’t something I carried alone. It was built in partnership, with people who trusted my steadiness and made room for the deeper person beneath it. Much of what exists in my life today only exists because that steadiness was met with patience, presence, and care.

So I want to be clear: nothing I’m naming here is a rejection of that man or the life he led. He was real. He was necessary. He was trying very hard to do right by the people he loved. What I couldn’t see at the time was how quietly fear had woven itself into every part of life.

Not fear showing up as panic or anxiety. Just a constant background hum. A constant, low-level demand for attentiveness to risk. A sense that if I didn’t stay engaged, stay aware, stay a step ahead, something important might slip. I didn’t experience that as fear. It was responsibility. And for a long while, that responsibility made sense to me.

When you see in systems and patterns, your attention never really turns off. You’re always tracking where burden is being carried, where it’s being avoided, and where something might give way if no one intervenes. After learning early that some things don’t hold on their own, staying alert doesn’t register as fear. It registers as care. As love expressed through never quite letting your guard down.

From the outside, it probably just looked like reliability. Like presence. Like being the person who handled things. From the inside, it meant I was almost always a little braced for anything. Not unhappy. Not overwhelmed. Just rarely at rest.

I didn’t yet have language for what that posture was costing me personally or emotionally, just the sense that I was always carrying something I never quite got to set down. But it must be carried.

What changed didn’t happen all at once. There wasn’t a moment where something broke, or I randomly chose a different way of living. What came first was quieter and more unsettling. I realized I could not answer the basic question ‘what makes you happy?’. Not productive, effective, or respected. I had no idea what made me happy if the answer could not be my wife or children.

That uncertainty was new. And it mattered. Because it meant that somewhere along the way, my attention had narrowed so tightly around responsibility and vigilance that I’d lost touch with the signals that tell you whether a life is being lived from the inside out. When I noticed that, other things started to come into focus.

I began to recognize brief stretches of time where, if I let go of hyper attention, nothing bad happened. Moments where I wasn’t anticipating the next failure and instead content. At first, those moments felt empty, almost suspicious. But over time, they became informative. They showed me that vigilance wasn’t the only thing holding my life together.

At first, those moments felt accidental. Temporary. Something to enjoy quickly before responsibility returned. But over time, they started to accumulate. And that accumulation did something unexpected: it challenged my very assumption that vigilance must be constant for life to hold together.

I didn’t become careless or lose my edge. What I lost was the belief that I had to stay slightly braced in order for things to work. That’s when I finally understood something that sounds so obvious now, but took me decades to learn:

Discomfort is not the same thing as danger. You can feel uncertain and be safe at the same time. You can leave things unresolved without them falling apart. You can loosen your grip without losing what matters.

As that understanding settled in, I started to see my life differently. Not as something I was holding together through effort, but as something that had been quietly accumulating meaning and relationship the whole time.

A marriage that didn’t survive because it was easy, but because we learned—often the hard way—how to stay honest without disappearing. Kids who grew into themselves in ways I couldn’t have planned, and who taught me more about trust than any theory ever could. Friends who didn’t require me to perform, impress, or explain myself in order to belong.

None of that happened because I optimized for it. It happened because I stayed long enough, paid attention, and eventually stopped believing that control was the same thing as care.

For a long time, I thought the answers were somewhere ahead of me. A place I’d arrive at one day. once I had enough information, discipline, and clarity. What I see now is that the answers were already present. What was missing wasn’t intelligence or effort. It was trust in myself. Trust in the people around me. And, eventually, trust in God. Here’s how faith actually showed up in my body and daily life — not as belief, but as permission.

For years, trusting God fully didn’t feel safe. It sounded like letting go too soon. Like confusing faith with passivity. And I don’t regret being careful. But faith, as I’ve come to understand it, isn’t about abandoning discernment. It’s about deciding who gets the final word. For me, it showed up as permission to stop treating fear as the default authority on how I live, even when it had once been useful.

Fear can be useful. It really can. It kept me attentive. It helped me carry responsibility when I needed to. But at some point—quietly, without any big moment—I realized it didn’t need to be in charge anymore.

What took its place wasn’t recklessness or letting go of care. It was rest. The kind that doesn’t feel like collapse or disengagement, just the relief of no longer bracing for what might happen next. The sense that I could be present without scanning, engaged without gripping, alive without managing every outcome.

I don’t feel triumphant about that shift, and I don’t feel finished. What I feel is grateful.

Grateful for the people who stayed close while I learned how to loosen my grip without losing what mattered. Grateful for a life that quietly grew rich while I was busy trying to understand it. Grateful for a God who didn’t rush me toward trust, but waited patiently until I was ready to rest in it.

I’m not writing this because something ended, or because I’ve figured everything out. I’m writing it because I finally recognize where I am —right here, in the middle of a life that turned out full.

Author’s Note

I want to say this plainly.

This piece exists because of my wife and our family.

The steadiness, patience, and willingness to stay present—especially during seasons when things were complex and not yet named—made it possible for me to grow without losing myself. Much of what I describe here didn’t happen in isolation. It happened in relationship, over time, through ordinary days, shared effort, and the grace of being allowed to keep learning.

To my wife: thank you for partnering with me, trusting the parts of me that were still finding their way, and helping create a life where honesty, rest, and joy could coexist. Your presence has been both grounding and freeing in ways I continue to appreciate.

To my kids and extended family: thank you for the laughter, the challenge, the patience, and the reminder that a life isn’t measured by how tightly it’s managed, but by how fully it’s lived together.

This reflection is mine to write, but the life behind it has always been shared.

Author’s Note

I didn’t experience safety only from policy manuals or audits. I’ve conducted hundreds of root cause analysis sessions on accidents and participated in too many debriefs after real people got hurt at work. I’ve seen good leaders wrestle with impossible tradeoffs and frontline people carry risk they didn’t create.

At the same time, I’ve witnessed organizations explain outcomes in meticulous detail while deliberately avoiding the decisions that made those outcomes inevitable. This piece is written for those who recognize that experience immediately.

If you manage people in operations, you already know the gap. What’s harder to admit is that the system depends on you to absorb the disconnect.

When a serious injury occurs on the shop or warehouse floor, senior leaders usually descend quickly and act decisively. Their discussion centers on local conditions. On housekeeping, maintenance, and procedure; and the site’s adherence to standards.

The questions are sharp. Accountability snaps downward with immediacy. The implication is clear, ‘this should not have happened’. Senior leaders are quick to assign accountability onto site leadership and close the loop. What does not enter the room is just as clear and far more damning.

Too often, the questions fail to revisit that the maintenance budget that was slashed to save expenses, or that aging equipment was kept in service well past its intended useful life. As was the case in one incident in particular, that I witnessed professionally, the senior leaders failed to connect that the persistent leaking oil across the shop floor was linked directly to capital decisions approved far from the site. Those decisions are spread across time and committees, insulated from the moment of injury. Rather than acknowledge the extent or root cause of the problem, senior leaders, instead made sure the leaking oil stuck to the local team when someone got hurt.

Corporate safety programs, meanwhile, run exactly as designed. Training is completed. Audits done. Incident rate tracked. From a corporate standpoint, the system was compliant. And yet someone still got hurt. That disconnect is not abstract. It is structural. Managers live inside it everyday with scorecards, monthly targets, utilization rates and cost-per-unit expectations. As a manager, you are accountable for outcomes produced by systems you did not design and often do not fully understand, operating within constraints that are explained as fixed rather than chosen.

You are expected to deliver results inside constraints you did not fully set—staffing levels, maintenance cycles, equipment condition, annual volume. You may technically control how those constraints are managed day to day, but you did not control the level at which they were funded. That distinction matters.

Senior leaders will say sites have autonomy: to set schedules, to prioritize maintenance, to decide how staffing is allocated within budget. What goes unspoken is that those choices occur after the most consequential decisions have already been made. Budgets establish the ceiling. Capital plans establish the horizon. Headcount targets establish the margin. Autonomy exists only inside those bounds. You can manage tradeoffs you didn’t choose, but you cannot manage safety you were never funded to create.

When you’re told “Safety First,” what’s actually being communicated is usually far more precise: manage safety without disrupting throughput. You are asked to decide when to interrupt production without knowing whether the risk you’re seeing will materialize. And without the option to materially change the conditions that made the decision necessary. This is the part almost no one says out loud.

Safety effort lives locally. Safety capacity is set elsewhere. And the distance between the two is where managers are asked to make judgment calls that carry real risk, operationally, professionally and even legally.

In theory, stopping work for safety is celebrated. You will be praised for being an advocate. In practice, it is often a professionally risky decision, especially when the feared outcome does not occur. Slowing production for a risk later judged “unfounded” is remembered, questioned, quietly counted against you and never fully forgiven. The production numbers still miss. The deadlines still slip. The explanation still has to be given.

Everyone understands why this happens. We are here to get product out the door. That is the real constraint. The language of safety exists alongside that reality, but it does not override it. Instead, it provides cover while the burden of deciding when to invoke it is pushed onto individuals.

You recognize it because you’ve felt it in your body. It shows up as a pause. A hesitation. A moment where something doesn’t feel right, but nothing is obviously wrong. Stopping feels premature. Continuing feels uncomfortable. Either way, you know you will own the outcome.

If you slow things down and nothing happens, the delay is visible and questioned.
If you do not and nothing happens, the decision disappears. When something does happen, the moment is replayed later as if the risk had been obvious all along.

You know this. It shapes how you lead, whether you say it or not.

Managers are not separate from the frontline experience. You are simply positioned where the contradiction becomes unavoidable. You often see conditions forming before anyone gets hurt. You know when maintenance was deferred too long, when staffing is too thin for the volume, when equipment is being asked to do more than is realistic. You also know exactly how those conditions land—as pressure, the need for shortcuts and workarounds, and quiet judgment calls made by folks without a say on the constraints.

When an operator hesitates and then keeps going, that decision did not start with them. It passed through you. And through the decisions you were handed. And through the ones you were not allowed to make.

That is the part safety language rarely admits. Frontline judgment is not independent. It is shaped, narrowed, and sometimes cornered by conditions managers are expected to normalize. So when something finally breaks and attention snaps to a missed step, a failure to stop, or a rule not followed, everyone is only seeing the last move in a chain that was already set in motion before the day began.

This is why post-incident conversations feel hollow. Not because anyone is lying, but because the story starts too late. It starts at the decision instead of how to avoid the conditions that made the decision inevitable.

Managers feel this because they are the last place where awareness exists before risk disappears again. You know when the operation is being held together by experience and luck. You know the difference between acceptable and merely tolerable. And you know that most days end safely not because the system is safe, but because people compensate.

When that compensation works, nothing is recorded. The system learns the wrong lesson—that the pressure is fine, that the risk was acceptable, that the design does not need to change. When it fails, the system looks for a decision to explain the outcome.

One of the most dangerous side effects of this system is the normalization of deviance. When pressure becomes constant and nothing bad happens, the abnormal starts to feel acceptable. Deferred maintenance becomes routine. Thin staffing becomes “how we operate.” Equipment running past its intended life becomes background noise. Each successful day under strain teaches that the risk is manageable, the margin sufficient, and yesterday’s workaround is today’s standard.

It isn’t recklessness, it’s adaptation. People adjust behavior to match the system they’re actually operating in, not the one described in procedures. Over time, the gap between “how work is imagined” and “how work is done” widens, and the organization slowly drifts into danger without any single moment that feels like a clear violation. When something finally fails, the response treats the last deviation as the cause, rather than recognizing that the deviation had already been normalized long before the day of the incident.

This is not a failure of care, but the result of a system that rewards uninterrupted production, penalizes visible disruption, and examines safety decisions primarily after harm has occurred.

Until organizations are willing to treat capital allocation, maintenance discipline, staffing levels, equipment lifecycle decisions, and schedule pressure as safety decisions, rather than simply financial, this pattern will repeat. Managers will keep absorbing the uncertainty created elsewhere. Frontline workers will continue to carry risk they did not design.

And when something goes wrong, the story will still begin at the wrong place.

Safety does not fail because people do not care. It fails because systems ask people to absorb risk quietly so organizations can protect margins they are unwilling to expose. And then act surprised when that bargain finally comes due.

Once you see that clearly, ignorance is no longer an excuse. And silence becomes a choice. And leadership is measured by which choice you make next.

Leave a comment

Post Author’s Note

This way of seeing didn’t start with safety. It comes from years of watching systems do exactly what they were built to do; and watching people absorb the consequences.

Bad systems hurt people. Not because anyone intends harm, but because incentives, constraints, and silence compound over time. I’ve applied this same lens across operations and leadership: follow what’s funded, follow what’s measured, follow what’s tolerated. Safety is simply the place where the cost of poor system design can no longer be abstracted away.

There’s a type of dishonesty that isn’t an outright lie. It relies on the disingenuous use of tone, timing, and reputation to guide reasoning and point toward a preferred conclusion without ever having to defend it.

That dishonesty is destroying journalism from within. Worse, it’s being carried out by people who know better and do it anyway because it serves them. It’s epistemic laundering, using the authority of journalism to enforce orthodoxy while pretending to arbitrate truth.

George Stephanopoulos is not an incidental practitioner of this form. He is its exemplar.

He speaks with the cadence of seriousness, invokes the norms of journalism, and then quietly uses that authority to shut down inquiry when inquiry becomes inconvenient within his worldview. Nothing overt, just enough effort to guide the audience away while maintaining the appearance that a question was addressed.

It’s journalism used as a mask for partisan behavior.

The reason this is difficult to call out is that it rarely announces itself as advocacy. It presents as professionalism and counterbalance. It’s often most visible during transitions, moments where a claim should be tested and instead is neutralized. Once you see the move, you notice it everywhere. It isn’t accidental. It’s an editorial posture, dishonestly wrapped in journalistic integrity.

A single exchange on This Week this past Sunday was among the most intellectually absurd moments I’ve seen in modern political journalism.

Marco Rubio was talking about Venezuela. Among the reasons the administration chose not to brief congressional leaders before the operation, Rubio said, was fear of leaks compromising the safety of the soldiers involved.

Stephanopoulos, bristling at the implication that leaks are a real risk in Washington, responded with an unusually clumsy retort before moving on:

“The congressional Gang of Eight has a history of not leaking.”

Wait. What?

Stephanopoulos didn’t test Rubio’s claim. He substituted reputation for inquiry.

The argument, reduced to its logic, is that the Gang of Eight has a history of not leaking, therefore a leak is not a realistic fear. That reasoning is meaningless. The same group also has a history of refilling the copy machine paper when it empties and not leaving used Keurig capsules in the machine after use. None of that tells you anything about access, incentives, changed circumstances, or how a leak would even be detected if it occurred.

The comment tells you nothing. It carries a quiet contempt for the viewer’s capacity to reason through the problem themselves.

I’m not reflexively cynical about the media. I understand its ambitions and its limits. But when intellectual honesty and consistency are replaced with appeals to trust, it stops feeling like journalism and starts feeling like something we’re being asked to accept without question. It begins to feel like we’re living in a simulation.

What I see now, repeatedly, is journalists who have quietly stopped asking the next question. Instead of testing claims, they call on viewers to grant unearned trust. Phrases like there’s no evidence are no longer openings for inquiry; they’re endpoints. This isn’t sloppiness. It’s an intellectually dishonest choice that demonstrates contempt for the craft itself.

The mechanism is simple and effective. Journalistic credibility and institutional legitimacy reinforce one another, forming a closed loop of protection. Challenging anything inside that loop requires overcoming both the claim and the authority dismissing it. Worse, simply asking the question is often treated as evidence of bad faith by the questioner.

The journalist doesn’t need to argue or investigate in this scenario. They only need to signal that the question itself is beneath serious consideration. Most people don’t reason analytically in real time; they reason socially. Tone, confidence, and familiarity do the work. When a trusted voice calmly implies a claim is unreasonable, the audience understands the cue and moves on.

That’s why this works.

Any competent journalist understands that absence of proof is not proof of absence. They were trained in this and built careers on it. When those standards disappear, it isn’t ignorance. It’s a choice to manage perception rather than pursue truth.

A free press doesn’t exist to make people feel safe. It exists to make those in power uneasy. To ask the question that threatens the story is the job of the journalist. Societies ambiguous on that fact, don’t collapse in flames right away. But they do grow less free.

Author’s Note

I think about systems for a living. Systems fail not because of malice, but because incentives drift, feedback loops close, and people learn—often unconsciously—what is rewarded and what is punished.

When a system stops tolerating honest friction, it harms people. It teaches them not to trust their perception, not to speak plainly, not to ask questions. Over time, it trains them out of freedom.

#FreePress #Journalism #MediaEthics #IntellectualHonesty #CriticalThinking #EpistemicLaundering #MediaCriticism #PressAccountability #SystemsThinking

I learned as a boy, no one was coming to save me. So I saved myself the only way a child could. I prepared for everything.

If fear showed up, I rehearsed my escape. When danger came near, I built a plan before it could touch me. If an old wound stirred, I threw up walls so fast I could outrun the panic.

That’s how a gentle, sensitive five-year-old boy survives in a world too chaotic and harsh for his protectors to notice the danger creeping toward him. He learns to stay ready for anything at all times. The man I have grow into lived for decades as if that same terrified little boy was tightly gripping the controls of life.

Preparation was my shield. My oxygen. My way of keeping the world from breaking me again. So when I recently stepped into a situation that carried all of the emotional weight of my childhood fears, my instincts kicked in before I even had time to think.

I tried to prepare. But something in me knew preparation would not be my means of salvations this time. So instead, I leaned on my faith to try something terrifying.

Surrender.

I walked into that room empty-handed. No script. No plan. No rehearsed lines to pull me through. I Just brought a belief that whatever strength God chose to give me would be enough. That day, He sent some very powerful forces to be with me in this moment.

From the very first question, I felt a steadiness rise in me that I cannot fully explain. Not detachment from my feelings. Not numbness from what I felt. Not a fake, forced calm. I felt something else. Something deeper. A force beyond my capabilities. It felt like a hand rested on my back and whispered quietly and gently. “You don’t have to carry this alone anymore. Rest here. I will protect you.”

For almost four hours, words came out of my mouth with a clarity, calm and precision that I never could have accessed. No matter how much preparation or intellectual firepower I thought I possess, I was unshakeable and confident in ways that move my soul.

My whole life, I’ve believed in grace. But that day, I felt it move through me. I didn’t shrink from the moment. I didn’t tremble inside. I didn’t over-explain or apologize for existing.

My answers were clean. Direct. Honest. Unflinching.

Opposite the table at which I sat in the room, there was a mirror on the wall.
Every so often, as my eyes took in my surroundings, I’d catch my reflection. It felt surreal. It was my face, but not the version of me I’m used to seeing in stressful moments. The man I saw in the mirror looked measured, strong, and anchored in a way I didn’t know possible. In that room, I transformed into a warrior made of calm. A man who finally knew his own worth.

And in that moment, I realized: This wasn’t me doing it. God was doing it through me.

The questioner was trying to get a reaction to help his cause, something he could twist, something he could use to question my character. But when he pushed into the most vulnerable parts of my life, I felt no panic. Just calm. I didn’t scramble for footing. I didn’t lose myself. I stayed right where I was. The words came on their own.

My questioner aimed straight at the places in me where fear used to live—my childhood, my marriage, the scars I’ve spent a lifetime untangling.

And I felt nothing break. No panic. No rush of old instinct. Just steadiness.
A certainty I’ve never felt before. It wasn’t until later, walking alone afterward, that the truth crashed into me. I stopped on the sidewalk and actually said out loud:

“How did I do that?”

The man who answered those relentless questions wasn’t the boy who learned to survive. Not even the man I thought I was. The man in that room was someone stronger, clearer, unafraid than I’ve ever been. Realizing fear is gone was its own kind of miracle. All I did was keep breathing and whisper inwardly:

“If this is mine to carry, help me.
If it is Yours to speak, speak.”

And He did.

When it was finally over, I walked out of that room more whole than I have ever been in my life. Not because I fought something. Not because I conquered anyone.
Not because I proved anything. But because I finally stopped fighting alone.

My wife and children had surrounded me with support so fierce it felt like armor on my heart. Their strength met God’s grace, and for the first time in my life, the five-year-old boy inside me stood safe and surrounded by love beyond measure. He was held. He was protected. He was finally free.

And that’s when I understood the truth I had been circling around my entire life. The Trauma in my family did not end because I was strong. It ended because, for the first time ever, I allowed God be stronger in my heart than my fears.

Author’s note:

I share this moment not to revisit old pain. Simply I seek to honor the grace that carried me through it. If you’ve ever have been called to face down the echoes of a painful childhood wound, may this remind you: You do not ever need to walk into those moments alone. God is always with you.

#Trauma Recovery #Spirituality #Faith #Healing #Personal Growth #Transformation #Inner Work #Breaking Cycles #Surrender #Grace

This is a love letter to a tool, a philosophy, and a way of perceiving the world that changed everything for me. Learning to See is a book about reclaiming clarity.

The Illusion of Metrics

If you’ve been in operations long enough, you know the scene: a room full of managers gathered, each having written their prior-day numbers on the board for the morning meeting. If the numbers are green, they exhale and tune out. If the number is red, they await the moment the attention turns to them. It begins. Almost in staccato.

“Have you identified the root cause?”
“When will you have countermeasures?”
“Who owns this and when will it be done?”

There usually is a flurry of words, action boards updated, and a promise is demanded to report back. The next meeting, the metric could be back to green again. Or still red, which leads to the same discussion, only louder and with a dash of “escalation.”

It’s a ritual. A war room of well-intentioned people managing symptoms using summarized data, taken from the system but not directly indicative of its health. Just a series of snapshots used to represent the movie.

Most leaders don’t understand how and why those numbers turn green in the first place. Conceptually, they get how the system flows but not how it works together. In truth, most managers know how to react to a signal, but not how to interpret it. They were promoted because they were strong in their function, but during the onboarding nobody taught them how the whole system works.

And now, they lead from dashboards instead of from the floor.

They walk the floor, on schedule, to be seen performing the act of leadership, then they spend the rest of the day updating spreadsheets, or in meetings. They mistake the the map of numbers for the territory where the work is done, the data for the truth. The dashboards are green, but the system is a gray box to mostly everyone.

That’s the dirty secret of most operations today. Everyone’s managing data. Who is managing the interdependent patterns and flows of interactions within the system? Those only are visible when you stop looking at the parts.

The Disconnect

It’s not malice or incompetence, just conditioning. Nobody ever taught them how to truly see.

They were trained to manage results, not complex relationships between processes. “That’s for the engineers!,” they retort. Most leaders can recite throughput and cost-per-unit, but they can’t tell you how information moves across the operation, how delays in one line cascade into others, or how waste accumulates unseen until it stops everything.

And that’s not their fault. Their leadership never gave them the tools to even begin to understand how the floor works in total, from one side through the other.

Most leadership teams are an organization full of good people, futzing around in silos, making local adjustments and causing global messes up or downstream doing actions without context. Everyone tweaks their piece, but no one understands the flow. It’s optimization without observation. Leadership without sight.

Learning to See (Again)

There’s a way out of this blindness. A simple, elegant discipline that reconnects leaders with the truth of their own operations. It’s called the Value Stream Map, and the book that introduced it to most of us — Mike Rother and John Shook’s Learning to See — remains one of the most quietly transformative texts in business.

Published in 1999, Learning to See was the first time Toyota’s internal process-mapping method was codified for the rest of the world. It teaches you how to trace the flow of value from customer request to delivery. Not as you imagine it works, but as it actually does. It reveals the terrain of your organization in a way dashboards never can show.

A value stream map isn’t a process diagram. It’s an x-ray. It exposes the arteries and nerves of your system — material, information, timing, handoffs, bottlenecks — all in one picture. It’s the closest thing to standing inside your business with the lights fully on, lines fully staffed and running at nominal speed.

The book’s title wasn’t metaphorical. It was an invitation. Learning to See teaches you to view the system with new eyes, as if seeing it for the first time. It helps you make the invisible visible by taking you into the interrelations between silos. And once you see, you can’t unsee.

The Gift of Seeing

I’ve said before that Learning to See changed how I lead. What I don’t often say is that “learning to see” also saved my life — long before I ever read the book.

For me, vision wasn’t only about eyesight. It was a tool of survival. As a child, my nervous system protected me by allowing me to see and read all types of patterns; emotional, relational, environmental; faster than anyone else in the room.

I didn’t learn to see as a leadership skill. I learned it as a self-preservation technique during a chaotic childhood. My body decided that clear seeing was protection, and it built a mind wired to notice everything in a system and how it works together.

That same wiring would later become my greatest gift — the ability to perceive systems, to sense where things connect, and to understand when they don’t.

But the irony is, my physical vision failed me. Many eye surgeries, long recoveries. Years of fighting for the simple act of sight.

Those experiences taught me something that transcends the literal: clarity isn’t just a condition of the eyes; it’s a condition of the soul.

Clarity is what happens when observation meets understanding. It’s the alignment between what you see and what is real. It’s the moment when you stop reacting to signals and start perceiving the kinetic pulse and movement of the system in its entirety. It’s halts. It’s limits.

That’s why Learning to See struck me so deeply. Because most organizations, and most leaders, are living with damaged vision, too. Their field of view has narrowed. Their depth perception is gone. They’ve learned to stare at dashboards instead of knowing systems, to scan for red and green instead of seeing the flow. Their entire culture is one of optical illusion. Performance theater dangerously posing as insight.

When I talk about learning to see, I don’t mean adding another metric. I am speaking of restoring clarity — in the truest, most human sense. The ability to look at your work and actually perceive it as it is. To notice cause and effect, variation and rhythm, interdependence and imbalance.

Clarity is grace made visible. It’s not perfection; it’s alignment. It’s when the noise quiets just enough for you to see truth move through the system in clear, simple, unmistakable ways.

Value Stream Mapping, at its heart, is a tool for clarity. It lets you trace every nerve of your organization, every pulse of value and waste, until the picture emerges. It’s not about documentation. It’s about illumination of how materials, efforts, information, waste and WIP (among others) move. When leaders map a value stream, they are learning to see. Not as managers of metrics, but as stewards of the system the are able to collaboratively direct.

My childhood taught me that seeing is sacred. My career taught me that clarity is how we turn survival into wisdom.

And that’s the divine act behind Learning to See. It’s the practice of returning to vision. Rediscovering how to look at what’s right in front of us until understanding begins.

Why This Matters

Most leaders aren’t blind because they don’t care. They’re blind because the system they inherited never gave them the ability to see. Dashboards replaced floor walks. Targets replaced teaching. Urgency replaced curiosity.

The VSM restores all three.

It gets you back on the floor, physically or metaphorically, to reconnect with how value really moves. It unites silos into a shared understanding of flow and shows the quirky overlaps. And perhaps most importantly, it gives you permission to learn your own system again without losing face.

A VSM isn’t about ignorance or courage. It’s about respect for the people who live inside the process every day, and for the truth of how work really flows.

The Invitation

I want to be the Johnny Appleseed of Value Stream Mapping. I want to plant this tool in every company that’s lost its ability to see.

So here’s my offer, open and unconditional. If you’ve never built a value stream map, if you’re intrigued but intimidated, or if you’ve tried before and it went nowhere: reach out. No consulting pitch, no invoice. Just a conversation.

Because the moment you learn to see your system clearly, everything changes. You stop fighting fires and start improving flow. Toyota teaches that if the system isn’t flowing properly, the leaders of the organization are disrespecting the workers. If you seek to be a manager of influence and value to your company, stop accepting reds and greens as the mark of system health.

Learn to see and you’ll rediscover the thing every great leader, every great human system, is built on: clarity.

Sources & Footnotes

1. Rother, Mike & Shook, John. Learning to See: Value Stream Mapping to Add Value and Eliminate Muda. Lean Enterprise Institute, 1999.

2. Lean Enterprise Institute. “Value Stream Mapping Overview.” Explains VSM as a comprehensive view of value creation from order to delivery, highlighting both material and information flow.

3. NIST MEP. “Value Stream Mapping.” Emphasizes VSM’s role in connecting cross-functional teams and aligning improvement efforts to a unified future state.

4. Graban, Mark. Lean Blog: Red/Green Analysis. Critiques red-green dashboard thinking and the failure to interpret green metrics as “safe.”

5. Flight Safety Foundation. “Normalization of Deviance.” AeroSafety World. Discusses how repeated tolerance of deviations leads to systemic failure.

6. Deming, W. Edwards. Out of the Crisis. MIT Press, 1982. Advocates for systems thinking, process understanding, and respect for people as the foundation of quality.

Subscribe now

Author’s Note

I’ve spent my life trying to understand why systems fail and how people survive them. As a child, my safety depended on seeing patterns; as an adult, my purpose depends on helping others see theirs.

This essay isn’t about metrics or management. It’s about the moral act of paying attention.

If we can learn to see clearly — not just our work, but the systems we build and the people inside them — we can begin to repair both.

That’s the work. That’s the gift. And I’m grateful every day for the chance to keep learning how.

— Todd Andrew Owings

Part of the Seeing Systems Clearly series
Essays on leadership, culture, and operational wisdom — where clarity meets courage.

The most dangerous failures don’t begin with a bang.

They begin with a shrug.

A checklist skipped because “we’re short-staffed.”
A torque spec ignored because “we’re already behind schedule.”
A warning dismissed with “we’ve done it this way before a million times.”

And then — nothing happens.
No explosion. No critical audit finding. No customer complaint.

So we do it again.

And again.

And again.

Until one day, the corner that’s been cut becomes the weakest link.
That small deviation that once saved time now invites failure.
The team, often stretched thin and running blind, can’t react fast enough — not because they don’t care, but because there is no margin for error.
And what was once a silent drift becomes a very loud reckoning.

We act shocked. We ask how it occurred when we are so careful, citing the a dusty binder or excel file filled with SOPs. We seek to find those to blame.
But the truth is, the system didn’t break overnight — it drifted.
Quietly. Gradually. Predictably.

And we allowed it to occur on our watch.

This phenomenon has a name: Normalization of Deviance.
Coined by sociologist Diane Vaughan in her study of the 1986 NASA Challenger disaster, it describes the slow, collective process by which small rule-breaking is ignored or permitted until it becomes standard behavior. What starts as a one-time exception becomes tolerated, then routine — until disaster exposes how far we’ve wandered from the original standard.

This isn’t just a problem at NASA or Boeing.
It’s in your plant, your warehouse, your hospital, your office. Perhaps, your home.
It’s in any system where people feel pressure to deliver more than they’re resourced to do — and where leaders turn a blind eye to how it gets done, so long as the numbers look good.

The question is not whether your organization will face stress.
The question is whether the shortcuts you’ve normalized will hold up — or snap — when put to the test.

The Drift Is Real — And It’s Everywhere

Normalization of deviance isn’t limited to rockets or aerospace. In healthcare, medication protocols are sometimes bypassed due to clunky software or staffing shortages. In construction, site inspections get rushed to meet client deadlines. In manufacturing, preventive maintenance slips because “we’ll get to it next quarter.”

A study by the Joint Commission found that more than 60% of adverse events in hospitals involved deviations from standard procedures — most of them known, but tolerated. OSHA reports similar patterns in industrial incidents: the hazards were documented, but workers had grown used to ignoring them.

This is how entire systems drift into dysfunction: slowly, quietly, and with plausible deniability. It becomes the culture.

“That’s just how it’s done around here.”

Until one day, this ad hoc, workaround system fails.

Boeing and the Price of Drift

The Boeing 737 MAX tragedies were not caused by one decision, but thousands of small, cumulative ones. Pressure to cut costs and accelerate production on the part of leadership led to a quiet erosion of standards. Tribal knowledge walked out the door as veteran engineers were bought out or let go to cut costs. Frontline concerns often were ignored. Documentation gaps began to widen. Feedback loops, never robust in most organizations already, begin to collapse.

And yet, nothing happened — at first.

Planes rolled out.
Metrics looked good.
Dashboards shone green.

Until two planes fell from the sky.

Following a complete investigation, the official reports laid it bare: warnings were downplayed, internal dissent was muffled, and speed was prioritized over safety.

This, from a company that once represented the gold standard in aviation.

Normalization of deviance isn’t an accident. It’s a pattern. And at Boeing, that pattern was actively being ignored.

“We warned Boeing that it was going to lose a mountain of expertise,” said Ray Goforth, executive director of the union representing Boeing engineers. “But the company blew us off.”

What began as exceptions quietly hardened into routine.
Voices from the front line were filtered at first, then softened, then ignored.
By the time leadership had finally recognized the depth of the drift, the damage was wired into the system.

What Drift Feels Like

Maria, a lead tech at Boeing with 15 years on the line, remembers when inspections were sacred. “Now?” she shrugs. “We’re told to skip them unless we’re being audited.”

She’s not angry. She’s worn down by the slow, steady corrosion of standards that no one at the top seemed to notice, or worse, chose to ignore. Over time, that silence became the policy. And in its place grew a culture where drift was tolerated, then baked in to the recipe. It doesn’t just burn out individuals — it breaks the system from the inside out.

It’s not just her. Across industries, workers are being asked to improvise while pretending that standards still exist. They are told to own the outcome — but not given the tools to influence the inputs.

That’s not empowerment. That’s systemic gaslighting.

Standards Are Not Bureaucracy. They Are Protection.

W. Edwards Deming, the pioneer of modern quality management, is best known for transforming postwar Japanese industry and advocating that sustainable excellence comes from improving systems — not blaming people.

Deming taught that standards, done right, are not red tape — they are a form of respect. Standards protect people. They reduce variation. They ensure continuity and remove ambiguity in a complex system. When leadership’s main focus is on short-term efficiency, standards are often the first thing to erode.

If a worker is asked to “just get it done,” even when a tool is missing or a checklist isn’t followed, that’s not empowerment. That’s abandonment.

At Toyota, leaders are taught that poor system flow is not just a technical failure — it’s a moral one. It disrespects the worker by forcing them to absorb the undue friction, take unnecessary risk, and do confusing, unnecessary work. A broken process is not the worker’s burden to overcome — it’s leadership’s duty to fix.

When companies fail to reinforce clear, human-scale processes, they invite fragility into their operations. It doesn’t always show up in quarterly reports. But it lurks. And when the system is stressed — by a surge in demand, a critical failure of a part during production, or a loss of key personnel — that fragility turns to chaos.

The Deming Counterweight

Deming never believed that you could shame or threaten your way to excellence. He believed that quality is built into the system — not inspected in after the fact. And he believed that dignity at work wasn’t just a moral imperative, but a strategic one.

“A bad system will beat a good person every time.”

In today’s landscape, many leaders still treat performance problems as personal failings. But when you zoom out, you see the truth: the system is driving behavior. And right now, that system is, too often, built around rewarding deviance from standards.

Good companies design systems that hold the line on standards. Great companies build systems that evolve — but fix them when those systems begin to erode.

Guardrails for Greatness

Normalization of deviance doesn’t announce itself with alarms. It seeps in through shortcuts in processes, unclear or changing expectations, and vague direction from leaders — until dysfunction begins to feel like efficiency.

Preventing that drift isn’t about drafting more work rules. It’s about cultivating a system that makes the right way the easy way — what Toyota teaches its leaders is the highest form of respect for workers. If the system doesn’t flow, the failure isn’t on the frontline. It’s on leadership.

It means building a culture that prizes integrity over expedience, where the value of doing something right is embedded in daily work — not just posters on the wall.

It means rewarding people for surfacing problems, not for hiding them. It means designing systems where adherence to standards is possible under pressure, not something workers have to figure out how to fit into the schedule. It means recognizing that real craftsmanship comes not from compliance, but from pride — and pride only thrives where people are supported, not squeezed.

This kind of culture doesn’t emerge by accident. It is built deliberately, patiently, and with a clear-eyed commitment to excellence that doesn’t compromise when the line backs up or the quarter runs short. It shifts the view to pride in workmanship. Here’s what that looks like in practice:

• Protect tribal knowledge. Don’t just replace senior staff — capture what they know. Their deep understanding of how the work really gets done is invaluable. Pair them with newer employees to pass on system memory. Interview them, document their insights, and treat their experience like the operational asset it is. If you wait until they walk out the door, you’ve already lost too much.

• Elevate frontline signals. Treat deviations from standard and near misses as gold mines for improvement, not nuisances to suppress. Dig into root cause.

• Reinforce standards daily — not as punishments, but as the foundation of craftsmanship. Ensure frontline leaders deeply understand the processes they oversee and how the work should be done. Teach supervisors to lead by observing with humility and managing with respect.

• Tie metrics to meaning. If your system rewards only speed or cost reduction, you’ll get drift. Balance output with integrity.

• Slow down when it matters. Speed is not a virtue if it erodes your margins for safety, quality, or resilience. If defects rise faster than output, you’re not scaling — you’re spiraling.

• Audit your standards. If they’re not being followed, ask why. If they no longer serve, improve them — don’t abandon them. Don’t tolerate uncontrolled variation in process — because it mathematically guarantees uncontrolled variation in output.

• Tell deviance stories. Normalize talking about mistakes — not with blame, but with curiosity. Use structured methods like Root Cause Analysis (RCA) or the Five Whys to uncover how systems, not individuals, created the conditions for failure. This isn’t about finger-pointing. It’s about learning. The goal is not just to correct the error, but to prevent its recurrence — and to foster a culture where people feel safe surfacing problems early, before they compound.

• Honor good friction. When a worker slows the line to flag a safety concern or refuses a shortcut that compromises quality, that’s not resistance — it’s integrity. In healthy systems, that kind of friction isn’t punished; it’s prized. Celebrate the people who raise uncomfortable truths, who protect the standard when it would be easier to bend it. Their courage is your early warning system — and your best defense against disaster.

The Positive Path Forward

Normalization of deviance isn’t inevitable. It’s not a failing of character — it’s a failing of culture. But culture can be changed.

It begins when leaders stop treating standards as obstacles and start honoring them as agreements. When doing the right thing is easier than cutting corners. When raising a concern is seen not as insubordination, but as stewardship.

Systems that respect their people don’t require perfection — they require clarity, consistency, and care. They understand that pride in craft is not born from pressure, but from purpose. From being part of something that holds the line because the line matters.

This isn’t about nostalgia for how things used to be. It’s about the hard, hopeful work of building systems that endure — not by pushing people harder, but by designing with them in mind.

Because excellence isn’t a result of squeezing more. It’s the reward of refusing to drift.

And in that refusal — that daily discipline to do it right — we recover something deeper than efficiency.

We recover trust. We recover dignity. We recover meaning.

And that’s the kind of system worth building.

Leave a comment

Author’s Note

This piece comes from two decades of watching systems drift — sometimes slowly, sometimes all at once — and seeing good people pay the price. I’ve worked inside plants where standards were sacred and others where they were optional. The difference wasn’t intelligence or capability. It was leadership. Culture. Courage.

Normalization of deviance doesn’t start with bad actors. It starts with good people under pressure. It spreads when silence feels safer than truth. And it calcifies when leaders stop listening.

This essay is not about blame. It’s about responsibility — the kind that starts at the top but belongs to all of us. I write this for the operators who’ve seen shortcuts become policy. For the leaders who want to do better but feel trapped by the urgent. And for anyone who still believes that dignity and discipline aren’t opposites — they’re allies.

You don’t have to be perfect. But you are required to notice.

—Todd Andrew Owings

Sources:

1. Diane Vaughan and the Challenger Disaster
   Vaughan, D. (1996). The Challenger Launch Decision: Risky Technology, Culture, and Deviance at NASA. University of Chicago Press. Vaughan introduced the term “normalization of deviance” in her analysis of how systemic drift contributed to the Challenger explosion.

2. Boeing and Normalization of Deviance
   Kitroeff, N., Gelles, D., & Nicas, J. (2019). “‘Shortcuts Everywhere’: How Boeing Favored Speed Over Quality.” The New York Times.
   https://www.nytimes.com/2019/12/15/business/boeing-737-max-crashes.html

3. Frontline Expertise Ignored at Boeing
   Flight Safety Foundation. (2020). “Normalization of Deviance.” AeroSafety World, Feb. 2020.
   https://flightsafety.org/asw-article/normalization-of-deviance/

4. Joint Commission Report on Deviations in Healthcare
   The Joint Commission. (2018). “Sentinel Event Data – Root Causes by Event Type.”
   Over 60% of adverse healthcare events involved known but tolerated deviations from procedure.

5. OSHA Data on Workplace Incidents
   Occupational Safety and Health Administration (OSHA). (2022). “Commonly Cited OSHA Standards.”
   Many citations involve known violations that were habitually overlooked on-site.

6. Deming on Systems and Respect for People
   Deming, W. Edwards. (1986). Out of the Crisis. MIT Center for Advanced Educational Services.
   Famous for the quote: “A bad system will beat a good person every time.”

7. Toyota’s Leadership Philosophy
   Liker, J. K. (2004). The Toyota Way: 14 Management Principles from the World’s Greatest Manufacturer. McGraw-Hill.
   Toyota emphasizes that poor flow is a sign of disrespect for workers — it signals a system failure, not a people failure.

8. Root Cause Analysis and Systemic Learning
   National Patient Safety Foundation. (2016). RCA2: Improving Root Cause Analyses and Actions to Prevent Harm. RCA isn’t about blame — it’s about learning and redesigning systems to prevent repeat failures.

9. Hidden Costs of Speed Over Quality
   Spear, S. & Bowen, H. K. (1999). “Decoding the DNA of the Toyota Production System.” Harvard Business Review.
   Demonstrates how chasing speed without maintaining process discipline leads to long-term inefficiencies and quality issues.

10. The Human Toll of Cultural Drift
    Field observations and interviews from U.S. operations and manufacturing environments across healthcare, logistics, and industrial sectors over the past 20 years.

We don’t just work at our jobs anymore.
We build our lives around them.

We structure our days, our energy, even our sense of identity around our roles at work. “What do you do?” is a common means to build connections between people. Yet, we willingly skip children’s plays and miss calls from friends. We eat lunch at our desks and carry stress home like a second backpack. We cancel plans, worry about taking too much time off, sacrifice sleep, and gut our attention spans, all in service of an arrangement we didn’t consciously choose.

The deal is whispered into us from the beginning:
Play by the rules.
Put in the hours.
Keep your head down.
Work hard, be loyal — and you’ll be safe.

But that deal is fraying.

Many are waking up to just how one-sided it really is today. Not with rage. Not yet. But with a quiet, hollow realization that something essential has been stolen — and we were convinced to hand it over.

Because the truth is, we’ve been trained to believe that our lives — our actual lives — are worth less than the places we work. Or rather, that our job is the key to everything else in life and must be treated with reverence above all else.

We’ve watched as companies draped themselves in the language of family, belonging, and purpose. Meanwhile, that same company willingly guts entire departments in order to hit a quarterly target. We’ve seen workers punished for doing what was right but not what was approved. We’ve felt it — in our bodies, in our bank accounts, and in the unspoken grief that something sacred has been lost.

We are not angry because we were asked to work.
We’re angry because we kept our end of the deal — and the system didn’t.

That’s the betrayal.

That’s the reason the stress won’t leave your chest at night.
That’s the reason your eyes glaze over during another “all hands” meeting where nothing human is ever said.
That’s the reason you flinch when someone calls your workplace a “family” — because you’ve seen what happens to families when profits fall.

And yet here we are. Still showing up. Still giving it everything.

Because the system is built to keep us grateful for scraps and terrified of change.

This is not a manifesto. It’s a wake-up call.

The deal is rigged.
And you deserve to know how — and why — before you sign away any more of your one and only life.

The Metrics We Watch

We didn’t just sign up for a job.
We signed up for a system that defines value in only one direction: what can be seen, measured, reported, and monetized.

Because once you step into the machine, the scoreboard changes.

It’s not about meaning.
It’s about metrics.

Every week, leaders huddle around dashboards filled with numbers: orders shipped, labor efficiency, uptime, customer calls answered, attendance percentages. These are observable metrics — neat, quantifiable slices of performance, praised for their objectivity and weaponized for accountability.

But what these dashboards leave out — what they can never capture — are the metrics that actually shape your life:

• The parent who misses bedtime five nights a week

• The stress headache that starts Sunday night

• The creeping fear that you’ll be laid off in the next reorg

• The resentment from knowing you gave everything and got discarded anyway

These are hidden metrics — invisible but foundational to the human experience.

And somewhere along the way, we made a bad trade.
We started sacrificing the hidden for the observable.
We gave up well-being for optics.
We surrendered dignity for dashboards.

Let’s talk about what that costs us. And why it’s time to stop pretending the trade is fair.

The Big Shift

Author Bruce Feiler calls it “the nonlinear life” — the reality that life doesn’t unfold in straight lines. People go through transitions, lifequakes, and periods of profound change. What defines the quality of our lives isn’t just how we perform, but how we adapt, connect, and recover.

We’ve built systems that ignore that truth.

Beginning in the 1970s, wages and productivity started to diverge. For decades prior, as workers became more productive, they were paid more. It was a social contract. But then things changed. From 1979 to today, productivity grew nearly 3.5x faster than wages. Productivity kept climbing. Wages flatlined. The wealth went somewhere — just not to the people who made it.

What filled the gap? Narratives. Incentive programs. Cultural carrots. The promise that work could be family. That fulfillment was a ping-pong table away. That pay wasn’t just compensation — it was validation.

And many of us bought in.

What We Gave Up

We started swapping hidden metrics for observable ones. We accepted that sleep didn’t matter as long as we hit the number. That missing dinner was worth the promotion. That being good at our jobs mattered more than being well.

Companies, in turn, stopped caring and merely shifted to pretending they care. A site could be fully green on its dashboards — KPIs met, shipments on time, labor hours optimized — and still be a toxic, morale-killing mess. The observable metrics said success. The hidden metrics screamed dysfunction.

In this system, it doesn’t matter how people feel — only how they perform. That’s the trade. That’s the sin.

A Story I Won’t Forget

At a distribution site years ago, I was present when a hostler left her yard truck running while she went inside the office to get instructions from a supervisor. While she was gone, one of the company’s wealthy owners — a man rarely seen on-site — happened to be in town and walked by the idling yard horse. He climbed into the cab, waited for her to return, and fired her on the spot for leaving the truck idling.

No written policy. No warning. Just a human being erased by power and ego.

The fallout wasn’t just hers. That hostler was critical to daily operations. Other workers scrambled to cover. Supervisors were blindsided. No one could say a word.

This, from a company that called its employees “family.”

It’s not about one boss. That man had bosses too — shareholders, pressures, and incentives. But the system enabled him. It asked for total loyalty from the worker and gave none in return.

The System Isn’t Broken — It Was Built This Way

The moral hazard in modern work is simple:
Companies demand your humanity — your loyalty, your effort, your flexibility — but they reward only what they can measure.

They say, “We’re a family,” but families don’t rank members on performance reviews or lay each other off to make quarterly targets.
They want you to care — deeply — about their mission, their customers, their future.
But when the numbers turn red, they’ll show you the door without a second thought.

And because you need your paycheck, your healthcare, your shot at a raise — you comply.
You show up. You stretch. You stay late.
You ignore the tension in your chest and the way your partner says, “You’re never really here.”

That’s the trap.
You give more than the job is worth — not because you’re weak, but because you’ve been conditioned to think this is how it works.
That if you work hard and stay loyal, something good will happen.

But here’s the truth:
The system is not broken.
It was designed this way — to extract as much value as possible while giving back just enough to keep you compliant.

It is not personal.
It is structural.

And if you don’t name it for what it is, you’ll keep blaming yourself for why it feels so wrong.
You’ll keep betraying your body, your peace, your kids, your sleep — for nothing.

This isn’t a call to burn it down.
It’s a call to stop betraying yourself inside of it.
To reclaim the hidden metrics.
To build a new kind of dignity, one grounded not in deliverables but in discernment.

Because when we stop pretending this deal is fair, we can start choosing something better.

Deming’s Forgotten Wisdom

W. Edwards Deming, the father of modern quality and systems thinking, never wavered on one point:
Respect for people wasn’t a slogan — it was the cornerstone of lasting excellence.

He didn’t believe in managing individuals with fear or praise. He believed most performance problems came from the system, not the worker. Fix the system, and people will thrive. Leave it broken, and even your best will burn out or leave.

“A bad system will beat a good person every time.”
— W. Edwards Deming

Today, we’re watching this happen in real time.

Good people are exhausted. They’re asked to do more with less — less clarity, less support, less humanity. Companies build feedback systems, but not reliable and consistent improvement systems. They chase quarterly targets, but ignore crumbling processes and aging equipment. They talk about culture but punish dissent. They reward metrics and ignore meaning.

And then senior leaders wonder why people stop caring.

We’ve spent years optimizing systems for control — not care. For outputs — not insight. For margin — not meaning.

Deming warned us. We didn’t listen.

But it’s not too late. His legacy isn’t just about Lean tools or process charts. It’s about rebuilding systems where people can think, contribute, and matter.

The fix isn’t just better dashboards. It’s restoring dignity to work — not through perks or slogans, but through honest systems that honor the people inside them.

What We Can Do

Most people will read this and nod.
They’ll feel it in their chest —
the way work eats at them, steals time from their kids, wakes them at 2 a.m., and leaves them hollow on weekends.

And then they’ll say,
“Yeah, but I can’t afford to change.”

That’s exactly what the system counts on.

It counts on you being too tired to question the trade.
Too stressed to plot a new path.
Too financially fragile to take a stand.

But you don’t need to flip the table.
You need to recalculate the deal.

Start with this:
You are not just a worker.
You are a whole person with needs, limits, values, and a soul.

The company will never track the hidden metrics for you.
So you have to do it yourself.

Start small:

• Log your energy, not just your hours. When are you most depleted? When do you feel alive?

• Track sleep, stress, and joy like performance metrics. They tell you more about your life than your bonus does.

• Audit your calendar. Are you prioritizing what matters, or just reacting to what screams the loudest?

• Set boundaries like a professional skill. Because they are.

And then—slowly, honestly—ask:
Does this job allow me to be the person I want to be?
Or does it require me to fragment myself to survive?

Years ago, I had to ask myself the same thing.

The role I was in had prestige, influence, all the right optics.
But the deeper truth was that I was being pulled away from who I was —
tasked with protecting a system that quietly punished its people
in order to reward shareholders.

They had deferred maintenance for years, then blamed the operators.
They cut staffing and called it efficiency.

The work no longer matched the values.

So I walked away.

I fired my employer.
I decided I would never again trade peace, presence, and purpose
for a system that demanded everything and gave the minimum back.

I now work like a consultant.
Not in title — in posture.
I offer my expertise, insight, and judgment to places that want it.
And I retain enough distance to never forget:
My worth is not defined by proximity to the machine.

I’m not suggesting everyone can or should do the same.
But I am saying this: You can stop betraying yourself.
Even inside a job you need.
Even within a system that feels rigged.

You can start protecting your hidden metrics.
You can start saying no.
You can build a life that respects the value you bring
and the humanity you carry.

Because if you don’t — if you keep trading your life
for a seat in someone else’s system —
then the risk isn’t just burnout.

It’s something deeper.

“Your worst sin is that you have destroyed and betrayed yourself for nothing.”
— Fyodor Dostoevsky

Don’t let that be your epitaph.

Don’t trade what matters most for what matters easiest to measure.

Reclaim the deal.

Sources & Notes

• Bruce Feiler, Life Is in the Transitions, 2020.

• W. Edwards Deming, Out of the Crisis, 1982.

• Economic Policy Institute: Productivity-Pay Gap, 2023.

• Personal field notes, observations, and experience across U.S. operations.

Editor’s Note
This essay is part of an ongoing series about reclaiming dignity, autonomy, and meaning in modern work. It’s written for those who feel the quiet erosion of self inside performance reviews, for the ones who sense something is off but haven’t had the words. This is for you — not the title you hold, but the person you are beneath it.

© 2025 Todd Andrew Owings

Rosie the Riveter knew.

They were building planes, tanks, and weapons at a scale the world had never seen. But speed alone wasn’t enough — reliability on the battlefield was the true measure of quality. And that required a new way to think about production.

So the U.S. government taught statistical thinking on the factory floor. Thousands of frontline workers were trained to understand variation and spot defects with precision. Not just inspectors or engineers — operators, machinists, line workers. Even Rosie the Riveter.

The underlying ideas came from two minds you may never have heard of: Walter Shewhart and W. Edwards Deming. Shewhart invented the control chart. Deming transformed it into a leadership philosophy rooted in systems thinking, variation, and respect for people.

Their work laid the foundation. America just applied it.

We Lost the Thread

Most managers today never learned what Rosie knew. Today’s leaders are handed metrics without method — and spend their careers reacting to spreadsheets. They call it being “data-driven,” but it’s really just reacting to noise without context or understanding.

When a number dips, they don’t ask what changed — they ask whether they’ll still be green by month’s end. Most don’t investigate; they do calculus in their heads. Will this roll up poorly? What actions will be expected? Their next move isn’t guided by data, but by bias, heuristics, and fear of looking bad in front of their boss.

They’re solving problems that never existed.

Because they were never taught to ask: Is this variation normal, or is it a signal?

Statistical Process Control answers that question. It teaches you the difference between common cause variation (inherent to the system) and special cause variation (a true signal). Without that knowledge, every bump looks like a cliff.

Precision Lost

Modern operations feel a lot like those maze puzzles where you tilt the board with two knobs to guide a ball. When you’re close to the action, the feedback is instant. You adjust. You learn. You see the pattern.

But in today’s corporate structure, leaders are turning those knobs from ten feet away, blindfolded, and someone else is holding the board. Then they wonder why they can’t hit their targets.

SPC is arguably the easiest and most impactful method that puts you back in control. Not by tightening your grip, but by helping you see the system clearly. It gave ordinary people the power to understand variation and act with precision.

We traded that for KPI dashboards and vibes.

I’m suggesting we pull it back in. Now.

An Example: Pounds per Labor-Hour (PPLH)

Let’s say you manage a distribution center, and your regional VP wants to discuss labor efficiency. The metric: pounds per labor-hour (PPLH). It’s red on the dashboard, and that’s all they give you.

In most sites, there’s a meeting where supervisors are asked to recall recent workdays and remember anything out of the ordinary. If you understand SPC, you skip the speculation. You go to the data and chart it.

• Average output: 12.3 PPLH

• Most weeks: 11.5 to 13.5

• Then two weeks drop to 9.6 and 9.4

SPC flags it instantly — not as a gentle nudge, but a jump-out-at-you drop below control limits.

Instead of panicking, you dig.

The first dip coincides with the rollout of a new automated sorter. Operators weren’t fully trained, and misfeeds required double handling — dragging down throughput. The second week? You had three temps unfamiliar with the layout, causing congestion in high-velocity pick mods.

Now imagine this conversation in your monthly site review.

Instead of defending a red cell, you show the chart.

You say, “Here’s our system’s typical range. Here’s the moment we fell out of control. And here’s what caused it — not speculation, but a clear signal.”

No politics. No blame. Just root cause tied to real events, with a plan to improve: better onboarding for temps, staggered rollout for new tech, cross-training in high-volume lanes.

That’s what SPC does. It gives leaders context. It shifts the conversation from anxiety to clarity. And it earns you something you can’t get from a dashboard alone: credibility.

Not because the numbers are good.

Because you understand them.

Leaders, This Is on You

You were never taught this. That’s not your fault.

But it is your responsibility to learn it now.

Because once you do, everything changes.

“In God we trust. All others must bring data.”
— W. Edwards Deming

Even the monthly site review — that grim theater of red-yellow-green charts and half-hearted root causes — becomes something else. With SPC, you don’t debate opinions or plead context. You bring evidence. You don’t fight over blame. You trace signals. Your team begins to distinguish the meaningful from the noise, and strategies start to converge.

Root causes aren’t wild guesses anymore. They’re plotted patterns. Actions become focused. Improvement becomes visible. And trust — that rarest commodity in today’s workplace — starts to rebuild. Not because of slogans, but because people finally feel in control of their own work.

You cannot lead a system you don’t understand.

Start here.

Plot your own data.

Ask better questions.

Teach your people the difference between noise and signal.

Because when you see variation clearly, you don’t just improve the process.

You improve everything.

Sources & Notes

1. W. Edwards Deming, Out of the Crisis, 1982.

2. Walter A. Shewhart, Statistical Method from the Viewpoint of Quality Control, 1939.

3. “SPC and the American War Effort,” Quality Progress, ASQ Archives.

4. U.S. War Production Board training manuals, 1943–1945.

5. Todd Owings, Personal SPC Application Archive.

[Rosie the Riveter image and SPC wartime training archive visuals included here.]

There was a time when leadership was an act of stewardship. The job was simple in principle, even if it was never easy: protect your people, build stability, and earn trust by doing the right thing even when no one was watching.

Responsibility meant something.

Some of the finest leaders appeared stern, even unpopular, but their authority was tethered to responsibility and human decency. There was humility in it — an understanding that the power existed to lift and support others, not to see them as headcount that could be cut whenever expedient.

That ethos disappeared faster than anyone expected.

The Descent

It began innocently enough — the near worship of efficiency, the rise of metrics as a measure of commitment to the company. By the late 1990s, the gospel of shareholder value had fully replaced the language of ownership and responsibility.

Then came the consultants.

They arrived speaking Lean, quoting Toyota, invoking Deming, and selling value stream enlightenment in meeting decks. Ultimately, they ushered in something colder: the ability to use Lean to quantify people more precisely as a measure of throughput.

Private equity noticed. Then, they reverse-engineered Lean.

They saw its elegance: the promise of process visibility, waste elimination, and operational discipline. Then they stripped out the human core — respect for people — and replaced it with advanced analytics, modeling and simulation.

For decades, investors had modeled labor savings in broad strokes. Lean gave them a microscope. Suddenly, every movement, every task, every second of human effort could be observed, measured, quantified, modeled, and monetized in a much more efficient manner.

What had once been a philosophy of empowerment became a precision-guided labor reduction tool. What was meant to make work meaningful was recast as a method for making it cheaper.

Private equity didn’t misunderstand Lean; they perfected its extraction potential.

The result wasn’t transformation. It was optimization without empathy — an economic Darwinism masquerading as science.

Voltaire once said, “No problem can withstand the assault of sustained thinking.”
He was right. But we’ve built a system where all that thinking is aimed not at solving problems — only at squeezing more value from the people still doing the work.

The Conversion of Fear

This new model needed a fuel source, and it found one: fear.

Fear of missing a number.
Fear of losing the client.
Fear of being labeled “resistant to change.”

It’s a remarkably efficient energy. It requires no inspiration, no loyalty, no shared purpose. Just pressure, targets, and the steady implication that everyone is replaceable.

Executives feel it from shareholders.
Directors feel it from executives.
Supervisors feel it from directors.
And the people actually doing the work — the ones lifting, driving, building — absorb it silently, like an airburst of radiation from above.

The fear changes people. It rewires behavior. It makes reasonable leaders transactional, and once-honorable ones often petty and cruel.

They start to equate their survival with obedience.
They stop challenging absurd expectations.
They stop defending their people.
They stop leading.

The Disconnection

This is the real legacy of the private equity era: a structural disconnection between decision and consequence.

Senior leaders don’t see the human cost of their directives anymore. They see dashboards and models — sterile instruments that turn frustration, fatigue, and injury into trend lines and bar charts.

The farther they get from the floor, the easier it becomes to confuse abstraction with real, authentic insight. Dwight D. Eisenhower once said, “Farming looks mighty easy when your plow is a pencil and you’re a thousand miles from the cornfield.” The modern executive plows with data and wonders, without irony, why their plans don’t meet specifications in an actual operational environment.

They talk about “our people” as if they’re an audience, not a responsibility.
They use the word team while dismantling the conditions that make teamwork possible. They repeat the language of Lean while violating its first principle — respect for people — in nearly every decision they make.

It’s not malice; it’s detachment.
A slow decay of empathy replaced by metrics and incentives.

The Corporate Ethic of Cowardice

Modern leadership has become a closed-loop system of fear and reward. Executives make cuts they know are destructive because it pleases investors. They announce them with language so polished it feels almost humane — “right-sizing,” “optimization,” “strategic transformation.”

In the middle, cowardice masquerades as doing-our-best pragmatism.
Managers explain away the perceived cruelty with a shrug — “It’s above my pay grade.” “I don’t make the rules.”

And on the floor, the people who actually hold the company together are told they’re part of a “family,” complete with monthly meetings meant to foster unity.
But they see the truth — that what was once trust has become theater, and that real families don’t need to be convinced they belong.

There’s no accountability anymore — only performance.
A hierarchy of self-preservation.

The Amazon Example

Consider the most visible case: Amazon’s October 2025 announcement of 14,000 corporate layoffs, potentially doubling in early 2026.

The company described the decision as a move to “reduce bureaucracy” and “become leaner in the era of AI.” Yet internal communications admitted the cuts came “despite the company’s performance” beating market estimates handily.

That single phrase captures the ethos of the age.

Success no longer protects anyone.
Profit is no longer the reward for excellence; it’s the justification for elimination.

This isn’t innovation. It’s institutional cowardice — fear of investor dissatisfaction disguised as strategy that belies the growth of real value over time in an operation.

And it’s not unique to Amazon. Every industry has its own smaller, quieter version.
The system has simply learned to make cruelty look like economic sacrifice for the greater good of the company.

The Moral Decline

The speed of this collapse still shocks me.
It didn’t take a generation to lose our moral bearings; it took a business cycle.

Once the language of stewardship was replaced with the language of extraction, everything else followed in short order.

Respect for workers gave way to performance management.
Loyalty gave way to accountability.
Trust gave way to compliance.

And humility — the essential trait of every great leader I ever knew — is a rare and valuable find in today’s workplaces.

Leaders no longer admit uncertainty.
They don’t ask questions; they issue talking points.
They don’t walk the floor; they schedule town halls
They’ve learned to mistake visibility for leadership.

They no longer see themselves as part of a continuum — inheriting something worth preserving and handing it off better than they found it.
They see themselves as interchangeable actors in a performance of competence, judged only by what the quarter says when the curtain falls.

The Red Line

There comes a point when all the euphemisms stop working.

If you lead people, you know this moment — when you’re asked to do something that crosses your own moral threshold. When your gut tells you the spreadsheet is lying. When you realize that protecting the business and protecting the people who make it possible are no longer the same thing.

That’s the red line for me.
Most cross it quietly, telling themselves it’s temporary.
But every compromise makes the next one easier.

Leaders once defined themselves by the burdens they accepted.
Now they define themselves by the risks they avoid.

The Reckoning

Every organization has two structures: one made of steel, and one made of trust.

The steel holds up the building.
The trust holds up the people.

Once that trust breaks, collapse is inevitable — slow at first, then sudden.

We’re living in that slow phase now.

The dashboards still glow green. The numbers still please.
But the trust is gone.

Listen closely, beneath the hum of normalcy — you can hear it.
The faint groan of a structure sagging under the weight of its own contradictions.

Leaders built this system.
They can rebuild it.

But not with slogans, not with governance frameworks, and not with another “alignment huddle.”
We’ve had a generation of those — pizza parties posing as gratitude, town halls sold as transparency, off-sites choreographed to look like connection.
They don’t build trust; they anesthetize it.

You don’t rebuild trust with frameworks.
You rebuild it when a leader finally looks in the mirror and admits they’ve been hiding behind one.

It takes humility. It takes personal responsibility. And it takes the courage to say, enough — not as a slogan, but as an act of freedom.

Because the system isn’t broken.
It’s working as designed.
And that’s exactly the problem.

Subscribe now

Sources

1. Reuters – “Amazon to Lay Off About 14,000 Corporate Roles in 2025,” October 28, 2025.

2. Business Insider – “Amazon Cuts 14,000 Jobs Despite Strong Performance,” October 2025.

3. CNBC – “Jassy: We Will Need Fewer People Doing Some of the Jobs That Are Being Done Today,” June 2025.

4. W. Edwards Deming, Out of the Crisis, 1982.

Editor’s Note

This essay continues my series on moral leadership and cultural decay in operations — a companion to The 5S Fallacy and The Death Cult of Operational Dashboards.

It’s written for those who still remember when leadership meant stewardship, when humility was a strength, and when being a boss meant being accountable — not afraid.

Lean wasn’t supposed to be a control system.

It’s supposed to be a human system.

It started with a purpose. Focus where the work is done and reduce waste, grow the people, and solve real problems. That was the soul of the Toyota Production System (TPS), evolving with the people, committed to fostering good change, grounded in respect. Lean was intended to carry that approach forward. Yet, somewhere between the stretch goals, operational dashboards and tightening budget targets, we lost the very soul of Lean.

What’s left in most places is just the toolbox of 5S, value stream maps, and standard work, among others. These were meant as part of a greater improvement philosophy built around the support of people, not control. Yet, stripped away from their roots, theses tools don’t truly guide improvement. They punish. And that’s where we are now.

But first, let me show you what good looked like.

A Story That Still Gets It Right

UPS built a process improvement team. One of their famous insights? Left-hand turns waste a lot of fuel, slow down all deliveries, and often are a factor in accidents. So the team developed a methodology to eliminate most left turns. The results were staggering:

• 10 million gallons of fuel saved

• 20,000 tons of CO₂ emissions cut

• 350,000 more deliveries a year

But here’s what matters: it made the drivers’ jobs easier and safer. Their workday became smarter and smoother. That’s actual Lean—improving efficiency by making work better for those doing the actual work. It even led to better serving the customer. Lean with its soul deeply intact.

“This was not just a sustainability initiative,” said UPS Senior Director of Sustainability Patrick Browne. “This was an operational efficiency improvement that also helped employees and customers.”²

Then There’s Amazon

Where the UPS Left-Turn story illustrates how Lean methods save money, increase throughput and support workers, Amazon has scaled Lean tools and paired them with advanced analytics. The result is a labor control system used to monitor and punish front-line employees if they fail to meet engineered standards.

Workers are tracked by algorithmic surveillance—“Time Off Task” scores, scan rates, pause metrics. Deviate too far, and the system fires you automatically. Warehouse employees skip water to avoid bathroom breaks. Injury rates skyrocket. People burn out. Thirty percent quit in 90 days.³

It’s not just Frederick Taylor with a stopwatch anymore. Today, it’s as if Taylor were armed with machine learning; real-time, swarm surveillance; and algorithmic control. The same Taylor who once timed individual bricklayers by hand would’ve reveled in today’s ability to track every scan, keystroke, and momentary pause across an entire workforce. We didn’t evolve past Taylor’s Scientific Management, we merged it with Lean tools and gave it shark teeth and attack capabilities.

Amazon didn’t misread Lean. They just surgically removed it’s tools from the embedded ethics upon which it is built, and weaponized those tools.

The 5S Fallacy Revisited

Last year, I wrote about The 5S Fallacy: the delusion that painting lines on the floor and hanging shadow boards is a magical gateway to culture change with minimal cost and only a few hours required by leaders spent watching others clean.

That article struck a nerve with some, but I didn’t go far enough.

Here’s what I’ve come to realize: Lean didn’t just lose its edge. It’s been co-opted. Most CI managers today aren’t focused on developing people or solving meaningful problems. If you are one of those who is doing the hard work on people, my apologies and thank you. Unfortunately, most CI mangers are tasked with finding ways to reduce headcount, automate human roles, and most importantly hit the monthly targets sent from above.

I’ve seen the pattern too many times:

• A project team maps out a process to improve flow

• Leadership asks: where are the savings?

• The answer they almost always are seeking is the same: fewer people.

On the shop floor, you understand the resentment that builds. Frontline employees watch as their workplaces experiences more turnover, declining quality, and a breakdown of previous routines. Over time it cascades into a brain drain as the tribal knowledge holders—those who quietly keep things running—walk out the door.

Why Culture Doesn’t Stick

Leaders love to ask why their Lean transformation doesn’t stick, as if they are merely giving feedback on the work of others from a distance, while standing within the area they own on the org chart. They wonder why morale erodes, why engagement plummets even in the “good times” when the dashboards glow green.

Here’s the answer: people can tell when your systems are designed to extract from them, not invest in them. Regardless of what you claim in your corporate mission.

A good work culture doesn’t stick when there isn’t trust. And trust doesn’t grow in a system that punishes deviation without asking questions. The workers work in the system created by leadership. There is no way to poster over or pizza-party your way out of a fear-based workplace. When workers work in fear, no KPI can help you earn their loyalty.

Where It All Went Off the Rails

Let’s call it what it is: a betrayal of intent.

Lean’s tools—VSMs, 5S, standard work—were meant to support human-centered systems. As the organizational improvement capabilities of those tools grew in influence, the essence of each was taken and weaponized by folks with a profit-above-people belief system. The same A3 that empowers a team is used to justify layoffs. The andon cord that signals help becomes a digital production leash.

It is my hypothesis that Amazon didn’t misunderstand Lean. They treated it like an unrelated set of highly effective tools, then fused it with machine learning, behavioral engineering, and swarm-level surveillance to optimize cost savings in the smallest measurable gaps of time.

It’s not operational excellence. It’s digital feudalism.

The Hidden Collapse

In my earlier piece, I warned that Lean had fallen into the trap of performative improvement—symbolic gestures in place of real transformation. But I now see that this performativity is just the surface symptom of a much deeper and darker problem with the discipline of Lean, that I love.

What’s really happening is more dangerous:

• CI practitioners are being pulled away from the floor.

• The voice of the front-line worker is being drowned out.

• Tribal knowledge is walking out the door faster than it’s being documented.

Lean isn’t just stuck. It’s being drained of the very humanity it was designed to serve.

A Different Path

This isn’t a call to abandon Lean. It’s a call to reclaim it.

Lean at its best is a human-centered philosophy of systems thinking and continuous learning. It is about developing people by removing the obstacles that prevent them from doing great work. Not measuring every motion of that work.

Start with better questions:

• Does this change make the job easier for the person doing it?

• Is it respectful to the people doing the work?

• Have we listened to the people who live in the process?

• Are we optimizing for customers and coworkers or just for financial wins?

Lean didn’t fail us. We failed it.

But we still have a choice.

Share

Author’s Note: This piece is part of Chasing Omniscience, my ongoing series exploring how visual-spatial thinking reveals the soul of systems—and what happens when that soul is ignored.

Footnotes

1. Seth Godin, Tim Ferriss Show, Episode #672 ↩

2. UPS Pressroom. “UPS Eliminates Left Turns to Save Fuel.” link ↩

3. Reveal News: “How Amazon Automatically Tracks and Fires Workers for Time Off Task.” link; NPR: “Injuries at Amazon Warehouses Continue to Rise.” link; The Guardian: “Amazon workers skip bathroom breaks to keep up with quotas.” link ↩

I don’t think in snapshots.
I think in movies—in motion. People, information, pressure all flowing within a system, all at once.

My mind runs the simulation automatically. From any point, I can see what that person in the system sees, sense where energy flows—or doesn’t. It’s like living inside the process itself.

That’s what it’s like to be a high-spatial thinker. I probably think differently than you. Most people use a verbal-linear mode of reasoning without even noticing it. Many visual-spatial thinkers can build complex things in their minds, seeing the finished object in 3-D before it exists. My gift is a little different—I don’t construct objects; I inhabit systems.

When I walk into a warehouse, a production line, or a leadership meeting, everything animates. Lines of communication, stress points, and unspoken rules come alive like current running through the wiring. I can feel where the flow is smooth and where it wobbles. When the story a company tells about itself doesn’t match what’s actually happening on the floor, the dissonance shows up instantly—like gears grinding under load.

Why My Writing Sounds So Critical

People sometimes say my essays are hard on management.
They’re not wrong.
But I’m not angry. I’m just describing what I see.

What looks like criticism is really diagnostics—mapping the spots where the story and the system part ways.

When a company claims it is “people first” but designs every process around throughput first, that’s not philosophy; that’s physics. Systems either align or they don’t. Respect and dignity aren’t slogans—they’re a real part of the operating system. Remove or diminish them and performance starts to rattle. Costs increase. Control fails.

I don’t write to scold; I write because ignoring that kind of friction feels dishonest. Once you see how easily harm moves through an organization, pretending it’s invisible feels like lying to yourself.

How My ‘High Spatial’ Brain Works

Researchers talk about two main kinds of visual-spatial thinkers:

• Object visualizers—they see vivid, detailed images.

• Spatial visualizers—they see relationships and motion.

I’m firmly in the second camp. My cognition is kinetic. (If you want the research, check out Maria Kozhevnikov and Mary Hegarty’s work on spatial visualization. They explain it well.)

I don’t just see where people stand in a company org chart; I see how communication and trust flow between them, how decisions ripple, how pressure looks and feels when it travels across a network. Once real, human empathy gets squeezed out of a process, it shows up immediately—conversation slows, initiative dies, the system starts squeaking like an ungreased wheel.

What I Actually See

Every organization runs two systems at once:

1. The declared system – the values, vision statements, and leadership slogans.

2. The lived system – the one people experience at 10 a.m. on a Tuesday.

Most of the dysfunction hides in the gap between them.
That’s where good intentions get lost in translation, where a “people-first” policy quietly becomes a “numbers-first” habit. Even if the dashboards glow green, the engine underneath is quietly running hot.

That space—the tribal knowledge zone—is where I spend my time. I’m not seeking to name villains; I’m tracing the source of the leak. Most of what I write about culture or leadership lives right there, where the promise of dignity gets tangled in the machinery of chasing metrics. Pointing that out isn’t rebellion—it’s maintenance on the system.

Why I Can’t Keep Quiet

I don’t hunt for flaws; I just see them.
Like an engineer who hears a bad bearing, I can’t tune it out.

I’m not angry about it; I’m fascinated, sometimes a little heartbroken by what I observe. Most broken systems start with decent people who stopped listening to feedback. My instinct isn’t to burn anything down—it’s to tune it carefully until it runs the way it was meant to.

So, yes, my essays read like critiques of leadership. They are. But they come from affection for the craft. I love watching a process run cleanly. I love when words and actions finally match up. I simply have a low tolerance for hypocrisy disguised as efficiency.

The Gift (and the Curse) of Seeing Everything

The upside of this kind of mind is foresight.
I can run a process in my head like a movie and see where it stalls before it happens; then simulate the potential countermeasures. That’s a super power in operations. It’s less fun when everyone’s celebrating a new project’s completion and I’m already seeing the downstream jam that’s coming soon.

But this is the wiring I’ve got. I see organizations the way musicians hear rhythm—patterns, tension, release. When the beat falls off tempo, I notice. Writing is how I bring it back into time.

Why I Keep Writing

I’m not out to save the world or tear down leadership.
I’m just describing what it looks like from inside a mind that sees systems in motion. The truth is, I respect good leadership profoundly. When it works, it’s a kind of alchemy—people moving in sync, information flowing cleanly, purpose showing up in every decision.

That’s what I’m after when I write. Not outrage. System alignment.
When I point out absurd or unethical structures, I’m not swinging an axe; I’m holding up a mirror to it. The difference between a complaint and a map is intention. I’m trying to draw the map.

If that comes off as critique, so be it.
I call it preventive maintenance—for organizations, and for myself.

Author’s Note
This essay is part of Chasing Omniscience—an ongoing exploration of how systems behave, what visual-spatial thinkers see inside them, and how dignity and design intersect in everyday work. Field notes from someone who can’t stop watching the gears turn.

Subscribe now

About the Author
Todd Owings is a Child of God, Lean Six Sigma Master Black Belt, Corporate Social Scientist, Visual Spatial Thinker & Translator, and Kinesthetic Empath based in the Chicago area. He writes about the patterns beneath operations, the culture hidden inside process maps, and the quiet mechanics of how people and systems succeed—or don’t.

For more information on High Spatial Thinking, check out:
Maria Kozhevnikov & Mary Hegarty, “Mechanisms of Visuospatial Thinking,” Cognitive Psychology, 2001.
Temple Grandin, Visual Thinking, 2022.
Howard Gardner, Frames of Mind, 1983.

Note: This is the 3rd in a series examining corporate performance art. The first two covered process and measurement. This one covers belief — the most dangerous system of all.

The curtain always rises the same way on the webinar: an executive thanks everyone present for their efforts on behalf of the company for their work last year. Next, they mention increasing pressure from “market volatility,” while simultaneously promising the team can defy it through discipline, innovation, and the sheer moral superiority of the leadership team.

The kingdom is uneasy, the markets unpredictable, and the High Leaders gather to declare that, while others may falter, their team will not. The air hums with recycled optimism. Heads nod as they speak of discipline, synergy, and focus—principles meant for the people below them, presented as faith, but functioning as distance.

They unveil the plan: an ambitious transformation fueled by focus, efficiency, and what might charitably be called corporate alchemy. The idea is elegant in theory — achieve more with less, deliver growth and savings in the same breath. It’s presented as innovation, a triumph of discipline and clarity over limitation. The language is so confident, so practiced, that for a moment it feels almost achievable.

The forecast is gold. The resources, inevitably, are lead.

Everyone understands the math doesn’t work, but that’s not the point. The exercise isn’t about precision; it’s about belief. The leaders frame it as agility, as the organization’s ability to “do more with what we have.” The middle layers translate this into commitments, careful adjustments, and just enough optimism to keep the process moving. It’s part performance, part survival — the delicate art of turning contradiction into alignment. What emerges is less a strategy than a shared illusion: a version of the future everyone agrees to believe in long enough to get through the meeting.

Thus begins the Fellowship of the Stretch Goal: a loyal band charged with achieving the impossible through willpower, PowerPoint, and denial of obvious truths.

The decree spreads quickly. Memos multiply, meetings spawn, and local leaders gather their teams to interpret the new commandments. Schedules are rewritten. Charts are redrawn. The familiar phrases return like ghosts from quarters past: With creativity and focus, we can do this.

No one says aloud that it would require time travel.

The work begins, as it always does. Supervisors stretch schedules past reason. Managers submit the same resource requests that will quietly die in the approval queue. Analysts scrub data until it looks less incriminating. Everyone performs the small, daily miracles required to keep a doomed plan alive.

At first, it almost works. Early numbers flicker upward if viewed from the right angle. But miracles demand repetition. When progress slows, the High Leaders demand urgency. They summon passion, resilience, and “ownership.” Excellence, they remind everyone, is a choice—a statement that always sounds noble when spoken by someone who doesn’t bear the consequences.

By mid-quarter, exhaustion is the only measurable improvement. What can’t be done is done anyway, and what breaks is hidden under words like efficiency and optimization. The people closest to the work realize that the company’s real product isn’t what it sells—it’s the illusion of control.

Then comes the review. Each site presents its numbers in turn, standing before the Council of Performance like villagers before a tribunal. The High Leader frowns at the charts, as if the red ink were an act of defiance. “Walk me through your plan,” he says, voice calm, eyes tired. “What’s standing in your way?”

They tell him. He doesn’t listen. Shortages sound like excuses. Fatigue sounds like lack of commitment. The problem, as always, isn’t the plan—it’s the people.

After the meeting, a cheerful note appears thanking everyone for their candor and celebrating “our relentless pursuit of excellence.” It closes with the good news that next quarter’s targets will be even more ambitious. The problem, apparently, was belief.

This is corporate anti-alchemy—the conviction that reality will yield to willpower. In the old days, alchemists tried to turn lead into gold with mysticism and fire. Today’s executives do it with confidence and calendar invites. The materials have changed; the hubris hasn’t.

No one sets out to deceive. They truly believe a strong vision and an all-hands meeting can overcome missing headcount and outdated, inefficient tools and systems. Faith in leadership has replaced feedback from the field. The organization no longer studies its problems; it auditions solutions that flatter the story it wants to tell.

By year’s end, the miracle still hasn’t arrived. Costs are up, morale is down, and the same people who spent the year performing operational gymnastics are told they “didn’t execute.” The slides are edited, the numbers reframed as progress, and the next prophecy begins. The market will be unpredictable, yes—but this team will be different.

And so the cycle repeats: lead distributed as gold, gold demanded as proof of loyalty, and anyone who points out the chemistry problem quietly reassigned to “special projects.”

Anti-alchemy isn’t a process—it’s a belief system. It feeds on conviction, punishes reality, and rewards those who can promise miracles without flinching. The rest of us polish the reports, tidy the residue, and pretend we don’t see the smoke.

Moral of the story

In business as in fairy tales, those who promise gold rarely touch the metal, and those who touch the metal rarely see gold.