Sri Lanka's New Test Captain Kusal Mendis: The 36.36 Average and the Selection Committee's Silence

The meeting the Selection Committee held at Sri Lanka Cricket's headquarters was not a match report. It was not the 42nd over of an innings, nor the ball after drinks. It was a file — a document of decision, in which a new name has been placed beside Dhananjaya de Silva's: Kusal Mendis, the new captain of Sri Lanka's Test side.

When I first read the news, I stopped. An announcement of this kind adds not a single run to the scoreboard, yet it reshapes the power structure inside a team. And with changes like this, an old habit of mine kicks in: before looking at the name, I ask — why now, why this man, and what are the facts that were left out actually saying?

The second question matters most here, because this announcement carries a large silence.

We need to understand where Sri Lanka's Test cricket currently sits. In the ICC World Test Championship (WTC) cycle, Sri Lanka is a mid-tier side. At home, on spin-friendly pitches, they are strong; away, in the seaming conditions of South Africa, England, Australia or New Zealand, they lose consistency. This pattern is not new, and it is not the product of a single series — it is a structural tendency built over decades.

Against this backdrop, a leadership change carries distinct weight. The WTC is a points-based championship, where selection consistency and planning stability across multiple series feed directly into the points table. If the captain changes every series, that consistency never forms. And in recent years, the rate of captaincy change in Sri Lankan cricket has been notably high.

Dhananjaya de Silva has stepped away from the role. The announcement states no reason. Form, results, workload, or a planned succession — none of it is stated. That silence is, in fact, the biggest piece of information here.

Let us look at Mendis's numbers. 75 Tests. 4,836 runs. An average of 36.36. Ten centuries, twenty-three fifties.

At first glance the numbers paint an established player — a career of more than a decade, a substantial volume of runs. But when the average is 36.36, the question becomes: why has a top-order batter with 75 Tests never crossed the 40 mark?

That average is the central question of this appointment. In Test cricket, an average below 40 for a specialist top-order batter means a gap between talent and output.

The gap becomes clearer in the conversion rate. Ten centuries from 33 fifty-plus scores — roughly a 30 percent conversion. For elite batters this figure generally sits between 40 and 50 percent. Thirty percent means the same pattern returning again and again: he gets in, but does not go big. For testing a selector's patience, this thirties-and-forties profile is ideal.

One important addition is needed. Whether Mendis plays as a wicket-keeper batter changes the meaning of the calculation. If he keeps, a mid-thirties average is broadly acceptable — keeping imposes a tax on batting output. But if he plays purely as a top-order batter, the same figure is a burden on the team. The announcement does not clarify his exact role.

This is my second concern. A wicket-keeper captain must carry three jobs at once: batting, keeping and captaincy. This triple load is mental as much as physical. And Test history holds precedents where the added weight of captaincy has temporarily pushed a batter's average down.

The age curve cannot be left out either. His Test debut came in the mid-2010s, which places him now between 27 and 33 — the prime batting window. At this age an average usually sits at its ceiling. This does not mean he is playing badly; it means the average is unlikely to jump dramatically through technical improvement alone.

Russia 2026 taught me to trust the timestamp before the story. There I learned that the press-conference sentence is not the witness — the clock is. The same applies here. The story of this appointment has not yet been written, because no one has shown the clock behind the decision.

Now I come to the place where the discussion usually turns the wrong way.

In Sri Lanka's cricket-mad market, the loudest question after this news will be: why was Dhananjaya removed? But the announcement holds no answer, so all discussion will end in speculation.

My way of reading is different. The real significance of this decision lies not in the name but in the process. The Selection Committee took the decision at a formal meeting at SLC headquarters. That is the ideal, rules-consistent route. There is no signal of government interference, no eligibility dispute, no integrity concern.

And here I stop. Because I do not name a pattern until I have seen it three times. The cleanliness of one appointment process does not prove that the next three will be clean. Sri Lankan cricket has a history of board-level turbulence — interim committees, suspensions; none of this is new.

There is another gap everyone skips. The announcement names no upcoming series or opponent. That means one of two things: either this is a forward-planning decision, or it is a reaction to a series absent from this news. The evidence for both possibilities is equally missing from this text.

Mumbai taught me that in scarce space, every decision is a luxury. For Sri Lanka's Test side, that scarce space is leadership continuity. The biggest contrarian point is this: the appointment leaves an unresolved question about the wicket-keeping role, and unless that is settled, the captaincy load will damage the batting.

So what do we watch now?

Mendis's batting average in the first Test series. If it falls below 36, the concern about captaincy load is validated. Second, Dhananjaya de Silva's status — whether he stays in the side will tell us if this was a clean handover or something else. Third, Sri Lanka's movement in the WTC points table.

Without these signals, all other discussion is a verdict reached before its time. And my habit is — not to decide before the time.