'Focus on your batting': Wasim Jaffer's question about Yashasvi Jaiswal's wicketkeeping, and an unfinished story

On the outskirts of Rangpur, as the light drains out of the evening, the same scene returns almost every week. A left-handed boy puts his bat down, crouches behind the stumps and stretches both hands to practise taking the ball bare-palmed, because there is still no money for gloves. His father stands nearby, checking a phone clock, working out when they must be home. This is not a national camp. It is not a coach's written instruction. It is a quiet habit of possibility.

When the same kind of decision surfaces at international level, the question changes completely. India's former Test opener Wasim Jaffer, reacting to a widely discussed plan around young batter Yashasvi Jaiswal's wicketkeeping, said it plainly: "Focus on your batting." Jaffer's reasoning is almost elementary: a top-order batter's greatest value lies in his batting output, not in adding another skill.

That is where the story becomes complicated. The "wicketkeeping move" at the centre of the debate has never been defined. Is it a decision that Jaiswal keeps wicket in a particular match? A plan to learn keeping as a secondary skill in training? A management suggestion that he be considered a backup keeper? These three possibilities produce completely different outcomes, yet the discussion packs all three into one package.

Context matters. Jaiswal is a left-handed top-order batter who takes on the new ball. His century on Test debut signalled that he might fill a gap Indian cricket had waited years to fill. Jaffer, meanwhile, is the leading run-scorer in the history of the Ranji Trophy, played Test cricket as an opener for India, and has become a reliable voice on batting technique since retiring. Both men come from the world of batting; both are products of the hard school of opening.

That similarity is what makes the episode interesting. When Jaffer says "focus on your batting", it is not merely one former player's opinion — it is the distilled experience of a generation of openers. The man facing the new ball has less time, and less room to split his attention. Learning to keep does not only cost extra hours; it costs a continuous division of focus that collides with the fine timing a top-order batter depends on.

Here the real analysis begins. In the contest between specialisation and versatility, the path of specialisation is usually the more profitable one for a top-order batter. The reason is not tradition but opportunity cost. If an opener trains three hours on batting and adds an hour of keeping, the true value of that hour must be measured in lost precision — the timing of the pull, the decision to leave the new ball, the sharpness of footwork. Keeping runs on a different track: it is essentially a skill of reaction and position, while batting is a skill of prediction and decision.

The arithmetic of opportunity cost is simple, but its consequences are slow. When a young batter learns several roles, his development curve does not merely flatten — it gets pulled in two directions. On one side, the fine work of batting, reading the line of the new ball or using the feet against spin, loses its continuity of practice. On the other, keeping technique is acquired so slowly that abandoning it halfway leaves it useless. The player ends up half-good at two jobs, which in international cricket is almost nothing.

Another dimension is physical. Wicketkeeping loads a batter's body in ways batting never does. Direct impact on fingers and wrists, hundreds of repetitions of squatting and rising, strain on knees and lower back — these look trivial before a Test series but accumulate over six months. Finger injuries are an old, almost inevitable chapter in a keeper's career. Before pushing a batter into that chapter, it is worth asking what the team gains in return.

Then there is team balance. If Jaiswal could genuinely keep, India could field an extra bowling option or an extra batter — attractive on paper. But that calculation collapses when you look at how deep India's keeping pipeline is. When several established keepers are waiting, the strategic case for converting a frontline opener into a "keeper-batter" weakens. Confusing team need with player development is the biggest trap in this kind of decision.

The keeper-batter idea is not new in modern cricket. Several teams already rely on players who bat high and keep, because it frees a squad slot. But that model has succeeded where the player has kept since childhood — alongside batting, not bolted onto it. Learning to keep midway through a career is a different matter, and examples of success there are rare.

The most neglected dimension is format. Curiously, the debate never says which format it is about. Yet keeping's value swings wildly by format. In Test cricket, a specialist keeper and workload management are essential, because five days of keeping is brutal wear. In T20, a keeper-batter can free an entire squad slot, a huge balancing advantage. The same decision is clever in one format and self-defeating in another. Running this debate without naming a format is building a wall with no foundation.

The format question runs deeper. A Test keeper works across five days, roughly ninety overs a session, with the repeated act of rising after every ball. That physical toll feeds directly into a top-order batter's legs and concentration, because batting and keeping use the same neural pathways — eye, hand, reaction. T20 compresses time but raises intensity; there a keeper-batter's value rises because he deepens the batting and fills a fielding slot at once. A decision cannot be separated from its format.

Let me offer something from my own experience. At the 2026 monsoon derby, the Abahani-Mohammedan match, I counted 4,000 umbrellas and learned from the sound of rain on corrugated tin that a crowd is a character. That day too the galleries argued about a young player and what his role should be. My years of watching matches tell me that outside noise about a young talent's role is often louder than the need inside.

A caution is necessary here. Jaffer's authority on batting technique is high, but he is not a specialist in the strategic value of wicketkeeping. That is no fault — it is a common limitation, because every skill in the game has its own school. Stretching an expert's opinion beyond the limits of his expertise is journalism's oldest mistake. What Jaffer says about batting focus carries weight; treating his view as conclusive proof about the technical side of keeper training would not be right.

Another weakness: the source rests on a single quote and a reader poll. No match data, no scorecard, no statistics. A vote between "focus only on batting" and "trying keeping could be useful" compresses a complex development question into yes or no. Such polls measure mood, not truth. In Indian media, the predictive reliability of these "should he or shouldn't he" debates about young stars has historically been low.

Media habit deserves a place here too. In Indian cricket journalism two narratives about young talent form fast — "the next great star" or "the talent crushed by pressure". The middle ground, where most young players actually live, is less attractive. So an ordinary training decision becomes a national debate within days. Jaffer's comment fuels that narrative because a former Test player's voice makes an ordinary opinion sound significant.

Now the other side. In modern cricket, the "multi-skilled player" is a live current. Teams look for players who can handle more than one role, because squad limits, injury cover and travel demands all require flexibility. In that context Jaffer's advice runs against the modern current. The question is therefore not about Jaiswal; it is about the philosophy of the game: will specialisation still rule, or will flexibility overtake it? The answer shifts with format, team depth and the player's age curve. In Jaiswal's case, youth itself argues for specialisation — because adding a second skill at the very start of a career can become an irreversible decision.

The age curve is decisive. A player's first three or four years are when fundamental technique sets. Hand position, stance and the habit of decision-making against the new ball are formed now, and carried for the next decade. The ideal moment to add a second skill usually comes later, once the primary skill is solid and the player understands his own game. In Jaiswal's case that first window is still open, and that is what gives Jaffer's argument extra weight.

The biggest gap, though, is elsewhere. The trigger event — the report or camp announcement that started this debate — is absent from the piece. So the reader cannot know whether this is a serious role change, a training experiment, or merely a backup plan. If it is a low-risk experiment, Jaffer's objection loses much of its edge. If it is a genuine role change, the objection is not just reasonable but essential.

"The rain arrived before the match, and so did we" — that line comes back to me in every unfinished cricket story. The Jaiswal case is the same: we wrote the forecast before the rain, while the ground is still wet.

So what should we watch? Several signals, together. If an official announcement actually assigns a keeping role, that is the first proof. Alongside it, watch whether Jaiswal's batting output changes after any keeping involvement. And watch the availability of keepers in the national set-up — a vacancy would suddenly raise the strategic value of a "keeper-batter" option.

The most important signal is off the field: if a second or third prominent voice joins, a small question becomes a big narrative. To me the real question is not Jaffer's, and not Jaiswal's. It is ours: will we let a young batter's bat tell his own story, or turn every decision into a debate before it happens?

"A cathedral can be silent and still be singing" — an opener's batting is like that. In the noise, his best answer lives in silence, and is written only on the scoreboard.