A Kingsmead Evening, Stubbs's Silence and Rabada's Shadow: The Proteas' Batting Question Nobody Wants to Hear

Around six in the evening the Kingsmead stands had almost emptied. One of the few people still sitting — a man past sixty, in a blue jacket, a small old notebook in his hand — did not get up even after the close-of-play announcement. Walking past, I saw him staring at the scoreboard, as if committing the numbers to memory, as if checking whether they were sitting in the right places. Later he turned to me and said, "I have been coming here since the seventies. Batting does not collapse like this — it is made to collapse."

That single sentence holds the whole Durban story. I have spent fifty years learning that the beat of cricket is never just the ball; the beat is in the people around it — the man in the empty stand, the small sums jotted in the corner of a notebook, the silence after a defeat. This Durban drubbing is not simply a result. It is a team squaring accounts with itself — and the road it has chosen to do that is the real news.

Tristan Stubbs has been dropped. A batter with just two Tests of experience has been called up. Kagiso Rabada's return is being eyed. Three decisions, one direction. But what is presented from outside as "accountability" points, from inside, to something far older, far more familiar — a problem the Proteas have carried in their bag for two decades and re-packed after every defeat.

Durban, Kingsmead, and an old address

Kingsmead in Durban is an old address for South African Test cricket. Here the ball seams, bounces, and tests a batsman's patience over and over. When a batting collapse begins at this ground, it is not the business of a single session — once an innings starts breaking, it spills across the day, like a wall that pulls itself down when one brick is removed. The coastal air, the moisture and the body of the pitch combine to build an environment where a batsman who opens his hands once, or gets stuck once, finds the road back hard either way.

So when I read this Durban drubbing, my mind goes back to 2026. On October 14, at the Etihad Stadium, Manchester City blew Stoke City away 7-2. I did not write a report of that match — I recorded a twenty-minute podcast from the press box, because I was beginning to understand that a demolition is sometimes not a scoreline but a system. Just as that night at Stoke told the story of Guardiola's inverted full-backs, the evening at Durban tells the story of a structure — only this time the ball is red, not round.

The man who has come since the seventies probably has the sums of eight or ten innings jotted in his notebook. Which means he can see a pattern that never shows on a television screen. He was saying that batting does not collapse — it is made to collapse. I noted that sentence that day, because it is the rare, honest explanation of the selectors' recent decisions.

Context: a team whose batting never settled

South Africa's Test side has long run on a familiar mould — strength in bowling, fragility in batting. Hashim Amla, AB de Villiers, Faf du Plessis, Dean Elgar — that generation has left one by one, and after them the top order has never fully settled. This is not the story of a weak generation. It is the story of a pipeline — one where the patience, defence and long innings that Test batting demands has fallen a generation behind.

My own experience tells me the Test top order is like the foundation of a house. Once the foundation shifts, however beautiful the floor above, the risk remains. In South Africa's case the bowling is the upper floor — arranged, sharp, a Rabada-led attack that can flatten any side in one innings. But the foundation, the top order, keeps shifting. And when, instead of fixing that shift, the selectors drop one batter and bring in another untested one, the problem is relocated rather than solved.

Without this context it is easy to dismiss the three recent decisions as mere "reaction to a defeat." But the asymmetry inside those three decisions is deeply telling.

The core: three decisions, one direction

The first and most revealing point is the asymmetry. When a team loses, its reaction usually reveals where it believes it failed. Here a batter has been dropped, and the team is eyeing the return of a fast bowler. This asymmetry speaks plainly — the team's own diagnosis is that the batting failed and the bowling attack needs reinforcement.

That is the biggest signal. When a team, after a failure on one side, busies itself strengthening the other side, it tells you they are looking for the problem in the wrong place — or know it, but do not want to admit it. If a batting collapse was the main cause at Durban, where is the logic in dropping one out-of-form batter and bringing in another with less experience? This does not raise the quality of the top order; it raises uncertainty.

The second point is the dropping of Tristan Stubbs, and it is far more complex than it looks. Stubbs is essentially a white-ball power-hitter — whose strength is scoring quickly, holding a strike rate, playing over fielders' heads. Test cricket wants the opposite: average, patience, the ability to leave the ball for long stretches, and the temperament not to score off good balls as well as bad ones.

Here the real question hides. If Stubbs's dropping is based on one Test's form, it is a decision; but if it is role-related — that is, he was being played in a position not natural to him — then it is a selection error, not the player's failure. Test history is full of examples: a talented batter is placed in a low or unnatural position, fails for two or three innings, is dropped, and is told "he cannot play Tests." Yet the problem was not the batsman but the place he was slotted into.

At this point I think of a former bowler — Syed Abid Hussain Sami, who taught himself and reached the international commentary box through a density of data and knowledge. His method was simple: do not judge on one innings, look at the pattern. The same is needed with Stubbs — which position he was batting in, what kind of deliveries he was falling to, in which session he was out. Without this information, dropping him means deciding a career's future from a single innings' sample.

The third point is perhaps the most worrying and the least discussed — the call-up of a batter with just two Tests. Settling into a Test middle order usually takes fifteen to thirty Tests. Sending a player with two Tests of experience into the match after a drubbing means placing him under pressure where the blame for failure lies not with his ability but with the team's lack of planning.

Here is my biggest observation. When a team brings in someone with two Tests of experience in place of a proven international batter, it means one of two things: either there is no better reserve for that position — a clear signal of a batting-pipeline crisis; or the selectors are consciously choosing a specific attribute over experience. Both carry risk, and in both cases the reality of Test cricket is this — the lack of experience shows in the first two or three innings, while the batsman takes his time against the movement of the new ball and the slip cordon.

There is talent in South Africa's domestic first-class cricket — no doubt. But having talent and converting it at Test level are two different things. This two-Test call-up points to a weak spot in the bridge of that conversion.

Rabada: a shadow that covers the whole attack

Kagiso Rabada has taken more than three hundred Test wickets for the Proteas, and his bowling average writes his name among the best fast bowlers of the modern era. These figures say more than one thing — they tell a story of dependence. Because when a team relies so heavily on one fast bowler, that is a systemic risk.

The currency of Test cricket is taking twenty wickets. A side that cannot do it cannot win a match — it can draw, it can lose. With Rabada the probability of those twenty wickets jumps; without him it falls. That is his true value — not how many wickets he takes in a given match, but what happens to the whole attack when he is there.

There is a subtle hint here worth spelling out. The report says the team is "eyeing" Rabada's return — that is, he has not yet definitively returned. If a team is uncertain about its lead fast bowler's return, the attack for the next Test will probably not be as sharp.

And here is the real story. The Proteas' problem is not this Durban defeat — the problem is that their model of success depends on one man's body. Reading Rabada's age alongside the natural cycle of fast bowlers, this dependence will face more questions in the coming years. If the board does not build a second strike option now, the innings-by-innings burden on Rabada will only grow.

Here I think of a former Bengali commentator — Shamim Ashraf Chowdhury, whose voice is one of the signature sounds of Bangladesh's home broadcasts. When an over with a new ball began in his voice, he did not merely describe the ball's pace — he could hear which bowler was coming on with the new ball, because a new ball means opportunity, and in whose hands that opportunity is placed tells you the team's plan. The Proteas' plan right now is simple and risky: the opportunity is in one pair of hands.

SA20, the calendar, and an invisible pressure

It is important to add a piece of context here, even though the core facts of this article do not directly prove it. The ownership of South Africa's franchise T20 league, SA20, lies mainly with IPL franchises — a well-known reality. That league has created a kind of tension with the red-ball calendar, where questions arise over players' rest, availability and priorities.

I mention this because behind a squad reshuffle there is sometimes not only form but the pressure of the calendar. But to be honest, in this specific case I have no information to prove the calendar's role. It is a background flag, not a conclusion. And that is the point — in searching for a clear reason behind everything in cricket, we often skip over the structural ones.

The outside reading, the inside truth

Now we come to the place where the outside world and the inside reality separate. What usually follows a drubbing is an atmosphere of accountability — pressure from media, fans and the board to "do something." What is done under that pressure looks like a decision, but is often just a pressure valve.

The most important argument of this piece is this: a single Test drubbing is not proof of a crisis — Test cricket is the very format where one session, one toss, one pitch can overturn a whole match's outcome. This five-day game creates the most sample noise of all. If a team begins to break its own structure after one bad session, it is really chasing smoke.

The outside reading is clear: Stubbs failed, so he is out. But the inside truth may be entirely different — Stubbs may have been batting in a position where he does not feel at ease, or the team may be heading into a series in an environment where a specific attribute is valued more than experience. Either way, the decision is not Stubbs's to own.

Another thing this reading drops — a batting collapse is usually not one person's failure, it is a collective one. A top-order collapse happens when, from top to bottom, no one holds patience, no one can carry the team through a session. In this situation, dropping one young batter and bringing in another with less experience is like removing one chair from a room and placing another — the crack in the wall remains.

I remember my own podcast. I started the podcast because the Blue Moon needed a heartbeat, not a highlight reel. The same is true of cricket. Supporters do not just want the scoreline — they want to understand why. And in this Durban affair the answer supporters are getting is probably incomplete, because the team itself has not yet managed to ask the right question.

Looking forward: what to watch

So in the days ahead I will keep an eye on three things. One, Rabada's availability — whether he is named in the squad or loses out to a medical bulletin. Two, the first two or three innings of that two-Test batter — success validates the pipeline, failure exposes the depth. Three, whether Stubbs's omission is a short-term rest or a long-term freeze-out.

The answers to these three questions will build a picture that no single scoreline can ever give. I have spent fifty years learning that the beat of cricket is never just the ball; the beat is in the people around it — the man sitting in the empty stand, the sums in his notebook, the question hidden in the silence after a defeat. Nobody wants to hear the Proteas' batting question — but the evening at Kingsmead said exactly that, and there is no way to deny it.