The Handoff
The app could launch before the behavior changed.
The surface story was simple: replace a legacy scanning workflow and move stations onto a new mobile platform.
The leadership problem was harder. A deployed system can still fail when frontline teams operating under pressure don't trust it enough to change behavior.
As RAMP Upload expanded across the Alaska network during Alaska Airlines' historic merger-era growth, the challenge shifted away from deployment itself and toward something much harder to see: operational confidence.
Some stations adopted quickly. Others quietly developed workarounds. Missing upstream scans created downstream recovery work. High-friction scenarios pushed teams back toward manual fallback behavior.
The organization could see rollout progress. What it struggled to see was adoption drift.
So the work evolved. Tre helped shift launch conversations away from training completion and rollout sentiment toward behavioral signals, station-level variance, frontline friction, and operational visibility — building a rollout system capable of identifying adoption gaps before they hardened into operational behavior.
Because deployment is technical. Adoption is behavioral.
Diagnosis
Deployment metrics were not enough.
Device access, training completion, and rollout milestones created the appearance of progress, but frontline behavior under real ramp conditions told a more complicated story.
RAMP Upload introduced the ability to deploy same-day fixes across the network. That flexibility accelerated recovery, but also increased the importance of release judgment, communication clarity, and operational trust.
Without adoption instrumentation, leaders could celebrate deployment success while stations quietly reverted to fallback behaviors, rescanning workflows, or manual recovery processes.
Adoption System
The rollout became launch, signal, response.
- Separate deployment from adoption
- Start with smaller rollout surfaces
- Instrument frontline behavior
- Watch station-level variance
- Pair fixes with field guidance
- Improve degraded-condition workflows
- Build faster operational response loops
The work evolved into building a leadership system capable of making adoption visible before operational drift became normalized behavior.
Result
Adoption became measurable enough to lead.
The lasting impact was not simply deployment coverage, but the operational model built around it: behavioral visibility, faster field response, stronger frontline trust, and a more evidence-driven approach to rollout management.
Field Signals
What the field said.
“That is awesome… a major improvement over our first attempts.”
“Really proud of the team… a lot of reports of things going well.”
“They really like how easy it is to change the commodity.”
“The fact that we had that notification was good and allowed us to prepare.”
