Dry Willow, Closed Door: What Wasn't Visible in Chennai's Defeat

The first thing I noticed was what wasn't there — after the innings ended, no Chennai batsman walked toward the media area outside the stadium. That corridor from the training ground to the dressing-room door, where a player normally gives a three-minute quote and moves on, stayed empty. Chennai's kit bags were being loaded onto trolleys one by one, none of them name-readable, and one staff member turned a bag over and set it down as if hiding something. I have covered this beat for several seasons, and I know that in this team a closed door does not mean a defeat — a closed door means something is happening inside that is not meant to come out.

This match looks like an ordinary loss for Chennai — balls remaining on the scoreboard, wickets falling, run rate slow. But what is written in my notebook does not start with the scoreboard. It starts with who was padding up first in the dugout after the toss and who wasn't. The order that emerged in this match was normal, but the time behind that order was not. What I saw at nets three days earlier unfolded over by over in this innings.

Chennai's batting structure has shifted in one direction this season — openers are spending time watching the ball instead of scoring quickly, and the middle order, trying to fill that time, is losing its natural tempo. This is not new. Look at the last five matches and their powerplay strike rate has fallen steadily, and that fall seems tied more to their own intent than to the quality of opposing bowling. Of the balls left alone in the first six overs of this match, three were deliveries this same batsman used to hit last season. That is not restraint. That is doubt.

The picture from the training ground in my notebook confirms that doubt. In the list of who batted first at nets, the same names were at the top that came lower in the match. This sounds small, but inside a team it is a signal that the technical staff and the captain are negotiating priorities. When the net order changes, intent changes in the match — and when intent changes, a batsman's tempo changes. In this match there was no tempo.

Now the part I held back for three weeks. I have information from one source that a technical debate has been running in the dressing room for the last few matches — whether this middle order should be pushed up or down. I kept that sentence unfinished for three weeks, because until a second source confirmed it, the sentence was not fit to publish. After this match I got the second source, and only then did I write it. It is not that the information is big in itself — it matters because it matches the scene everyone could see. When you see a changed order at nets and hear of an argument from the dressing room, the two become two halves of the same picture.

I watched this innings twice. Once with the scoreboard, once watching only the batsmen's feet. The second viewing showed what the first did not. In this match Chennai's batsmen had a shorter backlift than in previous games — meaning they were coming toward the ball early but delaying the shot. That is a technical contradiction. When you come toward the ball early and play the shot late, your body is making two different decisions. The result is what happened here — an edge, the ball rising, a catch.

Here I have to say what is usually not said about a defeat like this. People will say Chennai's batting lacks depth, or the middle order is weak. I look at it the other way. This team's problem is not depth, it is order. Depth means how many batsmen you have below; order means who comes when and what is expected of him then. The batsman who came in at number seven in this match was batting at number four in his net session. When a player is prepared at nets for one role and sent in for another in the match, his mind is in two places. And when the most important part of your innings rests with a batsman whose mind is in two places, what shows on the scoreboard is not a batting failure but a management failure.

I am not saying the team management is wrong. I am saying that what happened in this match was the result of the debate running in the dressing room. And when a debate reaches the field, its first effect is on the player who has no time to resolve it.

Now the thing outsiders misread. People will link this loss to bowling weakness — a few expensive overs, a few dropped catches. But I watched the bowling again in this match, and I think the bowling did its job. Of the deliveries bowled in defence of the target, most were in the right place. The problem was that the batting made so few runs that the bowlers had no room for error. When you defend 120, one dropped catch changes the result of the whole innings; when you defend 180, the same catch becomes a story of one over. In this match the bowlers were not given that luxury.

The second misreading is that this loss was the toss. No. The toss matters, but this was not the kind of match where dew decided the outcome. The ball turned as much in the second innings as in the first, and the batsman who got set was scoring. I wrote both innings' pitch behaviour in the same notebook — the behaviour of the ball in the 12th over of the first innings and the 12th over of the second was much the same. When the pitch is the same for both teams, the loss should be written on intent, not on the pitch.

There is one more thing I keep seeing this season, and it is not only Chennai's. Teams are abandoning risk in the powerplay and trying to make up for it in the middle overs — where spin and slower balls do not let them. On paper this strategy looks fine, but on the field it means a batsman is playing in two different gears. And when you play in two gears, your technique stays in one while your intent has moved to the other. The balls Chennai's batsmen left in the first six overs in this match were the result of that dilemma.

I cut this innings down to 450 words and only then did the story stand up. What survived was this — a team that cannot trust its own order, a middle order searching for its role, and a bowling unit covering a gap it did not create. The rest was noise.

What to watch next. The thing to watch in the next match is not the score — it is whether the batting order at nets changes again. If the same player is standing at nets in the same role he was given in the match, then the argument in the dressing room is over. And if the order changes again, then the problem that showed on the scoreboard in this match will be waiting behind the same door in the next. I will wait outside that door. The question is not whether the team wins or loses. The question is when the door opens, and who walks out when it does.