The Value That Disappears Between Decisions Rev

This is not a story about poor strategy or lazy execution. It is a story about how value escapes inside firms that are busy, staffed, and in motion. The prevailing belief is that if outcomes look acceptable, the system is acceptable, and any roughness can be smoothed with better reporting, tighter metrics, and more disciplined follow through. What would have to be true for this outcome to keep repeating. LNS Research called the pattern the Four Horsemen of the Enterprise Apocalypse. Fragmentation. Decision latency. Complexity. Value leakage. Most enterprises try to kill the fourth horseman because it is the one that shows up on the income statement. The mistake is thinking the fourth is the problem. The fourth is the consequence. The first three are the architecture, and architecture does not feel like a crisis until the day it does. The quarter closes. The leak stays open. Value Leakage is the systematic loss of economic value inside an enterprise despite stable or growing activity, caused by structural frictions that prevent intent, decisions, and execution from converting cleanly into outcomes. That definition sounds abstract until you translate it into the only language the enterprise speaks fluently. Work is happening. Money is not converting the way it should. The gap between effort and outcome is not a morale issue. It is a conversion failure. There is a reason value leakage is hard to name. Traditional financial metrics measure outcomes. Value leakage lives between decisions and outcomes. The leak is a space, not a number. It sits in the handoffs that never make the agenda because they look like coordination, not waste. It sits in the approvals that feel responsible until you measure what time does to cost, margin, and risk. Boards and CFOs are trained to trust lagging indicators because lagging indicators are audited, standardized, and comparable. That training becomes a trap when the enterprise’s real loss mechanism is not a bad outcome but a delayed intervention. By the time leakage appears inside EBITDA or ROIC, it has already been normalized. It has been absorbed into “how we do things.” It is now embedded in staffing models, freight lanes, buffer inventories, contractor spend, discounting behavior, and the silent bargain people make with a broken system. We will carry it this quarter, because fixing it will take longer than surviving it.

The first horseman. Fragmentation. The white rider of false conquest

The first horseman is fragmentation. The enterprise breaks into disconnected parts. This is not merely org chart separation. It is separation of incentives, separation of data, separation of authority, and separation of consequence. Fragmentation creates the illusion that local excellence adds up to system excellence. It does not. It creates the condition where nobody can see the whole, and nobody has the right to change the whole even if they do. Revelation’s first rider comes on a white horse and looks like conquest. He carries a bow and receives a crown. The symbolism is unsettling because it does not look like collapse. It looks like winning. That is the enterprise version of fragmentation. Fragmentation often arrives dressed as

professionalism. Specialization. Centers of excellence. Functional mastery. Scorecards that reward local performance. It feels like a crown. It feels like control. It feels like progress. Fragmentation is not a culture problem. It is an operating geometry. Enterprises treat fragmentation as a social failure because social failures are safer to discuss than structural failures. Leaders talk about alignment, collaboration, and breaking down silos. They schedule offsites. They launch cross functional councils. They add integrator roles. These actions can help at the margins. They also often make the problem worse by adding another layer of coordination without changing the underlying decision rights that created the fragmentation. Fragmentation becomes lethal when it intersects with value creation pathways. In most firms, value is not created inside a single function. Value is created when demand signals, production decisions, procurement commitments, pricing actions, quality controls, and delivery behavior cohere quickly enough to meet reality. Fragmentation breaks coherence. It replaces coherence with negotiation. Negotiation requires permission. Permission requires time. Time is where value starts leaking. The hard truth is that fragmentation can exist in firms that still win for a while. Market power can mask it. Commodity cycles can mask it. A strong product can mask it. Cheap capital can mask it. That masking effect is the comfort that keeps leaders chasing the fourth horseman. If we just protect margin. If we just squeeze cost. If we just run the plant harder. If we just add analytics. The firm can limp along. The bill still grows. A fragmented enterprise creates local decision making that is rational in isolation and destructive in aggregate. A sales team discounts to hit a volume target. Operations runs overtime to ship the discounted volume. Procurement buys ahead to protect service levels. Finance delays capex to protect cash. Quality adds inspection gates to prevent defects from escaping. Each decision is defensible. Together, they create a system that works harder to achieve less. That is not a character flaw. It is geometry. When leaders talk about “execution,” they often mean compliance with the plan. Fragmentation guarantees the plan will be negotiated in real time, because the plan cannot survive the first collision between a local goal and a system constraint. That negotiation becomes a hidden factory. It consumes time. It consumes attention. It consumes trust. It also produces artifacts that look like control. More meetings. More escalations. More dashboards. More “alignment.” Less conversion. Value leakage lives between decisions and outcomes. In a fragmented system, that space widens because decisions are no longer clean acts. They become multi party transactions. Every transaction has a cost. That cost is not just labor. It is delay. It is dilution of accountability. It is the slow erosion of the enterprise’s ability to act on purpose.

The second horseman. Decision latency. The red rider of internal war

The second horseman is decision latency. The enterprise slows at the exact moment speed becomes the difference between recovery and loss. Decision latency is not the time it takes to decide in theory. It is the time between a signal that something is changing and an authorized action that changes the outcome. Enterprises almost never measure this because it indicts governance. They measure cycle times, close times, lead times, and project timelines. They do not measure permission time, because permission time is where the firm admits it cannot control itself. In Revelation the second rider is red, and he is given power to take peace from the earth. That is the enterprise’s internal version of war. Not always loud conflict, but chronic contest. Every decision becomes a negotiation between functions. Every signal becomes a debate about ownership. Every intervention becomes a question of who gets blamed if it is wrong. Latency is what war looks like inside a governance system that cannot decide cleanly. Latency is what permission costs. Decision latency is often treated like an annoyance. It is discussed as a leadership style problem. Leaders are told to “move faster.” Teams are told to “empower the edge.” Those phrases sound good because they imply agency. They avoid the question of who holds authority and why. Latency is not a mood. It is an architectural property. If a decision requires five approvals, it will not be fast in the only moments that matter. If a decision is gated by a weekly meeting, it will not respond to daily drift. If a decision is pushed into a committee because nobody wants to own it, the enterprise will pay for that avoidance through time. Firms that treat time as free are always surprised when time sends an invoice. There is a subtle way decision latency hides. Leaders equate carefulness with prudence. They equate more review with less risk. They equate escalation with responsibility. That framing holds until you ask what risk actually is. Risk is the probability of harm multiplied by exposure. Exposure is a function of time. If latency increases exposure, then latency is not risk control. It is risk creation. This is where many transformation efforts go wrong. They see the symptoms of leakage and respond by adding controls. New approval steps. New stage gates. New compliance checks. New dashboards to prove diligence. Each addition is justified. Each addition also adds permission time. The firm becomes slower. The firm becomes more complex. The firm leaks more value. Leaders then conclude that people are resistant or that culture is weak, when the real culprit is that they tried to fix conversion failure by increasing transaction cost. Value leakage lives between decisions and outcomes. The space widens when permission replaces action. The enterprise can be full of smart people and still be unable to intervene fast enough to change the next outcome. That is the definition of controllability failure. It is not a performance problem. It is a controllability problem. Here is a diagnostic that can be read aloud in an ELT meeting without turning into theater. When a frontline signal says demand is shifting, quality is drifting, supply is tightening, or a customer

is at risk, who has the right to act. Not who can propose. Who can act. How long does it take from signal to authorized intervention. Not from problem to meeting. From signal to intervention. What gets approved quickly, and what gets routed into a cadence that has nothing to do with the cadence of the market. If nobody can answer those questions without guessing, the enterprise is not governed. It is stalled. Another diagnostic is even more uncomfortable because it touches the sacred metrics. What decisions drive the firm’s margin more than any cost program does. Pricing actions. Mix decisions. Capacity allocations. Supplier commitments. Customer service tradeoffs. Who owns those decisions. Can they be made without convening a cross functional audience. When the firm misses, can you trace the miss to a delayed decision and name the permission path that caused the delay. If the answer is “it depends” in every case, the firm has built a system where accountability is distributed so widely that nobody can correct drift in time.

The third horseman. Complexity. The black rider of famine

The third horseman is complexity. Complexity is what you get when interactions become opaque and nonlinear. Small errors do not stay small. They propagate through queues, dependencies, and coupled systems. They turn into second order costs that nobody owns because nobody caused them alone. Complexity is not the same as sophistication. It is not an achievement. It is the bill that shows up when fragmentation and latency are allowed to compound. Revelation’s third rider is black and carries scales. The imagery is famine. Rationing. Measures. Scarcity. The enterprise version is not always empty shelves. It is empty capacity to think. Empty attention. Empty slack. Leaders begin to weigh every choice because every choice creates consequences they cannot predict, and every consequence produces new approvals, new escalations, new workarounds. Complexity turns the organization into a rationing machine. Not because people are weak, but because the system consumes the very bandwidth required to run it. Complexity is what you get when you pay for time twice. Complexity is not just many moving parts. It is the condition where the behavior of the system cannot be inferred from the behavior of its parts. In enterprises, this shows up when a change in one area produces unpredictable effects elsewhere. A new policy fixes one risk and creates another. A cost cut in one department produces a service failure in another. A new software workflow reduces errors in one step and increases workarounds in three others. The enterprise often responds to complexity the way people respond to fog. They slow down, they add caution, they add checks. That response is understandable. It is also a trap. In a complex system, slowing down does not reduce uncertainty. It often increases uncertainty because the environment keeps moving while the firm holds still. Complexity also has a moral hazard. When outcomes become the product of many interacting causes, individuals can claim innocence. Nobody did it. The system did it. That sentence is true.

It is also a surrender. Firms that accept complexity as fate become firms that can be outmaneuvered by anyone who can see clearer and act faster. This is where the first three horsemen tighten into a single mechanism. Fragmentation makes decisions multi-party. Decision latency stretches the time between signal and action. Complexity ensures that the costs of delay are not linear. The firm now faces a world where small errors can escalate while permission is still being negotiated. When leaders finally act, they are acting on a world that has already changed. They then invest in prediction, because prediction feels like control, while the real need is faster correction of drift. Value leakage lives between decisions and outcomes. Complexity enlarges that space because it multiplies the number of points where a small delay can become a large cost. Rework is the obvious cost. Expediting is the obvious cost. The more damaging cost is opportunity loss that never gets recorded. A competitor secures a supplier slot because they committed faster. A customer defect becomes a contract loss because the firm needed three reviews to authorize a corrective action. A pricing window closes because the firm required consensus to move, and consensus arrives after the window is gone. It is tempting to treat those examples as anecdotes. They are not. They are the predictable behavior of systems with high transaction cost, slow permission paths, and opaque interactions. If you want a falsifiable prediction that should sting if it is wrong, run this test. Pick a material margin event that surprised leadership in the last year. Trace backward from the outcome to the earliest signal that existed inside the enterprise. Then measure the time between that signal and the first authorized intervention that could have changed the outcome. If that time is set by meeting cadence rather than signal cadence, the system is paying an avoidable tax. If it happens once, it is a miss. If it happens repeatedly, it is architecture.

Then the fourth arrives. Value leakage. The pale rider of death

Then the fourth arrives, without drama. Value leakage. Margin erosion despite revenue growth. Cost creep without clear ownership. Missed opportunities that do not look like missed opportunities, because nobody can prove a counterfactual on the quarterly call. A company can look healthy while it bleeds. That is what makes leakage so dangerous. The enterprise can be busy for years while its ability to convert intent into outcome quietly decays. Revelation’s fourth horse is pale, and its rider is named Death. The text is blunt about what follows. It is not a single strike. It is a sweeping consequence. That is the enterprise’s most uncomfortable truth. Leakage is not “one more initiative” away from being solved if the first three remain intact. Leakage is what the system produces once fragmentation, latency, and complexity have built a permanent gap between intention and intervention. Death in business rarely looks like a cliff. It looks like conversion decay that leadership explains away as “the cost of doing business,” until the market stops forgiving it.

Why attacking leakage makes the leak worse

Most enterprises fight value leakage the way they fight a visible wound. They apply pressure. They squeeze costs. They demand accountability. They launch margin programs. These efforts can produce short-term improvement. They often do. The danger is that they do not address the mechanism that created the leakage. They often reinforce it. Cost programs tend to centralize authority because leaders want control over spending. Centralization increases permission time. It turns local tradeoffs into escalations. It slows the firm in moments that require speed. The firm then expends more effort to hit the same outcomes. People become more heroic. The company becomes more dependent on heroics. Leakage becomes the permanent background condition that leaders treat as “the cost of doing business.” Dashboards and analytics can create the same problem when they are treated as substitutes for decision rights. Better visibility does not create controllability. Visibility can even increase paralysis if it adds noise without changing who can act. A firm can know more and control less. That is not a technology failure. It is an operating design failure. Governance reforms can also backfire. A well-intentioned governance model that adds review for every material decision will reduce variance in the decisions that make it through. It will also reduce the number of timely decisions that make it through. In markets that punish delay, that tradeoff is not neutral. It is a slow transfer of advantage to competitors. There is a strong counterargument that deserves respect. Some enterprises operate in stable environments where delay does not immediately translate into loss. In those contexts, heavy governance can prevent reckless actions and protect against idiosyncratic risks. It can keep the enterprise from chasing every signal. That is real. The point is not that speed is always good. The point is that unmeasured latency is always costly because it is unmanaged exposure. In stable environments, the cost is hidden. When volatility rises, the cost becomes visible. Enterprises do not get to choose when volatility arrives. The first three horsemen do not announce themselves as existential threats. They present as professionalism. Fragmentation presents as specialization. Decision latency presents as diligence. Complexity presents as sophistication. That is why leadership teams can be filled with competent, serious people and still walk into the same quarter end sentence. We hit the numbers, but it felt harder than it should have. That sentence is not a complaint. It is a signal that the enterprise is losing controllability. LNS Research’s framing is useful because it refuses to treat leakage as a finance problem and refuses to treat fragmentation, latency, and complexity as soft issues. It ties them into a causal chain with an economic consequence. Fragmentation breaks conversion. Latency increases exposure. Complexity amplifies errors. Leakage is the economic bleed that results. The board level error is thinking the only thing that matters is the fourth horseman because it is the only one that is easy to measure. The operator level error is thinking the fix is more effort. More effort can cover leakage for a while. It cannot remove it. The firm is still paying for time. It is still negotiating permission. It is still adding interactions that nobody can fully see.

Value leakage lives between decisions and outcomes. If the enterprise wants to find it, it must look where financial statements do not look. It must look at how intent turns into permission. It must look at how permission turns into action. It must look at how action turns into outcome. That is not a slogan. It is a tracing exercise. If the trace ends at “we could not get the decision fast enough,” the firm has found the leak. A final question closes the loop without offering comfort. If fragmentation, latency, and complexity are left intact, what happens when the enterprise faces a competitor who can correct drift faster than you can approve a response. That competitor does not need to be smarter. They need to be able to convert intent into action without paying your transaction tax. In that contest, the fourth horseman is not a threat. It is the only possible outcome. Leakage is the invoice for latency. References This argument rests on well-established work about transaction costs, coordination, bounded rationality, complexity, timing, and control. Coase’s “The Nature of the Firm” in 1937 explains why internal coordination has costs that can rival market exchange, which is the foundation for treating fragmentation and permission paths as economic forces, not culture talk. Galbraith’s Designing Complex Organizations in 1973 frames organizations as information processing systems, which clarifies why fragmentation and slow decision rights fail under uncertainty. Malone and Crowston’s survey of coordination theory in 1994 formalizes coordination as a measurable problem, not a motivational one. Simon’s “A Behavioral Model of Rational Choice” in 1955 anchors the realism that leaders face cognitive and time limits, which is why more data without decision rights often produces slower action, not better action. Perrow’s Normal Accidents in 1984 explains why tightly coupled complexity produces failures that are hard to predict and easy to amplify, which supports treating enterprise complexity as a non linear cost multiplier. Reinertsen’s The Principles of Product Development Flow in 2009 links queues and delay to economic loss through the cost of delay concept, which is the cleanest bridge from latency to money without relying on slogans. Dixit and Pindyck’s Investment Under Uncertainty in 1994 grounds the option value of waiting and acting under uncertainty, which is the proper finance lens for why timing and delay change expected value, not just feelings. Tett’s The Silo Effect in 2015 documents how silo behavior persists even in competent institutions, reinforcing that fragmentation is durable and often invisible to standard reporting. Muller’s The Tyranny of Metrics in 2018 supports the claim that measurement regimes can distort behavior and create control illusions, which is why attacking leakage through metrics alone can worsen the first three horsemen. Wiener’s Cybernetics in 1948 provides the original discipline language of control and feedback, which is why controllability is the correct noun for the enterprise problem being described. Pearl’s Causality in its 2009 second edition underpins the causal model stance that value leakage must be traced through interventions and counterfactuals, not correlations in lagging outcomes. Goodhart’s 1975 observation, now known as Goodhart’s Law, explains why turning outcome measures into targets can degrade the system that produces them, a risk that rises as firms chase the fourth horseman while leaving the first three intact.