Five Defeats in Six at Mirpur: Why the 'Four Causes' Missed the Only Question Worth Asking

I was sitting in the Mirpur press box waiting for one sentence. On the second evening the ground went quiet — and that quiet is always louder than the noise. The ball was turning, the bat was searching for the inside edge, catches were going to slip. Three seconds. But those three seconds had already written the story of the match. I still carry a directional microphone to grounds, for the sound. That afternoon the sound was studs on turf and thirty thousand people exhaling at once.

At the press conference, Najmul Hossain Shanto was asked about batting against spin. His answer came to roughly this: sometimes we play pace well, sometimes we play spin well, we cannot be consistent. It is an honest answer, and honesty is what I respect most about him. As analysis it is close to zero: it names the disease, not the cause.

Almost every piece published the next day contained a list of four causes. The pitch was wrong. The batsmen cannot play turn. Taijul and Mehidy did not put the ball in the right place. The preparation was insufficient. Each sentence is plausibly true. But what happened at Mirpur is not the sum of four parallel causes. It is a chain, and the links in that chain do not carry equal weight.

Start with the number nobody can dodge. Bangladesh have lost five of their last six Tests at Mirpur. That single sentence rearranges the weight of the whole argument, because it says that losing here is not a new experience — it is a repetition. And yet before this Test, Bangladesh were widely billed as clear favourites. On what basis? On the habit of the press, not on the record of the ground.

That is the first difficulty. If the favourite's tag is wrong, the match gets read as an upset. And an upset invites any number of causes you like. Read it as a pattern instead, and only one question survives: why does the same decision keep being made?

The surface this time was built for spin. Within the first couple of hours it was clear the ball would turn. West Indies' spinners took 16 of Bangladesh's 20 wickets. West Indies won by eight wickets. That number is clean, and it is the hardest truth of the match.

The preparation arithmetic is just as clean. Bangladesh arrived from a white-ball tri-series in the UAE with two training sessions in hand. West Indies had a ten-day camp in Chennai plus a warm-up match. Add the change of batting coach and the noise of the domestic auction — both sounds from outside the ground.

This is where the real work begins. If the four causes are read as four separate events, the reader cannot tell which is root and which is symptom. The actual sequence runs like this: the pitch pushed the game towards spin, that pitch opened up an old weakness in Bangladesh's batting order inside the first innings, the pressure of a low score landed directly on the spinners' shoulders, and the preparation deficit sits above all of it. Not four causes — one chain, and we keep grabbing the outermost link, the weakest one.

The hard number is one: 16 of 20. The rest are soft.

"Taijul and Mehidy managed just eight wickets" reads weak, I grant you. But whether eight is bad or good depends on how many wickets fell in total. An eight-wicket win means West Indies probably lost no more than twelve or thirteen wickets across two innings. Eight out of thirteen is roughly two-thirds. That is not "just". Yet the word "just" assigns the verdict before the division is done.

The next number is more troubling: 3.5 degrees against roughly 3.0 degrees of turn. Half a degree cannot carry a conclusion of "considerably more", because no sample size is given, no measurement definition is given — deviation from which line, stock ball or stump line, nothing is specified. Across a few hundred deliveries in a single Test, half a degree can easily sit inside the noise.

There is another sleight of hand. Sometimes the piece says turn, sometimes it says skid. Those are different physical quantities — lateral deviation versus pace off the surface. Merging them into a single verdict that the opposition's spin is stronger means answering two different questions in one sentence. And an average cannot measure variation. The piece itself mentions deceptive arm balls. If the threat came from variation, then comparing average turn is the wrong instrument entirely.

The most important thing is missing from the list altogether: the causal arrow may run backwards. "The spinners could not build pressure" may be an effect rather than a cause. If the first innings ends under two hundred, the spinner bowls in the second innings as the only route to wickets — length stops being normal, risk goes up, variation increases, control goes. The piece treats the symptom as the cause and never accounts for scoreboard pressure.

There is another absence that is not a number. No West Indies team management voice. Not one sentence from the board about the pitch. No explanation of the batting coach's plan. Everyone who made a decision is missing. Only a captain remains, taking responsibility onto his own shoulders with a line about sometimes playing pace well.

Here is my real disagreement. The analysis is one-sided. There is exactly one counterfactual — a pace-friendly pitch would have been better — and no serious effort to rule out the competing explanation: what if West Indies' spinners are simply better than Bangladesh's in these conditions? Then the story is not a preparation error. The story is a personnel gap in identical conditions. The politics of those two stories are entirely different.

Ask a simpler question. What is Bangladesh's record at Mirpur on pace-friendly surfaces? If they lose there too, the pitch is not the root cause — the team is. That test was never run, and it is the one test that would have told us which of the four causes actually was one.

And nobody asked the most important question of all: who chose the Mirpur pitch? The curator, the captain, the coach, the board? Who owns the decision? Until that question is asked, the piece remains an inventory of complaints rather than a search for a decision. If a team makes the same choice six times in five years, it is no longer an individual error. It is a procedural failure — and procedures only change when you know who signs off and which feedback loop is supposed to correct them.

The second displacement of blame is just as clear. "Insufficient preparation" is written as a moral failure of the players. But sending the squad to a white-ball tri-series in the UAE and handing it two sessions before a Test is a board scheduling decision, not a player's choice. The batting coach change and the auction calendar sit on the same level. Loading all of that onto the players as "cause number four" turns a structural problem into a personal one, and the structure survives untouched. This is an old disease of our cricket writing: fierce criticism that never points at power.

The truth is that "four causes" is not analysis, it is a format. A commentary wants four or five bullets for a reader to scroll. But the format demands equality while reality demands hierarchy. Line the causes up side by side and what disappears is proportion — how much each weighed, which one removed would have changed the result, and which one could have changed without anything happening at all. The reader never learns which is root and which is symptom. That is the real loss.

The second Test may start within days. My eyes will not be on the scoreboard but beyond the boundary line — in the curator's room and in the team meeting. First question: will the pitch be the same again? Second: if the first innings passes 250, do the spinners' lengths return? Third: will the board review the schedule at the end of the series, or will we hear again that sometimes we play pace well and sometimes spin?

Shanto's sentence is not false. But it is a confession, not an explanation. And for a side that has lost five of six at home, confession is not enough. What is needed is the open question nobody wants to ask: why do we keep building a Mirpur pitch that breaks our own batting first?