Whose Responsibility? The Gap Inside Gavaskar’s Verdict on India’s T20I Batting

Half past eleven at night. In Dhaka, on the balcony, the stream runs on the laptop and the notebook lies open beside it. Before the post-match handshake was over, the phone began to buzz. A single sentence had been cut out of the post-match segment and the feed was drowning in it — Sunil Gavaskar said the batting unit needs to show more responsibility. I noted the time. The gap between the last ball and the sentence going everywhere was barely ten minutes.

Let me also honestly record what my notebook holds from this match — no venue, no toss, no innings structure, no dismissal details. Five information points, one of which is a quote. When I started “Beat Notes” from the team hotel corridor in Cardiff in 2026, I built one habit: before writing a verdict on a match, at least know who did what, when, in which phase. That basic condition is missing today.

The beat arrived before the team bus — but this time it arrived in a notification, not on the ground.

T20 is a twenty-over game, and twenty overs must be read in three phases — powerplay, middle overs, death overs. In each phase, the word “responsibility” means something different. In the powerplay, responsibility means the courage to exploit fielding restrictions. In the middle overs, it means managing risk against spin without letting the run rate stall. In the death overs, it means deciding in advance who takes the risk and who holds the crease. Without clear answers to those three questions, “show more responsibility” is moral advice, not tactical diagnosis.

The India–West Indies T20 rivalry looks easier on the ranking sheet than it is on the field. West Indies have won the T20 World Cup twice — 2026 and 2026. They routinely sit outside the ICC top five, yet as format specialists their power-hitting depth and varied bowling attack have always been a competitive match-up for India. So this defeat is not, by itself, a scandal.

My working method is simple — the smell of the ground first, then the tactical pattern, then the source. Living 34 days inside the Bashundhara Kings bio-bubble in 2026 taught me that the real story often lives in what is not said — the echo of an empty stand, the nervous laughter in the dressing room, the question nobody asks. It is the same here. The report has no phase-by-phase scoring, so nobody can prove “batting failure,” and nobody can disprove it either.

So what is “responsibility”? In T20, responsibility means ownership of risk — whose name is written next to the risk.

A batting unit looks “irresponsible” precisely when risk ownership is blurred. Who attacks in the powerplay, who rotates strike through the middle, who owns the boundary duty in overs 16 to 20 — when that role hierarchy is unclear, everyone takes risk occasionally and nobody owns it. This gets misread as a character problem. In reality it is a structural one.

The debate that returns to India’s T20 batting year after year is the anchor–finisher boundary. When an anchor manages strike rate from overs 12 to 17 and loads extra weight onto the finisher’s shoulders in the last five overs, getting out after the 18th over is not irresponsibility — it is the output of a role design. From outside, the two look identical. Inside, they are entirely different.

One thing belongs here that rarely enters the discussion. In the international calendar — two matches a week, travel between bilateral series, format switches, then T20 again — a player never gets five straight matches in the same position. Role clarity is built through repetition. No repetition means no role. However good the medical team is, nobody can stop the physical and mental erosion of two games a week — and equally, nobody can teach the definition of responsibility to a batter who plays three positions in three matches.

West Indies’ bowling match-up matters here. The Caribbean attack mixes pace-off cutters, wide yorkers and hard lengths at the death, and they know that pinning India’s top order through the middle overs raises the pressure in the last five. Their batting philosophy runs the other way — they do not seek control across the innings, they seek one twenty-run over to flip the tempo. In that collision of cultures, “responsibility” means two different things to two teams.

In Dhaka, the crowd keeps time while the players forget the clock. Sitting at Mirpur I have watched many times how a shift in the gallery’s rhythm changes a captain’s decision — some admit it, some do not. This series may be in the Caribbean or at a neutral venue, but that clock has not disappeared; the metronome has simply moved from the stands to the feed and the talking heads. And social media’s clock runs far faster — one missed ball and the beat changes.

At the 2026 World Cup in Kazan, watching Japan’s closed training, I understood something. Carlos Sánchez’s third-minute red card against Colombia was not an accident; Japan’s 4-2-3-1 press and Yuya Osako’s drifting between lines manufactured that moment. Kazan taught me that silence can be a kind of drumbeat. Structure makes the moment, not individual virtue.

Watching Walid Regragui’s sessions inside Morocco’s camp in Doha in 2026 brought the same thought back. Without the ball, their 4-3-3 folded into a 5-4-1 block — that is not mood, that is shape. Discipline is not an attitude; discipline is a geometry. Batting “responsibility” works the same way — it is shape, not mood.

The bio-bubble had a pulse, and I listened for its off-beats — when Robinho scored in an empty stadium, the sound came from the bench, not the stands. That off-beat taught me the real picture of a match lives outside the scorecard. But to search that “outside,” you need at least phase-level data. A quote cannot do it.

The outside reading is almost uniform — “India’s batters were careless, they could not keep their heads.” The problem is that this reading is built on the result, not the process. In T20 an innings can break for three reasons — poor shot selection, good bowling, or pitch behaviour. Without dismissal modes and ball-by-ball data, separating those three is impossible. In a report with no scorecard, any diagnosis is only a guess.

Second, there is a subtler cost. A legend’s criticism — natural, and at times necessary — builds a reactive cycle. Pressure rises, selectors change things quickly, quick change blurs roles further, and blurred roles produce the next “irresponsible” innings. The criticism meant to solve the problem ends up reproducing it.

Third, sample size. Reaching a systemic conclusion from one T20 defeat is methodologically wrong. And if India fielded a rotated XI in the fourth match — normal in a packed calendar — the weight of the criticism drops sharply, because that was experimentation, not evaluation.

So what do I watch next? India’s intent in the first six overs, who bats at number five in overs 16 to 18, and how much continuity the XI keeps — those three will give the real signal. Selection, not statement, will tell us whether the definition of responsibility has changed.

What stays in my notebook tonight is a reminder — writing a verdict is easy, keeping the evidence is hard. The next time someone uses the word “responsibility,” I will ask first: which phase, whose risk, whose responsibility?