This is the 16th installment of Lighthouse, my monthly column for BLink, a supplement of the Hindu Business Line.
I saw the strangest thing the other day. Out on the road, there was a sleek Lamborghini with a man in a dhoti-kurta at the driver’s seat. His hands weren’t on the wheel. Instead, he held a whip in his right hand, which extended out of his window, and he was whipping a couple of bullocks tied to the front of the car. The engine was off; the bullocks were pulling the car.
Now, okay, this is perhaps a bit too weird even for India, and I confess that I didn’t see exactly this. But I did witness something very close. I was watching the IPL.
Twenty20 cricket is a relatively new form of the game which makes new demands on the teams that play it. Like a bullock cart driver who has just been given a Lamborghini, the men who run the teams and play for them haven’t quite come to terms with this. So they continue to whip the bullocks. When one-day cricket was born, teams played it much like they would a Test match—consider Sunil Gavaskar’s 36 not out in 1975 through 60 overs, and while that is an extreme example, consider the low par scores of those times. Eventually, players adapted. Even Gavaskar made a thrilling World Cup century before retiring, and par scores crept up until, as I wrote in my last installment of Lighthouse, they crossed 300 in the subcontinent, which was once an outlier score and not the norm.
Similarly, in T20 cricket, teams have basically adapted their ODI approach to this shorter format. So maybe they tonk in the powerplay at the start, then they consolidate and set a platform, then they tonk again towards the end. They often have freeflowing openers, but leave their hard-hitting maniacs, like Kieron Pollard of Mumbai Indians, to bat at the end. This is a flawed approach, because T20 is not just a modified version of ODIs, it’s a whole new format with its own imperatives.
First of all, consider that T20 cricket is played with the same number of players in each side as ODI cricket is: Eleven. This is not a banal point, but crucial to understanding how to approach the game. If T20 games were played 8-a-side, you would be justified in structuring your innings as you structure an ODI innings. But with 11 players, you have extra resources for the time given to you. Your task is to make sure these resources are not wasted, and are optimally used. If the hardest-hitting strokeplayer in the team routinely gets only four or five overs to bat, you are screwing up somewhere. So what should you do?
I’d written a piece after last year’s IPL for Cricinfo where I’d laid out what I felt was the biggest tactical advance of last year’s IPL: Frontloading. Basically, King’s XI Punjab decided to snort at the concept of building a platform, and just sent their hardest hitters upfront and treated every over as sides would usually treat overs 16-20. They attacked from the outset, with Glenn Maxwell, David Miller and George Bailey coming in at Nos. 3, 4 and 5, and sometimes if an early wicket fell, Wriddhiman Saha coming at 3, but also to tonk. Their frontloading ensured that batting resources were not wasted, and this approach got them off to an excellent start in the tournament. In contrast, Mumbai Indians consistently sent out their best hitter, Kieron Pollard, with just a handful of overs to go, and he had nowhere near the impact he could have had. Kolkata Knight Riders started poorly, but then adapted, dropped Jacques Kallis the accumulator, frontloaded the hitting, and things worked out. They also had a better bowling attack than Kings XI, and deservedly won the IPL.
This year has been bizarre. King’s XI, far from continuing to frontload, has reverted to traditional structures of building an innings, sending in Maxwell later than they did last year and even, at the time of writing this piece, dropping him from the side. Mumbai Indians haven’t learnt from their past mistakes, and continue to save Pollard for a dash at the end. They would be better served if Pollard and Corey Anderson batted 3 and 4, in whatever order, with Rohit Sharma opening. But no, they don’t use their elite V12 engine. The other day Mumbai Indians, with Pollard and Anderson mostly at the crease, added 81 runs between overs 16 to 20, but lost because the team scored too slowly in the first 15. What a waste. Imagine if they had scored those 81 runs between overs 6 to 10 instead. How nicely that would have set up the innings. Their chances of doing so between overs 6 to 10 were the same as between 16-20, but the upside of going for it early was far more and the downside the same. Keep the bullocks for later, if the engine fails.
The idea is not just to frontload resources but also to frontload intent. Every side doesn’t have a Maxwell or a Pollard. But whoever goes out there should attack, attack, attack. Sure, if a Starc or Malinga is on fire, play that one guy out. But otherwise go for it. Not only does it ensure you don’t waste batting resources, it also ensures that soft overs in between by lesser bowlers are not wasted. Batting strategies are so predictable that fielding captains can plan how to use their resources well, keeping their best restrictive bowlers, like Malinga, for the end of the innings. But what can they do if you’re going at them all the time?
The one team that has gotten frontloading right in this IPL so far is the Chennai Super Kings. Brendan McCullum and Dwayne Smith play every over like it’s the 18th of the innings, and Suresh Raina and MS Dhoni, two outstanding strokeplayers, follow at Nos. 3 and 4. This is exactly right, and good captaincy. Of course, Chennai also have an excellent bowling attack, which is why they’re among the favourites in the IPL year after year. All things being equal between teams, though, frontloading makes the difference. So when you have a Lamborghini, drive the damn thing.