Travis Head was in at the crease, the opening pair were still thriving in the middle, and with 75 runs already on the board SRH had the sort of control they love to seize early. Two deliveries remained in the Powerplay, meaning the momentum could still be stretched further. It is precisely this compulsive desire to grab the initiative quickly that can unsettle opponents when they face the SRH top order. Stephen Fleming had hinted at the same mindset ahead of the match, and CSK responded by trying to disrupt SRH’s left-handed rhythm. Along with their usual plans, they brought in Matthew Short, banking on the Australian’s part-time off-spin to keep SRH’s left-hand trio under pressure.
For a short while, the match-up seemed to deliver. Only 12 runs came off the bat in Short’s first two overs, suggesting CSK’s idea was doing enough to slow things down. However, the spell lost its edge when Short pitched one slightly wrong in his length and Abhishek Sharma punished it immediately, launching the ball over long on for a six. Even so, CSK’s approach largely held its shape for a time. As the fifth over began, they took another chance and handed Short’s off-spin a further opportunity against the left-handed openers. Head struck one through mid-wicket to move the ball along, then Abhishek managed the other half of the strike rotation.
With the required scoring rate climbing to 9.5, Abhishek chose to raise the tempo. He opened up his stance, repeatedly picked the ball as it came onto the bat, and swung against the turn and through the line on the rise. The result was a sudden surge: 24 runs off the next five balls, with every delivery crossing the boundary ropes either off the bounce or straight. That burst disrupted CSK’s earlier plans and also forced them to move Short out of the attack. Before 15 balls had passed, Abhishek had already reached another fifty, SRH’s chase of an ideal start continued, and CSK suddenly looked flat and uncomfortable.
When the Powerplay was nearly done, Head had every reason to maximise the final stretch. But in an attempt to loft Mukesh Choudhary over the infield, he misjudged a full-toss and the innings was cut short by a piece of fielding brilliance from Ruturaj Gaikwad. Diving low and stretching to his left from mid-on, Gaikwad completed a fine catch to end the partnership and swing momentum back towards CSK. All of this happened while Abhishek’s destructive spell was still unfolding, which meant Head’s own fading impact blended into the larger story. Against Short, Head produced just four runs in eight balls, and despite SRH’s boundaries continuing to rain, his knock ended at 23 off 20 deliveries.
In isolation, that 23 was not the worst Head has shown in recent times, especially when compared with how often he has been able to reach the 20-run mark. Since the start of 2025, it was only the 15th occasion in 32 T20 innings where he has gone past 20. The bigger issue is that his outputs have visibly softened since 2024—the season in which his early partnership with Abhishek set new reference points for T20 batting. From 2024 to the present campaign, his boundary rate has slipped from 31.43 to 26.73, dot-ball percentage has risen from 37.3 to 44.3, and his strike rate has dropped from 182.07 to 150.26. Those numbers alone may not look like an immediate alarm, but once the average is considered, the concern grows: his average has fallen from 41.20 to 23.41.
Head’s 2024 return also underlines the shift. He recorded 14 T20 scores of fifty or more that year, yet this season he has crossed that threshold only once. For SRH, it is not simply a dip in form; it is the beginning of a larger set of problems that have been stretching across their campaign. A side that has relied on batting power to set up wins has instead averaged only 202 runs per game this season. The situation is worsened by inconsistency and patterns that keep repeating, most notably the inability of the top order to fire together.
When Head’s contribution drops and his scoring pace slows, the burden inevitably shifts onto the rest of the batting group. In SRH’s attempt to keep the early momentum alive, they have also found themselves in a recurring situation: Head’s dismissal has often been followed almost immediately by another wicket, or it has arrived right after one. That is not entirely surprising given the high-risk angle SRH often plays with, but the repetition has become difficult to ignore—this has occurred in five of SRH’s six matches so far. Even against CSK, a similar rhythm played out: Ishan Kishan miscued a big hit off the very first ball and was dismissed right after Head’s exit.
Those quick strikes remove the momentum that SRH need—if it ever truly gets going strongly enough in the first place—and leave the batting side in an uncomfortable position. They are forced to stabilise for a stretch, even though their batting blueprint generally cannot afford extended pauses without risking collapse. The fear is that they could end up “going bust” in the same way they did repeatedly last season, and the successive wicket-falls are exactly what Heinrich Klaasen, SRH’s designated No. 4, pointed to when explaining why his plans have to be calibrated more carefully.
Klaasen has been among the slowest starters so far in this IPL, striking at only 106.66 in his first ten deliveries. It is during that early phase that opponents can seize control and set the tone. Addressing the reason behind his slow starts, Klaasen said, “I’ve been in situations where we have lost four wickets in one or two overs. So it’s not like I can just tee off. If we lose [a wicket] there, then five wickets are down. So, [my slow starts] are not on purpose. I still need to get the job done. We got it done on a slow wicket here, where we were three [wickets down] after the powerplay. So that’s why my strike rate is so low.”
Even if the data he cited exaggerates the narrative slightly, Klaasen’s position this season has still been striking. He has worn the Orange Cap at the same time, yet his strike rate of 144 makes him the slowest batter in the competition among all players who have scored at least 170 runs. In fact, among the top 35 highest scorers this year, only Tristan Stubbs has been even slower. Klaasen defended his method further, adding, “I’ve been in difficult situations, and I have to take the responsibility, and be mature about it. You can’t just tee off, that’s not how the game works. We get paid to do that job. I don’t care about the strike rates. I know there’s a lot being said about my strike rate this season, but I’ve been putting my team in good positions, and I’m just doing my job.”
CSK’s bowling also played its part in the eventual outcome. They kept chipping away with wickets in a fight they refused to relinquish, and as a result SRH brought Liam Livingstone in as the Impact Substitute rather than using him to strengthen the bowling attack. Still, Klaasen’s 39-ball 59 proved crucial. His innings helped SRH reach 194 for 9, a total that became their highest ever against CSK. That said, it might have mattered less if Ayush Mhatre had not been affected by cramps during his stay at the crease.
Against Chennai Super Kings, SRH did find a way through with a margin of 10 runs, benefiting from disciplined bowling in the final quarter and some assistance from reverse swing. Yet the larger question for SRH remains unresolved: they are still searching for a version of themselves that can hold its structure across all 20 overs rather than delivering only short bursts of brilliance. Until their most feared weapons consistently bare their teeth, those strong starts will always carry an element of vulnerability—and over time, the courage to threaten opponents may risk fading unless the patterns are corrected.
