2016 Formula 1 World Champion Nico Rosberg has claimed that Zak Brown showed a lack of “empathy” to Oscar Piastri following the Abu Dhabi Grand Prix.
Following the chequered flag at the Yas Marina Circuit, the McLaren CEO congratulated Piastri on an outstanding season.
Despite narrowly missing out on a maiden title, Piastri concluded the campaign with seven race victories among 16 podium finishes.
Alongside this, the Melbourne-born driver played a crucial role in McLaren achieving a second consecutive Constructors’ Championship.
Thus, Brown’s radio message focused on thanking him for his efforts in 2025, with a full focus on next year, when new regulations will be introduced.
“What a season, what a season,” Zak Brown exclaimed on the radio. “You’re a star. Seven wins. We love ya. We’ll do it again next year
“Thank you Oscar for everything you’ve done. What a year.”
He then thanked Piastri for being a “team player” in a season where McLaren’s contentious ‘papaya rules’ have been the talk of the paddock.
“Oscar, very proud of you. Awesome. What a team player. We go again next year. See you on the podium,” he added.

Rosberg questions timing of Brown message
While Brown’s comments seemingly had positive intentions, Rosberg questioned the timing and delivery of the comment.
The German suggested that in such a heartbreaking moment for the Australian, the message came across as insensitive.
“That’s his most horrible moment in his racing career,” Rosberg told Sky Sports F1.
Rosberg also highlighted that moments immediately after a title defeat are often emotionally raw for drivers.
For Piastri, who led this Championship for the majority of 2025, recognising the pain is just as important as acknowledging his successes this season.
“Maybe Zak could have had a little more empathy there, rather than celebrating,” he added.
“He could have said, ‘Next year will be your year’, but it’s difficult for Zak because he’s so ecstatic at the same time.”
READ MORE – Why McLaren is ‘optimistic’ it can retain F1 titles in 2026 despite extensive rule changes









Discussion about this post