You’ve made the investments. The platforms, the teams, the roadmaps. And you’re still explaining to the board why the data doesn’t tell a clean story. I get it. I’ve been there.
What this is
One pattern each week from twenty years inside airline data work—what’s broken, why the system keeps producing it and what fixed looks like. Plus a couple of sharp takes on what’s moving in the industry and a short note on what I’m building.
Every Sunday. About five minutes. No spam. No pitching. Just what I see working.
Recent issues
The System Design Pattern
No tool migration. No tech modernization. No platform fixes the flaw.
Read the issue →
Every issue ends the same way
Patterns are only useful if they change what you do Monday. So every issue closes with one box—what this means for the people building the data, the people leading the team and the executive funding the next investment.
What this means Monday morning
If you’re building the data: ask whether you know what business questions your work is answering—not what’s in the Jira ticket, but the actual decision someone is trying to make. If you don’t know, ask. Get in the room with someone who knows. You can’t validate your work unless you do.
If you’re leading a data team: ask how your team’s success is measured. If the metrics are all about delivery—on time, tickets closed—and none are the same as the business you’re supporting, you’ve found a system design flaw.
If you’re the executive funding the next investment: ask your data team and your business team the same question separately: “What’s our definition of revenue?” If you get different answers, you’ve just diagnosed the problem and buying that tech won’t fix it.
What will? A room with the right people and the right conversation.
From Issue 1. There’s one of these every week.
Read by commercial, technology and data leaders at airlines and the companies that serve them.
The next issue goes out Sunday.