De Silva Steps Down from Test Captaincy: An 18-Match Ledger, an Empty Chair, and a Ticking Clock

Hook: Four Numbers, One Unfinished Ledger

18 Tests. 7 wins. 1,130 runs at 36.45. 9 wickets at 44.44.

Stack those four numbers together and what forms is not a farewell speech — it is an unfinished account book. Dhananjaya de Silva has relinquished the Sri Lanka Test captaincy, but remains available as a player. Sri Lanka Cricket (SLC) CEO Ashley de Silva — a coincidental namesake — publicly thanked him and wished him well for the rest of his career.

I was reading the announcement at my own desk in Khulna. Regular readers of this column know I never read a transfer, an appointment, or a resignation through emotion first. I open the ledger first. Who paid, who received, under what clause, on what date, and whose shoulders the risk landed on. Dhananjaya's resignation contains the raw material for exactly that exercise — and also lacks it. What exists is nine specific data points; what is missing is the one figure that, without it, leaves this 18-match document half-read.

This is not a controversial sacking. No fire is burning, no protest placards are up. Yet when a Test side's captaincy chair empties, it becomes a structural event — and structural events always sit in a different column from match reports.

Context: Why Test Captaincy Is a Different Job

One thing needs clearing up first, because this is where most analysis stumbles. Test captaincy and white-ball captaincy are not the same post. In limited-overs cricket, the captain largely manages field settings, bowling changes, and death-over arithmetic. In Tests, that adds declarations, follow-on decisions, session-based planning, new-ball rotation, and the mental architecture of five days of patience. The same person cannot perform these two different jobs equally well on the same day — those who have managed it are the exception.

Dhananjaya's resignation is explicitly Test-specific. There is not a word about ODI or T20I captaincy. So if he holds white-ball responsibility, it survived this resignation, or it is not yet decided. That distinction is not small. Shedding one format's burden while retaining the rest is a deliberate workload decision, not a full surrender of leadership.

Sri Lanka's Test identity has another layer that sets this background. Sri Lanka's Test cricket is sharply polarized home and away. On Galle's spin-friendly surfaces they are formidable; in the pace-and-swing environments of South Africa, England, New Zealand, and Australia they are historically fragile. This is exactly why a Sri Lankan Test captain's success depends heavily on where his 18 Tests were played. Without that information, the number 7 alone says nothing — the same 7 wins could evidence a commendable rebuild, or could be a figure inflated at home.

Dhananjaya's predecessor is clear on the timeline: Dimuth Karunaratne. This duty came to Dhananjaya after Karunaratne's era. That is a normal succession chain, not the product of a sudden revolt. Counting a reign starting in early 2026, the 18-Test figure sits naturally — not long, but not fleeting either. A medium-length tenure.

Core: Opening the Ledger — The Real 18-Match Account

Now the actual work. To assess a Test captaincy I sit at three separate columns: the batting column, the bowling column, and the results column. In Dhananjaya's case, all three draw an unusually clear picture.

The batting column. As captain, 1,130 runs in 18 Tests at 36.45. Per match, roughly 63 runs. For a middle-order batter, that is a moderate but not outstanding return. A comparison is needed here. Dhananjaya's career Test average is broadly in the high thirties — around 39 — meaning his captaincy-era average sits slightly below his own norm. That gap is noticeable but not large. I will exercise caution: on a single format, in a sample of just 18 matches, a three-run dip cannot be turned into a final verdict that "the captaincy burden affected his batting." It is a directional hint, not proof.

But there is reason to pay attention to that hint. Cricket history repeatedly shows that when the leadership burden lifts, a batter's output rises — because attention shifts from strategic decisions to one's own game. Dhananjaya now stays as a player, not as captain. In that sense, a possibility has opened for his batting average to trend upward in the next Test cycle. It is a low-confidence inference, but not an unreasonable one.

The bowling column. As captain, 9 wickets at 44.44. That number establishes a specific truth: Dhananjaya is a batting all-rounder whose primary value is with the bat. His bowling is a supporting role, not a lead role. A part-time off-spinner's career average typically sits above forty — so 44.44 is no anomaly, but consistent with expectation. The implication: in Sri Lanka's Test XI, Dhananjaya can never be viewed as a specialist spinner. His place rests on batting.

From here an important conclusion emerges. Dhananjaya is a "balance" asset — a player who gives a selection a spare option, but is not a match-winning all-rounder in the Kallis or Stokes mould. That classification is why his release from captaincy is not a major tactical loss: he remains in the side, only vacating the chair.

The results column. 7 wins from 18 Tests. As a percentage, roughly 38.9%. For a mid-tier Test side, that is a reasonable return — neither spectacular nor shameful. But here is my biggest objection. How many of those 7 wins came at home, and how many away, is not given. Without that split, the number 7 is nearly meaningless in the results column. If all 7 came at Galle, it is merely a repeat of the team's historical home-ground tendency, no new story. If two or three came abroad, it is a significant achievement. The same 7 leads to two entirely different conclusions. This gap is an admission of my own limitation, not a weakness of the analysis.

Reading the Clock: Appointment, Resignation, and What Was Not Said

Since I timestamp every transfer and every appointment, I do it here too. Dhananjaya took over from Karunaratne in early 2026. The resignation arrives at the tenure's end — short-to-medium. This timeline carries a specific significance: it reads as a planned handover, not a forced removal. Why? Because the SLC CEO's tone is warm, and the player himself pledged continued availability as a player. A sacked captain does not usually carry both signatures at once.

Here my "clause-as-clock" logic applies. A release clause is a clock with a price tag, not a promise. Similarly, a captaincy tenure is a clock — how long, how many matches, how much mandate. Dhananjaya's clock has now stopped, but his successor's clock has not yet started. And for a Test side, the gap between these two clocks is the riskiest period. Who takes charge, how long they stay, whether they function in both home and away conditions — until these questions are answered, Sri Lanka's Test planning sits in an indefinite state.

Workload Management, or Generational Turn?

Two possible explanations surface. The first is workload management: Dhananjaya is in mid-career, plays multiple formats, and Test captaincy is the most time-consuming role. Lifting the duty extends his playing life. The second is generational turn: a board often wants to refresh leadership ahead of the next Test cycle, especially if the plan is to build a younger player for the long term.

I cannot choose between them, because the information does not allow it. But I note which explanation is more comfortable for the board. A warm farewell message fits both explanations — that is its diplomatic advantage. This ambiguity is not accidental; it is the language of a smooth handover.

The Namesake Trap

A small but important point. The CEO's name is Ashley de Silva; the player's is Dhananjaya de Silva. For media it is an appealing coincidence, but for analysis it is a trap. An executive and a player are two entirely different roles, different accountabilities, different ledgers. Conflating these two names instantly makes the analysis wrong. I avoid it here, but remind readers to stay alert.

Contrarian: The Blind Spot in the Official Narrative

The official narrative is simple and comfortable: an experienced captain gracefully stepped down, the board warmly thanked him, and he stayed as a player. No villain, no controversy.

And that is exactly where the blind spot hides. When a resignation is this clean, this polite, the question should be — who bears the cost of this cleanliness?

The answer is a ledger-level one. The biggest cost of this handover goes to no one's bank account; it goes to an empty chair. Eighteen matches of experience, a specific tactical memory, a learned skill of session management — this capital is written into no contract. When an experienced captain leaves, the side loses an invisible asset that never shows up in statistics.

The second blind spot is subtler. The announcement never says whether Dhananjaya resigned or was asked to. The difference between those two tells you how genuinely optional the event was. In a planned handover, the board fixes a successor first, then announces. Here there is no successor's name. No successor named means the chair has not yet been given to anyone — and in a Test side's planning, that is a real vacancy, not diplomatic courtesy.

The third blind spot: no one gave the home/away split of the tenure. The number 7 is a sealed envelope. It can be read any way you like — some will call it a successful tenure, others an inflated one. The truth is we do not know, and those who do have not yet said. This informational silence is the biggest warning.

Takeaway: Toward the Next Room

The question now is not "why did Dhananjaya step down." The question is: when does the next Test cycle's clock start, and in whose hands?

If SLC can name a credible, long-term Test captain within weeks, this handover becomes a small footnote in history. If the succession question drags, a mid-tier Test side loses its scarcest asset — stable leadership — exactly when the next cycle should be planned.

And Dhananjaya himself? An unburdened middle-order batter's average trending upward seems real to me. Some will call it a gain for the team. I would call it a rebooking — an empty chair in the team's column, a few more runs in the player's. The two columns of an account do not always balance; sometimes the debt merely changes direction.

I wait. In Test cricket the clock never stops — it only pushes forward the question of who can afford to take time, and who cannot.