BCB Removed Its Batting Coach Three Days Before Mirpur, and Won't Publish the Data Behind It

That morning Mohammad Ashraful ran a full session with the batters at the Mirpur nets. By that evening the Bangladesh Cricket Board had no national batting coach, and the news reached him through two words on a WhatsApp group: “Thank you.” The first Test against West Indies begins on 28 October at Sher-e-Bangla National Stadium; the second starts 5 November in Sylhet. The headline says four days, the body says three. That small inconsistency tells you everything about the report: it went out unedited, and not one number inside it was published by the board itself.

If you want to prove me wrong, the easiest route is a board statement carrying a date, a time and an evaluation scale. Until then this is an estimated report and I am reading it as one.

Method box — version 1.0 - Source: a single BCB statement; no byline, no named official, no captain or head-coach quote - Tenure: November 2026 – October 2026, as reported - Test record: 8 matches, 5 wins, 1 draw, 2 losses → 62.5%; WTC-equivalent points percentage (5×12 + 1×4)/(8×12) = 66.7% - Unverified: the 2-0 Test win over Pakistan, and the 64 all out in Australia

The open model worked because it admitted what it could not see. The 2-0 win credited to Ashraful’s tenure matches, in my records, the August–September 2026 tour of Pakistan — before he took the job. And as far as my database goes, Bangladesh have never won a Test match in Australia. Either the report describes a timeline I cannot verify, or it has aggregated results from two different eras into one bundle. Either way, the weight on its results narrative is close to zero.

Now the verified part, which cuts against the board.

Five wins in eight Tests. For Bangladesh that is an above-trend return. Converted to WTC points it is 64 out of 96, or 66.7 percent. The sample is small (n=8), so I will call this a signal rather than proof, and the interval is wide. But if Test outcomes were the operative criterion, removing a coach on that record tells you the criterion was something else.

So what was it? The report’s negative evidence comes in three parts: disappointing batting at the Asian Games, disappointing batting at the Abu Dhabi tri-nation, and a 3-0 T20 series loss to Australia in June. All three are white-ball events. Removing a batting coach three days before a Test series on T20 evidence is a category error in evaluation design, not a difference of opinion. The assumption that a coach’s methods transfer frictionlessly across formats is one cricket data has repeatedly refused to support.

The second number, favourite of both the board and the report, is “11 centuries in 34 international matches.” That figure bothers me. Thirty-four international matches pools Tests, ODIs and T20Is, whose base rates for hundreds are not comparable quantities; the pooled number has no analytical meaning. And the deeper point: centuries measure peaks, not consistency. A batting unit can produce eleven hundreds in a tenure and still collapse below 150 repeatedly — a bimodal distribution, common in cricket, not a contradiction. The report uses the centuries as an achievement and “inconsistency” as a criticism without noticing the two are compatible. The diagnostics that should have been published — innings-total distribution, percentage of innings below 200, frequency of three wickets for under 30, average partnership length — are all absent. A clean dashboard is not evidence; it is a question wearing a suit.

The third: 64 all out in Australia. It is the datapoint that stings. It is also one innings. Building a trend from a single innings is the exact habit I have argued against for years. Yes, the floor of this batting order is low, and that is worth worrying about. But the datapoint the board should have decided on was the innings-by-innings distribution, and it is nowhere in the public record.

Fourth, and most relevant: Mirpur. It is Bangladesh’s most spin-dominant, lowest-scoring Test surface. The decisive skill for the batting group in that first Test is not “consistency” in the abstract — it is the sweep, the use of the crease, and the capacity to bat ninety minutes against spin under scoreboard pressure. That is the entire remit of a batting coach. The specialist in that skill was removed three days out, and the interim replacement comes from the board’s High Performance department — a stopgap with no defined horizon beyond “until a permanent batting coach is appointed.”

Now the part that cuts against my own narrative.

I wrote and deleted this line three times today: “This change will cost Bangladesh at Mirpur.” The problem is I have no evidence for it. No public dataset anywhere measures the effect of a batting coach — not with the board, not with me. When I built my possession-value model from a Guwahati hotel room during the 2026 U-17 World Cup, the cleanest lesson was this: data tells you what happened, not whose hand was on it. What a coach can change in a three-day window is not technique; it is confidence, or triage.

So the real risk here is procedural, not performance-based. A coach who ran a session in the morning and was gone by evening implies a board-level decision with no pre-agreed handover. “He will be given another responsibility later” is the standard South Asian board formula, and the missing title, role and timeline make it a polite exit rather than a redeployment. Which is why the question stops being about cricket and becomes one about governance: when no reason is given, rumour becomes the only available explanation, and in the case of a former captain like Ashraful, rumour does the most damage.

From Mirpur’s first session I will log three things: how long the first innings lasted, the score at three down, and whether an innings below 200 arrives. If Bangladesh bat past 300 first up, the argument will not end — it will only be postponed. Because we still have no instrument to measure what a coach change does, and that gap will not close.