The result cast doubt on India’s batting order decisions, particularly the decision to move Shivam Dube to No. 4 in place of Shreyas Iyer. India suffered their second Twenty20 International defeat to the West Indies in Ranchi on October 9, 2026. The visitors tied the five-match series at 1-1 by chasing down 249 with six wickets remaining. The West Indies secured their most successful T20I chase in 18.3 overs, despite India’s score of 249-5 in the match.
Shivam Dube‘s endeavour to secure the advertized time slot was unsuccessful. Roston Chase, who recorded 3-24 in the innings, dismissed him after he scored only 7 runs off 10 deliveries. During the post-match media conference at JSCA Stadium, head coach Gautam Gambhir addressed the decision to promote Shivam Dube and offered an explanation.
Performance and advancement of Shivam Dube in Ranchi
The Indian head coach emphasised the importance of his team management strategy and the need to adjust positions in response to opposition bowling attacks and match circumstances. Gambhir has consistently maintained that adaptability in the middle order is essential for T20 success since assuming the team’s leadership. However, the decision to deploy Dube against Chase, who was demonstrating success against Indian left-handed pitchers, has been met with criticism.
Also Read : Simon Harmer Hopes for Two-Spinner South Africa Attack at Kingsmead
Gambhir also commended the West Indies’ bowling performance. He expressed his gratitude to all-rounder Roston Chase for his exceptional ball-playing performance, which was instrumental in the visitors’ successful pursuit. Despite the defeat, the head coach of India declared that the team would continue to experiment with batting positions as part of their T20I strategy.

Covering the latest cricket news, match updates, player performances, statistics, records, tournament highlights, and important developments from the world of cricket.







[…] Also Read : Shivam Dube Struggles in 2nd T20I as Gautam Gambhir Talks About Team Flexibility […]
Comments are closed.