The IPL 2026 has delivered contrasting fortunes for a number of Australian internationals, with several franchises investing heavily to bring fresh urgency and high-end T20 skills into their squads. One of the most closely watched additions has been Travis Head, whose ₹6.80 crore acquisition by Sunrisers Hyderabad in 2024 was expected to translate quickly into match-winning impact. Yet after a promising beginning, Head’s output has not matched the standard of his debut season, and the pressure has only intensified during Hyderabad’s recent playoff exit.
Head’s IPL journey: from debut promise to 2026 scrutiny
Head arrived with momentum, having delivered immediately after his move to SRH in 2024. In that debut campaign, he amassed 567 runs and looked set to become a dependable top-order force. However, his numbers have dipped in the seasons since.
- In IPL 2025, the opener managed 374 runs, a below-par return by his own standards.
- In IPL 2026, he has again struggled to recreate the level of production he showed early on.
- The most intense criticism followed SRH’s Eliminator defeat to Rajasthan Royals on May 27, where Hyderabad fell short by 47 runs.
Eliminator turning point: Rajasthan set the tone with a chase-defining burst
In the Eliminator at the New Chandigarh Stadium, Rajasthan Royals—led by Pat Cummins—posted a formidable total, leaving SRH with a target of 244. The innings hinged on a rapid surge from Vaibhav Sooryavanshi, a 15-year-old RR product, who blasted 97 off 15 deliveries. That explosive spell swung momentum decisively toward Rajasthan and made the chase one of the toughest SRH could face in a playoff scenario.
Why SRH fell short: wickets lost at the wrong moments
To even contemplate what could have become the highest successful chase in IPL playoff history, SRH required their batting unit—anchored by Head—to hold firm and then accelerate when the opportunity opened. Instead, the chase started slipping early.
- Abhishek Sharma was dismissed for a duck after being sent back by Jofra Archer.
- Ishan Kishan, who had been in form, also failed to convert—his wicket fell after poor shot selection against Archer’s pace.
With the required momentum demanding steadiness as well as aggression, Head’s role was crucial. But his dismissal became a focal point for debate, especially because it arrived during the third over of the chase, in the powerplay.
Third-over wicket under the microscope: Archer’s plan executed
Head’s exit sparked fury among supporters and commentators. The criticism centered on how the opener appeared to misread the match rhythm and failed to handle the pressure at a stage when SRH needed him to absorb the bowling and guide the innings forward.
Former India all-rounder Irfan Pathan took aim at Head’s decision-making, suggesting that the dismissal reflected a lack of match awareness despite Head’s experience and World Cup-winning credentials, including past match-winning contributions in high-pressure situations.
Pathan’s breakdown of the dismissal focused on the tactical setup:
- He pointed to the significance of the third over, describing it as the phase where bowling strategy becomes clearer.
- He suggested that Rajasthan captaincy likely aimed to have Archer complete his spell in the powerplay after already striking twice, with the intent of removing Head and/or Klaasen.
- He argued that Head, knowing that a bowler in rhythm is often given another over to take wickets, should not have allowed the situation to unfold in Archer’s favor.
Pathan also claimed that Head’s response to the over—moving away from the stumps and creating room—was unnecessary and played into the opposition’s plan, adding that when runs have been hard to come by in the season, the priority should be selecting a safer approach to blunt momentum swings.
Crucially, SRH’s early run rate had looked workable after Kishan’s sharp burst of 33 off 11 balls. But the chase lost its spine when Head was clean bowled for 17—after attempting an attacking shot rather than seeing out the over.
- Head was dismissed for 17, caught up in an aggressive attempt instead of surviving the over.
- SRH’s chase had started with signs of control, helped by Kishan’s 33 off 11 balls.
- Even with that early momentum, SRH could not protect wickets while chasing 244.
Result and aftermath: missed Qualifier 2 spot extends the title wait
SRH’s inability to hold their wickets ultimately proved decisive. While they were capable of scoring quickly and maintaining the run rate at moments, the failure to preserve wickets during the pursuit of the mammoth total cost them a place in Qualifier 2.
The defeat also extended SRH’s wait for another IPL title, continuing a long gap since their championship triumph in 2016.
