What Business Can Learn from a Well-Designed Cockpit
This is the third post in the dashboard-and-design block. The first two were about specific tools — the weekly financial dashboard, the fleet renewal NPV. This one steps back and asks a broader question: what design principles, taken for granted in a modern cockpit, would make most small businesses dramatically better at making decisions?
I’m a flight instructor, and dashboards aren’t a casual analogy for me. The instrument panel a student first encounters in training is the result of about eight decades of human-factors research, accident analysis, regulatory iteration, and design discipline. The fact that a 1956 instrument layout is still recognisable in a 2024 glass cockpit isn’t laziness — it’s the result of a slow, hard-won process of figuring out what works for a human under workload and stress.
Most small business owners, including most aviation business owners, have never thought about their decision environment with the same seriousness. The desks they work at, the dashboards they look at, the meetings they run, the alerts they get on their phones — none of it has been designed. It has accumulated. And the consequences show up everywhere: missed signals, fatigue, decisions made under unnecessary cognitive load, important things drowned out by noise.
This post is about borrowing some of that cockpit discipline.
The standard six-pack and the principle of layout
Open any general aviation training aircraft built between roughly 1960 and 2010 and you’ll see the same six instruments in the same six places: airspeed top-left, attitude top-centre, altitude top-right, turn coordinator bottom-left, heading bottom-centre, vertical speed bottom-right. This is the “six-pack” layout, sometimes called the basic-T scan.
The placement is not arbitrary. The top row contains the instruments needed for primary flight control — the immediate, second-by-second variables. The bottom row contains the secondary instruments that confirm or refine what the top row says. The eye learns to scan in a predictable T pattern, and after a few hundred hours of training the scan becomes automatic. A pilot under workload doesn’t decide where to look — they look where they’re trained to look, and the information is there.
The lesson for business is direct: the most important information should be in the most prominent place, and that placement should be stable over time. Most small business owners have a dashboard somewhere with thirty rows where the cash balance is in row 17 and the receivables aging is in row 24. By any standard of cockpit design, that’s broken. The two or three numbers that matter most should be where the eye lands first, every time, without searching.
In last week’s piece on financial dashboards I argued for six numbers. Notice the number — it’s not a coincidence. Six is approximately the number of distinct data points a human can scan reliably without losing context. Pilots learned this lesson over decades. Business owners can borrow the answer.
Alerting hierarchies and the cost of false alarms
A modern cockpit has roughly three categories of alert: caution (yellow), warning (red), and advisory (white or cyan). Each category has a calibrated visual treatment, a calibrated audio signature, and a calibrated severity threshold. Crucially, the design constrains what gets to use each category. You can’t just promote any alert to red; the system has been engineered so red is genuinely rare and genuinely demands attention.
Compare that to the alerting environment of a typical small business owner. Every notification on the phone, every email marked “high priority”, every Slack ping, every “URGENT” subject line claims the same level of urgency. The result is alert fatigue — the cognitive equivalent of a smoke detector going off during dinner three times a week, until you stop responding to it.
The cockpit principle is severe and useful: most things should not be alerts at all, most alerts should be advisories, and warnings should be vanishingly rare. Applied to a small business, this means almost nothing should generate an immediate notification. A weekly review handles 90% of operational data. A daily check handles 8%. The remaining 2% — actual cash failures, safety events, contractual breaches — gets the equivalent of a red warning. Everything else is, by design, quieter than the noise floor.
Most owners I’ve worked with run with the inverse calibration: everything is urgent, so nothing is. The fix isn’t a better notification app. The fix is to demote 95% of what currently generates alerts to “review at the next scheduled time” and to mean it.
The checklist as cognitive prosthetic
The checklist is the most exported and least understood cockpit invention. Most people, if they think about checklists at all, imagine a tedious bureaucratic ritual. Pilots understand them differently: a checklist is a prosthetic for finite working memory. You use a checklist not because the items are hard, but because under workload — fatigue, distraction, time pressure — the items will be skipped without one.
The same pilot who can recite the cruise checklist verbatim still uses the checklist. The point is not to remember the items; the point is to externalise the act of remembering, so that the cognitive bandwidth is available for the things that genuinely require judgement.
Small business owners almost universally underuse checklists. The owner who personally interviews every new hire has a checklist in their head that gets executed inconsistently because they’re tired, distracted, or running late. The owner who reviews the management accounts at month-end has a checklist in their head that misses the same line items every quarter. The owner who handles AR each week skips the awkward conversations because they were already mentally moved to next week.
Each of these would benefit enormously from a written, visible, run-every-time checklist. Not because the items are complicated. Because cognitive bandwidth under workload is finite, and the checklist is the technology that makes that finiteness manageable.
A flight school owner I worked with had been losing roughly 2,000 € per quarter in slipped invoicing — small line items, training extras, fuel surcharges, the kind of thing that drops between calendar boxes when nobody is specifically looking for them. The fix wasn’t software. The fix was a one-page Friday checklist with eight items, run every Friday at 17:00, no exceptions. Within two months the slippage was effectively zero. The owner used to pride herself on remembering everything; the checklist was the admission that no human reliably remembers everything, and that the alternative is a steady trickle of unbilled work.
The sterile cockpit rule and protected time
Below 10,000 feet, in commercial aviation, a rule called sterile cockpit applies: no non-essential conversation, no non-essential activity, focus exclusively on flying the aircraft. The rule exists because a study of incidents found a strong correlation between non-essential cockpit activity in critical phases of flight and accidents. The fix wasn’t training pilots to be more disciplined; the fix was a structural rule that made it socially and procedurally easier to focus.
The business analogue: most owners do critical work without protected time and don’t notice the cost. Strategic planning happens in the gaps between meetings. Pricing decisions are made while half-watching email. Hiring evaluations happen during phone calls. The cost is not catastrophic on any single occasion, but it accumulates into a pattern of consistently lower-quality decisions on the most important things.
The sterile-cockpit equivalent is simple to define and hard to enforce: a defined window each week or each month — phone off, door closed, no email, no Slack — for the work that genuinely requires uninterrupted thought. Three hours a week is enough for most small businesses. The structural barrier matters more than the duration. A scheduled, named, defended block of time is qualitatively different from “I’ll find time later”.
Redundancy that’s actually redundant
A well-designed aircraft has multiple independent systems for everything that can fail in flight: dual electrical systems, dual fuel pumps, redundant flight controls, multiple radios. The point is that no single failure should ground the aircraft. Crucially, the redundancy is independent — both pumps don’t share the same wiring, both radios don’t share the same antenna. Pseudo-redundancy that has a common failure point is not redundancy at all.
Small businesses are routinely structured with pseudo-redundancy. The owner thinks they have backup because both their finance person and their operations person can do basic accounting — but if both are out the same week, neither covers. The owner thinks the schedule is robust because two instructors can teach the syllabus — but both instructors get sick in the same flu cycle. The owner thinks the customer relationships are diversified because they have ten clients — but eight of them work for the same parent company.
True redundancy is independent. It survives the most plausible joint failures. It costs more than pseudo-redundancy, which is why pseudo-redundancy gets chosen by default. Cockpit design assumes the cheap version is unsafe; small business design rarely makes the same assumption.
A practical exercise I run with clients: list the things that would shut your operation down for a week if they failed, and for each one ask “what’s the redundancy, and is it actually independent?”. The list of items where the answer is “we don’t really have redundancy” is usually longer than the owner expects.
CRM and the architecture of speaking up
Until the late 1970s, commercial aviation accidents had a recurring pattern: the captain made a wrong decision, the first officer noticed, but social and hierarchical dynamics prevented the first officer from speaking up effectively. The industry’s response was Crew Resource Management (CRM) — a body of training and procedure that explicitly engineered the team dynamics of the cockpit so that speaking up became normal, expected, and structurally easy.
CRM didn’t trust people to overcome social dynamics by willpower. It built the structural conditions that made the right behaviour the easy behaviour: standardised challenge phrases (“captain, I’m uncomfortable with this”), required briefings before critical phases, defined responsibility allocation. The result was one of the largest safety improvements in any industry’s history.
Most small businesses have no CRM equivalent. The owner makes decisions; the team executes. When the team disagrees, the disagreement either doesn’t happen or happens in a hallway after the meeting. The cost of this absent-CRM design is a steady stream of decisions that the team knew were wrong but didn’t have a structural pathway to challenge.
The fix doesn’t require a culture transformation. It requires structure: a standing agenda item where pre-decision concerns are surfaced, a written protocol that defines what challenge looks like, a manager habit of asking “what am I missing?” and meaning it. Small things. They work because they’re structural, not because anyone is being asked to be braver than human nature usually allows.
Fatigue and the design of effort over time
The other thing aviation has spent decades figuring out is the management of fatigue. Duty time limits, rest minima, circadian-aware scheduling, the recognition that decision quality degrades dramatically with hours worked and that the degradation is invisible to the person experiencing it. Pilots are constrained by regulation in ways that prevent them from being unsafe even when they themselves judge they’re fine.
Small business owners are usually the inverse: they work until they’re exhausted, judge themselves to be still effective, and the people around them — staff, family, advisors — are not structurally empowered to push back. The owner who is making strategic decisions at 22:00 on Friday after a fourteen-hour day is making them at meaningfully lower quality than the same owner at 09:00 on Tuesday. Both pieces of work feel about the same to the owner. They are not the same.
The cockpit-derived principle: important decisions should be scheduled during high-quality decision windows, not assigned to whatever time happens to be free. The fleet decision we discussed last week is a Tuesday-morning decision. The pricing review is a Tuesday-morning decision. The hiring evaluation is a Tuesday-morning decision. Friday-evening decisions get downgraded to operational items that any human in any state can handle reasonably.
What this all adds up to
A cockpit is not a tribute to the pilot. It is a working environment designed to make good decisions easier and bad decisions harder. The instrument layout, the alerting hierarchy, the checklists, the sterile-cockpit rule, the redundancy, the CRM, the fatigue protocols — none of them assumes the pilot is unusually capable. They assume the opposite: that the pilot is a normal human under workload, and that the design needs to make the right behaviour the path of least resistance.
Most small business design assumes the inverse — that the owner is unusually capable, and that the environment can be sloppy because the owner will compensate. This works, badly, in good times and breaks visibly in bad times. The cockpit principle is more honest: design for a tired, distracted, normal human, and the operation runs reliably regardless of what kind of day the owner is having.
For aviation businesses specifically, this is doubly applicable. Owner-operators of ATOs, aeroclubs, and aircraft operators tend to come from a flying background, where they were trained in cockpit discipline. The transfer to business design is not automatic but it should be — the ideas are already in the head, just compartmentalised under “flying” rather than “working”.
A few small experiments
If any of this resonates, here are a few low-cost experiments to try in the next month:
A six-number dashboard, posted physically. Not a spreadsheet open on a screen. Six numbers, printed, on a wall in your office, refreshed every Monday. Notice over a month how often you actually look at it and whether decisions start flowing from it.
A Friday checklist. Eight items, written out, run every Friday afternoon. The items should be the things you currently rely on memory for and that occasionally slip. Track for a month whether anything that used to slip stops slipping.
A protected three-hour block. Same time each week. Phone off, door closed. Use it for the strategic work that currently happens in fragments. Notice over six weeks whether the strategic work starts moving forward at a different rate.
A “what am I missing?” question, asked deliberately. At every meaningful decision meeting, before closing, ask the team explicitly. Mean it. Wait long enough for someone to actually answer. The first three weeks will feel awkward; by week four it will be the most useful question on your agenda.
None of these are expensive. None of them require new technology. All of them are taken-for-granted in cockpit design and routinely absent in small business design.
Looking forward
Next week’s piece is the natural sibling of this one: why pilots underuse their technical knowledge when starting a business. Many pilots become aviation business owners and then quietly stop using the operational discipline they were trained in, treating “running a business” as a different domain. It isn’t. The skills transfer; the framing has to.
After that, we close the June block with a piece on economies of scale lessons from low-cost airlines.
Cockpit design is a discipline because aviation eventually decided it had to be. The accidents that drove the discipline were public, expensive, and sometimes catastrophic. Small business doesn’t have the same forcing function — businesses fail privately, slowly, and rarely with a clear single cause — so the design pressure never builds up the same way. As a result most small businesses are run on improvisation and willpower, with predictable consequences.
The good news is that the design principles transfer cleanly. Small businesses don’t need to invent them; they just need to borrow them, with the same seriousness pilots take for granted.
At AYRAM we work with aviation owners on operational design as part of broader strategic engagements — not selling templates, not licensing software, just helping owners apply to their business the kind of discipline they apply to their flying without thinking about it. As independent buy-side advisors, we have no transactional incentive to make any of this more complicated than it is. The principles really are this simple. The discipline of applying them is what’s hard.
If your operation feels like it depends on you holding it together by force of will, the cockpit conversation is one worth having. We’d be glad to be in it with you.