250 on the Board and Nobody on CSK's Side Thought to Change the Plan
Ambati Rayudu watched CSK concede 159 runs in the last 10 overs against RCB and had one question: who was supposed to intervene? The answer, apparently, is nobody.
91 for 1 After 10 Overs. 250 for 3 After 20.
Here's the statistic that should keep CSK's coaching staff awake at night: Royal Challengers Bengaluru were 91 for 1 after ten overs at the Chinnaswamy on Saturday. A competitive score. A manageable platform. Nothing to panic about.
They finished on 250 for 3.
That's 159 runs in the last ten overs. Nearly 16 an over. Against a bowling attack that included Jamie Overton, Khaleel Ahmed, and Matt Henry — three bowlers who, on paper, should be capable of executing at the death.
RCB didn't just accelerate. They went from cruising at 9 an over to sprinting at 16. And CSK's response was to keep doing exactly what wasn't working.
"More than a bad plan, they just stuck to that bad plan. There was nobody to intervene and to just take some time off, take those 20-30 seconds, just make it slightly more slow and then guide the bowler with a message."Ambati Rayudu
The Tim David Problem
Tim David walked in when RCB were well-set but not yet destructive. He left 25 balls later having scored 70 runs. Eight sixes. Three fours. A strike rate of 280.
David didn't edge his way to those numbers. He stood still at the crease, picked his lengths, and hit everything that was short or full into the stands behind mid-wicket. It was the kind of innings that makes bowlers question their career choices.
The partnership that broke CSK was the unbeaten 99 between David and skipper Rajat Patidar — 99 runs in 35 balls. That's not a batting partnership. That's a controlled demolition. Patidar finished with an unbeaten 48 off 19, playing the perfect foil to David's brutality.
RCB vs CSK — Match 11 Breakdown
| RCB Total | 250/3 (20 overs) |
| CSK Total | 207 all out |
| Result | RCB won by 43 runs |
| Tim David | 70 off 25 (8 sixes, 3 fours) |
| Rajat Patidar | 48* off 19 |
| David-Patidar Stand | 99 off 35 balls (unbroken) |
| RCB Runs in Last 10 Overs | 159 (15.9 per over) |
The Around-the-Wicket Debate
Jamie Overton bowled the 19th over from around the wicket. He conceded multiple sixes. It was, by every available metric, the wrong approach against two right-handers who were sitting on the pull and the flick through mid-wicket.
Here's where it gets interesting. Analyst Gaurav Sundararaman pointed out that the around-the-wicket angle at the death is something the CSK franchise has actually been implementing across its affiliated teams in other leagues. It's a deliberate strategic choice — angle the ball into the body, cramp the batter for room, force mishits.
The problem? MS Dhoni never approved of that angle. When Dhoni was behind the stumps, CSK bowled over the wicket at the death. The yorker corridor, the wide line, the bouncer — all delivered from the conventional angle. Dhoni's reasoning was simple: around-the-wicket gives the batter an easier sightline for the leg-side boundary.
With Dhoni no longer on the field, CSK's coaching staff implemented the tactic they'd been wanting to try. Against David and Patidar, on a Chinnaswamy belter, it was exposed for exactly the flaw Dhoni had identified.
The Captaincy Vacuum
Rayudu's most damning criticism wasn't about the plan itself. It was about the absence of anyone to change it.
In Dhoni's era, CSK had someone who could read the game in real time, pull a bowler aside mid-over, switch the field, call for a different length — all within seconds. The plans were simpler because the in-game adjustments were constant.
Under Ruturaj Gaikwad, CSK are playing with plans that are set before the game and rarely adjusted during it. When RCB were accelerating through the death overs, there was no intervention. No timeout called at the right moment. No senior player grabbing the ball and saying "not like this."
As Aaron Finch observed from the commentary box, the issue wasn't just bad planning or bad execution — it was both. And when you're failing on two fronts simultaneously, you need someone on the field with the authority and instinct to rip up the script.
CSK don't have that person right now.
"When you're missing both of them, that's worrying signs."Aaron Finch on CSK's combined failure of planning and execution
RCB's Ruthlessness Is the Real Story
While CSK's collapse makes for the more dramatic narrative, the quieter story is how RCB have transformed under Patidar's captaincy.
Rayudu noted that RCB are "not letting anything just pass by — they want to control every scenario, every over." That's a philosophical shift for a franchise historically associated with chaos and individual brilliance.
250 for 3 isn't an accident. It's the product of a batting order that knows when to consolidate and when to attack, a captain who promotes himself at the right moments, and a finisher in Tim David who was bought specifically for innings like this one.
RCB are 2-0. CSK are 0-3. The gap between these two franchises hasn't been this wide in years — and it's not about talent. It's about clarity of thought under pressure. One team has it. The other is still looking for someone to provide it.
What Happens Next for CSK?
CSK's 0-3 start is their worst in franchise history. The bowling has conceded 200+ in two of three matches. The death-over strategy is being questioned by former players on live television. And the franchise that defined IPL dominance for a decade is now defined by a single, uncomfortable question: what happens when the system depends on a person who's no longer there?
Dhoni built CSK's culture. He set the tactical framework. He made the in-game decisions that turned good plans into winning ones and saved bad plans from becoming disasters. Without him, CSK aren't just missing a player. They're missing the operating system.
Three matches isn't a season. But three matches without a single course correction — three matches of sticking to plans that aren't working — suggests the problem goes deeper than form or luck. It's structural. And structural problems don't fix themselves.
Want data-backed predictions for every IPL 2026 match?