Case Study
About
The situation
One of Panasonic Avionics’ flagship airline customers had a revenue problem. Passengers were successfully connecting to in-flight wifi — but instead of being routed through a captive portal, they were landing on dead-end error screens. The kind of redirect that every airport and coffee shop handles automatically wasn’t working at 35,000 feet. The airline was delivering connectivity they couldn’t monetize.
They brought the problem to me. I was embedded between Panasonic’s engineering organization and its major airline partners — responsible for the relationship and the outcomes, but with no formal authority over any of the teams building the product. That gap is where this kind of problem lives.
Scope
Problem
Revenue leak
Passengers connecting to in-flight wifi but landing on dead-end error screens — the airline was delivering connectivity it couldn’t monetize.
Constraint
No direct authority
Responsible for the relationship and the outcomes, but with no formal authority over any of the teams building the product.
Timeline
2 months to ship
From reframing the request to a platform feature shipped to production and adopted across major airlines.
Result
~30% revenue lift
Increase in both connectivity revenue and wifi adoption — adopted as default by major airlines across the platform.
My Approach
The path from a hard ‘no’ to a shipped platform feature.
Step 1
Finding the path
I started inside the organization. Through conversations across engineering, I found something useful: an engineer who had actually built a captive portal prototype years earlier that was quietly shelved. We pulled it back out, scoped the feasibility, and revised the requirements. Four days of work — two days of development, two days of testing — to field a fix that would directly address the revenue leak. I built the business case and brought it to software engineering leadership. The answer was no. I escalated — to my manager, then to the COO and CTO, who both agreed it was the right call and tried to push it through. The software engineering manager still wouldn’t move.
Located a shelved captive portal prototype built years earlier
Scoped feasibility: four days of work total
Escalated to COO and CTO — they agreed but still couldn’t force it through
Step 2
Changing the ask
At that point, the path forward wasn’t more pressure — it was a different question entirely. I sat back down with the CTO and head of product and reframed the problem. This wasn’t a custom fix for one airline. Wifi revenue at Panasonic was split between the company and the airlines — which meant every airline on the platform was sitting on the same monetization gap. A captive portal wasn’t a customer accommodation; it was a platform-level revenue feature with a clear ROI across the entire fleet. That reframe changed everything. The feature went into the core development pipeline and shipped within two months.
Reframed: not a customer accommodation, but a platform-level revenue feature
Made the fleet-wide ROI case explicit across the entire airline network
Feature entered the core development pipeline
Step 3
The result
The airline saw roughly a 30% increase in both connectivity revenue and wifi adoption following the rollout. The feature was adopted as a default by major airlines across the platform — turning what started as one customer’s frustration into a durable revenue driver for the business.
~30% lift in connectivity revenue and wifi adoption
Adopted as default by major airlines across the platform
One customer’s frustration became a durable revenue driver for the business
The broader pattern
The work isn’t finding the solution — it’s finding the frame that makes the solution possible.
This is the kind of problem that stalls at every level of a growing organization: a clear customer need, an obvious technical solution, and an org structure that makes it nearly impossible to execute.
The most valuable thing you can do is find the frame that makes the right answer easy to say yes to. That’s what I do.
More Cases
