Room For Growth

The episode contains solid operational insights about customer journey mapping, iterative deployment, data architecture, and organizational structure, but much of the conversation retreats into motivational generalities about leadership and listening. Kevin provides concrete examples (Brightline's transition from disparate systems to API-driven platforms, the mobility/Uber integration decision, two-week sprints), but spends considerable time on broad leadership philosophy that many operators would have already encountered.

“We mapped out what are those places and moments that are going to matter for our guest...and we unlocked doors and closed other doors that were breaking the system.”

“We don't launch 18-month projects anymore. We launch two week sprints of feature function and we learn from them as we go.”

While Kevin articulates a useful customer-centric philosophy and specific organizational practices (vertical team structures, data-as-a-service, careful AI rollout), the core ideas - listen to customers, move in small iterations, hire good people, empower teams - are not novel. His framing is pragmatic but not distinctly contrarian or first-principles. The AI/ML caution is sensible but increasingly common among mature operators.

“Provide your guests what they are asking for, when they want it, where they want it, how they want it, and it becomes a powerful tool of commerce.”

“It's all about building trust in all of that to have outcomes that feel trustworthy, consistent, and loyal to the guest.”

Kevin is a legitimate operator with real scale experience: he led digital transformation at Disney, Travel + Leisure (major publisher), JPMorgan fintech, and now governs all tech and innovation at a high-profile infrastructure startup (Brightline). He has shipped products, managed large budgets, and navigated organizational complexity across multiple industries. His credibility is solid, though he is not a founder or CEO, which slightly limits the scope.

“Chief Technology and Digital Innovation Officer at Brightline Trains”

“I worked for Disney...T+L...JPMorgan, which is fintech and Walt Disney World, which is tourism”

Kevin provides some concrete examples: the Adobe Experience Platform deployment in under 3 months, two-week sprint cycles, the decision to drop in-house mobility and partner with Uber, team evolution from one blob to vertical structures with iOS/Android/AEM/QA disciplines. However, much of the discussion lacks specific metrics, dollar figures, or quantified business outcomes. He mentions Fivetran, Databricks, Power BI, AWS, and other tools by name, but rarely shares KPIs, revenue impact, or cost savings.

“we brought some of that technology to market in less than three months, which in the Adobe space is a record speed”

“we have a bigger team, because we have different disciplines now...where there's disciplines around specific function”

The host asks reasonable setup questions and shows familiarity with Kevin's background, but rarely pushes back, challenges claims, or digs deeper into trade-offs and failures. When Kevin makes broad statements (e.g., 'embrace failure'), the host does not follow up with specifics. The conversation flows smoothly but lacks the friction that would yield more actionable nuance. Several long Kevin monologues go unchecked.

“But I'm curious how you feel about innovation today and how you build a culture of innovation when innovation is low.”

“I'm curious how you spot future leaders in your teams and how do you help raise them, and how do you hold them accountable?”