Taijul's Omission Isn't the Story — Bangladesh's Batting Is

February 2026. I was sitting at Lahore Qalandars' three-person analytics desk, handed the job of building a 214-player valuation sheet because the franchise had finished bottom of PSL 2 with three wins from eight. Every domestic cricketer with a T20 strike rate above 120 across the previous two National T20 Cups was on that sheet. The franchise ignored half of it. The half it used — three Emerging picks — outscored its Platinum signing across the season. Since that day I have attached a sample size to every claim: if a number cannot survive the question "how many balls is this built on?", it does not make the paragraph. Reading the report that Taijul Islam has five wickets in his last four Tests, and that Amite Hasan has been added as Mominul Haque's concussion replacement, the same rule applies — because the material question here is not Taijul's place, but the batting unit that has not won in any format since August.

The selection problem Bangladesh face before the Sylhet Test only makes sense against the Dhaka backdrop. The pattern of the first Test was clean: West Indies' spinners — Roston Chase, Jomel Warrican and Rahkeem Cornwall — took 16 Bangladesh wickets between them, while the hosts' spinners took eight, all in the first innings. In the second innings the spin threat collapsed entirely. What head coach Phil Simmons said afterwards matters more than the selection debate: he stated plainly that Bangladesh's larger concern is its batting, that the players' preparation and work ethic were not in question, and that the gap was match-day execution. That is not a coach's shield; it is a process-oriented message that gives a losing side a direction. And the losing run is long: since winning the Darwin Test in mid-August, Bangladesh have not won in any format — two defeats at the Asian Games, a winless UAE ODI tri-series, and now the Dhaka Test.

Taijul's numbers are the most misleading part of this story, because "five wickets in four Tests" is a figure that leads to the wrong conclusion when read without context. First: at 34 he sits exactly at the edge of the typical spin decline zone, not past it. Second, and more important: his left shoulder is injured, and reports say that injury is affecting him most. For a spinner the shoulder is not merely a joint; it is the entire biomechanical base of revs, arm speed and drop. When the shoulder is compromised, loop, drift and turn all suffer — and that is not "losing form", it is "bowling hurt". Third, and this overturns the whole debate: inside that same lean window comes his 7/138 against Zimbabwe in Harare in July. Bangladesh lost the match, but seven wickets is a strong individual return. When a seven-wicket haul sits inside your bad-form window, the diagnosis of "his bowling is gone" becomes very weak. The fair technical read is: injured and out of rhythm, not a 34-year-old in decline. Dropping your country's highest Test wicket-taker on form alone risks mislabelling an injury effect as a skill collapse.

The Sylhet pitch argument is the real key to this selection debate, and here the original reporting leaves a gap. Sylhet is being described as a surface where fast bowlers are expected to have an impact — unusual for Bangladesh, where home tracks usually favour spin. If true, picking a seam-led attack is a rational, conditions-led gamble. But two things need saying. First, this is a one-Test, one-venue decision, not a verdict on Taijul's career. Second, the report never establishes why Sylhet is thought to seam. If the team goes in without a left-arm spinner on such a surface, it is a structural rebalancing rather than a like-for-like swap — and that is the actual risk. Bowling a shoulder-compromised spinner defensively on a seamer-friendly track, or holding him back entirely, mismatches the workload in either direction. Simmons' comments are silent on whether this is rest or demotion, and that ambiguity is the biggest uncertainty in Taijul's career narrative.

Amite Hasan's story is the most interesting element of this crisis — not just because of his numbers, but because the coach himself is cooling the hype. Amite's domestic record is excellent: three first-class double-centuries, the latest in the National Cricket League, and a batting average of 62.23. As a wicketkeeper-batter his value doubles, because he offers selection flexibility. But he has played one Test, against Zimbabwe in July. A 62.23 average is not a predictor until you know the innings count, the quality of opposition and NCL conditions; domestic first-class figures often inflate on friendly tracks and small all-round samples. The original report calls him "arguably the best domestic batter in five years", but that label is the writer's opinion, not a verified ranking. And Simmons himself said publicly that the level of international cricket is substantially different from domestic cricket — the most analytically important quote in the piece, because a coach is publicly tempering a domestic star's fever. Amite was added as Mominul's concussion replacement, and it is possible he does not play at all. That means he is not an immediate option but a future investment and squad cover.

There is a counter-intuitive side here that cannot be ignored: Bangladesh were beaten in Dhaka by their own spin-reliant home model. The template that defines this team — crushing opponents with spin in home conditions — was reversed, as West Indies' three spinners bowled the hosts out 16 times. This is Bangladesh's long-standing vulnerability to quality spin surfacing at home, a problem usually associated with away tours. Opting for seam in Sylhet is adapting to conditions, but it carries a side-effect: it shows the team reacting to conditions rather than dictating them. In a multi-format losing run, dropping a senior player is often the easiest way to "do something", and that is precisely where injury management and batting-structure repair get lost. Simmons' process-oriented language is a partial safeguard against that instinct, but it is not a batting solution.

The biggest risk here is not Taijul's selection but the batting unit's repeated collapse against spin. Changing one bowling slot may change a match; rebuilding a batting structure changes results. A second risk is running alongside: Mominul's concussion and Mushfiqur Rahim's finger injury have destabilised the middle order in two places at once, deepening the instability the coach has already flagged. A third is incomplete information: Taijul's five wickets, Amite's 62.23 average and the 16-wicket spin figure are all single-source, unverified numbers. Until they are cross-checked against ESPNcricinfo or the ICC database, treating them as final truth is dangerous. That discipline is what I learned in 2026, when I hand-coded all 64 World Cup matches and tried to port xG to cricket — cricket's discrete wicket events, limited ball counts and single-innings samples are dishonest with metrics borrowed from football. I published the part of that series where the model broke, because boundary conditions matter more than findings.

The signals to watch before the Sylhet Test are clear and measurable. If the pitch genuinely seams, omitting Taijul will be rational — but it must then be clear whether this is rest or demotion. If Taijul is rested and Bangladesh lose, a backlash about dropping the record wicket-taker will build quickly. And if the batting collapses below 200 again in the first innings, it will prove the real problem is not a spin selection but the spine of the batting order. For me the question is not whether Taijul plays — it is whether Bangladesh are picking the attack that can control Sylhet's conditions, or making a reactive change in a losing run that the data will audit without mercy over the next six months.