Adelaide's 36: A System Failure Decoded from a Coach's Notebook

Adelaide's 36 was not just a batting collapse. In my notebook, it is a sequence of ten dismissals, eight of which were catches behind the wicket — all on good length, on top of off stump. I have been reading that score backward for three years, and every time it reveals the same thing: no magic, no bad luck. A pattern that made headlines that day but was already visible in the first session. I am a coach and commentator, and for the past few years I have been auditing that Adelaide day — where every ball is an entry, every shot a receipt.

Context: The story was not the pitch, it was the process

The Adelaide Oval pitch historically aids fast bowlers, but what happened in December 2026 was not just about the pitch. In the first innings, India scored 244 and the match was evenly poised at lunch. Then, in the second innings, they were bowled out for 36. I logged every ball that day: which bowler, which release point, where the catch went. This is the same method I learned during the 2026 Karnataka Premier League — when I called a carrom ball a straight one in my first over and then started writing every bowler's release point on my palm. Since then, I have two notebooks: one for what happened, one for what almost did. Adelaide's 36 belongs to the second category — what almost showed itself, but we chose not to see.

Core: Ten dismissals, eight catches behind — why?

In that innings, 10 wickets fell. According to my notebook:

• 8 catches behind the wicket (keeper or slip) — all on good length balls on top of off stump.
• 1 LBW — a ball that came in and hit the pad.
• 1 bowled — a ball that stayed straight and hit the stumps.

None of these dismissals were the result of a batsman attempting a big shot. They were all around defensive prods — either edging or hitting the pad. The bowling was accurate, but there was a clear gap in the batting strategy. The rhythm the Indian batsmen built in the first innings broke in the second, and with it, the angle of the backlift changed. I mapped the batsmen's shots against balls from three different pace bowlers (Cummins, Hazlewood, Starc): where in the first innings batsmen were leaving balls to the keeper, in the second innings the same balls were popping up to slip. It was purely a technical imbalance that had already started showing in the last few overs of the first innings when Starc beat the batsman twice.

My key finding: Adelaide's 36 was not a 'collapse' but a 'process failure'. The batting order failed to read the slight bounce and seam movement that changed within a session in the second innings. The Australian bowlers started pitching the ball on top of off stump, and the Indian batsmen tried to defend on that same line when they should have left it.

Contrarian: Was '36' a warning that paid off in Brisbane?

Here is a counter-intuitive angle that common analysis misses. What I saw in Brisbane in January 2026 made me start reading my Adelaide notebook backward. In Brisbane, seventh-wicket batsmen Washington Sundar and Shardul Thakur shared a 123-run stand. How did they defend? They left the same balls that our top order tried to play in Adelaide. Adelaide's 36 was a lesson that the team applied in Brisbane — but the question is, should it have taken a month to apply? As a coach, I would say: no. If we had a simple field map of that innings — showing a 'corridor' where every catch went behind — the correction could have come in the next innings. But in cricket, we often treat the result as the 'lesson', whereas the lesson lies in the process. The first field map in my notebook began where the L4 cracked — that is, when I was 17 and could not go onto the field, I started drawing every over. That habit taught me that if you cannot draw where the nine fielders stood, you do not understand the passage of play well enough.

Takeaway: Next time a score reads 36, don't look at Adelaide — look at the notebook

Whenever a team collapses for 36, the media fills with phrases like 'the stadium held its breath'. For me, that score is a list: ball, line, length, catcher's position, bowler's wrist. Next time India find themselves in such a situation, I will look for whether the team has a 'pitch-behaviour' data sheet that can warn them in the last ten overs of the first innings. Because Adelaide's 36 was not an end — it was a pattern I can read backward, and one you can read forward next time.

Next time a batsman is out at 36, ask: did this wicket fall, or had it already fallen?