Sunil Gavaskar Defends Gautam Gambhir's Decision: The Left-Handed Batting Strategy Behind Promoting Axar Patel to No. 5

Gavaskar Defends Gambhir's Decision, but Wellington Conditions Raise Questions About India's Selection Strategy

The decision to send Axar Patel ahead of KL Rahul at No. 5 during the second ODI between India and New Zealand in Wellington became one of the major talking points after the match. India eventually secured a four-wicket victory through the Duckworth-Lewis-Stern (DLS) method, but the middle-order adjustment during the chase raised questions about the team's batting strategy. Former India captain Sunil Gavaskar, however, supported the decision taken by head coach Gautam Gambhir and captain Shubman Gill. His argument was that introducing a left-handed batter forces opposition bowlers to adjust their lines and lengths. The change can create opportunities not only for the incoming batter but also for the right-hander at the other end.

The immediate result on the field did not favour the strategy. Axar Patel was dismissed for seven runs off 17 deliveries. After his wicket, India were reduced to 47/4, leaving KL Rahul and Shreyas Iyer with the responsibility of managing the chase. This distinction is central to evaluating the decision. The intention behind a tactical move and its actual outcome are two different things. Gavaskar highlighted that distinction, saying that had Axar scored runs, the captaincy decision would have attracted praise. In his assessment, such experiments sometimes work and sometimes fail to produce the expected result.

Match Context: A Target of 135 and Pressure from Early Wickets

In the second ODI at Wellington on November 7, 2026, New Zealand were dismissed for 134 in 41 overs. India's fast bowlers prevented the hosts from building a substantial total. Gurnoor Brar claimed four wickets for 30 runs, while Auqib Nabi and Anshul Kamboj took two wickets each. Daryl Mitchell attempted to hold the innings together with 55, but the remaining batters struggled against India's bowling attack. India needed 135 runs to win. On paper, the target appeared manageable, but batting on the Wellington surface proved considerably more difficult.

India's innings exposed that difficulty early. Shubman Gill was dismissed without scoring. Virat Kohli returned to the pavilion after making seven, while Rohit Sharma could not progress beyond 23. Following those early wickets, India were 39/3. The team management faced two options. It could send specialist middle-order batter KL Rahul to stabilise the innings, or promote left-hander Axar Patel to disrupt New Zealand's established bowling lines and lengths. Gambhir and Gill chose the second option.

Axar was sent in at No. 5, with Rahul following him in the order. The decision prioritised a left-right batting combination. However, New Zealand's bowlers exploited the conditions and did not allow Axar to play freely. He was dismissed for seven from 17 balls, leaving India at 47/4. That situation intensified the selection debate because the alternative of promoting an experienced batter such as Rahul had been available.

Gavaskar's Argument: The Strategic Value of Changing the Batting Order

Speaking during a post-match discussion on Sony Sports Network, Sunil Gavaskar explained the thinking behind Axar's promotion. He said that when bowlers who have been operating against a right-handed batter suddenly face a left-hander, they have to adjust their line and length. During that adjustment, their accuracy can be affected. The direction of their deliveries may change slightly from the areas they had originally targeted against the right-hander. That can create scoring opportunities for the batter at the other end as well.

Gavaskar made it clear that there was nothing wrong with the underlying thought process. He said that if Axar had scored runs, the captaincy would have been praised, but the experiment had not worked on this occasion. He also pointed out that a strong batter such as KL Rahul was available after Axar, giving the management room to experiment. His comments are important because they suggest that the batting order was not determined solely by individual batting ability. The team was also attempting to disrupt the opposition's bowling plans.

The most important part of Gavaskar's argument is that he separated the quality of the decision from its immediate result. In cricket, the batting order is not an entirely fixed list. It can be adjusted according to match circumstances. However, every adjustment should have a clear purpose and the selected player must be suited to the intended role. The purpose of promoting Axar was to create a left-right combination. That combination could become useful only if the batter survived the initial deliveries and took advantage of the changes in the opposition's lines and lengths.

The Left-Right Combination: How Does the Strategy Work?

The use of left-right batting combinations has long been an option for captains and coaches in ODI cricket. One of its immediate effects is on the bowler's angle and line. When a bowler is operating against a right-hander, the arrival of a left-hander may require a change in line. The bowler may have to adjust the run-up, release point, angle and fielding positions. If the adjustment is not made quickly, the batter may find additional scoring opportunities.

A second effect concerns field placement. The captain may have to modify the field to accommodate the new batting combination. When the two batters use opposite hands, it becomes more difficult for the bowler to apply exactly the same plan continuously. However, this does not mean that every left-handed batter automatically creates a problem for the opposition. Bowling pace, swing, bounce, accuracy and the nature of the pitch remain equally important factors.

In Wellington, New Zealand's fast bowlers kept India's batters under pressure during the early phase of the innings. After the first three wickets fell, Axar faced more than the pressure of the scoreboard. He had to bat on a surface where the pace and bounce required time to understand. Promoting a left-hander therefore made strategic sense, but executing the plan was difficult.

The management's decision should be examined at two levels. The first question is whether introducing a left-handed batter could have forced New Zealand to change its bowling plan. The answer is yes. The second question is whether Axar was the most suitable batter for that specific situation. That cannot be answered solely through his seven-run innings. It requires a closer assessment of his recent batting, the match-ups against the bowlers, the pitch and the alternatives available.

KL Rahul's Position and the Responsibility of the Middle Order

One of the main reasons for criticism of Axar's promotion was the presence of KL Rahul. Rahul is a versatile Indian batter who has handled responsibility at several positions. He can stabilise an innings and accelerate when required. His role at No. 5 has been particularly significant. Sending such an experienced batter in after early wickets could have provided India with greater stability.

However, the team management chose to make Rahul wait. One possible explanation is that Axar's presence as a left-hander could alter New Zealand's bowling plans and allow Rahul to bat in a potentially more favourable situation later. This interpretation is consistent with Gavaskar's comments, although the team management has not publicly provided a detailed account of the specific plan. It is therefore more appropriate to treat it as a possible strategic objective rather than a confirmed explanation.

After Axar's dismissal, Rahul attempted to rebuild the innings alongside Shreyas Iyer. Iyer scored 30 from 46 deliveries, while Rahul remained unbeaten. He made 26 from 38 balls. Rahul began cautiously, playing 18 dot balls in his first 20 deliveries. That figure helps explain the batting conditions at the time. Despite the relatively small target, India's batters needed to preserve wickets and understand the surface rather than immediately chase a high scoring rate.

Judging Rahul's innings solely by his strike rate would be incomplete. When a team has already lost early wickets and the chase may be affected by rain, balancing risk becomes important. Rahul initially concentrated on understanding the ball before looking for opportunities to accelerate. His unbeaten contribution proved useful to India. The innings also demonstrated the importance of experience in the middle order.

Axar Patel's Previous Role and the Background to the Selection

Promoting Axar Patel up the order was not an entirely new experiment for India. In the 2026 T20 World Cup final against South Africa, he was promoted in the batting order and built an important partnership with Virat Kohli. India needed a batter who could contribute under pressure and help the innings progress. Axar fulfilled that responsibility.

He was also given opportunities at No. 5 ahead of KL Rahul during India's successful 2026 Champions Trophy campaign. The management therefore had previous experience of using him higher in the batting order. This means the Wellington decision was not a completely unfamiliar experiment introduced without precedent. India had previously attempted to use Axar's batting ability in the middle order.

Nevertheless, different tournaments and match situations should not be treated as identical. The pressure of the 2026 T20 World Cup final, the conditions during the 2026 Champions Trophy and the second ODI in Wellington were three different contexts. A strategy that succeeds in one match does not have to be repeated in every situation. The player's role and the opposition's bowling, pitch conditions and match circumstances can all change its suitability.

Axar's previous successes gave the management another option, but they did not guarantee success in Wellington. This is why arguments supporting and opposing the decision need to be considered separately. Axar's all-round ability provides additional value to the team, but sending him at No. 5 also increases the expectation that he will fulfil a specialist batting responsibility.

Pitch and Bowling Conditions: The Story Beyond the Scoreboard

Comments from New Zealand's captain and India's batters also made it clear that the target of 135 was not as straightforward as the scoreboard suggested. After the match, Shubman Gill said that dismissing New Zealand for 134 had initially made him think the chase would be easy, but batting proved difficult. He also acknowledged that India had lost two more wickets than they would have liked.

Gill's observation is important for the technical assessment of the match. When chasing a small total, batters may initially try to avoid unnecessary risks. However, once early wickets fall, pressure increases. Bowlers also understand that batters chasing a modest target may be reluctant to take major risks. They can maintain pressure through disciplined lines and lengths. New Zealand benefited from precisely this situation.

India's problem was not limited to the change in batting order. After the early wickets, every incoming batter had to redefine his role. Axar was expected to provide a left-handed option and disrupt the bowling plan. Rahul was required to stabilise the innings later. Iyer had to build a partnership. The dismissal of one batter affected the responsibilities of the next player as well.

Consequently, Axar's seven-run innings cannot be assessed only as an individual failure. He entered the match as part of a team strategy but was dismissed before he could fully carry out the intended role. At the same time, a clear strategic objective does not remove the responsibility of producing results on the field. If similar experiments are repeated without producing runs, the management will eventually have to reassess its options.

Why Rain and the DLS Result Complicated the Debate

The result at Wellington added another dimension to the discussion. India were 113/7 after 26 overs when rain interrupted play. At that stage, India were four runs ahead of the DLS par score of 109. India were consequently declared four-wicket winners and took a 2-0 lead in the five-match series.

The result of the match and the assessment of the batting-order decision must be kept separate. India won, but that does not automatically establish that promoting Axar to No. 5 was the correct decision. Equally, his dismissal for seven does not prove that the underlying tactical idea was wrong. The result was determined by several combined factors, including bowling, early batting performances, partnerships, rain and the DLS calculation.

India's victory was built on the performance of its fast bowlers. Gurnoor Brar's 4/30 played a major role in restricting New Zealand to a modest total. Auqib Nabi and Anshul Kamboj also maintained pressure with two wickets apiece. Without India's bowlers restricting New Zealand to 134, the discussion surrounding Axar's promotion would have taken place in a different context. The team's victory therefore cannot be attributed to one batting decision.

Because rain ended the match, India did not need to complete a full 50-over chase. The DLS method determined the result using the available overs and match situation. It was a rule-based outcome. It cannot be used as evidence either supporting or opposing Axar's selection. Winning a match and declaring a particular tactical decision successful are two separate assessments.

The Basis of the Criticism: Is the Decision Being Judged Only by Its Outcome?

In Indian cricket, discussions about batting positions often become more intense after the result is known. If a player promoted up the order scores quickly, the captain is praised for his foresight. If the same player is dismissed early, the decision is described as an experiment or a mistake. Such reactions are a normal part of public cricket discussion, but they can distort the technical assessment of selection decisions.

Gavaskar drew attention to this tendency. He argued that the same people questioning the decision might have praised the captaincy had Axar scored runs. There is an important point in this argument: the reasoning behind a tactical decision should be examined alongside its outcome. However, that does not mean every failed experiment should be accepted without review.

At least three questions are necessary when assessing a decision. Was the team's situation such that a change in the batting order was required? Was the selected batter suitable for that specific situation? And did the team have an alternative plan after making the change? In Wellington, the first and third questions are particularly important. India were 39/3, and Rahul remained available later in the order. However, answering the second question requires a detailed examination of the deliveries Axar faced, the bowlers' plans and the actual pitch conditions.

The limits of the criticism must also be understood. Available reports establish that fans and some experts questioned the decision to send Axar ahead of Rahul. However, there is no detailed record establishing the actual scale of the criticism, the number of people involved or any formal response from the team. It would therefore be inappropriate to describe the matter as an internal dispute or a serious institutional crisis. For now, it remains a public debate about selection and captaincy strategy.

Gambhir and Gill's Decision-Making Process: Who Is Responsible?

Attributing the entire decision solely to Gautam Gambhir would also provide an incomplete picture. Available reports mention both head coach Gambhir and captain Shubman Gill. A change in the batting order can involve coordination between the captain's understanding of match conditions and the coaching staff's strategic planning. Detailed information about the selection committee's role, prior team discussions and the responsibilities communicated to the players is not publicly available.

It would therefore be premature to hold one individual solely responsible for the decision. As head coach, Gambhir has an important role in providing strategic direction, while the captain must implement decisions according to the conditions on the field. If Axar's promotion had been planned in advance, it may have been part of the team's broader batting structure. If it was an immediate response to the match situation, it would need to be assessed on a different basis.

Gavaskar's support is significant because he did more than defend Gambhir. He also provided a technical explanation for changing the batting order. According to his argument, introducing a left-handed batter can alter the bowlers' plans. This is a cricketing rationale that can be tested against the match conditions. However, his support is not equivalent to an official selection policy or conclusive proof that the decision was correct.

Accountability in team management does not mean issuing a public apology after every unsuccessful decision. It means assessing the results of repeated experiments. If Axar is regularly sent in at No. 5, it will be necessary to understand exactly what kind of innings the team expects from him. Is he being promoted to attack spin? Is he being used primarily to create a left-right combination? Or does the team intend to develop him as a regular middle-order option? The answers will be important for future selection decisions.

The Contradictory Element: Holding Rahul Back Was Also Part of the Strategy

An interesting feature of this decision is that promoting Axar was not merely an expression of confidence in him. It also meant keeping Rahul away from the crease for a little longer. When an experienced batter has already established his usefulness at a particular position, moving him down the order naturally creates debate. However, team management sometimes prioritises collective advantages against a specific opposition over an individual's preferred batting position.

Rahul's record at No. 5 also became part of the discussion. According to an Outlook India report published on November 8, 2026, Rahul had scored 1,646 runs in 36 innings for India at the position. The report listed his average at 68.58 and his strike rate at 103.19. These figures are relevant when examining his value at No. 5. However, career statistics cannot be applied directly to the circumstances of one particular match.

A player's average represents the outcomes of previous innings. Conditions during a match, the quality of the bowlers and the timing of wickets can all change. The situation in which Rahul batted at Wellington was different from the one Axar faced when he entered. Axar had to deal with the early pressure, while by the time Rahul arrived, New Zealand had taken another wicket and India needed a new partnership.

This also means that the innings of Axar and Rahul must be compared carefully. They entered at different times and faced different circumstances. Axar was expected to change the bowling pattern as a left-hander, whereas Rahul was required to stabilise the innings. A comparison would be clearer if both had batted in the same situation, but the available match details do not permit that conclusion.

Should Axar Continue to Receive Opportunities at No. 5?

Future discussion about Axar's role will depend on how the management views him. He is a useful spin-bowling all-rounder for India. His batting provides additional depth to the team. However, batting at No. 5 carries different responsibilities from arriving at No. 7. A No. 5 batter often has to rebuild an innings after early wickets. He must balance the effects of the new ball, aggressive fast bowling and pressure from spin during the middle overs.

If the team wants to use Axar regularly in this role, it must provide him with sufficient opportunities and a clearly defined responsibility. One seven-run innings should not be enough to remove him from the position, just as one successful innings should not automatically establish him as India's permanent No. 5. Selection should be assessed across several matches, against different bowling attacks and through his technical responses in varying conditions.

The management must also consider whether promoting Axar affects the bowling combination. An all-rounder is expected to contribute with both bat and ball. If he is regularly used higher in the order, his responsibilities during the match should be clearly defined. However, there is insufficient information from the Wellington match to draw conclusions about his workload or injury risk.

The Road Ahead: Consistency in the Experiment Matters More Than the Immediate Result

Promoting Axar Patel to No. 5 in Wellington did not succeed in terms of the immediate batting outcome. His seven-run innings did not provide India with the benefit the team might have expected. Nevertheless, Sunil Gavaskar refused to label the experiment a mistake. His argument was based on the left-right batting combination and its potential impact on the bowlers' lines and lengths.

India won the match by four wickets and took a 2-0 series lead. That victory did not end the selection debate because the match result and the impact of the batting-order decision are separate subjects. Gambhir and Gill must now decide the circumstances in which they intend to apply this strategy in future matches. If Axar is again promoted to No. 5, the decision should reflect a consistent plan. If Rahul is given priority, the middle-order structure will need to be organised accordingly.

The real test of a strategy is not whether it is abandoned after one unsuccessful innings, but whether the management understands the conditions in which it can work. India's next matches will provide a stronger basis for assessing Axar's batting position, Rahul's role and the use of left-right combinations. Gavaskar has defended the thought process; the team's performances must now demonstrate how that thinking can translate into results on the field.