Gavaskar's 'Responsibility' and the Match Whose Scorecard We Never Saw
**Core answer**: চতুর্থ টি-টোয়েন্টিতে ভারত হারের পর সুনীল গাভাস্কর ভারতীয় Batting ইউনিটকে More দায়িত্ব দেখানোর আহ্বান জানিয়েছেন। প্রতিবেদনে স্কোরকার্ড, ভেন্যু বা তারিখ নেই, তাই হারের প্রকৃত কারণ যাচাই করা সম্ভব নয়। **Key facts**: - সুনীল গাভাস্কর প্রথম ব্যাটসম্যান যিনি টেস্টে ১০,০০০ রান করেন; তাঁর ৩৪ সেঞ্চুরির ১৩টি ওয়েস্ট ইন্ডিজের বিরুদ্ধে। - ওয়েস্ট ইন্ডিজ পুরুষ টি-টোয়েন্টিতে দুবার বিশ্বচ্যাম্পিয়ন — ২০১২ ও ২০১৬ সালে। - ভারত চতুর্থ টি-টোয়েন্টি হেরেছে; ম্যাচটি ভারত-ওয়েস্ট ইন্ডিজ দ্বিপাক্ষিক সিরিজের অংশ। - প্রতিবেদনে ভেন্যু, তারিখ, স্কোর বা Inningsের তথ্য নেই; বিশ্লেষণ কেবল একটি উদ্ধৃতির উপর দাঁড়িয়ে। **Source attribution**: সূত্র: Stage-2 গভীর পেশাদার বিশ্লেষণ প্রতিবেদন; মূল ম্যাচের ভেন্যু ও তারিখ উল্লেখ নেই, তাই সুনির্দিষ্ট ক্যালেন্ডার তারিখ নিশ্চিত নয়। | Cross-checked: cricsultan.com **Related Q&A**: Q: এই হারের পর ভারতের Batting অর্ডার কি বদলাতে পারে? A: প্রতিবেদনে কোনো নির্দিষ্ট খেলোয়াড়ের নাম নেই, তাই নির্বাচন পরিবর্তনের পূর্বাভাস দেওয়া যায় না। Q: গাভাস্করের সমালোচনা কি ডেটা-সমর্থিত? A: না; উদ্ধৃতিটি মতামত-ভিত্তিক, এবং বল-বাই-বল ডেটা ছাড়া এটি যাচাই করা সম্ভব নয় — দেখুন cricsultan.com Player Depth Index। Q: টি-টোয়েন্টিতে ওয়েস্ট ইন্ডিজ কি ভারতের চেয়ে শক্তিশালী? A: আইসিসি র্যাঙ্কিংয়ে ভারত এগিয়ে, তবে টি-টোয়েন্টি বিশেষজ্ঞ হিসেবে ওয়েস্ট ইন্ডিজ সর্বদা প্রতিদ্বন্দ্বী।
On a fourth-floor balcony in Dhaka, I watched the fourth T20I of the India–West Indies series on a phone stream running three seconds behind my neighbour's radio. The same ball happened twice — once in my ear, once in my eye. The match was over, and the scorecard still hadn't settled in my head. Into that gap came Sunil Gavaskar's voice, soft as a blade: "The batting unit needs to show more responsibility."
The sentence reached the tea stall before it reached my ear. One man said the openers were rushed. Another said the middle order couldn't hold the chase. A third, who hadn't watched the match at all, declared with total confidence that the captain had made the wrong call. I stayed quiet and asked myself what we had actually watched — a match, or a sentence? In eight years of this work I have learned that cricket's most powerful thing is never the ball or the score; it is a sentence that spreads after play and then covers the play.
The setting looks simple, and that simplicity is a trap. This is a bilateral T20I series, India against West Indies, and India lost the fourth match. That much is certain. Where it was played, on what date, who won the toss, how the pitch behaved, what India scored or chased — none of it is in hand. We have a result and no process. In cricket analysis that is the most dangerous position to occupy, because without process you cannot explain a result; you can only judge it.
The man who spoke carries weight. Sunil Gavaskar was the first batter to reach 10,000 Test runs, and 13 of his 34 Test centuries came against West Indies, the side that once assembled the most feared pace attack in the world. A man who stood in front of that attack and scored at that volume does not sound light when he says "responsibility." Add that Gavaskar has been one of Indian cricket's most fluent broadcast voices for decades, and his criticism often carries a moral lesson rather than a match report.
West Indies, meanwhile, are two-time men's T20 world champions, in 2026 and 2026. India sit consistently in the ICC top three; West Indies often drift outside the top five — yet in the shortest format their power-hitting depth can squeeze any side on any night. Ranking and format-specialism are different things, and that gap is the shortest format's great uncertainty.
Indian cricket carries another layer this debate usually skips. The calendar is so crowded that squad rotation is normal. Some players rest, some return from injury, some get a first run. In that condition, one match's failure cannot establish a team's permanent weakness. The question lingers: did India field a full-strength side in this fourth T20I, or an experimental one? Without that answer, the weight of the criticism stays unknown.
One clarification matters here: this discussion is locked to T20I. A single T20I cannot settle questions about ODI or Test cricket. Change the format and the question changes, the definition of responsibility changes, and the batter's role changes.
The real event of this report did not happen on the field; it happened in language. "Responsibility" is among cricket's least falsifiable words — it is a feeling, not a measurement. When someone says the batting unit failed to show responsibility, the reader has no way to disprove it, because we hold no ball-by-ball list of which shot was reckless and which was aggressive-but-justified. Nor can we prove it. The sentence sits outside verification, and a sentence outside verification is the most dangerous thing in cricket talk, because the louder it is said, the truer it sounds.

"Batting unit" is itself an abstraction, and that abstraction is the critic's greatest convenience. Blame the whole unit without naming one batter, and nobody faces individual accountability. Which batter fell to an unnecessary shot, who slowed the tempo and raised the pressure, who lost the match in the final over — with no names, the blame belongs to no one and everyone. In media, this is a familiar device: an abstract accusation lands on no single shoulder while hanging over all of them.
From my years of watching matches, I can say the sharpest damage from this kind of remark lands on selection. When a former great says on television that the batting unit lacked responsibility, the next XI may quietly drop a young batter — even though the data says a single match's failure cannot define anyone's ability. A T20I defeat is not a trend; it is a sample, and leaping from a small sample to a large conclusion is analysis's oldest trap.
What would we see if the evidence existed? A T20I innings needs at least four layers. Scoring rate and wicket loss in the powerplay — did India attack or fold in the first six overs? Strike rotation against spin in the middle — did the ball turn over from overs seven to fifteen, or did it stick? The boundary-to-dot ratio at the death. And the mode of dismissal — how many outs came from big shots, how many from good balls. Not one number from these four layers is in our hands. Where there is no measurement, "responsibility" is not analysis; it is a moral remark.

There is a further layer usually left out. The cause of the defeat could be batting alone, or batting could be no cause at all. Perhaps the bowlers leaked runs in the powerplay, perhaps the death-over economy climbed, perhaps two catches went down. India could even have won the match because of its batting, with the bowling losing it in the final over — we don't know, because there is no scorecard. Gavaskar's criticism points at batting, which lets us infer batting failure was the main cause. But inference and evidence are different things, and a commentator's view is not a dataset.
In T20I, responsibility means balancing risk and reward. Attacking in the powerplay is not irresponsibility; it is necessity. Holding patience against spin in the middle overs is responsibility. Rotating strike at the death is responsibility. Without knowing which phase broke, saying "not enough responsibility" blurs an entire innings into one vague picture. That vagueness hands selectors a dangerous tool, because a vague blame can be pinned on any player.
In Indian cricket, the voices of former greats act like an unwritten governance. Standing between the selection committee, the coaching staff, and the media, a former captain's sentence can shape the next series' squad. It is not a formal rule, but it is real influence. That is why such remarks cannot be read as opinion alone; they are a kind of pressure arriving from outside the process.
The outcome of that pressure is not always good. After one defeat, when the debate heats up, fan expectation and media tone together press the selectors. Patience then looks like weakness, and change looks like courage. But in a format as volatile as T20I, patience is the deepest strategy — because the format itself is built so that the best side loses and the weakest side wins.
Here is my objection. We remember the critic's sentence and forget the match. Collective memory keeps the speech, not the defeat. Twenty years on, when someone recalls this series, no one will remember who scored what in the fourth match — but the Gavaskar line will survive. The criticism becomes history, and the match becomes background. In cricket memory, this reversed order is the most common sight: we write the history of remarks, not the history of play.
We naturally assume the batting lost, because the criticism is about batting. But that logic runs backwards — we are inferring the result from the criticism, not the criticism from the result. Had the report described a bowling failure, we would now be discussing "the death bowling lacked responsibility." Our frame of memory is not the truth of the match; it is the loudest sentence.
From Dhaka, this becomes clearer. We watch India's crisis in our own mirror — like hearing a neighbour's argument through the wall, the words unclear but the anger legible. Our stream lags three seconds, our commentary is in Bengali, our radio belongs to the neighbour. We watch the match through a translation, and translation loses fine process first, keeping only the dramatic sentence. Gavaskar's sentence is more real to us than the match, because the sentence survives translation and the ball does not.
Watch the next match not only for the scoreline but for two questions. Is India's batting order staying the same, or shifting under the weight of the criticism? And if it shifts, is the decision built on data or on a television sentence? And when the next report arrives, will it carry a ball-by-ball account, or only a sentence?

I do not know what actually happened in the fourth T20I. I have a result, a quote, and the three-second lag of that stream, which keeps me thinking. The question is not about Gavaskar — it is about us. Do we watch cricket, or do we watch the loudest sentence said about it? On the evening a result arrives before the process, who is responsible — the batter, or us, who write the verdict without a scorecard?
