Gavaskar's 'Responsibility' and India's Batting: The Question Nobody Asks Beyond the Scorecard

It was half past eleven at night in a small Mumbai flat. The match on my laptop screen had finished a while earlier, but I had not closed the lid. The studio lights were still on, and sitting in front of the camera, Sunil Gavaskar said one short line: India's batting unit needs to show more responsibility.

Fewer than twenty words. Yet the page in front of me was emptier still. The report I was reading had no score, no venue, no date, no innings structure, not a single over described. It had one result — India lost the fourth T20I to West Indies — and one sentence from a former opener.

I scrolled the piece three times. Each time I stopped at the same place: the scorecard was missing. A sentence becomes analysis only when data stands behind it; without data it is atmosphere, and atmosphere can never do a scorecard's job. That, not the match, is the real story here.

Context: what we actually know, and what we do not

From the entire source, only a handful of things are certain. One: a bilateral T20I series between India and West Indies was underway, and this was its fourth match. Two: India lost it. Three: after the defeat, Gavaskar criticised the Indian batting unit and said it needed to show more responsibility.

That is all. Beyond it, there is no venue, no pitch description, no toss, no dew, no DLS involvement, no DRS controversy, no crowd. If someone asks me how many India scored in the powerplay, how the middle overs were strangled by spin, or what the last five overs produced, my honest answer is: I do not know. And saying "I do not know" is the most important sentence in this piece.

The standard frame for T20I analysis splits an innings into three phases: the powerplay (overs 1–6), the middle (7–15) and the death (16–20). Each has its own logic. In the powerplay the field is restricted, so strike rates rise. In the middle, spinners take control and run rates slow. At the death, both risk and reward peak. If India lost, the question should be: in which phase did they fall behind? Answering that requires ball-by-ball data, dismissal modes and partnership lengths. A single word like "responsibility" can survive without them; a diagnosis of where responsibility failed cannot.

The venue question is not small either. Caribbean pitches are often slow and spin-friendly, but they can also be flat. If dew falls, chasing gets easier and the toss decides nearly half the result. Without knowing the venue, I cannot say whether this defeat was a batting failure or a toss-and-dew lottery — and labelling a lottery as a failure of responsibility is journalism's oldest disease.

Nor should the opponent be diminished. West Indies have won the T20 World Cup twice, in 2026 and 2026. They do not sit at the top of the ICC T20I rankings as consistently as India, but in the shortest format their power-hitting depth and varied bowling attack can break any side on any day. India have long been a top-three T20I team, yet their away dominance has been weaker than their home record. This defeat, in other words, is not a neutral-ground upset by default.

A fourth match in a series is the middle or back end of it. In a five-match series, this loss could even hint at conceding the series. That kind of series-level pressure is exactly what makes the voices of analysts like Gavaskar louder. It is not cricket analysis; it is the rule of cricket theatre.

Let me bring in my own work. At Lord's in 2026, England made 228/7 and India were bowled out for 219, losing by nine runs — Anya Shrubsole's 6/46, Punam Raut's 86, Mithali Raj's 71. Watching that match taught me that behind any result lie hundreds of small decisions, and that journalism's job is to make those decisions visible. In 2026, empty stadiums taught me that a newsletter can be a crowd. That lesson is why I am writing this: an empty scorecard is a kind of empty stadium.

Core analysis: what lives inside the word 'responsibility'

"The batting unit needs to show more responsibility" first sounds moral. In fact it is shorthand for a technical demand. In cricket, responsibility usually means a few measurable things.

First, shot selection — the quality of deciding which ball to attack and which to leave. In a T20I there are roughly six balls an over; three or four are worth attacking, the rest carry disproportionate risk. Irresponsibility is not always a bad shot; it is choosing the wrong ball. Catching that distinction needs a ball-by-ball log.

Second, dot-ball pressure. In T20I, a dot ball is silent damage. Five dots waste almost an over, and the pressure compounds into the next over, where a batter forces a shot and loses a wicket. If India lost, was the dot-ball ratio the reason? The source does not say.

Third, strike rotation — the ones and twos, the singles, getting the non-striker back on strike. This is the least discussed part of responsibility. Many critiques count boundaries, when the real gap may be a shortage of singles.

Fourth, role definition. Modern T20I batting separates the anchor from the finisher. The anchor holds the innings; the finisher explodes in the last five overs. A team's problem is often not a lack of responsibility but an ambiguity of roles. If a side has not settled who anchors and who finishes, every batter hesitates in the middle, and hesitation looks exactly like irresponsibility.

Here is my central observation: a source that does not name a single player can place responsibility on a 'unit', but it cannot ask which batter held which role — and without roles, responsibility is a meaningless word.

The West Indies matchup deserves its own layer. Their attack is built on pace and variation: some bowl above 140 kph, others use cutters and slower balls to destroy timing. If India's middle order stalled against spin control, that is not irresponsibility but a matchup failure. Confusing the two is analysis's greatest sin.

Death-over arithmetic is not simple either. Often a match is lost by conceding fifteen extra runs at the death, or by scoring ten too few. But the source provides no phase data at all. So I cannot write that India fell behind at the death, because that would be inference dressed as fact.

Luck factors cannot be ignored. Toss, dew, rain, DLS, dropped catches, DRS controversies — none appear in the source. If I explain a result as a batting failure and it later emerges that dew made the second innings easier, my entire analysis collapses. Finding one cause for one result is a human instinct; the analyst's job is to distrust that single-cause explanation.

The small-sample trap is acute. One T20I is not a trend. A single defeat can be variance; three defeats begin to be a pattern. Concluding "the batting is weak" from one match is statistically immature.

And if the side was rotated rather than full-strength, the arithmetic changes. In India's packed calendar, resting seniors is normal. But the source carries no squad list. So I do not know whether this was a first-choice batting line-up or an experiment — and that unknown determines the weight of Gavaskar's criticism, while the source refuses to determine it.

Now the dimension I cannot avoid. When we demand responsibility of men's cricket, we usually have ball-by-ball data, phase splits and strike-rate graphs — at least we should. With women's cricket the opposite happens. Even six years after the 2026 Lord's final, ball-by-ball data for many matches is hard to find. At the MCG in 2026, Australia made 184/4 and India stopped at 99 — an 85-run defeat, and the rise of sixteen-year-old Shafali Verma. That match was analysed, but mostly in the language of feeling, not data.

I keep asking who is missing from the highlight reel — and why. The answer usually lies in journalistic priorities, not in the quality of the sport. The nine runs of 2026 still echo in every girl who almost made it; yet count how much tactical analysis those nine runs have produced, and the answer is embarrassing.

So what is the real asymmetry? In men's cricket we ask for responsibility on the basis of data; in women's cricket we ask for inspiration on the basis of emotion. Both are two faces of the same emptiness — too little accounting on one side, too much storytelling on the other.

That asymmetry is today's biggest information gain. Before arguing about Gavaskar's remark, we should ask whether the data to test it even exists. For men's matches the answer is often "yes, but nobody is looking". For women's matches it is often "no, because nobody is recording it".

What data would settle this debate? A few specific things: each Indian batter's dismissal mode — bowled, caught behind, lbw, stumped, caught. Each batter's phase-wise strike rate. Average partnership length. Dot-ball percentage. Scoring rate in the overs after a wicket. With those five metrics, instead of the word responsibility we could write: "the number three batted at a 92 strike rate in the middle overs, against a series average of 135." That is not a lack of responsibility; it is a misallocation of roles.

There is another layer: media governance. In India, criticism from former greats functions as an informal accountability mechanism. It is not a formal committee, but its influence is real. It keeps the team under pressure while also placing uneven pressure on selectors. The source shows this dynamic — one former opener's remark instantly became news.

Contrarian angle: the problem is not the batting unit, it is the evaluation system

Here is my contrarian argument. Everyone says India's batting unit was irresponsible. I say the problem may not be the batting unit at all, but the method used to evaluate it. We judge batting with moral words rather than technical ones — and moral words never translate into coaching instructions. "Show more responsibility" — what does a batter change in response? Fewer shots? Fewer runs? A lower strike rate? The answer is unclear. But "drop the sweep against spin in the middle overs, take the single" is a clear instruction, and it comes from data.

A second contrarian point: this kind of criticism often drives selection by narrative rather than evidence. If the team changes after one defeat, is that a statistical decision or a public-opinion decision? The source has no trend data, so I cannot be certain — but the risk is clear, and it is medium to high.

Third, the word responsibility installs a hidden moral yardstick that seats the player in the dock. Yet the same match may contain a toss, dew, or a remarkable spell from a bowler, none of which earns credit in this discussion. If West Indies' bowlers bowled superbly, then blaming only India's batters, without acknowledging that, is an injustice to analysis.

Fourth, the narrative is short-lived. This is the immediate reaction phase, which usually cools within a month, because its fundamental support is weak: no data, only opinion. But short life does not mean small damage, because selection decisions are made precisely during this hot phase.

I also accept that Gavaskar's experience is exceptional. He is a top-tier former opener and a long-standing analyst; his opinion carries weight. But having weight is not the same as having proof. A legend's opinion strengthens a hypothesis; it does not convert a hypothesis into evidence. Miss that distinction and we slide from analysis back into personality-driven journalism.

Forward-looking thought

The next match of the series is the real test. If India's batting unit returns with the same structure and produces a different result, this criticism was the atmosphere of one match, not a trend. If the same collapse recurs, the question shifts from responsibility to role allocation and phase planning.

The real question for me lies elsewhere. When we demand responsibility, how much data do we hold while demanding it — and for whom do we preserve that data? Where there is no ball-by-ball record, criticism is easy and correction is hard. And for the players who never enter the highlight reel, the chance to correct is never created at all.