Rahul Dravid’s approach as Rajasthan Royals’ IPL coach faced its toughest challenge yet as Yashasvi Jaiswal crept closer to the 300-run mark in 2026. The young opener had piled up 287 runs across 15 matches, just 13 shy of joining the season’s most reliable run-scorers. But here’s the thing: Jaiswal’s strike rate had slipped to 142.8 over his last five innings, making some wonder if Dravid’s safer tactics might be holding back the 22-year-old’s fireworks at the top. With the Rajasthan Royals IPL playoff dreams teetering, this milestone chase could have ended up deciding their fate.

How Rahul Dravid’s Tactical Shift Changed Jaiswal’s Game
The Strike Rate Debate: 287 Runs But At What Cost?
Playoff Mathematics: Why 300 Runs Matters for RR’s Net Run Rate
Rahul Dravid IPL Legacy Faces Ultimate Test in Final Matches

How Rahul Dravid’s Tactical Shift Changed Jaiswal’s Game

The stats paint quite a picture. In RR’s first eight matches under Dravid’s bold gameplan, Jaiswal averaged a remarkable 52.3 runs an outing. Then, things changed.

After Rajasthan lost to Mumbai Indians on March 28, Dravid’s tactics grew more cautious. He shifted Jaiswal from his home at No. 1 to a floating opener—sometimes dropping him to No. 3 if an early wicket fell. Instead of boundary-bashing, the focus became building steady partnerships.

“Yashasvi has matured as a batsman,” Dravid said after a win over Punjab Kings. “We’re asking him to build innings, not just smack boundaries.” At first, the new approach worked. RR picked up four wins from their next six matches. But there was a cost.

Jaiswal’s boundary percentage dropped from 18.2% early on to 14.1% in more recent games. His dot ball percentage climbed to 31.4%—the highest among IPL 2026 openers with at least 250 runs. CricInfo pointed out this change reflected Dravid’s style as a player: steadiness over showmanship.

The big question is, did Dravid go too far? Jaiswal’s natural rhythm depends on momentum. Constantly tinkering with his role might be throwing him off, even if the runs keep coming.

The Strike Rate Debate: 287 Runs But At What Cost?

Now, let’s talk about where Dravid’s IPL experiment stirred debate. Jaiswal’s overall strike rate of 148.2 looked great at first glance. But look closer—lately, the numbers tell a different story.

Over his last five knocks, Jaiswal scored 34(28), 41(32), 19(15), 52(38), and 28(21). That’s 174 runs at a strike rate of just 129.9—well below the 140+ standard that top T20 openers set. For comparison, RCB’s Virat Kohli struck at 151.3 this season, and he’s five years older.

It wasn’t just about Jaiswal’s stats, either. Rajasthan’s powerplay run rate dropped to 8.7 in their last seven outings, down from 9.4 in the first half. When your opener stops setting the pace, it has a ripple effect through the whole line-up.

Here’s the other side: Jaiswal’s reliability anchored RR’s season. Out of 15 matches, he missed double digits only twice. That’s rare for young openers—SRH’s Abhishek Sharma had five low scores, DC’s Prithvi Shaw had six.

Key Ahead IPL analysts argued Dravid was thinking long-term. He wanted a technically sound Jaiswal to catch fire during the playoffs, when cool heads matter more than just raw hitting.

The numbers partly back that up. In matches where RR won, Jaiswal averaged 43.7 runs. When they lost, that dropped to 31.2. So it’s clear—his ability to anchor at the top is tied directly to the Royals’ success.