An ODI Glow, a T20I Call-Up: The Question Nobody Is Asking About Amir Jangoo

Last week, sitting at home in Sydney, I opened the three scorecards of the West Indies–India ODI series one after another. Fifty-eight not out in the first match, 114 in the second, 67 in the third. The same batsman, three different days, three different situations — runs every time. To me, Amir Jangoo's consistency did not look like an isolated explosion; it looked like a pattern. And right then the news arrived: because of Jewel Andrew's finger injury, Jangoo has been added to the five-match T20I series squad as cover. That is where my first doubt was born. Valuing a player for one format on the runs he made in another — this reasoning looks so natural in cricket, yet is so weak mathematically. Many people treat ODIs and T20Is as two editions of the same game. To me they are two separate economies. In ODIs there is time to build an innings across 50 overs — you can defend, rotate strike, control risk. T20Is have no such luxury. There the only currency is strike rate — how many runs per 100 balls. However fluent a batsman is in ODIs, whether he can fulfil the compressed arithmetic of 20 overs is an entirely separate question. Just as in football, when the Euros and Olympics collide, I stop treating fatigue as a weakness and start counting it as a tactical variable, in cricket too a change of format means a change of unit. Let me come to the actual point. Jangoo is a 29-year-old wicket-keeper batter whose international debut came in December 2026. His call-up has one very specific cause — as cover. That is, this is not an assured place in the first XI; it is a conditional addition. The X-ray on Andrew's finger injury showed no fracture, and he has not yet been ruled out; he is merely under observation. That means Jangoo's role is still fluid. The moment Andrew returns fit, Jangoo's need may evaporate; and if the injury drags on, he could suddenly become the main reliance. The series is on Indian soil, across five different venues — Lucknow, Ranchi, Indore, Hyderabad, Bengaluru. A five-match T20I series in India is one of the toughest away assignments in the format. For West Indies as the touring side this is a big handicap, because conditions, crowds and pitches all favour the hosts. And five venues mean long travel, little recovery, and extra load for a specialist role like wicket-keeping. That is exactly why not just the first XI but the depth of the whole squad becomes decisive here. Jangoo's ODI record is genuinely strong. Two hundred and thirty-nine runs across three innings, the third-highest run-scorer of both teams — only Shubman Gill and Shai Hope are above him. Contributing three times in three matches means this is not a one-match fluke. But one thing must be added here: the third ODI at New Chandigarh (Mullanpur) produced a record successful chase. A record chase usually signals a true-bounce, batting-friendly pitch. In other words, the surfaces on which Jangoo made his 239 runs were kind to batsmen. Whether the same output would have come on a turning or seaming wicket remains an open question. Now to the T20I arithmetic. Jangoo has 163 runs in seven T20Is at a strike rate of 120.74. In the modern T20I game the normal strike rate for a top-order or middle-order batsman is 130 to 145; for finishers, above 150. The expectation for a wicket-keeper batter is even higher, because he earns his place through a dual role — gloves and bat, both. 120.74 is low by that benchmark. So there is a clear contradiction here: the man being called up on ODI form has an existing T20I record below the benchmark. Of course, it must also be remembered that seven matches is a very small sample. In a small sample the uncertainty around a strike rate is high; a good series could quickly lift 120.74 toward 135. So the low strike rate is a caution flag, not a final verdict. The more I map the pitch, the more I feel that runs are really a story of controlling space; for Jangoo the question is this — can he hold that control in the cramped space of 20 overs? The age question is tied in here too. Twenty-nine means he is not a young prospect but a seasoned domestic performer. The batting peak is usually 27 to 33. He is right in that window, yet he has entered the international stage very late. There is a positive side — greater short-term reliability; and a limitation — there is no long-term development story here. The rising star framing is therefore misleading. There is another gap in this report that many may not notice: nowhere does it say who won the series. The framing is therefore individual-centred — one player's runs in front, the team's result behind. This habit hides a familiar journalistic device: covering team context with individual sparkle. Yet a player's value in a T20I side is set by the team's balance, not by his runs alone. Here is my real objection. The adjectives in this headline — stunning, sparkling — come from ODI runs. But the criterion for earning a place in a T20I side is not those adjectives; it is cold numbers. When media framing runs faster than format-specific data, a gap opens between expectation and outcome. I call this cross-format contamination — the analytical error of using one format's performance metrics to build another format's expectations. The second thing that is not easily seen: this call-up is as cover. Cover usually means time-limited and revocable the moment the incumbent is fit. That is, Jangoo's squad status is provisional by its very construction. If that condition is lost, the whole story becomes a misunderstanding — as if he were a certain pick, as if he were a reward for form. In reality he is one piece of contingency planning. And another angle — the more I have covered cricket, the more I understand that the second screen is now part of the stadium. Where the scorecard, strike rate and pitch-map are in the palm of the hand, the viewer is also an analyst. And if that viewer, seeing Jangoo's ODI runs, takes him for a T20I messiah, the disappointment will form not only in the result but in the structure of expectation itself. West Indies' wicket-keeper depth weakness is also exposed here — one keeper gets injured and a cover must be summoned mid-tour. Top sides usually carry two ready keepers, so that one injury does not break the whole balance. There is one more layer hidden inside this decision. Jangoo's clearest route into the T20I side is actually not the bat but the gloves. The main reason for his selection is keeping; batting is the secondary argument. But the media framing reverses this — it puts the ODI runs in front and pushes the keeping role to the back. This swap is what distorts the balance of expectation. One comparative context is relevant here. Sides like England or Australia have a ready pipeline of wicket-keeper batters; if one is injured, another is ready. In West Indies' case a cover must be summoned mid-tour — this is not merely individual misfortune but a signal about squad structure. So across the next five matches I will watch three things. First, when Andrew is declared fit — that will decide whether Jangoo sits on the bench or plays in the XI. Second, if Jangoo plays, whether his strike rate climbs toward 130. Third, what position he is sent in — top-order or keeper only. Read these three pieces of information together and it will become clear whether the ODI glow truly lit up in T20Is, or whether it was merely one format's good fortune.