What Flight 401 Can Teach Us About Customer Health Scorecards

The crew of Eastern Air Lines Flight 401 had every instrument they needed. They flew a perfectly serviceable L-1011 TriStar into the Florida Everglades on a clear December night in 1972 because all three pilots spent the final minutes of their lives staring at a landing gear indicator light that wouldn't illuminate. A single burned-out bulb. Meanwhile, the altimeter — the instrument that tells you how far you are from the ground — went unwatched. One hundred and one people died.

NASA psychologist John Lauber studied that crash and others like it. Seven years later he coined "cockpit resource management" to describe the gap between having information available and being able to interpret it correctly under pressure. The problem wasn't the instruments. It wasn't pilot skill. It was attention allocation.

I've flown enough hours to know that the cockpit is the original dashboard. And if you want to understand what's broken about how most companies manage their customer portfolio, aviation is a remarkably good place to start.

The Six-Pack Principle

The basic flight panel — what pilots call the "six-pack" — contains exactly six instruments: attitude indicator, airspeed indicator, altimeter, turn coordinator, heading indicator, and vertical speed indicator. Six instruments to keep several hundred tonnes of metal in the air.

The number isn't accidental. It represents decades of design iteration to determine the minimum sufficient information a pilot needs for safe flight. Not the maximum available information. The minimum sufficient. Every instrument earns its place because removing it would create a dangerous gap. Nothing is there for decoration. Nothing is there because someone in procurement thought it might be useful.

Now consider the typical enterprise customer health scorecard. Eight to twenty metrics. Product adoption rates. License utilization. Support ticket volume. NPS scores. Executive sponsor engagement. Renewal probability. Expansion ARR. Login frequency. Feature depth. Stakeholder map completeness. The list grows every quarter because somebody in a QBR asked "what about this?" and nobody had the authority to say no.

The six-pack philosophy is the opposite of metric accumulation. It's metric curation. The attitude indicator sits center-top because it's the primary reference — the answer to "are we wings-level?" Everything else supports that question. Airspeed tells you if you have energy. Altimeter tells you if you have terrain clearance. Turn coordinator tells you if you're coordinated. Heading indicator tells you where you're pointed. Vertical speed tells you if you're climbing or descending.

Each instrument answers a specific operational question. Together they form a complete picture. Add a seventh and you don't get more safety — you get more scan time, which means less time on the primary reference.

Hub-and-Spoke vs. Dashboard Sprawl

The layout matters as much as the count. The six-pack arranges instruments to support what pilots call the hub-and-spoke scan: eyes return to the attitude indicator between every other reading. Attitude → airspeed → attitude → altimeter → attitude → heading → attitude. A continuous cycle. Pilots train this scan until it becomes automatic, because the moment you stop scanning systematically is the moment you start fixating.

Fixation is what killed Flight 401. The crew didn't ignore the altimeter because they didn't know it mattered. They ignored it because their attention collapsed onto a single anomalous input.

Customer success dashboards almost never enforce a scan pattern. They present grids. Tables. Heatmaps. Twenty metrics given equal visual weight, arranged alphabetically or by data source. The CSM opens the account page and sees… everything at once. No primary reference. No enforced return path. The eye wanders. The mind latches onto the red cell — the burned-out bulb — while the altimeter equivalent (usually "time since last value-delivery conversation" or "executive sponsor engagement trend") sits green and unwatched.

The hub-and-spoke discipline requires a designated primary metric. In customer health, that's almost always a value-realization indicator: "has this customer achieved their stated business outcome?" Everything else — adoption, NPS, stakeholder map — is a spoke. They matter only insofar as they explain or predict the hub.

Training the Scan

Airlines don't hand pilots a six-pack and wish them luck. They train the scan in simulators. They test it. They retrain it. The scan is a skill, not an intuition.

Most companies roll out a new health scorecard with a 30-minute enablement session and a Confluence page. They treat the dashboard as self-evident. It isn't. A scorecard is an interpretation framework disguised as a visualization. "Red means bad" is not a scan pattern. "Check value realization first, then check the two leading indicators that most predict its trajectory, then check the lagging indicator that confirms retention risk" — that's a scan pattern.

The best CS organizations I've seen treat scorecard literacy like instrument rating. They run calibration exercises: here are five accounts, score them independently, now compare. They audit scan compliance: when a CSM opens an account, what do they look at first? What do they look at second? Do they return to the hub? They fire CSMs who can't demonstrate the scan, same way airlines pull pilots who can't hold a scan under workload.

The Fixation Traps

Flight 401 teaches three fixation traps that map directly to customer health.

First, the anomaly trap. A burned-out bulb draws disproportionate attention because it's binary, visible, and wrong. In CS, this is the single red metric on an otherwise green account — the NPS score that dipped, the support ticket that aged. The CSM spends the QBR explaining the ticket. The renewal slips because nobody discussed the missing executive sponsor.

Second, the familiarity trap. The Flight 401 crew knew the landing gear system. They'd troubleshooted it before. They trusted their mental model of it more than the unfamiliar demand to monitor descent rate. In CS, teams fixate on product adoption metrics because they understand the product. They neglect commercial health metrics — procurement cycles, budget ownership, competitor engagement — because those live in a different mental model.

Third, the workload trap. The crew was busy. Configuring for approach. Talking to ATC. Running checklists. The scan requires cognitive bandwidth. When bandwidth compresses, the scan collapses to the loudest signal. CSMs running eight QBRs in a day with prep time measured in minutes don't have bandwidth for a disciplined scan. They have bandwidth for the red cell.

Building the Six-Pack

If you're redesigning a health scorecard, start by cutting. Ruthlessly. Identify the hub — the single metric that best answers "is this customer realizing value?" Everything else must earn its spoke position by demonstrating predictive power for the hub. Not correlation. Predictive power, validated on your cohort, in your motion.

Arrange the dashboard to enforce the scan. Hub center-top. Spokes in a ring. Visual hierarchy that makes the return path obvious. Disable sorting. Disable column reorder. The layout is not a preference.

Train the scan. Simulate. Calibrate. Audit. Make scorecard literacy a promotion criterion.

And accept that the six-pack leaves things out. No fuel quantity. No engine temperature. No hydraulic pressure. Those live on secondary panels, checked on different schedules, by different scans. Your scorecard is the primary panel. Build a secondary panel for the deep dive. But never, ever crowd the primary.

The crew of Flight 401 didn't die because they lacked data. They died because the system let them allocate attention to the wrong datum at the wrong moment. Your CSMs have every metric they need. The question is whether your scorecard design and your training regimen ensure they watch the altimeter when the ground is coming up fast.