The Ruthlessness Lesson in Indore: Where Even 223 Runs Isn't Enough

I was watching the match from the Holkar Stadium in Indore. India had posted 223. Normally, that's a score where you can lean back and relax, but I couldn't. Since 2026, watching the West Indies batting lineup tells you one thing: this team can lose five wickets for fifty runs and still win. That's not an exaggeration. And that's precisely why India's 14-run win on Sunday sounded more comfortable than it actually was. Abhishek Sharma's post-match comment captures the real theme of this series: 'They have that capability to turn things around for themselves. If they are 50 for 5 as well.' Having tracked West Indies T20 matches over the past few years, I can see a clear pattern. When their top order fires, the scoreboard moves so fast that no defending captain can relax. Shamar Springer's innings in Indore is proof of that. Those shots weren't easy, not at all. Lining up and lifting, or driving straight against the length — these aren't technically simple shots. Looking at the numbers: India scored 223 in 20 overs, a run rate of 11.15. But the interesting part is they managed just 13 runs off the first 14 balls while losing Sanju Samson for 3 off 6. This is what made me think: in modern T20, a slow start isn't always a disaster if one batter anchors and another attacks in the middle overs. Abhishek's 69 off 30 and Ishan Kishan's 37 off 18 — their 108-run partnership off 40 balls for the second wicket was the turning point. I've been tracking this pair since last year's IPL. The combination they share isn't just about skill. Abhishek himself said, 'I have to make him laugh, I have to relax him a little.' That's a small detail, but in T20 partnership dynamics, its importance is massive. When a new batter walks in, anxiety sets in during the first two or three balls. If you can free him from that moment, his output changes. That's exactly what happened with Kishan. But here's a contrarian point that creates some inner conflict for me. We all marvel at a score of 223. But the question is: has this score become a normal thing due to conditions and ground dimensions? With Holkar's small boundaries and Indore's flat pitch, how much is this score a product of a batter-friendly venue? If I look at data from major tournament venues, scoring rates drop in big finals and knockouts. That means when evaluating Indore's 223, we need to apply condition normalization. Another thing bothers me. Abhishek said, 'We were talking about this in the huddle that we will be ruthless, we will not leave, and we will not give a single chance for a comeback.' That's a sign of capable leadership. But the question is: West Indies reaching 209 while chasing 223 reveals some weaknesses in India's bowling plan. In T20's structure, one bad ball can shift the match's momentum. One thing is clear: West Indies' batting depth is actually stronger than people think. If a team can lose five wickets for fifty runs and still finish within 14 runs, it shows their lower-order planning is well constructed. India's win should therefore be seen as a warning. Because upcoming matches in this series could be at bigger venues where this run-scoring flood will subside — then India's middle-overs plan will be tested. I always believe a scoreboard is just a number. The real story lies in those moments when a team handles pressure. India handled that pressure in Indore on Sunday. But what if they can't next time? That's the real question of this series.