Chase Travel: Connected
From booking utility to membership platform
Goal
Make travel where the card’s value is felt — a reason to hold the card.
Problem
The portal was a commodity, silent about the card — so customers shopped on price, the one argument a premium fee cannot win. Inside, dozens of teams shipped releases that never summed to a product.
Customer Promise
"Every booking reflects who you are as a cardmember — not just where you're going."
Constraints
- Tech: legacy booking over multiple vendor backends. No pause.
- Partner: every supplier with its own contract and cadence.
- Compliance: pricing disclosure, everywhere.
- Time: quarterly release trains.
Options Considered
- Option A: refresh the interface. The same commodity.
- Option B: rewrite the experience layer while the backend migrates beneath it.
- Option C: full rebuild. A year customers could not feel.
Decision
Option B. Rewrite search, comparison, trip detail and checkout while the infrastructure migrates beneath, decoupled so neither blocks the other. More coordination — and a middle funnel that improved every quarter.
The Mechanism
Metrics
- Primary: progression from discovery to booked.
- Guardrails: satisfaction, error rate, accessibility.
- Strategic: card-tier value legible in every inventory.
Risks & Mitigations
- Two workstreams, one surface → the abstraction layer.
- Fragmentation at scale → product leads per pod, one standard.
- Vision decay → the promise, used as the tiebreaker.
What Changed
- Dozens of teams behind one vision.
- A commodity portal became a card-tier-aware platform.
- The parallel model, and the organization built to hold it, outlived the program.