Blaming the captain when a cricket team loses is the easy move, and almost always the wrong one. Selectors, coaches, and directors shape outcomes too — and they should own the failures.
Every time a cricket team loses, the same ritual plays out. The captain gets roasted, the press calls for his head, and the fans pile on. Meanwhile, the selectors who picked the squad, the coaches who prepared the players, the director of cricket who set the strategy, and the administrators who shaped the culture all walk away untouched. It's scapegoating dressed up as accountability.
The captain is the softest target. He's visible, he's in charge on the field, and when things go wrong, the anger needs somewhere to land. But captains don't select teams. They don't control player contracts. They don't design long-term strategy. They work with the players they've been given, execute plans agreed upon with the coaching staff, and lead within a system they didn't build. Blaming them alone for a collapse isn't honest — it's the easy way out.
It's like blaming the pilot for a plane that was never serviced and then overloaded.
Modern cricket is a complex system. Selection panels, analysts, conditioning coaches, psychologists, administrators — all of them shape what happens on that field before the first ball is bowled. When the team wins, everyone celebrates together. The moment they lose, somehow it's only the captain's fault? That logic doesn't hold.
When a team underperforms, the right question isn't "what did the captain do wrong?" It's "how did the system fail?" That reframe matters, because it forces accountability onto the people who actually control the levers.
Did the selectors pick the right squad? Did the coaches prepare the players properly? Did the director of cricket set the right strategy and culture? Did the cricket committee give the team stability, clarity, and direction?
If the answer to any of those questions is no, blaming the captain alone isn't just unfair — it's not being honest with yourself.
If any of those answers is no, then the captain was already being set up to fail before he walked out for the toss. He can only lead effectively if the system behind him is competent, aligned, and accountable. A captain leading a poorly selected, underprepared, strategically directionless team is not the architect of that failure.
Cricket understands this when things go right. A World Cup win is everyone's triumph — the selectors get praised, the coaches get credit, the board takes a bow. The logic has to work in both directions.
Cricket victories are collective. Everyone shares the credit. So cricket failures should also be collective.
Treating the captain as the sole repository of blame whenever a series goes badly doesn't fix the deeper structural problems. It papers over them. The selectors stay. The director of cricket stays. The same culture that produced the losing team stays intact. And the cycle repeats with a new captain in the firing line.
Holding the whole system accountable is harder. It requires the cricket world to look at uncomfortable things: selection politics, long-term planning failures, misaligned coaching appointments. But that's exactly what honest post-mortems demand. Stop pointing at the captain and start looking at what built the team around him.
