India vs Australia: 36 All Out in Adelaide to the Gabba Win — A Scheduling Problem, Not a Character One

19 December 2026, Adelaide Oval. Third session of a day-night Test, floodlights on, pink ball. India had already folded for 244 in the first innings, and as they began the second the scoreboard read 0 for no loss after 9 overs. Then Indian Test history's lowest total arrived: 36 all out. Josh Hazlewood took 5/8, Pat Cummins 4/21, and eight Indian wickets fell inside 25 runs. I was running a YouTube watchalong for 3,000 viewers from a rented desk in Hackney, and by the time the score hit 26/8 the comment section had one refrain: this team has sold out, this is a defeat of character.

What I said on air that night remains my position, and after 17 years of watching this sport I can state it more cleanly: India did not collapse to 36 because they lacked courage, but because the third session of a day-night Test is the worst possible time window for that batting order — and before that match India had done no competitive rhythm-building for 14 days. It was a scheduling and preparation problem, and that is precisely why the conclusion drawn from it changes completely.

Context: What the Scoreboard Doesn't Say

Look at the conditions before Adelaide. India arrived in Australia with limited access to pink-ball practice matches; several senior batters had seen the pink ball only in nets, under daylight. Australia had Hazlewood and Cummins, both capable of exploiting the bounce the ball takes from the Adelaide surface in the evening — this is not a secret, it is the physics of that ground. Yet the centre of the discussion became mental toughness.

I want to establish a clear distinction here: batting in the third session of a day-night Test is a different game. The ball swings, it reverses, the bounce becomes uneven, and all of this happens together with changes in light and temperature. India's second-innings collapse in that Adelaide Test happened to a side that had just begun, nine overs earlier, to read the weather and the ball — that was not technical ignorance, it was a lack of experience created by the calendar, not the coaching staff.

The centre of my argument that night was simple arithmetic nobody printed: the collapse to 36 took 90 minutes, whereas in 2026 India had made 250 and 307 at the same ground in a day Test. The difference was not the batters; the top order was almost identical. The difference was the timing of the ball.

Core Analysis: The Calendar Took the First Wickets

To understand Adelaide you have to look at the previous 18 months. India had played back-to-back home and away tours through 2026-20, and in the post-COVID bio-bubble teams sat in one place for weeks. When you put a side in quarantine for 14 days and then drop it straight into a day-night Test, the intensity you demand is both physical and technical — and both require time.

The counter-intuitive point is this: the Adelaide defeat saved India. Had that match been played in daylight, India might not have been bowled out for 36; they might have made 200, and the familiar improvement narrative would have taken over. The genuine capitulation forced the team management to accept an uncomfortable truth: 244 in the first innings on that pitch was actually better than 244, and in the second innings the batters did not throw their wickets away — the ball took them.

That was the gist of my twelve-tweet thread that night, and I stand by it. India's reserve depth at the time was remarkable; on air I named five players on the bench who could have walked into the XI — Shubman Gill, Mohammed Siraj, Navdeep Saini, Hanuma Vihari, Wriddhiman Saha. That was the greatest strength of that tour, and it is exactly what got buried under the noise of 36 all out.

The Contrarian Angle: How I Could Be Wrong

The weakest part of my argument is the implication that scheduling and session timing mattered so much that individual decisions were irrelevant. That is an over-correction. At least three dismissals in the 36 were technical, not session-driven — one batter played a defensive shot instead of leaving a ball that deflected off the inside edge onto the stumps, a shot he might have played ten times all home season. That does not mean a lack of character; it means old habits return under pressure.

The second counter-argument: if scheduling was so decisive, how did the same side that made 36 in Adelaide chase 328 at the Gabba on 19 January 2026? The answer is simple and strengthens my thesis: by Brisbane India had played four Tests. The team had rhythm. Rishabh Pant's 89 not out was not proof of a talent that had been absent in Adelaide — it was proof of the process that began after Adelaide. Once you put a side into the rhythm of Test cricket, the same players who folded for 36 can chase 328. The difference was continuity, not courage.

Takeaway: Next Time the Scoreboard Says 36

Adelaide 2026 is not a lesson in character; it is a lesson in calendar design. Whenever a side collapses in the third session of a day-night Test, the question should not be whether they have the stomach for it, but how many days of preparation they had for that session. When the India-Australia programme comes around in the 2026 cycle, I will look first at where the pink-ball Test sits and how many practice matches precede it. If the answer is the same as 2026, another 36 is possible — and the commentary box will again explain it away as soul. I will count again, and say again what I said that night: read the schedule first, then talk about character.