The 36.45 Average That Ended a Tenure: Inside Dhananjaya de Silva's Test Captaincy Exit

The north stand at the Galle International Stadium was nearly empty that day. It was the second session of the third day—the post-drinks overs where a Test match is actually decided, the passage the scorecard treats as nothing. I wrote a number in my notebook: 36.45. It was not a team's run rate, not an over's score. It was the batting average of Sri Lanka's Test captain, Dhananjaya de Silva, while wearing the armband. The match was not over yet. But another match was playing in my head, one whose scorecard nobody shows you. A few days later the announcement came, and it came quietly. No thunder, no resignation drama, no "aggrieved captain" headline. Sri Lanka Cricket's CEO, Ashley de Silva—yes, the name is identical to Dhananjaya's, a pure coincidence, two entirely different people—issued a warm tribute. And Dhananjaya made it clear he remains available to represent Sri Lanka as a player. Those two sentences hold the real character of the event. This is not a retirement. This is the retirement of a captaincy. Not an announcement of giving up bat, ball and gloves; only an announcement of giving up the armband, the toss and the declaration call. In all my years writing about the machinery underneath domestic and international cricket, I have learned that catching this distinction is the most important thing. Because a captaincy transition and a retirement are two entirely different events, with two entirely different tactical and structural consequences. I launched the Sylhet Tactics Lab in 2026, out of a reading of empty stadiums. My first viral video dissected Real Madrid's 4-3-1-2—the formation that starts as a diagram on paper, and then, the moment Isco drifts into the right half-space, stops being a diagram and becomes a living machine. I brought that habit into cricket: a Test captaincy is also a diagram. Toss, field set, spell rotation, declaration timing—all a structure. The question is what Dhananjaya de Silva's structure actually was, and where it cracked. Start at the foundation. Dhananjaya de Silva took the Test captaincy from Dimuth Karunaratne. Karunaratne was a Sri Lankan opening batter, the classic Test-opener model—patience, leave, the architect of long innings. Dhananjaya is a completely different cricketer. He is a middle-order batter and, alongside that, a part-time off-spinner. So the very style of leadership changed: in place of an opening-architect captain came a middle-order all-rounder whose primary value is with the bat, with the ball as a supporting role. Now to those numbers I wrote in the notebook. Dhananjaya de Silva led the side in 18 Test matches. Sri Lanka won 7 of them. A win rate of roughly 38.9 percent. On first glance, a mid-tier return—neither spectacular nor disastrous. But here is the first trap. We are scorecard people; the moment we see a number, we start treating it as a verdict. Yet inside those 7 wins and 11 non-wins, we do not know how many were home, how many away, how many draws, how many losses. And without that split, turning 7/18 into a measuring stick for captaincy quality is a serious error. To understand why, remember Sri Lanka's Test identity. Sri Lanka is a classic home-away polarized side. At home, especially on Galle's spin-friendly surfaces, they are excellent—spinners rule there. Away, especially in SENA conditions—South Africa, England, New Zealand, Australia—Sri Lanka's Test record is historically weak against pace and swing. So how many of those 18 matches were at home and how many abroad is exactly what determines how meaningful the captaincy results are. Without that data, we are standing in a dark room holding a mirror. I think the right way to judge a Test captaincy is to see it like a football manager. In club football you judge a manager by points per match, but nobody ever asks—how hard were his first five fixtures? How bad were his injuries? How much was his home ground? In cricket we have lost that instinct. If we had a captaincy points table, the coaching mapping would be clearer. For Sri Lanka, the home matches were spin-friendly turning tracks and the away matches were pace-friendly seaming tracks. The same captain, the same squad, two different conditions, two different structures. Compressing that into a single number (38.9%) means erasing half the picture. Now to the personal data, because that is where the real story is. As captain, Dhananjaya de Silva scored 1130 runs at 36.45. That is about 63 runs per match—moderate for a top-order batter, not dominant. And here my curiosity begins. Dhananjaya's career Test average is generally in the high thirties, around 39 (this figure needs verification). So the captaincy-period average sits slightly below his own career norm. What does that say? Carefully. The gap is small, and it could be ordinary variance. But the direction hints—faintly—that the captaincy burden may have pressed down on his batting output. I am not asserting this; it is a directional hypothesis. But that hypothesis raises an important question: will his batting rise after shedding the captaincy? The bowling data tells a clearer story. As captain, Dhananjaya took 9 wickets at 44.44. For a part-time off-spinner, that average is entirely normal—part-time spinners usually average above 40. It proves he is not a lead spinner. Nor is he a match-winning all-rounder of the Kallis or Stokes mould. He is a batting all-rounder whose primary weapon is the bat, with the ball as a balance tool—giving the side an extra spin option so the team combination gains flexibility. That balance-asset role is his real value in Test selection. On home spin wickets, a part-time off-spinner means you get an extra option alongside the frontline spinners without weakening the batting order. Away, on pace conditions, he is primarily a batter. This dual role gave him a special place in Sri Lanka's selection structure. It will remain after the captaincy, because it is a property of his skill set, not of his title. Now to my favourite frame—the Sylhet Lab. I have said many times that a low-attendance domestic venue is a controlled laboratory. Sylhet, a weekday Mirpur, a morning Dhaka Premier League match—there the crowd roar, the hype and the broadcast pacing all recede, and the tactical intent becomes visible to the naked eye. Dhananjaya's captaincy tenure is just such a match to me—a low-hype, low-emotion leadership term where the structure had no crowd to hide behind. Here I want a measurement. Every decision needs a metric, or it is only atmosphere, not insight. Of the 18 matches, how many home, how many away? How many tosses won? How many declarations, how many follow-ons enforced? Without answers to these, any verdict on Dhananjaya's captaincy is incomplete. Sri Lanka's Test success is condition-dependent, so captaincy success is bound to conditions too—and that data is missing. Now to what the scorecard never shows—the timestamped turning point. In football we say "the 64th minute," where a match turns. Cricket has its own punctuation—the first over after drinks, the first over of a new spell, the 14th over of a chase. I believe matches are decided in three or four discrete minutes that the scorecard flattens into nothing. Dhananjaya's captaincy surely had such moments—a declaration, a field set, a bowling change—hidden inside 7/18 that nobody isolates. Here I want to add a warning, the easiest mistake in this event. Dhananjaya's resignation is Test captaincy only. Nowhere is an ODI or T20I leadership change stated. But our brain always wants to simplify—the captain stepped down, so something changed in every format. That is wrong. Test captaincy and white-ball captaincy are entirely different roles with different tactical demands. In Tests, declaration, session management, new-ball rotation—none of which exist in white-ball captaincy. So reading this resignation as affecting white-ball leadership means moving from wrong information to wrong conclusions. A small but interesting detail belongs here, because it is structurally important. The Ashley de Silva who gave the statement is SLC's CEO. The Dhananjaya de Silva who stepped down is the team's player. Same surname, two people. Part of the media may conflate them for a moment, but in analysis this confusion is a big trap. Matching names do not mean matching events—I always keep that caveat. Now to the counter-intuition that exposes the real structure. We all want to believe that shedding the captaincy frees a batter, that the runs return, that confidence comes back. The story is beautiful, but does the data support it? Here is my doubt. Losing the captaincy burden improves performance—this assumption is often true, but it is not a certainty. The gap between 36.45 and the career average is so small it cannot be labelled a "burden effect." It is a direction, not a decision. And here is the real counter-point: if we read this resignation as a verdict on captaincy failure, we make the biggest mistake. Because any number on a scorecard is the output of a diagram, and I believe the diagram fails before the player does. Dhananjaya's 7/18 is not proof of personal failure; it is a picture of a team structure with a vast home-away gap, a structure with no reconciliation between a spin-dependent home identity and a pace-weary away identity. Changing the captain does not change that structure. I want to be clear about one more thing, because it is my extra caution. In news like this, the easiest work is pinning blame on one person—a dropped catch, a slow innings, a wrong declaration. But who put him there to drop that catch, who made that decision? The captain, the selector, or the system? The diagram in which the fielder stood in that position was already broken. So any simple, result-driven blame of Dhananjaya contradicts this analysis. I also want to speak from the pressure of the home market, because I was born in this market and work in it. I face pressure from two sides—either softening to support Sri Lanka cricket, or becoming extra harsh to prove objectivity. I want to avoid both. So I judge against a neutral external baseline. 7/18 is a mid-tier Test return, close to the average win rate of the world's middle-tier Test sides. It is neither a shameful number nor a proud one. It is a normal number with an abnormal condition-split hidden behind it. Remember where Sri Lanka's Test team sits. They are a strong mid-tier Test side—home-dominant, away-challenged. That identity does not change when the captain changes. Dhananjaya's resignation is a leadership change, not a rebuild. Nothing in the Stage-1 information signals a broader squad overhaul. So this event should be seen as a leadership event inside a structurally stable team, not a crisis. The succession question is now central. Who does Sri Lanka make the next Test captain? And is that appointment long-term or interim? This matters because Test captaincy is a particular role. When to declare, when to enforce the follow-on, which bowler to use how much in which session—these are Test-specific tactical decisions that a white-ball captain never learns. So the next captain's format fit is a real question, currently unanswered. I can offer one cautious inference—this resignation is probably a planned or negotiated leadership handover, not a forced removal. The reason is clear: the warm SLC CEO statement and the player's stated continued availability both signal an amicable, board-endorsed change. Forced removals rarely produce this kind of warm language. Similarly, the absence of any ODI or T20I mention implies that Dhananjaya's white-ball captaincy status (if any) is unaffected or not yet decided. That is an inference, but a reasonable one. One more thing I want to be clear about, because it is the commercial dimension. A Test captaincy has far less direct commercial value than white-ball captaincy. It does not move broadcast-rights value, franchise valuations, or player salaries much. So this resignation is unlikely to shift Dhananjaya's market value materially. That is a medium-confidence inference. And I want to state firmly: any claim of a scandal, dispute, or financial driver behind this resignation is unsupported by the source. All the information is captaincy- and leadership-related. Nothing in Stage-1 involves integrity, playing-rule controversy, or DRS disputes. This is a routine administrative leadership change. From a governance view, the transition is procedurally clean. The SLC CEO publicly thanked him, the player affirmed availability—the marks of a managed, amicable change. But one governance question remains open: no successor has been named, leaving a leadership gap awaiting filling. Now a brief look at risk. I would rate the overall risk here as low. There are no integrity, commercial, or governance red flags. The two main residual risks are sporting—the timing of the successor announcement—and personnel—the loss of an experienced captain's tactical input, though mitigated by his remaining as a player. An indirect risk is the veteran core's age curve (Dhananjaya was born in 2026, so in his early-to-mid thirties), which raises a generational handover question. One thing I want to say clearly, because it is this article's core counter-intuition: this resignation raises near-term uncertainty rather than lowering it—until a successor is confirmed. That sounds backwards. But the reality is that an unnamed leadership vacuum always leaves a question mark over Test planning. Now to the public narrative. The heat of this event is low. There is no outrage, no protest, no march. What happens in the India or Pakistan market—the moment a captain changes, someone threatens to burn something, someone puts up posters—is absent here. Sri Lankan media will likely frame it as a generational-transition moment, a little louder than the neutral international tone. But the core narrative will stay calm, unless the successor choice proves contentious. On industry transmission, the effect is minimal. A Test captaincy change in a mid-tier market does not move broadcast rights, league economics, or capital flows. The India-centric South Asian market is barely affected by Sri Lanka's Test captaincy. There is no significant signal in betting or fantasy sports either. Over the long horizon, though, the quality of succession—not this single resignation—is what determines Sri Lanka's Test competitiveness. That is a low-confidence inference. I follow a notebook habit: I write the thesis before drafting, then re-read it at the close. My thesis was: Dhananjaya's resignation is a planned, low-hype leadership handover, whose main open question is the successor, and which cannot be judged by 7/18. While writing, I found a new observation—that small batting-average gap (36.45 versus the career average). It did not change my thesis, but added a possible direction. And I do not hide it—it is a possibility, not a certainty. One tactical point to close. Part of Test captaincy is declaration and the follow-on—two tools that exist only in the five-day format. To measure a captain's tactical record, you need the quality of those two decisions. For Dhananjaya, we do not have that data, so a verdict on his tactical record is impossible. That is a clear limitation for me, and I acknowledge it. Now to the forward-looking question I always keep for the end. Who will Sri Lanka make the next Test captain, and will that appointment fill the structural gaps Dhananjaya left, or merely change a name? Because if the diagram does not change, changing the captain gains little. And I have a tracking list. How quickly the successor is appointed—weeks or a prolonged gap. Dhananjaya's post-captaincy batting average—whether it lifts from 36 past 39, confirming the "freed-up" theory. The home-away split of the 18 matches—knowing it would recalibrate the tenure's assessment. And the ODI/T20I captaincy status—any change would define the scope of this transition. I have sat in empty stadiums many times and heard the game confess what the crowd usually hides. Dhananjaya's resignation is such a confession—not a story of one captain's failure, but a story of a structure, where the home-away gap, the spin-versus-pace tension, and a mid-tier team's search for leadership all become visible at once. The 7/18 number is a question, not a verdict. The question is: will Sri Lanka place the next captain inside that structure, or redraw the structure itself? I have left the answer blank in my notebook, because the answer is not yet written on the field. One last word. I believe a tactical wizard does not cast spells; he notices where the space already breathes. In Dhananjaya de Silva's resignation, that breathing space is the Test leadership vacuum. The question now is this—will Sri Lanka recognise that breathing space in time, or cover it by installing another name?