Since the start of the 2024 season, the IPL has largely witnessed high scores, with new benchmarks being set. In that respect, the Punjab Kings-Kolkata Knight Riders game on Tuesday (April 15) was a throwback to T20 games of yesteryear, where there was a significantly greater contest between the bat and the ball. The game saw both teams being bowled out, that too inside 16 overs, but KKR skipper Ajinkya Rahane didn't use the surface as a reason behind the loss. The defending champions were well on their way through the 55-run partnership between Rahane and Angkrish Raghuvanshi, chasing a pitiful score of 112. At 62/2 in the eighth over, the result seemed a foregone conclusion before Punjab's bowlers engineered a sensational collapse. KKR lost their last eight wickets for just 33 runs as the match saw a new record for the lowest successfully defended total in IPL history. "The wicket was good. "It wasn't an unplayable wicket or that something was wrong," Rahane said at the press conference following the match. "The wicket was very good. The ball was coming a little late. However, the bowlers completed half of the work. They were all out at 111, as you stated. It was comparatively easy to chase at 112 on this wicket. We also got a good start. We got 50 in the Powerplay and at 70, I think we had 3 wickets. But again, it's a collective failure of the batting unit." Often in run chases, the required run rate is a huge trigger for batting collapses. Ironically for KKR, that was never the issue in their innings. KKR were in a position where they needed just 50 off the last 75 deliveries with eight wickets in hand, having started the chase needing well under run-a-ball. That's when the Rahane-Angkrish partnership was broken with the skipper's dismissal. Thereafter, the innings nosedived in a sensational fashion. "Many times, it's not only about hitting sixes or playing big shots. Strike rotation is also very important. Our batting unit, on the other hand, I'm pretty sure didn't do that. It's not like Punjab bowled extremely well. I think we played bad cricket as a batting unit. I take this responsibility as a captain, as we couldn't chase this down. But individually, I am sure all the players, especially the batters, will think about their own game and improve in the upcoming matches. "The tournament is over for half of it. Seven matches have been played. And half is still left. It's always about coming back with good intent but still look to learn and improve as a batter and take it on in the next game." Yuzvendra Chahal (4-28) was the star for Punjab in their bowling effort while Glenn Maxwell's part-time offies were also very effective for the hosts. Marco Jansen's three-wicket haul was also a talking point, but the major twist in the game came through Punjab's spinners. Earlier on, KKR's spin twins Sunil Narine and Varun Chakravarthy also had a great outing as they derailed PBKS's dangerous batting line-up. In hindsight, playing Moeen Ali as the third spinner could have been a potent choice, given the amount of turn and bite in the surface. Instead, in the visitors' first game of the season, Anrich Nortje had a moderate performance. When asked whether a third spinner in Moeen could have furthered KKR's advantage, Rahane gave a pragmatic reply. "We thought we wouldn't need three spinners when we looked at the pitch. Fast bowlers can get help, and historically, I don't think more than two spinners have played on this ground. This was our tactical call, although Moeen Ali bowled very well in the last two games. We thought it would be better for Nortje to bowl really well and come on this wicket. "If you look at it, it's our fast bowlers who took the wickets. They kept the pressure on them. If Moeen Ali played on this wicket, maybe he could have taken wickets, but we as a management felt that three pacers and two spinners was the way to go on this pitch." Rahane was among the three KKR batters who managed to get into double digits. The skipper looked assured in his brief stay and his drama-filled dismissal was just the tonic PBKS needed to get back into the game. Rahane fell to a sweep shot against Chahal, trapped LBW, but replays showed that a review could have saved the batter as the impact was well outside off stump. Rahane did ponder briefly about the review, but with no clear input from Raghuvanshi, the KKR skipper opted to walk off. "I thought I would save the review for later as a batter. Because it shouldn't happen that I take the review and then only one review is left. And the communication between the two batsmen was also not that clear. If someone comes and tells you clearly that the impact can be outside or missing, so as a batter, you take the review. However, there was a lack of clarity in the batsmen's communication. Due to that, I declined the review. "But again, no complaints. Apart from that, we did bad batting as a batting unit. And the result of that is why we lost the game today." Given their high-flying template that was the talk of their title-winning campaign in 2024, KKR's intent has often seen its share of struggles against spin bowling. Even with the extreme lack of scoreboard pressure, their batters seemed all at sea in negotiating the chase and seemed to have just one gear to fall back on. Rahane insisted that his side weren't aiming for a net run rate boost, although some of the bizarre dismissals did suggest an air of ultra-aggression. "Definitely, we were thinking about two points. What comes first is two points and then the net run rate. Till I was batting, it was sure that two points were important. "As I stated earlier, it is not about hitting sixes or increasing the net run rate. It was not a flat wicket. It had something for the bowlers. We had to persevere. In T20, it's okay to play a maiden over from time to time. Or play a strike rate of 70 or 80, that's fine.But I think just grind it out. It's all about rotating the strike as a batting unit. And T20, personally, I believe it's not only about hitting sixes. Though we are seeing at this moment, most of the players are going for big shots." They want to look good on the field while batting. It's not about that. It's all about reading the situation well, having that game awareness as a batter, as an individual. And then take the game forward. That's what I thought we lacked today." Choosing whether or not to include Moeen in the discussion is not an easy task. The Englishman's bowling is more valuable to KKR because his batting returns have decreased in recent years. This is especially true on turning pitches, where the off-spinner's accuracy is a big plus. The southpaw does boast of spin-hitting prowess - a quality lacking in KKR's batting unit - but his dwindling batting form means that it can't be a major factor. "Depending on the wicket, we can only play four foreigners, four overseas players. So far, Moeen has been fantastic for us. It's very hard for me to tell him, Moeen, you're not playing today, though he did really well in the last game. He has, however, been understanding. He's played cricket enough everywhere. He understands the situation. He also comprehends the dynamics of the team. So, good on him. "He's always been a team man. So, I would love to have Moeen in the team. But again, depending on the situation and on the wicket, we will take a call." Having won on a slow surface in Chepauk with ease, KKR would have fancied their chances of another crushing win in Mullanpur. Instead, they crashed and burned to a shocking defeat. Rahane dismissed talks of possible complacency as a reason behind the loss. "Not really. See, all the boys, all the players, they're confident. They're confident enough. They are pretty experienced enough to handle all the situations. I wouldn't say we were complacent or we were overconfident. We didn't bat well. That was the truth. "We didn't have that game awareness. The circumstance and the requirements for playing on that wicket. When we lost those three, four wickets, it was only about taking your time. Even singles, rotating the strike.That was important."