I might drink this beer

Logo

I am a jack of some trades and definitely a master of none. That doesn't mean I haven't had some experience and a handful of opinions to go with it. All of the opinions expressed here are my own and do not reflect the views of my employer

@mjmengerGitHub

Encrypted chat via Keybase markjmenger

mstdn.socialmastodon

mastodon.f2a.iomastodon

pdx.socialmastodon

RSS

summer
sweet
devops
dark
year-round
big-ip
automation
hashicorp
terraform
winter
brewing
yeast
complexity
fragile2agile
technology
history
lean
modernization
evolutionary
revolutionary
innovation
strategy
security
agility
linguistics
ai
architecture

4 April 2026

The Wake and the Horizon

by Mark J Menger

The Wake and the Horizon

There is a particular kind of organizational failure that doesn’t look like failure until it’s too late to correct. The company is profitable. The quarterly reports are clean. The executives are confident. And then, somewhere between the boardroom and the customer, something has gone quietly, irreversibly wrong.

Boeing is the most documented example of our time.

For most of its history, Boeing was an engineering company in the deepest sense. Its identity was organized around the people who built things — the aeronautical engineers, the safety culture, the institutional pride that came from solving hard problems well. When Bill Boeing and his friend Conrad Westervelt took turns in a barnstormer’s seaplane at a 1914 Fourth of July fair on Seattle’s Lake Washington, both engineers, Boeing’s reaction was characteristically direct: “There isn’t much to that machine. I think we could build a better one.” That orientation — see a problem, solve it better — defined Boeing for decades.

What happened afterward is meticulously documented by Bloomberg investigative journalist Peter Robison in Flying Blind: The 737 MAX Tragedy and the Fall of Boeing (2021). His account, drawn from extensive interviews with current and former Boeing and FAA employees, describes how a company that had played a central role in commercial aviation, World War II bombing missions, and moon landings became, in his words, “obsessed with the bottom line, putting shareholders over customers, employees, and communities.” Robison identifies the inflection point as the 1997 merger with McDonnell Douglas — the moment when, as one observer described it, hunter-killer assassins met Boy Scouts. The Boy Scouts lost.

The 737 MAX crashes of 2018 and 2019 killed 346 people. The cause, in its final analysis, was a decision to software-patch a physical aerodynamics problem rather than redesign the aircraft or require pilot retraining — because redesign and retraining would have cost money and delayed delivery. The financial logic was internally consistent. The engineering logic was not. And the people making the financial decision were sufficiently removed from the engineering reality that they could not see the difference.


This is the pattern I want to examine in this series of articles. Not the dramatic failure — that is the endpoint, not the explanation. The explanation is subtler and more general.

Every organization navigates. And navigation requires a reference point. The question is: what reference point are you using?

A ship’s wake is real data. It records exactly where you have been, with precision and without ambiguity. A navigator who steered exclusively by the wake would know their history perfectly and their future not at all. By the time an obstacle forced attention to the forward view, the momentum of a large vessel would make correction nearly impossible.

Financial metrics — revenue, margin, earnings per share, return on capital — are organizational wake. They record, with precision and without ambiguity, what has already happened. They are the residue of value that was created, delivered, and captured in a prior period. They are real. They are useful. And they are entirely backward-facing.

The horizon — where you are actually going — is composed of different things. Customer trust. Product quality. The motivation of the people doing the work. Institutional knowledge. The capacity to adapt. These are harder to see clearly and impossible to reduce to a single number. But they are the only things that tell you what your organization will be capable of next quarter, next year, and in a decade.


Boeing’s engineers understood this distinction. For most of the company’s history, the people setting direction were close enough to the work — and to the consequences of the work — that the horizon was visible to them. When that changed, when financial orientation displaced engineering orientation at the top of the organization, the navigation instrument changed too. The wake became the reference point. And the rocks, when they appeared, were seen too late.

The question this raises is not unique to Boeing. It is structural. What are the conditions that cause an organization to mistake its wake for its heading? What mechanism converts a company that once built things well into one that manages metrics well while the underlying capability quietly erodes?

That is what I want to explore. Not as a polemic against business or profit — both are necessary — but as a precise diagnosis of a failure mode that is, I think, more common and more consequential than we usually acknowledge.


Next: What financial metrics actually measure — and what they don’t.


References

tags: innovation - history - technology - strategy