Ollie Robinson's Decline from Test Cricket Star to Outcast

Ollie Robinson once seemed destined to follow in Stuart Broad's footsteps. However, he now finds himself out of favour with the England management, likely for good.

Robinson, who had at times surpassed Broad in the pecking order and even took the new ball from him, was excluded from the first home Test squad in the post-Anderson-Broad era. Interestingly, he wasn't even the most considered Ollie Robinson for selection, with Durham's wicketkeeper competing against Jamie Smith for Ben Foakes's spot.

The squad was selected with a focus on the future, particularly with an eye on Australia next year. Robinson's reliability and durability were questioned, casting doubt on his suitability for such a crucial assignment.

This decision seems more permanent than previous reprimands Robinson received. Last year, amidst multiple long-term central contracts, Robinson was given only a 12-month deal, intended to motivate him to improve. Unfortunately, the message was not received.

Robinson's final act for England may have been the Ranchi Test in March. His performance was lacklustre, with his pace dropping below 70mph, bowling six no-balls, suffering a back strain, and missing a critical catch as India staged a comeback. He bowled just 13 overs in the game. In the second innings, when England needed to defend 192, Ben Stokes did not trust him to bowl. Following the defeat, Brendon McCullum reminded the team that prioritising the team's needs would ensure individual support—a pointed message believed to be directed at Robinson, who, despite arriving in India in peak fitness, again failed to deliver.

Robinson's talent was undeniable: 76 Test wickets from 20 matches at an average of 22.92, coupled with the ability to bowl effectively on any surface and a competitive edge, should have secured a successful Test career.

Despite missing the first four Tests of the Bazball era, Robinson managed to regain some trust. He had faced criticism for his fitness during the previous Ashes tour, prompting a wake-up call from Stokes. "I had an honest conversation with Stokesy. He said you haven't played enough, you haven't backed up enough, and I realised I needed to change," Robinson admitted last year. Motivated, he joined the Stokes-led tour to Pakistan and performed admirably on flat wickets. Yet, fitness issues resurfaced during the Ashes, and Robinson left the third Test at Headingley with another back spasm, again raising concerns about his dependability.

Robinson was given another opportunity when selected for India after convincing England he had improved his fitness. Despite starting strong, his performance declined as the game progressed.

Throughout the tour, Robinson was accompanied by his new partner, a social media influencer, and launched a podcast with her while in India. This led to perceptions that he was distracted from his primary focus of getting fit and ready for Test matches in challenging conditions.

In contrast, Stokes set an example by pushing his body to recover quickly from knee surgery and return as a bowling all-rounder, demonstrating commitment and leadership.

The decision to drop Robinson was made weeks ago, unrelated to his recent poor performance for Sussex against Leicestershire. Dillon Pennington, Matthew Potts, and Gus Atkinson were preferred for the first Test against the West Indies, and Essex’s Sam Cook is also ahead in the selection order when fit. This move sends a clear message to other players: while Stokes and McCullum are supportive and focused on team culture, their patience has limits.

For years, Test squad announcements have been relatively uneventful, but the recent decisions to drop Robinson, Ben Foakes, Jack Leach, and Jonny Bairstow, along with Anderson’s retirement, signal a significant shake-up as England prepares for the next Ashes challenge. Robinson should have been part of the mix, but he squandered that chance in Ranchi.