Lost in the First Seven Overs: Bangladesh's Batting Collapse Against Afghan Spin

The evening at Sharjah began with an odd silence. Watching Bangladesh's openers warm up, one might have thought the pitch was a batting paradise. But before the seventh over ended, the scoreboard read 28/4. Sitting beside the commentary box, cross-checking the scorecard, I felt the story of this match had already been written in those first seven overs. The remaining 34 overs were merely an explanation of that story. Bangladesh won the toss and elected to bat. On a neutral venue, on the UAE's dry, slow surface, batting first meant preparing the wicket for the spinners. Yamin Ahmadzai struck twice in the first over, and Azmatullah Omarzai added two more. 28/4 in the powerplay meant that although Bangladesh had 43 overs of batting left, their top order could not use them. A 93-run fifth-wicket partnership offered some hope, but from 121/4 to 160 all out—the last six wickets fell for just 39 runs. Rashid Khan's 4-31 (8.2 overs) was at the heart of that collapse. This spell from Rashid was the most valuable performance of the match. Four wickets while conceding at an economy of 3.7 in the middle overs—combining run-stopping with wicket-taking. For a spinner in ODI cricket, that is the ideal. The interesting part is that Rashid did not bowl his full 10 overs. Eight overs and two balls—meaning he was used in two bursts, not as a stock bowler but as a strike weapon. On the UAE pitch, the pair of Nabi and Rashid became poison for Bangladesh's middle order. But perhaps the biggest discovery of this match was Parvez Hossain Emon's 70 runs off 96 balls. In a match where the team was bowled out for 160, the top scorer is a youngster. But his strike rate of 73 is somewhat slow for a top-order batter in modern ODIs. The question is: was it the pitch's demand, or a limitation of Emon's own game plan? He was tasked with rebuilding from 28/4, so perhaps he did not take risks. But in the end, the team folded in just 41.2 overs—meaning the batting resources of the last 8.4 overs were never used. Afghanistan's innings looked like an easy win. Seven wickets, 87 balls remaining. But the start was not easy at all—39/2. It was Rahmat Shah's 67* (90 balls) that turned the match. He built partnerships of 56 and 66 to hold the chase together. His strike rate of 74—in a 161-run chase, with wickets falling, that tempo is ideal. This is the definition of a captain's innings. Taskin Ahmed's 2/36—the only Bangladesh bowler who threatened the Afghan batsmen. But the other bowlers could not sustain the pressure. Now comes the question that will shake Bangladesh cricket beyond this match. 28/4 and then 121/4 to 160—two collapses in one match. Is this just a bad day, or a structural weakness? I think Bangladesh's top-order crumbling against Afghan spin on a UAE pitch is nothing new. Outside the subcontinent, especially in spin-friendly conditions, Bangladesh's batting collapses in the same way repeatedly. The selectors should think about this. Afghanistan's win, however, did not depend solely on Rashid. Yamin's new-ball spell, Omarzai's two wickets—together their bowling plan was phase-based. Attack in the powerplay, pressure in the middle overs, then Rashid-Nabi at the end. This is a complete ODI bowling blueprint. But the Afghan camp should also have a worry. How does this bowling attack look without Rashid? Without Nabi? Both played in this match, so there was no problem. But in a major tournament, if even one gets injured, Afghanistan's spin dependency could become a boomerang. In the end, this match knocked Bangladesh out of the tournament, and Afghanistan advanced to the final against Zimbabwe. Afghanistan's success in UAE conditions is nothing new—they play almost like a home team here. But for Bangladesh, it leaves a tough question: when will their top order learn to survive the new ball? If they again lose three wickets for 40 runs in the next matches, it will no longer be an accident but a habit.