Memo 02 / 04 · Decision record · 3 min read
Chase Travel: Connected
From a booking utility to a platform that expresses membership
Goal
Move travel from a price-comparison utility to the place where the card’s value is felt — a trip as a reason to hold the product, not a transaction it happens to fund.
Problem
The portal was a commodity: functionally any travel agency, and silent about the card in your pocket. When every issuer competes on travel, sameness teaches customers to shop on price — the one argument a premium fee cannot win.
The harder problem was internal: dozens of teams shipping defensible releases across flights, hotels, cars, cruises and experiences that never summed to a product. The gap was not execution. It was one vision with enough gravity to hold that many teams in orbit.
Customer Promise
"Every booking reflects who you are as a cardmember — not just where you're going."
Stakeholders
- Customers arrive mid-decision and leave the moment the funnel makes them work.
- The firm needs travel to carry retention and premium spend — a benefit used, not offered.
- Delivery teams and partners need a vision specific enough to build against, stable enough to plan a year around.
A decision counted when it served all three. Anything serving two went back.
Constraints
- Tech: legacy booking infrastructure over multiple vendor backends. No greenfield, no pause.
- Partner: supply relationships, each with its own contract, data model and cadence.
- Compliance: pricing transparency and disclosure, everywhere.
- Time: quarterly release trains. The business could not wait for a rebuild.
Options Considered
- Option A: refresh the interface. The same commodity in better clothes.
- Option B: rewrite the experience layer while the backend migrates beneath it. Costlier coordination, real differentiation.
- Option C: full rebuild. A year of shipping nothing customers could feel.
Decision
Option B. Rewrite the experience where card value is felt — search, comparison, trip detail, checkout — while the infrastructure migrates underneath, decoupled by an abstraction layer so neither blocks the other.
It cost more coordination than a sequential plan, and bought what sequence cannot: a middle funnel improving every quarter while the foundation was replaced.
The Mechanism
Metrics
- Primary: progression through the middle funnel — discovery to comparison to booked.
- Guardrails: satisfaction, error rate and accessibility held flat or better.
- Strategic: card-tier value legible across every inventory, not just the flagship.
Risks & Mitigations
- Two workstreams, one surface → the abstraction layer; either side ships on its own cadence.
- Fragmentation at scale → product leadership embedded per pod, one shared standard of record.
- Vision decay under quarterly pressure → the promise written down, used as the tiebreaker.
What Changed
- Dozens of teams aligned behind one vision — shared outcomes instead of isolated backlogs.
- A commodity portal became a card-tier-aware platform across the full inventory.
- The parallel model — transform above, migrate below — outlived the program.
- A product organization built to sustain the standard, and handed on.
Where It Stands
The platform kept shipping after the handoff, and the operating pattern outlived the program: transform the experience above, migrate the rails below, never make the customer wait for either. The standard — and the organization built to hold it — carried on without me, which is the point.