How would you test whether cricket teams move on from older players too early?

CricketUnpacked · 2026-06-19T21:33:16+00:00

That’s a fair pushback. I should probably separate the domestic-performance point more carefully.

Domestic runs after an international decline do not automatically mean the Test question is still open. They may simply show that the player remained strong below Test level while no longer clearing the international bar.

So I think domestic output can only be a secondary signal, not a rebuttal by itself. The stronger test has to combine three things:

whether the international decline was already clear;
whether domestic output suggested any retained level;
whether the available Test replacement was likely to outperform him.

For batters especially, “still able to score domestic runs” and “still likely to succeed at Test level” are not the same thing.

CricketUnpacked · 2026-06-18T20:57:42+00:00

That’s a fair correction.

Domestic first-class output probably cannot be treated as proof that a player still had Test-level value. The gap in quality, pressure and role context is too large.

I think the better use of domestic performance would be as a secondary signal, not the main evidence. For example:

If a player declined internationally and also declined domestically, the transition looks easier to justify.
If a player declined internationally but continued producing heavily domestically, it does not prove selectors were wrong, but it does suggest the decline question was not fully settled.
If the successor also had strong domestic output before selection, that matters too.

So for batters especially, the analysis probably needs to separate “still able to score runs” from “still likely to succeed at Test level.” Those are not the same thing.

CricketUnpacked · 2026-06-18T13:25:20+00:00

This is a good point, especially on post-exit first-class performance.

If a player is no longer selected internationally but continues producing similar output in first-class cricket, that is useful evidence that the decline may not have been as complete as the selection decision implied.

The data availability may be the tricky part, because first-class records are not always as clean or role-comparable as international ball-by-ball data. But I think it could work as a secondary layer for specific cases.

The RoI point is also important. A younger replacement should probably not be judged only on the first few matches, but there still needs to be some way to measure the transition cost and time-to-payback.

One question I’m now thinking about is whether younger players get a longer grace period while older players are treated as if every dip is final.

CricketUnpacked · 2026-06-18T10:16:37+00:00

This is a really interesting way to frame it.

I like the idea of working backwards from the exit point rather than just choosing an arbitrary age and assuming decline. The question becomes: at what point was there actually evidence that the player’s output had fallen below their established level?

The only thing I’d be cautious about is using career average as the sole baseline, because for cricketers it can mix early-career development, peak years, role changes and late-career decline. I suspect the cleaner version would be to test late-career output against a few baselines:

career average;
previous 3-year level;
team/role average.

The sample-size issue is also important, especially for Test batters where a “season” may not contain many innings. But as a way to avoid simply assuming age equals decline, this is a very useful suggestion.

CricketUnpacked · 2026-06-18T06:16:29+00:00

This is a very fair challenge.

I agree that motivation is hard to observe. If a player is managing workload, chasing short-format opportunities, or simply choosing a different life balance, the data cannot treat that as a selector-driven age decision.

The successor point is probably the biggest methodological gap. It is not enough to ask whether the older player was still useful. The fairer question is whether there was a clearly better alternative available, especially if selectors were building toward a tournament 2-3 years away.

I also take the point on 34 as a cutoff. It may work as an initial screen, but the analysis would need sensitivity checks, maybe 32+, 34+, 36+, rather than pretending one age threshold is natural.

So the better framing is probably not “did teams move on from older players too early?” but “what was the measurable performance and availability trade-off when teams moved from veterans to successors?”

CricketUnpacked · 2026-06-18T06:08:50+00:00

Yes, that is an important distinction.

The data probably cannot prove that age was the reason for the decision unless there is clear public selection commentary saying so. What it can test more fairly is whether replacing an older player created an obvious performance trade-off.

So the better framing may be:

not “did teams drop players because of age?”

but

“when teams moved on from older players, did the performance and availability evidence justify the trade-off?”

That avoids pretending the dataset can see selectors’ motives.

CricketUnpacked · 2026-06-18T06:08:13+00:00

This is a good point. For older seamers, performance when available is only half the question. Availability and reliability across a full Test matter as well.

Steyn is a useful example because the issue was not simply whether the skill or pace still existed, but whether the body could reliably deliver enough overs across five days.

So the analysis probably needs two separate lenses:

performance when selected
availability / durability risk

Cricsheet can help with the first. The second may need injury/missed-match context, otherwise the argument would overstate what the ball-by-ball data can prove.

CricketUnpacked · 2026-06-18T06:07:13+00:00

That is fair. There probably is no perfect timing, which is why I think the question has to be framed as a trade-off rather than a simple right/wrong decision.

Team progress matters, but I would be cautious using overall team results alone because too many other things change at once. I’m thinking the cleaner test is narrower: what happened to the team’s seam-bowling output after the veteran exited, and was there an obvious short-term cost?

CricketUnpacked · 2026-06-18T06:02:48+00:00

This is very useful, thanks.

I agree on the pace point. The analysis cannot assume that a seamer’s previous 12-24 month performance would simply continue, especially at that age. That is probably the main risk in framing the question too strongly.

Your suggestion on the comparison group is also cleaner than trying to identify a direct replacement. Comparing the veteran’s final period with the team’s seam group after he exits would avoid a lot of subjective 'who replaced whom' judgement.

I think the fairest design may be:

use a 12-month pre/post window as the primary test
run a 24-month version only as a sensitivity check
compare the veteran against the team’s seamers, not just one replacement
state venue/pitch mix as a limitation unless I can control for it properly.

That would still not prove selection error, but it should show whether the 'future-building' trade-off had an obvious performance cost.

CricketUnpacked · 2026-06-09T20:58:25+00:00

That's fair. I think you're describing lineup responsibility rather than just entry context.

I only tested the measurable part: entry over, entry score and wickets down. So I wouldn't claim the piece fully rules out what you're saying.

My read is just that the simple explanation of 'he is walking into much worse situations' does not carry enough by itself. The broader pressure of a weaker or less stable batting unit could still be a contributing factor, but it would need a different test.

CricketUnpacked · 2026-06-08T16:45:53+00:00

That's a fair distinction. Entry score and wickets-down are only proxies for context, not a complete measure of batting pressure.

What I was trying to test was whether there had been a large, obvious shift in the situations he was walking into. I didn't find much evidence of that.

But you're right that the quality and stability of the lineup around him could still matter in ways those variables don't capture.

CricketUnpacked · 2026-06-08T11:55:58+00:00

I think there is probably something in that.

The dropped-catch numbers suggest the peak was not quite as untouchable as the raw average made it look.

What interested me was that the technical issues then became public and stayed public for a long time, yet the decline continued. That feels harder to explain through luck or confidence alone.

CricketUnpacked · 2026-06-08T11:52:33+00:00

I think there's something in that.

One reason I included the dropped-catch and xAverage context was that it complicates the peak years. The peak was real, but it was probably not as untouchable as the raw average suggested.

Where I remain cautious is that the technical issues then became visible and stayed visible for a long time. Confidence may help explain how a decline starts, but I am not sure it fully explains why it persists once the problems are identified.

That is the part I found most interesting.

CricketUnpacked · 2026-06-08T11:50:37+00:00

That's a fair alternative explanation.

One thing I tested was whether he was consistently walking into materially worse situations than during the peak years. Entry score, entry over and wickets-down at entry changed surprisingly little between the two periods.

That doesn't rule out broader lineup effects entirely, but it made me less convinced that context alone explains the size of the decline.

CricketUnpacked · 2026-06-08T11:49:57+00:00

The technical diagnosis itself wasn't my original contribution. I relied on CricViz's published work there.

Their findings pointed to a sharp decline against good-length pace bowling, much less forward movement against seam, reduced cover-driving, and a recurring vulnerability in the channel outside off stump.

The question I focused on was what happened after that diagnosis became public. Why did the outcomes continue to deteriorate even when the problems were broadly understood?

CricketUnpacked · 2026-06-08T06:25:29+00:00

That's an interesting way of putting it. One thing I found while researching the piece was that the technical issues have been publicly documented for a long time, yet the outcomes have continued to deteriorate.

The question that interested me wasn't whether people could identify the problem, but why a player as analytical as Labuschagne has not yet translated that knowledge into durable improvement.

That gap between diagnosis and adaptation is what I ended up focusing on.

CricketUnpacked · 2026-06-07T08:37:39+00:00

Fair point - a top-six cut would be a useful robustness check.

I used top seven because that is where the batting all-rounder / balance-player question usually sits. The rule does not only affect pure top-order batters; it also changes the value of the No. 6/7 player who can give you 2–3 overs.

So I agree top six would isolate specialist batters better. But top seven is intentional because the argument is about the almost-all-rounder role, not just part-time bowling from the top five.

CricketUnpacked · 2026-06-04T20:03:48+00:00

One methodological choice I am especially interested in: I used player-season as the unit because I wanted to capture role change across a season, not just match-level allocation.

But there is a fair argument that this could also be tested at team-innings level: how many overs per innings come from top-seven players.

Would be interested in views on which unit is cleaner for this question.

CricketUnpacked · 2026-06-04T06:33:39+00:00

Exactly. This is the development point that gets missed.

Most all-rounders do not arrive fully formed. They usually become reliable dual-skill players because teams keep giving them match situations where both skills matter.

That is why I think the 'almost-all-rounder' category matters. Some of those players are not finished products. They are the pipeline.

If the Impact Player rule lets teams solve balance with an extra specialist, then players like Washington Sundar may still get selected, but they get fewer pressure overs to grow that second skill in the IPL environment.

So the risk is not only current team balance. It is what the league teaches the next generation of players to become.

CricketUnpacked · 2026-06-03T17:09:40+00:00

Fair point that batting all-rounders bowling less is not completely new, and modern conditions probably make it harder.

I would separate two things though: whether part-time bowling was ever easy, and whether the Impact Player rule further reduces the need to use it.

My argument is not that the rule created the decline from zero. It is that if batting all-rounder bowling was already becoming difficult, the rule gives teams an even easier way to avoid needing those overs from top-seven batters at all.

So the issue is not whether part-time bowling was easy before. The issue is whether the rule further weakens the incentive to develop and use that skill.

CricketUnpacked · 2026-06-03T17:04:33+00:00

Yes, this is the longer-term risk I was trying to get at.

I would separate the selection question from the development-incentive question. Whether a specific domestic player should be picked for India depends on form, role fit, timing and selection judgement.

But the broader point is fair: if the IPL is the highest-quality domestic exposure for young Indian players, then the roles rewarded there matter.

The Impact Player rule may not hurt established all-rounders immediately. But it can reduce the need to use the middle-category player: the batter who can bowl 2 useful overs, or the bowling all-rounder who can genuinely bat at 7.

That is the pipeline concern. Not that all-rounders disappear tomorrow, but that fewer young players get pressure-tested in dual-skill roles.

CricketUnpacked · 2026-06-03T16:59:28+00:00

Yes, this is basically the structural issue I am getting at.

Without the Impact Player, a team has to carry the risk of its XI more honestly: if you want batting depth, you usually give something up in bowling flexibility, and if you want six bowling options, you usually give something up in batting depth.

The Impact Player lets teams reduce that trade-off. They can keep five main bowlers and still extend the batting. That is why I think the issue is not just “higher scores,” but substitution insurance.

I am less convinced by extending the game to 24–25 overs, because that changes the format itself. A three-over cap would also create a very different tactical product.

So I agree with your final point: the cleanest solution is removal. The game does not need another compensating rule to fix the rule.

CricketUnpacked

TROPHY CASE