De Silva Steps Down from Sri Lanka Test Captaincy: What the 18-Match Ledger Says — and the Column It Leaves Blank

Eighteen rows in a ledger. Seven of them carry a win in the right-hand column — 38.9 percent. At first glance the number looks middling, almost tepid. But the story moving through Sri Lanka's cricket circuit this week is not a scorecard from a single match; it is a leadership handover — Dhananjaya de Silva has stepped down from the Sri Lanka Test captaincy. That is exactly where my objection begins. A ledger only works when both its columns are filled. Here the debit column exists; the credit column was never shown. Test captaincy is a distinct profession, and its mechanics do not match ODI or T20I leadership. Declarations, session management, new-ball rotation, field placement — every calculation differs. De Silva inherited the role from Dimuth Karunaratne. He is primarily a middle-order batter with part-time off-spin — meaning his core capital sits in his batting. Sri Lanka Cricket's CEO, Ashley de Silva, publicly thanked him, and the reports are explicit: Dhananjaya remains available to play for Sri Lanka as a player. One small, curious detail — the CEO and the cricketer share the surname 'de Silva.' The namesake coincidence has generated interest, but it has no bearing on the decision itself. Now let us look directly at the numbers, the only measurable evidence in this chapter. Across 18 Tests he scored 1130 runs at 36.45. That is roughly 63 runs per match — respectable for a top-order batter, but not dominant. With the ball he took 9 wickets at 44.44 — a high cost per wicket that marks him as a part-time spinner, not a frontline bowler. The profile is clear to me: he is a batting all-rounder whose selection rests on his batting, with bowling as a supporting function. But here is the ledger's first gap. Where were those 18 Tests played? On Galle's turning surfaces, or in the pace-friendly conditions of South Africa, England and Australia? Sri Lanka is historically a condition-dependent side — strong at home on spin, weaker away against pace. Without that split, the figure of seven wins is nearly meaningless. Seven wins at home and seven wins away are not the same asset. In Mymensingh I learned that a ledger is a prayer said in numbers; and a prayer is only true when every number sits in its proper place. Here, it does not. One thing, however, is clear from the information: the decision is Test-specific. There is no mention of ODI or T20I leadership — which means there is no room to mix the formats. Those who inflate this into a broader 'stepping back from leadership' are adding a column that simply is not in the source data. The market is a crowd; the ledger is a monastery. However loudly the crowd shouts, the monastery keeps its own accounts. Now to the point where most analysis stops — and where caution matters most. Looking at the numbers, many will write: 'See, the captaincy burden dragged his batting average down.' The argument rests on 36.45, slightly below his normal career average. But this falls into an old trap: mistaking correlation for causation. The gap between his career average and his captaincy average is small; across an 18-Test sample, that gap is easily explained as ordinary variance. Without separating opposition, venue and batting position, explaining it with the word 'pressure' means calculating with feeling, not with numbers. This is the danger of ledger blindness. A ledger denies whatever it cannot measure — yet the weight of leadership, the trust inside a dressing room, the distance from family, the silence in a dressing room — none of these show up in an average. I deliberately keep this off the books, and I leave it unresolved. Because an analyst who forcibly fills every blank cell no longer has a credible ledger. What can be done instead is a directional hypothesis — handled with care. When the captaincy burden lifts, many batters see a modest uptick in output; it is a familiar pattern, but not a guaranteed rule. For Dhananjaya the possibility exists, but the proof has not arrived. When the stadiums went quiet, I heard the model breathing — but a model only speaks once enough sample has accumulated. Here, the sample is still accumulating. The handover process itself looks clean. The CEO's public thanks and the player's stated continued availability, read together, suggest this is not a controversial removal but a mutually agreed, board-endorsed baton pass. The CEO's phrase 'wishes him the very best for the remainder of his career' clearly implies he will keep playing, but not captaining. That clean division of roles is the most reliable element of this story. So where does the real significance lie? Not commercial, not integrity-related — it is organizational. A mid-tier Test side now carries a leadership vacuum, and the speed and quality with which that vacuum is filled will shape Sri Lanka's Test fortunes over the next six to twelve months. Will a new captain bring a different approach away from home? Or will the same home-condition reliance continue? The identity of the successor is still unknown, and that unknown is the largest uncertainty of this moment. I want to be clear about one thing, because keeping inference and evidence apart is my job. What is fact here: 18 Tests, 7 wins, 1130 runs at 36.45, 9 wickets at 44.44, the succession from Karunaratne, and his continued availability as a player. Anything beyond that — pressure, disagreement, fatigue — is inference, at a low confidence level. An honest analyst does not collapse the two into one. What to watch next is clear. First, the successor's appointment — swift or prolonged? Second, Dhananjaya's batting average after shedding the captaincy — does it settle above 36-39? Third, and most important, the home-away split of those 18 Tests. Once that split is published, the figure of seven wins must be re-read. Until then my ledger stays incomplete, and I will not force it closed. Because a ledger that refuses to acknowledge its own blank cells is no longer a ledger — it is an advertisement. The account of Dhananjaya de Silva's Test chapter is not yet closed; until the successor's name and the home-away split arrive as two entries, no correct conclusion is reachable. The question is therefore not 'who was the better captain' — the question is, 'who can write the next balance sheet correctly?'