The Cost of Being Right

The problem is not the dashboard. The problem is not the competence in the room. The problem is the kind of thinking the enterprise rewards when it is under pressure. That is the quiet way manufacturing loses. It loses not through a single failure, but through a method of reasoning that keeps failure repeatable. This piece is about a pattern that looks like rigor but behaves like drift. It is the dependence on detail and examples as a substitute for mechanism. It is the habit of chasing symptoms and calling it problem solving. It is the belief that if we explain the last incident well enough, the next one will not arrive. The hidden question underneath every operating review is whether the firm is learning, or whether it is producing paperwork that flatters itself as learning. “What would have to be true for this outcome to keep repeating.” That line forces the room to do something it has been trained to avoid. It forces the room to name conditions, not incidents. It forces the room to state what the system is doing, not what a person did. It forces the room to accept that most recurring outcomes are designed, even when nobody designed them on purpose.

The example trap that wears a lab coat

There is a version of detail obsession that is healthy. Manufacturing lives on specification. Quality lives on evidence. Safety lives on clear work. When a line is unstable, details matter. When a customer is hurt, details matter. When a product fails in the field, details matter. Nobody serious argues for hand waving. The trap is different. The trap is when details stop being inputs and become refuge. The trap is when a request for an example is not an attempt to verify a claim, but a way to avoid naming a claim. The trap is when the plant is drowning in after action narratives while the conditions that cause the narratives remain in place. Example addiction has a predictable shape. A team surfaces a pattern. Leadership asks for instances. The team delivers a stack of instances. Leadership then asks for more, often in the name of rigor, and the discussion returns to the uniqueness of each case. The uniqueness becomes a reason the pattern cannot be addressed at the level of structure. The enterprise ends up with a museum of stories and a shortage of mechanisms. In practice, the example becomes a loophole. An example makes every claim contestable because someone can always find a case that does not fit perfectly. If the aim is to keep the system intact, examples are useful because they keep the conversation in exception land. Exception land is where accountability goes to die. It is where nothing has to change because the last thing was “different.” A mechanism is not like that. A mechanism corners people. A mechanism forces ownership because it points to control surfaces. A mechanism makes time and money connect in a way that cannot be massaged with language. If the firm says the issue is decision delay, the obvious question becomes who has decision rights, where the approval sits, and what it costs when

approval waits. If the firm says the issue is process instability, the obvious question becomes what condition is unstable and why it is tolerated. Mechanism talk creates consequences. Example talk creates motion. Examples keep the conversation safe. Mechanisms make somebody responsible. This is why the detail trap is not primarily an intelligence problem. It is a governance problem that presents as an intelligence problem. It is an institutional habit that trains smart people to stay small. It teaches them that the safest kind of competence is the kind that never threatens the system’s arrangement of power. Manufacturing organizations often defend example addiction with a reasonable claim. Plants are complex. Operations are not clean. Every line has edge cases. Every incident has context. A single explanation can become arrogant. If you have ever watched a corporate initiative crash into the floor because someone oversimplified, you develop a reflex to demand detail. That reflex becomes a liability when it turns into an operating standard that delays commitment until the firm has explained every corner. Real systems do not wait for that. They keep producing outcomes while you gather examples. The firm then pays for time as if time were free.

When problem solving becomes theater

Symptom chasing is not merely poor analysis. It is a form of theater the organization learns because it pays. A symptom is visible. A symptom can be measured. A symptom can be assigned. A symptom can be mitigated inside a function. A symptom can be managed without stepping on someone else’s territory. A symptom creates the appearance of control. A cause is politically expensive. A cause often sits across lanes. A cause often implies an owner with power. A cause often requires redesign. Redesign requires money, attention, and the willingness to admit the current architecture is producing the wrong outcome. So the firm builds a parallel factory. One factory makes product. The other factory makes proof. The proof factory produces trackers, sign offs, training attestations, audit trails, meeting minutes, and slide decks that show the system is being managed. It is a rational adaptation. If careers are made by avoiding blame, proof matters more than mechanism. If promotions go to people who keep the plant calm, proof matters more than learning. The proof factory expands until it competes with the work. The most reliable signal that the proof factory is winning is the language used to close actions. In too many plants, the default closeout is a human instruction. Train. Communicate. Reinforce. Remind. These are not always wrong. They are often the cheapest thing that can be done quickly. They also rarely change the probability of recurrence when the condition that produced the failure remains.

Here is a prediction that should be embarrassing if it fails. Pull the last year of corrective actions from your quality escapes, your safety events, and your chronic downtime. Read the closeout language. If your system is caught in the detail trap, most closures will be some version of telling a person to do better, and the issues will recur with fresh names. If the opposite is true, the record will show engineered changes to conditions, and recurrence will drop in kind, not just in count. That prediction is not moral. It is testable. It is an audit of how the firm thinks. Mitigation makes the week survivable. Mechanism makes the year repeatable or not. The reason symptom chasing is so contagious is that it is rewarded in the short run. A leader who can close issues fast looks decisive. A leader who refuses to close issues without mechanism looks slow. The firm quietly punishes the second leader because the second leader forces the bill into the open. When the enterprise trains itself this way, it loses the ability to see fundamentals. It starts mistaking activity for progress. It starts mistaking explanation for understanding. It starts mistaking metrics for reality. Metrics then join the theater. The moment a number becomes a target, people start protecting the number. Some do it consciously. Most do it without admitting it. The metric stops being a signal and becomes a negotiation surface. The organization learns to optimize the presentation of performance rather than the conditions that generate performance. Reporting becomes an art. Reality becomes background noise. This is why so many organizations feel oddly busy and oddly stuck. They are learning how to manage the appearance of control. They are not learning how to produce control.

Smart people and the comfort of self deception

There is a particular failure mode that shows up in the most capable rooms. A famous physicist who won the highest prizes of his field warned that the easiest person to fool is yourself. His point was not about stupidity. It was about pride and identity. He argued that intelligence can become the perfect tool for rationalizing a belief you do not want to test. The smarter you are, the more convincing your story can be. You can defend a bad decision with a good argument. You can bury doubt under sophistication. You can explain away counterevidence until you are left with a clean narrative that protects your status. This shows up in manufacturing as a kind of disciplined blindness. The sharpest people can become the best at explaining why the system cannot be changed. They do not say no. They say it needs more diligence. They say the risk needs review. They say the organization needs alignment. They say it needs a pilot. They say it needs another example. Every sentence is reasonable. Together, they form a machine that prevents redesign.

This is why the detail trap is so hard to confront. It is not a room full of unserious people. It is a room full of serious people using seriousness as a shield. The firm calls it rigor, but the output is delay and recurrence. The demand for examples is often the giveaway. A leader who is genuinely testing a claim asks for the one example that could disprove it. A leader who is protecting a belief asks for enough examples to bury the claim in exception. The two requests sound similar. The consequences are opposite. The deeper issue is epistemology. It is how the firm decides what it believes is true. If the firm treats explanation as proof, it will live in stories. If it treats proof as proof, it will demand mechanisms that can be tested. The second approach feels harder because it carries the risk of being wrong in public. The first approach feels easier because it allows the firm to keep its identity intact. A good story can defend a bad system longer than any failure can. There is a reason people retreat into detail when the stakes rise. Detail feels controllable. Detail feels like work. Detail creates the comfort of motion. Mechanism creates the discomfort of consequence. Mechanism tells you that the architecture is producing the outcome, and architecture is owned by leadership. This is why some of the most educated leaders can be the least effective at changing outcomes. Education can produce confidence without producing humility. Technical skill can produce mastery inside a lane without producing the ability to see across lanes. The result is a leadership class that can optimize parts while the whole decays.

The mess that no one wants to own

Manufacturing problems rarely arrive one at a time. They arrive as clusters that interact. A schedule miss triggers overtime. Overtime triggers fatigue. Fatigue triggers errors. Errors trigger scrap. Scrap triggers expedites. Expedites trigger planning churn. Planning churn triggers more schedule misses. Each problem can be handled locally, and each local handling can be justified. The combined result is a mess that eats margin. This is why symptom chasing is so seductive. A symptom looks like a single problem. A mess demands systems thinking. Systems thinking demands cross boundary authority. Cross boundary authority is scarce. So the firm assigns symptoms to functions and calls the work done. A plant can become very good at this and still get worse. The team feels productive because actions are closed. Leadership feels in control because meetings are full. The board sees a thick packet that shows diligence. Then the same outcomes return. The firm acts surprised, as if recurrence were a failure of effort rather than a consequence of architecture.

The cost of this pattern is not only operational. It is cultural. When teams see that root causes are not safe to name, they stop naming them. When they see that the safest action is training, they stop proposing redesign. When they see that the firm rewards explanation more than elimination, they get better at explanation. Over time the organization forgets how to learn. Learning, in this context, is not reading. It is the ability to change the system’s output by changing the system’s conditions. If the system keeps producing the same output, then whatever the firm calls learning is not learning. It is commentary. The most painful part is that everyone involved thinks they are doing the right thing. They are not lying. They are doing what the incentive structure asks them to do. They are minimizing exposure. They are avoiding the career risk of being the person who touched a fundamental control and then got blamed for a downstream event. They are acting like rational humans inside a system designed to punish structural ownership. This is why fixing the detail trap is not a matter of telling people to “think bigger.” The system must demand bigger thinking or it will not appear. People do what the system pays for.

The board questions that change the room

A board cannot manage a plant. It can manage the standards by which the executive team claims it is managing the plant. If those standards reward theater, theater will grow. If those standards reward mechanism, mechanism will rise. Here is a paragraph that can be read aloud in an ELT meeting without sounding like a sermon. When an issue recurs, do we ask what condition makes it repeatable, or do we ask for more cases until the pattern dissolves into exceptions. Do we close actions with changes to the work, the design, the controls, and the authority, or do we close them with messages to people. Do we measure whether recurrence drops in kind, or do we measure whether the count moved enough to stop the discussion. A second paragraph belongs beside it. When we say we have an insight, what is the next actuation that must follow if the insight is real. Who has the right to act. What approval does it require. What delay does that approval create. If we cannot describe the path from signal to act without hand waving, are we managing the business, or are we narrating it. Those questions are not abstract. They are about control. They separate an enterprise that can shape outcomes from an enterprise that can only report outcomes. There is a quiet phrase that belongs as a recurring standard in every operating review. If we cannot prove it will act, it will negotiate. Negotiation has its place. Negotiation is also how firms pay for time with margin. If we cannot prove it will act, it will negotiate.

The detail trap survives because negotiation feels responsible. It arrives wearing good words. Governance. Alignment. Diligence. Risk management. Each word has value. Each word can also become architecture. When architecture hardens, the firm becomes slow in the only way that matters. The time between signal and action expands until competitors buy advantage with speed, and the firm explains the loss as “market pressure.” The most dangerous part of this pattern is that it compounds. A little delay creates workarounds. Workarounds create variation. Variation creates more exceptions. Exceptions create more need for detail. Detail creates more delay. The firm thinks it is becoming disciplined. It is becoming brittle. A law from early control theory says a system must have enough variety in its responses to handle the variety in its environment. When leadership responds to rising variability by adding friction instead of adding capability, it reduces its ability to cope. It produces a system that can explain why it failed but cannot prevent the failure. This is the hidden trade the detail trap forces on the enterprise. It trades adaptability for documentation. It trades learning for proof. It trades mechanism for story. It calls the trade responsible. Then it acts surprised when the outcomes keep repeating.

The only question that survives the next decade

There is a reason manufacturing leadership is being tested in a new way. Variability is rising. Supply networks are less predictable. Labor is less stable. Customers tolerate less drift. Technology compresses information lag and raises expectations for action. In that environment, the old leadership style fails quietly. It can keep a plant running. It cannot keep a business ahead. The leaders caught in the detail trap do not fail because they do not care. They fail because they have been trained to think inside procedures, not inside systems. They have been trained to answer questions, not to redesign conditions. They have been trained to produce diligence, not to produce proof of control. The most corrosive effect is what it does to the next layer. High performers learn that the path to safety is to become a master of detail and a master of narrative. They learn to stay out of mechanism because mechanism creates consequences. They learn to avoid ownership of control surfaces. They learn that asking for examples is a socially acceptable way to keep a conversation from landing on causality. That is how a firm reproduces the problem across generations. It becomes an institution of mitigation. There is a sentence that belongs as an internal oath for any executive team that wants to keep manufacturing as a source of advantage. Intent does not count. Systems produce outcomes. If the outcomes are repeating, the system is doing its job. It is doing the job you designed, or the job you tolerated.

Intent does not count. Systems produce outcomes

The consequence is not philosophical. It shows up in cost, delivery, safety, quality, and trust. It shows up in the exhaustion of frontline leaders who spend their days managing exceptions that could have been designed out. It shows up in the drift of an organization that mistakes an increase in meetings for an increase in control. It shows up in the quiet repricing of manufacturing firms that cannot convert insight into act at speed. The fix is not another pile of examples. The fix is a different standard of truth. A firm can keep asking for instances and remain trapped in stories. Or it can demand mechanisms, test them, and accept the career risk that comes with naming conditions as leadership owned. A company that cannot do that will still look competent. It will still have dashboards. It will still have audits. It will still have action trackers. It will still be busy. It will also keep paying the same bill. References This essay draws on the operating logic and it leans on the long running management argument that systems, not exhortations, explain recurring performance, as framed in W. Edwards Deming’s Out of the Crisis in 1986 and reinforced by the wider quality movement that treats variation as a design problem rather than a moral problem. The cognitive mechanics behind example addiction and story based closure track closely with Herbert Simon’s Administrative Behavior in 1947 and his later work on bounded rationality, where decision makers stop when a narrative feels “good enough” for the institution they live in. The way metrics convert from signal to negotiation surface follows the warning in Charles Goodhart’s 1975 paper on monetary targets and the later operational reading of that principle in performance management. The systems view that problems arrive as interacting messes rather than isolated tickets is grounded in Russell Ackoff’s work on management and systems design in the nineteen seventies, which helps explain why local excellence can coexist with global decay. The control side of the argument, that a system must match the variety of its environment and that friction can masquerade as control while reducing adaptability, traces to W. Ross Ashby’s An Introduction to Cybernetics in 1956. The section on smart people defending bad decisions is anchored in Richard Feynman’s mid seventies “Cargo Cult Science” warning about self deception and the way pride can protect error, which the Good.is summary helped surface for this piece, even as the primary ballast remains Feynman’s own insistence on testing what you want to believe. The learning claim, that organizations do not learn until their outputs change in kind, not only in explanation, sits inside the systems discipline popularized for executives in Peter Senge’s The Fifth Discipline in 1990. The causal spine, that explanation is not intervention and that a firm must distinguish observation from actuation, rests on Judea Pearl’s Causality, first published in 2000 and expanded in later editions. Finally, the manufacturing specific motifs and house language, including decision delay, negotiation surfaces, and outcome shaping standards, are consistent with Michael Carroll’s own work in The Latency Tax, The One Degree World, and

Permission is a Decision, which treat the gap between signal and action as an earnings relevant design choice, not an unfortunate habit.