Skip to main content
The High Performance Podcast

Haas F1 Boss: How the Smallest Team in F1 Plans to Shock in 2026 (E387)

79 min episode · 2 min read
·
Guenther Steiner

Episode

79 min

Read time

2 min

Topics

Productivity, Leadership, Software Development

AI-Generated Summary

Key Takeaways

  • Crisis management through transparency: When Haas discovered their car was six-tenths slower than competitors at lap two of FP1 in Melbourne, Komatsu immediately aligned technical directors and engineers without blame or politics, focusing solely on solutions rather than finger-pointing to maintain team cohesion.
  • Driver conflict resolution framework: After Ocon and Bearman crashed into each other at Silverstone, Komatsu gave them one week to agree on racing rules themselves before imposing team orders, creating ownership and trust that eliminated future conflicts without management intervention throughout the remaining season.
  • Rookie development strategy: Komatsu told Bearman after Melbourne crashes to prioritize completing every lap over speed in Shanghai, removing performance pressure to build consistency. This approach helped Bearman achieve his first P4 finish in Mexico by season end, holding off Verstappen, Russell, and Piastri.
  • Cultural transformation indicators: Komatsu spent one week each in Banbury UK and Italy facilities doing one-on-one sessions with staff upon becoming team principal in January 2024, discovering communication breakdowns where Italian engineers received contradictory messages about car development priorities after official debriefs.
  • Performance development proof: Haas demonstrated consistent development capability two years running, with major upgrades in Silverstone and Austin 2025 showing immediate Friday pace improvements, disproving critics who claimed the team could only start seasons strong but never develop cars mid-season effectively.

What It Covers

Haas F1 Team Principal Ayo Komatsu explains how his smallest team in Formula One recovered from being six-tenths slowest in Melbourne 2025 to achieve their second-best season finish through cultural transformation and transparent leadership.

Key Questions Answered

  • Crisis management through transparency: When Haas discovered their car was six-tenths slower than competitors at lap two of FP1 in Melbourne, Komatsu immediately aligned technical directors and engineers without blame or politics, focusing solely on solutions rather than finger-pointing to maintain team cohesion.
  • Driver conflict resolution framework: After Ocon and Bearman crashed into each other at Silverstone, Komatsu gave them one week to agree on racing rules themselves before imposing team orders, creating ownership and trust that eliminated future conflicts without management intervention throughout the remaining season.
  • Rookie development strategy: Komatsu told Bearman after Melbourne crashes to prioritize completing every lap over speed in Shanghai, removing performance pressure to build consistency. This approach helped Bearman achieve his first P4 finish in Mexico by season end, holding off Verstappen, Russell, and Piastri.
  • Cultural transformation indicators: Komatsu spent one week each in Banbury UK and Italy facilities doing one-on-one sessions with staff upon becoming team principal in January 2024, discovering communication breakdowns where Italian engineers received contradictory messages about car development priorities after official debriefs.
  • Performance development proof: Haas demonstrated consistent development capability two years running, with major upgrades in Silverstone and Austin 2025 showing immediate Friday pace improvements, disproving critics who claimed the team could only start seasons strong but never develop cars mid-season effectively.

Notable Moment

Komatsu watched restricted onboard footage of Grosjean's Bahrain crash and observed every survival decision was correct, including the counterintuitive choice to go back down into flames when his foot stuck, forcing his race boot off to escape before fireproofs failed at the limit.

Know someone who'd find this useful?

Episode Transcript

I always say to people that failure doesn't define us. What defines us is how we get up from the other team together. If I'm totally honest, I was ready to quit in, Baku '23. I was very close to just walk. Very first instance, I didn't know it was Romain. And then the minute I re realized it was Romain, obviously, I'm thinking he cannot be alive. And he's my friend. You're listening to High Performance. Thanks to everyone who's already subscribed. If you've not, right now is the time because you'll get new episodes the moment they drop, and your support helps us bring more world class guests onto the show. Tap subscribe right now, and keep growing with High Performance. Ayo, welcome to the show. Thank you for having me. So last season, you got your second best ever points finish with the Haas Formula one team. Rewind to the very first race of the season, and I bet you would never have imagined that you would finish so strongly. Yeah. Absolutely. That first race in Melbourne, as soon as the car started running in f b one, then when as soon as I realized how big the issue was, that was really sickening. You know, at that point, we are facing the season of potentially scoring zero point. You know? Because we are not just slowest. We are the slowest by, like, six tenths. We had a huge problem. So when did you first realize that the car wasn't what you thought? Lap two of f p one. Yeah. What are you thinking at that point? Yeah. No. So so, again, so f p one, you start running very fast lap. Okay. I looked at those high speed corners. Okay. We are very slow, but it's lap one. It's okay. Maybe your driver's just in sighting lap. Then you cool down the tires, and then you go again second lap. It should be not not your quickest lap, obviously, but should be not a huge amount off, miles and miles off. It's like you are going through wet patch. Right? Then I realized, okay. We got some serious problem. Then by the end of f p one, it was totally clear. We got some serious issue. Then the focus is okay between f p and f p two. What can we do to mitigate this issue to see if we is that something we can solve with the reasonably big change on the car setup? Then by the end of FP two, I had to know that something we can deal with the setup or not. Then by the end of f p two. So by the end of Friday, it was totally clear that is a serious fundamental fluidity. Everything on the Friday and nothing would make the car quicker, really? Yeah. I wouldn't say everything because you only got, like, a hour to do it or two hours to do it if you include …

Get the full transcript (16,885 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all The High Performance Podcast transcripts →

You just read a 3-minute summary of a 76-minute episode.

Get The High Performance Podcast summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

More from The High Performance Podcast

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

Explore Related Topics

This podcast is featured in Best Mindset Podcasts (2026) — ranked and reviewed with AI summaries.

Read this week's Software Engineering Podcast Insights — cross-podcast analysis updated weekly.

You're clearly into The High Performance Podcast.

Every Monday, we deliver AI summaries of the latest episodes from The High Performance Podcast and 192+ other podcasts. Free for one show.

Start My Monday Digest

No credit card · Unsubscribe anytime