44.44 vs 36.45: The De Silva Captaincy Ledger That Never Made the Headline

Two numbers have been stapled to Dhananjaya de Silva's name in the coverage of his Test captaincy resignation. The first is 1130 — his runs in Tests as captain, at an average of 36.45. The second is 9 — his wickets, at 44.44. The first belongs to a middle-order batter; the second to a supporting off-spinner. Both are true. But set side by side, they produce a third picture: a bowling average eight runs higher than his batting average. That gap is the tell. Sri Lanka never picked him as a frontline bowler; they picked him as a batting-balance cricketer. And that is exactly why his captaincy deserves reading rather than summarising. Eighteen Tests, seven wins — that is the only sample left. Test captaincy is a separate profession. It has little in common with white-ball leadership, and the differences run deep. When to declare, who takes the new ball, how to divide the sessions, where to place the field, whether to enforce the follow-on — these are all Test decisions, and none of them show up in limited-overs cricket. De Silva's resignation is therefore confined to a single format. Not a word was said about ODI or T20I leadership. That boundary matters, because captaincy news is routinely smeared across all formats — which is a misreading. He took the job from Dimuth Karunaratne. In the rhythm of Sri Lankan Test succession, that handover is nothing new — the island has a long habit of handing the five-day burden to an experienced batter and easing change through. But the sample is small: 18 Tests. A full World Test Championship cycle is longer than that. This is not a long reign; it is a medium-length chapter. Sri Lanka Cricket's CEO, Ashley de Silva — who shares a surname with the player Dhananjaya, a coincidence that produced some mild curiosity in the coverage — publicly thanked him and wished him well for the rest of his career. The language of that statement is cool, polite, institutional. No anger, no grievance. This was not a removal by force; it was a step down negotiated through agreement. Now the ledger itself. Seven wins from 18 Tests is a win rate of roughly 39 per cent. For a mid-tier Test side that is neither shameful nor remarkable. But here the first problem appears: those seven wins cannot be read without knowing how many of the other eleven were draws, how many were defeats, and which were at home and which away. The home-away split is the central question for Sri Lanka. The island's Test identity runs on two poles. On the spin-friendly surfaces of Galle they are formidable; in South Africa, England, New Zealand and Australia they have historically struggled. So without knowing how many of those seven wins came at Galle and how many abroad, judging the captaincy is impossible. Anyone drawing a verdict from the aggregate is taking a full decision from half a picture. The individual numbers fall into the same trap. As captain he scored 1130 runs at 36.45 — a little below his own career Test average of roughly 39. The gap is small, but it exists. The question is whether that dip reflects the weight of leadership or ordinary variance. The honest answer: the source cannot say. The figure covers only his captaincy period. The rest of his career, the splits by opposition, the splits by pitch — none are given. There is no clean before-and-after base. The bowling picture, by contrast, is clear. Nine wickets at 44.44 is the average of a supporting off-spinner, not a frontline bowler. It is tempting to assume his place in the side is built on bowling; in reality it is not. His selection rests on batting. He brings balance to a Test XI, but he is not a match-winning all-rounder in the Kallis or Stokes mould. That distinction matters, because the word 'all-rounder' carries a great deal of excess weight in subcontinental cricket talk. So what was his real contribution as captain? Probably the things the scorecard cannot hold: session management, trust placed in young bowlers, the patience to keep a spin attack pressing on a home surface. Those live not in the numbers but in the tempo of a captain's decisions — and the only way to measure that is match by match, not from a list of results. This is where the conventional explanation stops working. A line has been circulating: freed of the captaincy, de Silva will bat better, because the burden lifts. The argument sounds good, and world cricket has precedents. But it is a hypothesis, not proof. Look at the numbers: his captaincy batting average of 36.45 sits below his career average, yes — but by only three or four runs. A gap that small does not prove 'burden'. Real pressure would show a wider gap, or collapses in the biggest series. Nothing in the source shows that. The likelier explanation is plainer: across a small 18-Test sample, a few poor innings drag an average down, and that is all. There is a second trap, one this kind of story almost always falls into — turning a leadership change into a 'crisis'. There is no crisis here. If anything, the opposite: the board's statement, the player's stated willingness to keep playing, the language of praise — together they mark a clean, board-endorsed handover. Anyone trying to build a tale of power struggle or discontent has no material to work with. No such claim is made here, because the source does not support it. It is worth stating plainly what this model cannot explain. Without the home-away split, the strength of opposition, the type of pitches, the effect of injuries, the luck of the toss, anyone who claims 7/18 proves de Silva a good or bad captain is on thin ground. Sometimes results are fixed by fortune, injury or one bad session, not by a structure. Admitting that is a strength of the analysis, not a weakness. The biggest gap, though, is elsewhere: no successor has been named. That silence is the most important fact in the story. Test leadership is not merely a name; it is a direction. If a new captain arrives with aggressive fields and quick bowling changes, Sri Lanka's Test face shifts; if a defensive, patient model is chosen, the current line continues. Until the succession question is answered, this resignation remains an unfinished picture. Age belongs alongside it. De Silva was born in 2026 — now in his early-to-mid thirties. That is the age at which careers bend, and the age at which sides should start blooding the next Test generation. If this resignation sits on that curve and on a rebuilding plan, then it is not one man's decision but a generational handover. The media temperature is low, too. This is not a story of outrage but a polite, administrative item. In the India-Pakistan market, a sacking generates a cycle of fury; here there is not a shadow of it. Sri Lankan cricket media may frame it as a moment of generational change, but the effect on the global game is slight. Test viewing figures are a small slice of the worldwide cricket audience as it is. On the industry side the effect is close to zero. A Test captaincy change in a mid-tier market does not move broadcast rights, league economics or capital flows. Test captaincy carries less direct commercial value than white-ball leadership or IPL association, so this resignation will not shift de Silva's market value materially. That is a fact, not a forecast. One further possibility deserves a mention — workload management. Test captaincy is an added load for a batter who plays every format. If the board calculated that shedding the armband would protect both his batting and his fitness, then this is a deliberate decision, not an abrupt walk-away. Three signals are worth watching over the coming months. First, how quickly Sri Lanka Cricket names a successor — weeks, or a long gap. Second, whether the home-away split emerges, which would revalue the whole 18-Test record. Third, de Silva's next Test innings — does the average climb above 36, or settle there. Sri Lanka's Test planning now faces a clear deadline. Once the next captain is known, before the coming Test cycle begins, it will be possible to judge whether this was a clean exit or the start of a new method. For de Silva the question is simple: with the weight gone, does the bat truly free itself, or does it stay near 36.45? The next few Test series will answer it. Before that, though, we need the home-away split nobody has yet shown.