An Average of 17.68 and a Calendar Built for 32-Year-Olds: It Wasn't Cricket That Retired Jimmy Anderson

There is a photocopy stuck to a page of my notebook from last summer. It is a cut-out of a Lancashire County Championship scorecard — the bowling figures column, with fifty wickets and an average of 17.68. Directly underneath, in my own bad handwriting, I had written a single word: calf. It was not a conclusion. It was an unfinished reminder that something sits behind that number which the scorebook does not show.

There is now another cutting stuck beside it. After twenty-five years, Lancashire declined to renew the contract of England's leading Test wicket-taker. There was no retirement announcement. An Instagram post, a silence, and Emma John's column in The Guardian, in which she described a man who still wants to play — twelve days in Rome wearing the co-owner's hat at Napoli Knights, putting himself into an IPL auction at forty-two, more interested in playing the game than in his own ego.

I do not see romance in this story. I see the gap between two dates — the date on which a body was still available for bowling, and the date on which a calendar decided it should not be. For eight years my work has been to treat injury as mechanism rather than mood. In this man's case the mechanism was not cricket. It was administration.

What is public, and what is not

Let me declare my position first, because twenty-five years has taught me this lesson more than once — access is your comparative advantage and it is also your lean. I have not spoken to Anderson. I have not spoken to Lancashire's medical staff. I do not have the spreadsheet that franchise and county physios hold. What I have is public scorecards, my own notes on televised spells, the public injury log I have kept for Gujarat's seamers since 2026, and that Guardian column. Where I am inferring, I will say so and grade my confidence. Where there is arithmetic, there is arithmetic.

The month between Rob Key and Lord's

In May 2026, Rob Key travelled to Manchester and told Anderson that England would not carry him forward. The line travelled quickly into received wisdom: Anderson's international career was over. But note what happened. This was not a retirement. It was a selection decision. A board used its central-contract and selection power to close a player's door. In July 2026 he played a final Test at Lord's, and the tributes flowed. When administration retires you, you are left with three sentences and one unfinished: I told you I could still bowl, and you did not listen.

The story is not isolated. In 2026, for the first Test against West Indies at the Ageas Bowl, both Anderson and Stuart Broad were left out, and everyone assumed the careers were finished. Broad eventually chose his own ending at The Oval in 2026. Anderson did not choose his. He kept pushing until the system pushed in a different direction.

In between, he reached seven hundred Test wickets — March 2026, Dharamsala, Kuldeep Yadav. He finished with 704 Test wickets in 188 matches at somewhere around 26.6. That figure always looks incomplete to me, because it does not count the part of the work he did for Lancashire, in front of almost nobody, in April cold.

2026: when the body was raw

This is where the story actually begins and I cannot skip it. Lord's, 2026, five wickets in the first innings on debut against Zimbabwe. That was his first false signal. Five wickets against a weak batting side is not evidence of what is coming; it is frequently the opposite.

Later that same first summer, South Africa arrived, and Graeme Smith made 277 at The Oval while Herschelle Gibbs made 183. Young Anderson's figures were taken apart. That tells me more than any tribute does: raw against the top three, sharp against the bottom six. That is not a difference of technique. It is a difference of repeatability and control.

The 2026 World Cup — Cape Town, against Pakistan — is another layer. He out-yorked Wasim Akram and Waqar Younis, two old predators, in a high-pressure moment. For a young fast bowler that is the real examination: can he run in against his own heroes? He could.

Then came the injury that cost him two years — a lumbar stress fracture and a remodelling of his action. With Troy Cooley he rebuilt the action, made it more front-on, reduced the lower-back arch. That was a technical and medical decision, and it became the insurance policy of the entire career. When you take load off the lumbar spine and release front-on, the load does not vanish. It migrates to the hip and the calf. You save somewhere; you pay somewhere.

On the 2026-08 New Zealand tour he broke through properly, alongside Broad. What followed was a rare age curve for a fast bowler — a bowler who did not get quicker with age, and did not get slower, but got more precise.

I went back through three seasons of load notes, and the pattern was embarrassingly simple

Here I have to put my own favourite method on trial. Fifty wickets at 17.68. That average is the number the whole argument rests on, so it needs dismantling.

The column does not give economy or strike rate. So I build a box, and I label the walls. A fast bowler's typical county strike rate sits between forty and fifty balls. Take forty — generous for his level — and fifty wickets means roughly 2,000 deliveries, about 333 overs. Spread across the ten or eleven Championship matches that fifty wickets requires, that is thirty to thirty-four overs a match. That is far above his Test career norm, which is normal, because a Test side carries four or five bowlers.

The real question is not the total. It is the density. The Championship calendar is built in blocks — four days on, three or four days off, four days on. A month can hold ninety to a hundred overs with less than seventy-two hours of recovery between two bowling innings. The Test calendar is the inverse: forty to forty-five overs at a time, then four to six weeks. County equals high total, loosely controlled spacing. Test equals lower total, tightly controlled spacing.

Fatigue does not read the fixture list, so I translate it from football into cricket. In football we measure high-speed running, sprint distance, acute:chronic ratio — vocabulary I absorbed on Australian state beats in the 1990s. In cricket it measures almost nothing that matters, because fast bowling is high-impact and low-distance work. In a spell you run 120 metres and generate 500 kilos of torque. GPS will report a light day. The calf will report twenty-eight overs.

So in cricket we must count overs, spell length, and the number of front-foot landings, not kilometres. And here is the deeper point I have repeated since 2026: the bowler who looks freshest on the sheet is often the one already compensating. Fatigue does not announce itself; it changes the grammar. The release point drops slightly, the front leg swings a little wider, and the calf begins paying for the hip.

Every injury has a denominator, and the interesting part is who chose not to count it. The denominator here is: how many overs last season, at what intervals, and how many of those rest days were actually rest. None of that reached me from Lancashire, and that is the most honest part of this piece. I can estimate, and I will, but I will not call it evidence.

The calf: a small muscle, a large question

Calf injuries get treated as minor in cricket. That is an expensive misunderstanding. At front-foot contact, the soleus and gastrocnemius absorb a braking load of six to eight times body weight, and they absorb it eccentrically — the muscle is lengthening while it brakes. That is the same mechanical profile that loads the Achilles and the muscle-tendon junction first.

Age enters that equation twice. First, collagen turnover slows, so micro-trauma takes longer to repair — forty-eight hours for a teenager, perhaps seventy-two to ninety-six at forty-three. Second, the strength base changes. At 90mph your muscles are trained one way; at 78mph, relying on swing and seam, they are used another. Anderson chose correctly — he shed pace and kept craft. It was the most sensible decision of a thirty-year career, and it is exactly why he was still bowling at forty-two while contemporaries were three years into commentary work.

But that decision charges rent. A bowler who survives on repeatability rather than pace must reproduce the same action, many times, very precisely. Craft-based fast bowling changes the load profile: fewer explosions, more repetitions. And repetition is precisely what finishes a calf.

I have to draw the boundary of my inference here. A recurring calf is a medical signal, not a moral one. I do not have the MRI, the grading, the re-injury interval. What I do know is that soft-tissue injuries returning repeatedly across eighteen months mean the management strategy did not work. Not the player's. Ours.

The arithmetic of 17.68, and its three walls

Now the number the whole argument rests on. Seventeen point six eight in the County Championship. A good bowler in a strong Division One season averages somewhere in the low-to-mid twenties. So 17.68 is nearly as extraordinary as it looks. And I accept that it is extraordinary.

But there are three walls, and an honest analyst names them.

Wall one: conditions. This is an English summer, a Dukes ball, April to September, seam movement. It is his home environment and the ground of his core strength. His Test average sits around 26.6 across the world, on flat decks, in the fifth session of a day. This is the translation that always gets dropped: when a forty-three-year-old returns 17.68 in home conditions, you have not measured his world-class-ness. You have measured his home-class-ness.

Wall two: sample. Seven for thirty-five against Nottinghamshire on his County Championship return is the most quoted number in this affair. It is one innings. The journey from one innings to 'he is still world-class' is common in journalism and a felony in analysis. Seven for thirty-five and fifty wickets belong to different questions. One is a performance; the other is a consistency.

Wall three: the calf. The fifty-wicket consistency and the recurring injury are both true, simultaneously. Keep them apart and the story is simple: he performed superbly on a managed load. Merge them and it complicates: an exceptional average also implies he was run on selected spells rather than full quotas. My inference is that Lancashire rotated him — or rather, that is not inference but a conclusion the arithmetic forces: a forty-three-year-old bowling 330 overs and averaging 17.68 did not bowl them at full quota. Confidence: medium.

The conclusion that stings most

Now the thing I have not said this way before. A county club gave this man twenty-five years, and did not renew him despite 17.68. Everyone will call it the system's injustice. My first reading is different: this was never a performance decision. You cannot decline a 17.68 average on quality grounds. It was an age, succession and squad-planning decision. And the fact that the ECB and Lancashire moved in the same direction in the same season suggests a quiet alignment inside both that his competitive pathways should now separate.

The cut that was also a shield

The popular reading says the system is cruel. It is not. Lancashire and the ECB did not act cruelly; they lowered the dose.

Look at it as a medical figure. A forty-three-year-old bowler, recurring calf, obliged to bowl 320 to 340 overs in a county season. Load does not ask whether he is good. Load asks when the muscle-tendon junction will fail. And at forty-three that failure is not usually a new strain; it is an Achilles rupture. That is the distinction nobody explains: at that age the character of injury changes — a three-week problem mutates into a nine-month surgery. And the career was ended by neither. It was ended by the third thing.

So was the cut a shield? In part, yes. When you cannot stop a body from working and you want to keep it, you reduce the dose. Both county and country did exactly that.

But — and this is the real criticism — they reduced the dose and dropped the man. The system took care of the body and not of the person. That is where the debate worth having sits. Not system versus individual, but process inside the system versus person outside it.

The checklist is an act of care, and it is missing

In the lockdown film room I learned that a checklist can be an act of care. It remains my least fashionable argument, and I will keep making it, because Indian cricket still romanticises 'he will tough it out' as courage, and that culture is the injury factory it pretends to despise.

What should the checklist have been here? An overs cap inside the season, a spell-length cap, a minimum seventy-two-hour gap between four-day matches, weekly calf screening, and a pre-agreed exit with a formal coaching or advisory role. The last item is the cheapest and the most skipped. For a club it is a one-line press release. For a player it is two years of psychological balance.

There was no retirement announcement — the column is clear on that. There was an Instagram post, then silence. I read that as a signal rather than sentiment. It means the player has not accepted the administrative decision as final, and if he keeps performing elsewhere, every good spell becomes an indictment — of the system that released him and the people who made the call. That is not a legacy. It is institutional risk. And I say it with sympathy: Rob Key and Lancashire did what they had to do. They only did half of it. They delivered a result without completing a process.

Football's vocabulary, cricket's grammar

Now the part that garbles this story most. Workload management has become a magic phrase in both England and India, and most people import football's model into cricket without auditing it.

I will state plainly that the translation does not survive intact. Acute:chronic ratio — seven-day load against twenty-eight-day average — works in football because load can be measured in distance and recovery sits in a stable weekly rhythm. Cricket's rhythm is not weekly. It is match-based. Four days on, ten days off, six days on. Any seven-day ratio will lie to you.

Measuring cricket load requires three things: spell length, spell sequence (which spell — second morning or fourth evening), and total front-foot impacts. GPS gives you none of it. Which is why when someone says a bowler's workload is being managed, I have to ask: in what unit? If the unit is not overs, the conversation has not started.

I have one further suspicion, and I will label it a suspicion. The bowler who looks freshest is often already compensating. He changes his rhythm so he does not have to bowl through pain. The sheet shows low load; the film shows an altered action. In the logging I did on Gujarat's seamers, the most useful part was never the load. It was the drift in mechanics. In 2026, tracking Chintan Gaja's 47.2 overs across three Ranji innings in nineteen days, logging seam position and release height on 126 deliveries, the pattern I saw appeared two weeks before the injury — not in an average, but in a small shift of action.

One experience from outside cricket belongs here. During the 2026 World Cup a digital desk asked me why twenty-three-man squads looked cramped. I compared sixty-four matches and 736 players against IPL 2026's sixty matches and 1,024 player appearances, and built a load-spike table from fourteen medical papers. I missed the deadline by ninety minutes because I spent too long on the arithmetic and too little on naming my assumptions. Since then every tournament-density box I write carries its conditions. Anderson's story asks for that box.

The counter-case: the myth of 'he is still better'

Here I challenge myself. My entire argument has been that 17.68 is real and that he was moved on despite it. There is a second reading, and it is harder.

The second reading is that 17.68 is an illusion — it measures how good he is in home Dukes-ball conditions, which we already knew. It is not evidence of anything he could not do in Tests, because he did it in Tests, until forty-three, and was still removed — and that removal was part of preparing a contest whose result is not yet settled.

My hardest question is not whether Lancashire were right. It is whether England's new seam attack, if it underperforms over the next two years, will be judged against what they had and released. I see no data for that. There is no optimised replacement model. There is only a different roster. Which means this was a selection decision, not a theory decision — and that should be said as plainly as we defend his 17.68.

The market for a name: T10 and the IPL, and why they must stay separate

Now the part everyone finds fun and I find tiresome: Rome in twelve days, Napoli Knights, co-ownership, and an IPL auction entry at forty-two with no short-format cricket in a decade.

A transfer is a medical file with a price tag, and I read it in that order. File first, tag second.

What does the file say? Forty-three, recurring calf, no T20 match in ten years, no death-overs reverse-swing record. Whatever bowling happens in twelve days in Rome will be exhibition, not competition — and I am not diminishing it, I am classifying it. Red-ball 17.68 and any T10 number cannot share a scale. People who merge them make the same mistake in injury stories: change the format and the body's demands change, and fast bowling's demands barely overlap with T10's.

What does the tag say? Name. Legacy. Footfall. This is a marquee premium, not a scarcity-position premium. And the co-ownership arrangement is almost certainly sweat equity rather than cash — an emerging league buying credibility with shares instead of salary. Confidence: medium.

A football parallel fits directly. Goalkeeper distribution is now priced so heavily that declining shot-stopping hides behind it — clubs pay a premium for a skill that appears once or twice a match and forget the basic that appears in every one. The same is happening to Anderson's name in T10. He is being bought not for his bowling but for a name that sells tickets. That is not an accusation; it is precisely where his anti-diva reputation is a relief. He wants to play, and if the market wants to buy, no harm. We simply should not treat that bowling as proof of anything.

On the abuse of numbers

One point I have made for years applies directly. We complain about xG for the right reason: without context it cannot explain in-game decisions, form, or standards. 17.68 behaves the same way. It is a fine predictor and a poor verdict. It cannot tell you he should have been retained; it can tell you that what he did was extraordinary for his age. That is the limit, and the limit is the honesty.

Risk: where the pressure actually sits

| Category | Risk | Level | Likelihood | Impact | Mitigation | |---|---|---|---|---|---| | Physical | Recurring calf/soft-tissue injury | High | Medium-High | Medium | Load caps, exhibition format, spell limits | | Physical | Red-ball specialist into T10 | Medium | Medium | Low | Treat T10 as exhibition, not a test | | Personnel | No structured transition or mentor role | Medium | Low-Medium | Medium | Formalise ambassadorial/coaching pathway | | Commercial | Sustainability of the T10 venture | Medium | Medium | Low-Medium | Single marquee-name dependency | | Commercial | Marquee premium read as sporting value | Low | Medium | Low | Keep the two valuations separate | | Public | 'System vs individual' narrative if he keeps performing | Medium | Medium | Medium | Frame as a celebration of longevity | | Governance/integrity | No material signal | Low | Low | Low | Standard ACU oversight |

Overall: low-to-medium. There is no integrity crisis here and no geopolitical layer. The material risks are the body, the optics, and the commercial dependency of an emerging league on one name.

What changed seven days earlier

I stopped asking who got hurt and started asking what changed seven days earlier. In Anderson's case the better question is what changed seven months earlier. A room in May 2026, a conversation, a decision. After that, a county club looking at its seam pipeline and concluding that next season's 330 overs had to come from somebody else. Two different logics, one shared date. That is not coincidence.

Which is why I do not read this as the sad ending of a great bowler. I read it as an administrative event that happened to a body, and whose real fault is that nobody designed a new calendar for that body.

What to watch

I will watch three things, and I am writing them down in advance so that later I can catch myself pattern-fitting.

First, those twelve days in Rome. Not the number of balls, but their distribution — consecutive days versus gaps, and what the first over of the following day looks like. If his run-up shortens on day three, my 17.68 inference was right and so was my reading of the cut as a shield.

Second, any red-ball contract. A county will get an injury and a phone will ring; that is not in question. What matters is whether the contract arrives mid-season. If it does, the entire administrative rationale collapses and we must concede this was a calendar decision, not a capability decision.

Third, whether the ECB builds a formal pathway. This is the dullest and most necessary item on the list. A checklist is an act of care, and so is an exit checklist.

A bowler who averages 17.68 at forty-three is not retired. He is scheduled. The only question is whether anyone wants to build the schedule — or whether we are all more comfortable telling the story of a great ending. I sit between the doctor and the coach, and my job is to make both of them precise. In this story there is a third man, the administrator, and nobody has asked him to be precise at all.