Devdutt Padikkal Chance: “It’s Important Whenever I Perform”

Devdutt Padikkal, speaking on 18 August 2026 during India’s No. 3 debate, made it clear that his approach is simple: “It’s important that whenever I get that chance, I perform,”…

August 21, 2026
6 min read

Devdutt Padikkal, speaking on 18 August 2026 during India’s No. 3 debate, made it clear that his approach is simple: “It’s important that whenever I get that chance, I perform,” as India continues weighing the best fit between him and Sai Sudharsan.

The bigger picture has been brewing for a while, but the conversation sharpened in the first Test in Galle, where Padikkal’s red-ball output forced selectors to take the No. 3 slot decision seriously.

Key Details: Padikkal’s words on the No. 3 slot

Worth noting: Padikkal’s remarks were published on 18 August 2026, with the article timestamped 17:11:56 UTC and last updated at 16:59:55 UTC. In the same piece, he addressed questions about the No. 3 role for India and the competition with Sai Sudharsan for that spot. The message was consistent across his comments—opportunities may not arrive in long, uninterrupted runs, so execution matters each time he gets a chance.

That said, the “perform when given the chance” idea was not just rhetoric. In Sai Sudharsan’s absence, Padikkal put his case forward with a strong showing in the first Test against Sri Lanka in Galle, scoring 167 and 44. According to ESPNcricinfo, these knocks were part of a broader push that effectively forced India to “choose” for the No. 3 spot. (Reference: ESPN, via its reporting style under ESPNcricinfo coverage.)

Before vs After: what changed in India’s selection thinking

Before the No. 3 conversation narrowed, India’s middle-order identity looked tied to continuity—who would most reliably anchor at No. 3 without waiting for perfect conditions. But the after state arrived when Padikkal delivered two knocks in Galle—167 and 44—making his availability at that position hard to ignore.

This is the kind of “form with a role” that selection panels crave because it reduces guesswork. Here’s the thing: Padikkal’s comments also reveal how he views the modern Test rhythm. He said he does not expect players to get a long run of games in modern cricket and that cricketers must perform whenever they get opportunities. He also linked his Test goal—he called it his “ultimate goal”—to technical adjustments against red-ball bowling, suggesting the focus is not just on runs, but on repeatable preparation.

FactorBefore (debate open)After (No. 3 case strengthened)
Role clarityNo. 3 decision still contestedPadikkal stakes a clear claim in Galle
Form evidenceSmaller sample pressure167 and 44 in the first Test
Mental frameworkExecution not always consistent“Perform whenever I get that chance”
Selection pressureGradual evaluationReports framed it as forced choice

Context that matters: pitch, technique, and pressure management

Selection battles in Tests rarely stay “only about talent.” They become about how a batter reads conditions and handles pressure, especially when the batting order shifts due to availability. In Padikkal’s case, his Galle performance did more than add runs—it provided a concrete reference point for how he handles red-ball bowling in real match pressure. For more detail, see BBC Sport.

On the technique side, Padikkal tied his red-ball ambitions to adjustments he has been making, with Test cricket remaining his “ultimate goal.” That matters because the No. 3 slot often demands both temperament and timing: you are expected to absorb hostile spells, yet also build momentum rather than just survive. If you want the clearest signal, the quote is the headline—opportunities are finite, so preparation has to convert each chance into a statement.

What’s next for India’s No. 3 call

The immediate outcome is selection tension being forced into the open: Padikkal’s numbers in Galle and his direct stance on opportunity-taking mean India’s No. 3 choice can no longer be treated as a soft preference. Instead, it becomes a high-stakes comparison between two profiles—one shaped by form at the slot, and the other still competing for supremacy.

That said, the deciding factor will likely stay the same across matches: who can turn technical adjustments into runs under pressure, and who can do it quickly when the order shifts. ESPN’s coverage framed Padikkal’s performance as part of India having to “choose,” and that framing captures the practical reality for coaches—when a batter performs at the role, it becomes difficult to ignore the evidence. For your own XI logic, if you value role-specific output, devdutt padikkal chance should be treated as the performance-led pick; if you value longer-term continuity, you pick based on how often the team expects stability around No. 3.

Verdict: Padikkal’s “perform when it happens” line matches his Galle impact (167 and 44), making the No. 3 call performance-driven rather than theoretical.

Related Articles


FAQs

Why did Devdutt Padikkal talk about the No. 3 role?

He addressed questions about the No. 3 spot for India and explained that when he gets a chance, it is important to deliver, especially as the modern schedule may not allow long runs in the same role.

What match did Padikkal’s comments connect to?

His No. 3 case was strengthened by his performances in the first Test between Sri Lanka and India in Galle, where he scored 167 and 44.

What did Padikkal say about opportunities in modern cricket?

He said he does not expect a long run of games, and therefore players must perform whenever they get opportunities.

How should fans interpret the devdutt padikkal chance debate?

Treat it as a role-and-output comparison: if a batter produces in the slot, selection pressure rises, and if you want a performance-led XI, devdutt padikkal chance points toward the immediate impact approach.

Was this article helpful?

Your feedback directly improves future articles on this site.

Follow us on Google News Get real-time updates & exclusive tech coverage
Follow

Leave a Reply

Your email address will not be published. Required fields are marked *

wp_enqueue_script('jquery', false, [], false, true); // load in footer