About this episode
In this week’s episode of the PolicyViz Podcast, I chat with Michael Gethers, former Head of Data & Strategy for the McLaren IndyCar team, about how a personal side project analyzing IndyCar timing PDFs turned into a job building real-time data tools for a professional race team. We dig into what it’s like to design data products for engineers, strategists, and drivers who need to understand information instantly while a car is on track. Michael shares how he moved from making public visualizations on Twitter to building an internal analytics application from scratch, why “pretty charts” weren’t enough for the engineers, and how user feedback shaped the product. We also talk about race strategy as a probabilistic data science problem, the difference between dashboards and data products, and what he learned about designing for cognition under extreme time pressure. If you care about dashboards, data storytelling, or building tools people truly use, this conversation is a goldmine.Keywords: data dashboards, data product design, data visualization, motorsports analytics, race strategy, McLaren IndyCar, telemetry data, timing data, data science in sports, user centered design, dashboard design, real time analytics, D3 visualization, data engineering, analytics applicationSubscribe to the PolicyViz Podcast wherever you get your podcasts.Become a patron of the PolicyViz Podcast for as little as a buck a monthFollow me on Instagram, LinkedIn, Substack, Twitter, Website, YouTubeEmail: jon@policyviz.com
