In maintenance and defense aviation, speed is a number everyone tracks — turn-time, RFI response, time-to-return-to-service. Trust rarely shows up on the same dashboard. It should. Trust is not a culture nicety sitting alongside the real metrics; it is one of the biggest levers on the metrics themselves. Where trust is high, information moves without being checked twice, decisions get made at the level closest to the work, and problems surface early instead of hiding until they’re expensive. Where trust is low, every one of those steps gets a toll booth.
The trust tax and the trust dividend
Stephen M.R. Covey's research popularized the framework that best captures this: trust always moves two numbers — speed and cost — and it moves them in opposite directions from what people assume. Low trust adds approval layers, redundant sign-offs, and CYA documentation; it slows everything down and raises cost. High trust removes friction; it speeds things up and lowers cost.1 Organizations that operate with a demonstrated trust deficit have been shown to underperform high-trust peers by a wide margin on Total Return to Shareholders, and a Warwick Business School study of partnering relationships found that high-trust partnerships captured a dividend worth up to 40% of contract value — value that low-trust relationships spend on oversight instead.1 None of that is abstract for an MRO or a defense contractor: every layer of re-verification between the hangar floor and the customer is the trust tax, itemized.
What high trust actually buys you
Neuroeconomist Paul J. Zak spent two decades measuring what happens inside organizations where trust is genuinely high, using both survey data and biometrics tied to oxytocin response. The differences are not marginal. Compared with people at low-trust companies, people at high-trust companies report 50% higher productivity, 76% more engagement, 40% less burnout, 13% fewer sick days, and 74% less workplace stress.2 Every one of those numbers converts directly into operational performance: fewer errors from fatigue and disengagement, less absenteeism disrupting shift coverage, and people who stay rather than walk out the door with the institutional knowledge that took years to build.
Psychological safety and decision speed
Google's multi-year Project Aristotle study set out to find what separated its highest-performing teams from the rest. After examining 250 attributes across 180 teams, the single strongest predictor wasn’t who was on the team — it was whether team members felt safe speaking up, disagreeing, and admitting a mistake without fear of punishment.3 That is trust operating at the speed of a conversation. On a shop floor or a program team, psychological safety is the difference between a technician flagging a near-miss the moment they see it and that same near-miss surfacing three shifts later as a finding. It is the difference between a young engineer challenging a senior one before a design flaw ships and staying quiet until it’s a field issue.
Trust doesn’t just make an organization more pleasant to work in — it makes it faster and cheaper to run.
The market rewards it too
This isn’t only an internal story. Great Place to Work's long-running analysis of the Fortune 100 Best Companies to Work For shows those companies delivering annualized stock returns of roughly 13.4% over 28 years, against 9.2% for the Russell 3000 — a margin that compounds into nearly three times the return over time — and earning 8.5 times more revenue per employee than the broader public market.4 Investors and customers pick up on high-trust operations even when they can’t name why. In a sector where a customer’s decision to award a contract often rests on confidence in leadership as much as capability, that matters directly.
What this looks like in an MRO
Picture a mid-size MRO facility, three years past an ownership change, still running on the old leadership team’s habits. The new VP of Operations inherited a culture where every deviation went up the chain for sign-off before work continued — a habit built after a costly quality escape under the previous ownership had made everyone gun-shy. Turn-times had crept up 18% over two years. Shop leads privately knew where the bottlenecks were but had stopped raising them; the last person who flagged a scheduling problem got told to fix it himself and got no support doing it.
The fix wasn’t a new process. It was leadership behavior: the VP began closing the loop publicly on every issue a shop lead raised, whether or not the news was good, and pushed sign-off authority for routine deviations back down to the crew chiefs who actually understood the work. Within two quarters, near-miss reporting had roughly doubled — a leading indicator that people trusted the system enough to use it — and turn-time on standard checks had come back down past where it started, because fewer items were waiting in an approval queue for someone above the floor to have time to look at them. Nothing about the technical work changed. What changed was how fast decisions could move once people trusted that raising a problem wouldn’t cost them.
Building the dividend, not the tax
Covey’s work identifies four consistent drivers of trust in a leader: integrity, intent, capability, and results — do what you say, want good outcomes for others and not just yourself, be competent, and deliver.1 None of that is complicated to describe. It is difficult to sustain under pressure, which is exactly when it matters most and exactly where coaching earns its keep — building the habits that hold up when a program is behind schedule or a quality issue is unresolved, not just when things are calm.
For leaders in maintenance and defense aviation, the practical takeaway is this: every approval layer, every escalation, every meeting that exists to double-check someone’s work is a symptom worth diagnosing before it’s accepted as how things are done. Some of that structure is genuinely required by regulation and safety. A meaningful amount of it is trust debt, quietly slowing the organization down and taxing everyone who works in it.