Amid Pakistan's Winning Run, the Saim Ayub Question: An Unresolved Batting Puzzle Before the Final

Pakistan is currently unbeaten in the home ODI tri-series. Three matches, three wins, and the team has already secured a place in the final. Reading the scoreboard, everything seems fine. But if you look beyond the results and examine the route to them, the picture looks somewhat different. Pakistan's three wins were not identical. The first two came on the Rawalpindi surface where batting was easy and big scores piled up almost automatically. The third came in Lahore, where the team was chasing 242 with nine wickets down and finished the match in the 48th over. That is the match that kept Pakistan unbeaten, but it is also the match that exposes the team's biggest weakness. Because on the day the pitch did not help, the top order collapsed entirely and the win was somehow salvaged by the lower order. During this very series, another major story emerged. The Pakistan Cricket Board announced that young opener Saim Ayub had been released from the squad. Ayub himself requested that he step away from the team and play domestic cricket so he could work on his form and technique. The board respected this request, and after discussion with the head coach, it was decided that the player would be given a chance to prove himself in domestic cricket. This decision was approved by mutual agreement between the team management and the national selection committee. Sahibzada Farhan was added to the team in Ayub's place; he was recently appointed T20 captain but was not part of the original ODI squad. Now two different narratives are running side by side. The first is the one presented by both the board and the player: an honest player admitted his weakness and decided to step out himself. The second is the one the numbers tell. In this series, Ayub managed three single-digit scores in three innings. Adding all three together, his total does not exceed 27 runs, meaning an average of under nine runs per innings. In ODI cricket, a top-order batter is expected to average above 35. By that standard, Ayub's performance was extremely poor. But one thing must be made clear. Three single-digit scores do not prove whether the player has a technical flaw or not. In ODI cricket, a top-order batter can also be dismissed by three good balls in a row. This series does not reveal how he was dismissed, which bowlers troubled him, or what was wrong with his footwork, because none of this information has come out. Therefore it would be wrong to say Ayub's technique is bad. This is only a signal of form. But the most striking thing in this whole episode is not the score, but the player's decision to step out of his own accord. A player who is part of the national team setup, who is playing on home soil, and whose team has reached the final, removes himself from the squad. This can only mean two things. First, the player and coaching staff concluded that the improvement needed while sitting in camp was not happening and he needed to work out in the middle. Second, this is a dignified way of moving out of the selection process while preserving everyone's respect. If you read the board's language carefully, it does not rule out the second possibility. Words like "respecting the player's decision", "appreciating his honest assessment" and "mutual agreement" are exactly what boards use when the decision is partly blended, that is, a name removed but in a consensual manner. This is not the board's fault; this is the style of professional communication, but the reader should read it through this lens. Ayub's departure affects another cricketing dimension. He is a left-handed batter and plays in the top order. His presence keeps changing the bowling angles for opposing captains, because a mix of left-hand and right-hand batters forces bowlers to constantly change line and angle. Who the replacement will be and which hand he bats with is not available information, so the extent of the impact cannot yet be stated. Now let us talk about the innings that kept Pakistan in the series. Chasing 242 in Lahore, the team had lost nine wickets. The last pair put on an unbeaten 89-run partnership and won the match. Shadab Khan's contribution in this partnership was the largest. He scored 113 runs off 96 balls, his first ODI century. His strike rate was around 117, well above the normal average for the lower order while chasing. In the 89-run last-wicket partnership, Haris Rauf contributed seven runs, meaning the bulk of the partnership was built by Shadab alone. This means that roughly 37 percent of the 242-run target was scored by the last pair. This win proves the lower order's spirit, but at the same time raises questions about the top order's performance. The significance of Shadab Khan's innings is not limited to the 113 runs. It is hard to find a player in ODI cricket who can bowl leg spin and also come in at number seven or eight and score a match-winning century. This is considered the rarest squad slot for any team. This innings has raised the ceiling of Shadab's batting, but whether it will change his role, that is, whether he will be promoted up the batting order, is a selection question not answered in this report. One thing should be made clear here: this is only one innings. His ODI batting record outside this century is not included in this information. Therefore, on the basis of 96 balls, he should not be upgraded from a "useful lower-order hitter" to a "genuine all-rounder". Sahibzada Farhan's entry is also worth noting. He recently became T20 captain but was not given a place in the original ODI squad. Now he is joining the team mid-tournament. There are two risks here. First, T20 captaincy and T20 form do not directly correlate with ODI form; this is a general rule of cricket. Second, suddenly placing an ODI burden on a newly appointed T20 captain is a concern from a workload management perspective, especially when a T20 cycle lies ahead. This looks less like a promotion and more like a forced move driven by necessity. Looking at the team's structure, Pakistan's batting situation is very strange. The top order is weak and the lower order is strong. Winning by one wicket after losing nine is proof that the top order left even a 242-run chase to the last pair. The bowling situation cannot be assessed because the series' bowling figures are not available. Questions arise about bench strength, because the replacement is a player who was not in the original squad and is being brought in mid-series without preparation. This suggests that Pakistan's reserve pool of dedicated ODI batters is thin. In terms of age, the team is mixed: Ayub is early in his career, Shadab is at his peak and Rauf is experienced, but in pressure moments the team appears dependent on senior players. The difference between the Rawalpindi and Lahore performances also matters greatly. In Rawalpindi, batting first, the team posted big scores of 305 and 302/9, because that pitch is considered the most favourable for batting. In Lahore, chasing 242, the team stumbled. This makes clear that Pakistan's real strength depends on the pitch. Where the pitch helps batters, the team dominates, but where the pitch is slow or helps bowlers, the team's weakness emerges. This is a common trait of South Asian teams, but from the final's perspective it is also a warning. In a night match in Lahore, dew is likely to fall, which favours the chasing team. This information is not in the report; it is only an inference drawn from the venue and match type. If dew had an effect, the toss result could also have influenced the match and luck would have played a part in the win. Now the question arises of how seriously this unbeaten record should be taken. On the basis of three matches, a team's lasting strength cannot be assessed. Pakistan won all three matches, that is true, but two wins came by big margins and those too on the pitch where it had the greatest advantage. And in the match where the pitch did not help, the win came by one wicket. That is, the big-margin results that make the team look stronger actually came in the most favourable conditions for it. And the closest win, which looks the least glamorous, is the one most worth analysing. Before the final, Pakistan's biggest question is whether the top-order collapse will recur. Finals carry more pressure and less room for error. If a team with strong death bowling comes up against them, the lower order's heroics cannot be repeated every time. The second question is Saim Ayub's. After his departure, the team has neither a fixed return timeline nor any stated criteria he must meet to return to the national team. If everything is not made clear, a narrative will build among cricket fans and the media that Ayub was dropped and dressed up as honesty. This is a question the board should answer quickly so that unnecessary pressure does not build on the player. The injury and workload dimension also cannot be ignored. Shadab played 96 balls and is also the team's frontline spinner. Rauf batted under pressure at the last wicket and likely bowled nearly his full quota as well. In a match that went to the 48th over while chasing, it is natural for the physical burden on these two players to increase. If the team relies entirely on these players in the final, fatigue could show. Therefore rotation should be considered before the final. The way the board handled this episode is also a message in itself. Statements like "respecting the player's decision" and "appreciating his honest assessment" are not just words in a press release; they are an attempt to show that the board is modern and player-friendly. Building this image among sponsors and its own players matters. But the real issue is whether there are written criteria for such a process. If in future another player suddenly requests to step out of the squad in the same way, on what basis will the board decide? This question is important because this one decision has set a precedent. The best approach would be for the board to create a clear process defining in what situation a player will be sent to domestic cricket, when he will be recalled and what criteria must be met along the way. This will increase the credibility of the selection system, not reduce it. One more thing is necessary to understand this whole episode. Pakistan's selection system appears to create separate squads for separate formats with limited overlap between them. That is why T20 captain Farhan was not in the original ODI squad. This is not wrong; it could be a deliberately adopted policy, but the consequence is that when an ODI player has to step out, he is replaced by a player who has not played ODI cricket recently. That is, the replacement is available on paper but not ready on the field. Shadab Khan's century innings can also be viewed from the perspective of his brand. A leg-spin all-rounder who scores a match-winning century in ODI cricket is very valuable in the cricket market, and this directly matters on platforms like franchise leagues. But this is a player-level event, not an industry-level one. This tri-series does not signal any broad market shift. Sentiment in segments like broadcast, advertising and fantasy cricket may remain positive until the final, but beyond that no prediction is possible without data. Now if we put all this together, the picture that emerges is this. Pakistan has reached the final unbeaten; that is an achievement, but the way the team got there is also a matter of concern. The collapse of the top order, the lower order repeatedly rescuing it, a young player leaving the team without a fixed path, and a replacement arriving without preparation: all of this together creates a picture that should not be viewed only through the figures of three wins. This unbeaten record is largely built on pitch assistance, and the team's true capability will be known in the final, when conditions will not be the same and every mistake will have a price. The most important lesson in this story is that in cricket, result and process are two different things. Wins are always counted, but if the story behind a win is ignored, the same story returns as a defeat next time. Pakistan have a chance before the final to fix their weaknesses rather than cover them in the intoxication of victory. The Saim Ayub matter offers an even bigger lesson. A young player admitting his mistake and stepping out to improve himself may be brave, but it will only matter if the path for his return is clear and the system truly supports him. Otherwise it will remain a beautiful veneer of honesty, hiding behind it only the story of being sidelined.