Smart Cricket, Brave Calls: How Royals Captain Riyan Parag Set Up CSK’s Collapse

There is one underrated luxury that only the inexperienced can afford: the freedom to look like a 'dumb duck'. Riyan Parag, stepping into his first full-time captaincy role with Rajasthan…

April 1, 2026
9 min read

There is one underrated luxury that only the inexperienced can afford: the freedom to look like a ‘dumb duck’. Riyan Parag, stepping into his first full-time captaincy role with Rajasthan Royals, was willing to wear that cloak without hesitation.

The payoff? The dismissal of Sanju Samson, and ultimately, Chennai Super Kings’ complete unravelling in an 8-wicket defeat with nearly eight overs to spare.

The Unconventional Trap

In the second over, Parag stationed Ravindra Jadeja at short third and asked Jofra Archer to control deep backward point—placing two of his most athletic players in positions that don’t usually require the best to be there. This sent a signal to Samson, the in-form opener now donning yellow, of which areas his former teammate wanted him to hit towards.

With movement on offer for pacers, Parag gave Samson the bait to cut early. Samson didn’t fall for it immediately but was left uncomfortable trying to access new scoring areas while pacers tempted him. As pressure mounted, Nandre Burger teased him with inswingers before getting one to move away and hit the top of off stump.

Nandre Burger

It looked an outstanding delivery in isolation, but it was poetry of planning set in motion. The funky field-set paid off.

For as unconventional as that strategy was, it was data-driven, Parag confessed. “We were just trying to target where he plays his first three to five balls. We set the fielders accordingly and asked him to hit a better shot or hit a different shot, which is a gamble of sorts. But then that gives us a lot of percentage in our favour.”

“If it comes off, looks very good. If it doesn’t come off and he gets hit for a few cuts, I’ll be sitting here like a dumb duck,” Parag added.

The Powerplay Collapse

That dismissal set the tone for CSK’s collapse. Archer and Burger’s rapid spell upfront, with movement and tight lines, had already made run-scoring challenging. Samson’s dismissal opened the gates for bowlers to attack CSK’s inexperienced top-order.

CSK Powerplay DismissalsHow Out
Sanju SamsonBowled by Burger (off stump)
Ayush MhatreBurger’s pacy bouncer
Matt ShortSandeep Sharma’s lack of speed
Ruturaj GaikwadBowled by Archer (ugly hack)

Ayush Mhatre was undone by Burger’s pacy bouncer, Matt Short was tricked by Sandeep Sharma’s lack of speed, and Ruturaj Gaikwad was pushed under the pump, forcing him to play an ugly hack and have his stumps knocked over by Archer—leaving the five-time champions four wickets down within the powerplay.

Conditions and Panic

The toss went to Royals on a gloomy evening with moisture on the surface courtesy of rain hours before the match. While they made use of favourable conditions, CSK batters crumbled under a double whammy of quick wickets and slow scoring. Their inexperience came to the fore as they attempted to wriggle out.

The panic was evident with Gaikwad’s dismissal. In Jadeja’s first over with his old team, CSK made it worse. Earlier in the fourth over, they called on Impact Player Sarfaraz Khan, who ditched his newly developed open stance for a conventional approach. In the company of Short and debutant Kartik Sharma, he promised revival. However, that promise withered away.

Ravindra Jadeja

A wild swipe against Jadeja had him pinged on his pads in front. Shivam Dube announced himself with a powerful six, but the need to put pressure back meant he was back in the dugout before the next over, caught at long off while unable to channel his ultra-aggressive hitting.

The eventual 8-wicket win with nearly eight overs to spare was as much due to sharp plans and disciplined bowling by Royals and the blazing half-century from Vaibhav Suryavanshi, as CSK’s inability to handle pressure with the bat, read the game situation, and shot selection—to go with dropped catches and fielding lapses.

Injury-hit and without their team patriarch, they looked completely out of sting for a fight.

Hussey’s Assessment

“Our batsmen struggled to adjust to that movement early,” Michael Hussey, CSK’s batting coach, admitted. “If we had our time again, maybe we would have been more cautious and tried to get through that first six overs without losing too many wickets. But it’s easy to say that in hindsight.”

“The way the game is being played these days, they want to be aggressive, they want to play their shots. Probably the conditions weren’t quite right for that today. We need to take lessons from this game that if the conditions aren’t perfect, maybe we need to adjust our sights and try and score our runs in different areas.”

On the poor shot selections by experienced players, Hussey explained: “It’s never ideal to lose the early wickets. It puts players in an awkward situation. Which way do they go? Do they try and soak up pressure, score slower but preserve wickets? But then sometimes you dig yourself into a hole, so you still need to keep scoring.”

“I’m sure a few guys will say, in hindsight, maybe I could have played differently, but on another day it comes off and they change the momentum.”

Moving Forward

Hussey was adamant CSK must not let this cloud their mindset: “I don’t want our batsmen to have clouded thoughts or put doubts in their mind. I don’t think players play their best when they’re second-guessing themselves. I would prefer them to come in with a clear attitude, assess the conditions quickly and then back themselves. If it comes off, great. If it doesn’t, well, then that’s sometimes cricket.

“I don’t want this performance to cloud and put doubt and fear into our team. We need to move forward quickly with a positive attitude and say, ‘OK, yes, it wasn’t a great performance’. We were outplayed today. But let’s leave that behind and keep our positive attitude moving forward.”

The Irony

CSK will leave for Chennai on Tuesday more deflated than the unit that landed in Guwahati. Maybe they were the ones looking like ‘dumb ducks’ eventually on Monday against the enterprising Royals.

But that’s the beauty of inexperience. Hope can be rested on them to improve and come good even if they folly.

Parag’s willingness to risk looking foolish—to station his best fielders in unconventional positions based on data—paid rich dividends. His ‘dumb duck’ trap wasn’t dumb at all; it was calculated, brave, and devastating for CSK.

The five-time champions, meanwhile, fell into a different trap—one of their own making. The pressure of early wickets, inability to assess conditions, panic-induced shot selections, and failure to adapt their aggressive approach all contributed to their undoing.

AspectCSK’s FailureRR’s Success
PlanningPoor shot selection, no adaptationData-driven field placements
ExecutionCrumbled under pressureDisciplined bowling, tight lines
MindsetPanic after early wicketsWilling to risk looking ‘dumb’
Result8-wicket loss, 8 overs spareBlazing win (Suryavanshi 50+)

While Hussey is right to want batsmen to avoid second-guessing, there’s a fine line between backing yourself and adapting to match situations. CSK’s experienced players should have known better than to persist with ultra-aggressive approaches when conditions and scoreboard demanded caution.

The loss exposed not just technical deficiencies but mental fragility. Without their team patriarch, injury-hit and facing early adversity, CSK looked bereft of the fighting spirit that has defined their five IPL titles.

For Parag and Rajasthan Royals, this was a statement victory. The first-time captain showed that inexperience isn’t always a liability—sometimes it’s the freedom to innovate and take risks that established voices might shy away from.

CSK

CSK, paradoxically, looked more inexperienced despite having seasoned players. The ‘dumb duck’ trap worked because they failed to recognize it, adjust to it, or counter it with smart cricket of their own.

Read More: Powerplay Promise, Middle-Overs Collapse: KKR’s Familiar Story

FAQs

What was Riyan Parag’s ‘dumb duck’ trap that dismissed Sanju Samson?

Parag stationed Ravindra Jadeja at short third and Jofra Archer at deep backward point—unconventional positions for their best fielders. This data-driven strategy targeted where Samson plays his first 3-5 balls, forcing him into uncomfortable scoring areas. Nandre Burger then bowled inswingers before getting one to move away and hit the top of off stump.

How badly did CSK collapse in the powerplay?

CSK lost four wickets within the powerplay: Samson (bowled by Burger), Ayush Mhatre (Burger’s bouncer), Matt Short (Sandeep Sharma’s lack of speed), and Ruturaj Gaikwad (bowled by Archer after an ugly hack). The early collapse set the tone for their complete unravelling.

What did Michael Hussey say about CSK’s poor shot selection?

Hussey admitted batsmen “struggled to adjust to that movement early” and acknowledged they should have been “more cautious” in the first six overs. He emphasized wanting batsmen to assess conditions quickly and back themselves without second-guessing, saying “I don’t want this performance to cloud and put doubt and fear into our team.”

What was the final margin of CSK’s defeat?

Rajasthan Royals won by 8 wickets with nearly eight overs to spare. The comprehensive victory was driven by sharp planning, disciplined bowling, and a blazing half-century from Vaibhav Suryavanshi, while CSK suffered from poor shot selection, dropped catches, and fielding lapses.

What conditions favored Rajasthan Royals in Guwahati?

RR won the toss on a gloomy evening where rain hours before the match had left moisture on the surface. This helped Archer and Burger generate movement and tight lines early on, making run-scoring challenging. CSK’s aggressive approach didn’t suit the conditions, contributing to their collapse.

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