Pandya Blames 'Early Wickets' — But His Own 0/38 Told the Real Story

There's an art to the post-match press conference when your team has just been bowled out for 104 chasing 208. You can own it. You can rage. You can lay out exactly what went wrong with the clinical detachment of a man who knows what's broken. Or you can do what Hardik Pandya did on Wednesday night at the Wankhede: blame the powerplay.

"I think that in the power play, losing that early wicket is always going to be tricky. You are always chasing the game, and we could not cope after that," Pandya said, as if 11/3 after three overs was an act of God rather than a consequence of being outplayed by Akeal Hosein's left-arm spin on a Wankhede track.

He added: "For us to chase this down, we needed to have a good power play, and the momentum had to be with us, but that could not happen." As explanations go, this is the cricket equivalent of saying you lost a marathon because you tripped at the starting line. It's not wrong. It's just nowhere near enough.

Here's what Pandya didn't address in his carefully worded presser: his own bowling figures. Two overs, no wickets, 38 runs conceded. Nineteen runs per over. That's not death-overs carnage — that was his opening spell. Samson and company treated him like a net bowler at the very ground where he's supposed to be the alpha.

The timing makes it worse. Just one match earlier — the 99-run win over Gujarat Titans on April 20 — Pandya had specifically emphasised the need to "restrict high-scoring overs." Four days and one opponent later, he personally delivered two of the most expensive overs in the CSK innings. The man preaching containment became the man leaking at 19 an over.

When asked about the pitch, Pandya at least had the decency to refuse that excuse: "I'm not someone who would like to say that. They batted well; they scored 207." Fair enough. But if the pitch was fine, and the opposition batted well, then the question becomes: what exactly did the captain do to stop it? The scorecard says 0/38.

While Pandya was carefully navigating the presser, former India batter Manoj Tiwary was doing the opposite — saying exactly what a growing chunk of Mumbai Indians supporters have been thinking since Match 5.

"If a solution is needed, Hardik should step back from the captaincy and hand the responsibility back to Rohit," Tiwary said on Cricbuzz. Then came the line that will echo through this season: "When you removed Rohit, you did an injustice."

That word — injustice — carries weight. This isn't a tactical disagreement. Tiwary is saying that the original sin was stripping the captaincy from the man who delivered five IPL titles. Every loss since, in Tiwary's framing, is a consequence of that decision. And with MI sitting on 2 wins from 7, the argument is getting harder to counter.

To his credit, head coach Mahela Jayawardene tried to shield Pandya. "I don't think it's just on Hardik, it's on me and everyone involved in the management," he said, spreading the blame across the coaching staff and the wider squad.

It's a classy move. It's also insufficient. Because Tiwary wasn't just criticising results — he was criticising specific decisions. Pandya promoting himself above in-form Sherfane Rutherford. Pandya opening the bowling with a struggling Deepak Chahar instead of Bumrah. Pandya conceding 38 in two overs while preaching containment. These aren't systemic failures that Jayawardene can absorb. These are captain's calls, made by the captain, and they keep going wrong.

The uncomfortable truth is that Jayawardene's defence might actually make things worse. If it's a collective failure, then why is the collective not changing? If it's not just Hardik's fault, then whose decisions are producing these results? At some point, "we're all in this together" stops being solidarity and starts being a refusal to identify the problem.

Here's the cruel twist in Tiwary's captaincy solution: the man he wants to hand the armband to isn't available. Rohit Sharma has been out since April 12 with a hamstring injury sustained against RCB. He missed both the GT win and the CSK humiliation. His scans came back inconclusive. He's not walking into any press conference, let alone a dressing room shake-up.

So even if the MI management wanted to make the change Tiwary is demanding — and there's no indication they do — the logistics don't cooperate. Pandya is captain of a sinking ship because the man everyone wants at the wheel is sitting in the physio's room.

MI's next game is against KKR on April 27. Rohit's availability remains uncertain. Pandya's excuses are running out. And somewhere in Mumbai, a five-time champion franchise is trying to work out how you go from beating GT by 99 runs to losing to CSK by 103 in the space of three days.

Hardik Pandya walked into a press conference after his team's worst defeat in 18 seasons of IPL cricket and blamed the powerplay. That's like a pilot blaming turbulence after the plane landed in the wrong country. Yes, the powerplay was bad. But so was the bowling. So was the batting order. So was the captaincy. So was everything that happened between over 1 and over 19.

Tiwary's "injustice" framing may be harsh, but it's asking the right question: is this the best version of Mumbai Indians under this leader? Seven matches in, the answer is resoundingly, historically, 103-runs-at-home clear. When the captain's own contribution with the ball is 0/38 and his post-match explanation is "we could not cope," the gap between the words and the evidence isn't a gap anymore. It's a chasm.