Frustrating Aussie selectors make me wanna take up Mitch Marsh-ial arts

By Samlaurence26 / Roar Rookie

As is regularly the case for those who grow up watching Test cricket, I am often involved in unsuccessful attempts to persuade my non-cricket watching friends that the five-day game is captivating and spell-binding like no other.

One such conversation took place with a Belgian friend during the 2017-18 Ashes. In keeping with my cricketing spiel, I had taken it upon myself to explain what it means to ‘get out’ and the different ways of doing so.

Luckily for me, Mitchell Marsh had just come out to the crease and, with my friend looking increasingly puzzled, I remarked that in a few moments he would see for himself what it means for a batsman to get out.

Marsh was a rubbish batsman after all, and bound to follow his brother back to the sheds quick smart. To this day, however, my friend has never seen someone dismissed, as Marsh cursed my cynicism and promptly banged 181 runs off 236 balls.

With the creaking backs and spinal make-ups of our lanky pace attack under threat from the rigours of Test match cricket, selectors have opted to select Marsh over Travis Head for the fifth and final Ashes Test at the Oval.

Mitch Marsh (Photo by Ryan Pierse/Getty Images)

I was previously unmindful of why Marsh’s ever-impending ascension into the Test team riled me, and many other fans, up to such a degree. After his latest selection, that confusion no longer remains.

This is my thought process, so please bear with me.

Previously, it was rather unerring that a man who was so often out of form and seemingly on the periphery of Australia’s best 11 Test players could be so dramatically and abruptly catapulted back into the side.

This was especially true during the 2017-18 Ashes series. Surely, it was this abruptness coupled with the unnecessary drama associated to his selection that annoyed me so much. However, this most recent selection was neither abrupt, dramatic or unexpected.

The moment he was selected in the wider Ashes squad we all knew this was coming. So please, let us not, as fans, embarrass ourselves by expressing a false sense of shock and surprise at his selection. It was predictable.

When Peter Handscomb was dropped for Marsh in the last Ashes series, I believed it to be a harsh decision.

Handscomb had averaged 99.75, with two centuries, in four matches during the 2016-17 Summer of Cricket.

I reasoned at the time that despite Handscomb’s technical frailties, his record made him deserving of at least one more Test to come good. This time, however, Travis Head does not have the same weight of runs behind him.

Given there are valid cases against all of the top six batsmen to be dropped, bar Steven Smith and Marnus Labuchagne, it is far more valid to label Head as particularly unlucky. But not undeserving.

Last time around, Marsh exposed my cynical reaction to his selection and so I will at least give him one Test to perform before allowing myself to fall back into my old cynical ways.

After all, Head has set the bar low with recent scores of 0, 25, 19 and 12. He can’t grumble too much about getting the axe.

If not unpredictability of selection or a batsman who selectors should never have dropped, then what else causes a tangle of angst and dismay to cultivate inside the greenhouse that is my brain when I see Marsh’s name up in lights?

Mitchell Marsh of Australia (Photo by Scott Barbour/Getty Images)

Let us return to basic selection decision-making. At its core, selection rests on the two following questions.

One, does a player improve the team’s ability to take 20 wickets throughout the course of a Test match?

Two, does a player improve the team’s ability to score runs? Marsh, as an all-rounder, should force selectors to answer both questions with an affirmative answer. He does neither.

The proof is in the literal reasons provided for his selection, shared by the Australian captain no less.

1. Fitness. “Mitch has worked his backside off actually for the last six or seven months’… “Mitch at the moment is as fit as we’ve seen him”… “We’re looking forward to seeing him put all his hard work into action this week”

2. Easing the workload on the bowling group. “They’ve [Aussie bowlers] bowled a lot of overs and we feel that bringing Mitchell in will ease a bit of the workload on them’…’we just wanted a bit more bowling depth in the squad.”

3. On dropping Head. “We want to get the make-up right to win this Test match and unfortunately we had to make a really tough call on someone, and it happened to be Travis.”

I have to say, this is a load of nonsense. Firstly, fitness doesn’t win you Test matches, skill does.

Secondly, if selectors were so primarily concerned about the bowler’s workload, they could have easily dropped Pat Cummins and Josh Hazlewood for Peter Siddle and James Pattinson.

Thirdly, Australia has managed to win two matches without an all-rounder in the team so clearly our current make-up works just fine!

If the selectors think Marsh makes either our batting or bowling better, then they should say so. The fact of the matter is that they can’t justify such a claim and they know it.

Travis Head of Australia (Photo by Ryan Pierse/Getty Images)

This leads instead to selectors offering other vague, clunky and laughably unconvincing reasons for his inclusion. And as long as such an insulting and substandard selection attitude remains, Marsh’s place in the Test team will continue to cause dismay and frustration among fans.

That being said, he could single-handedly get rid of this reoccurring emotional circus, if he actually proved himself and performed. So Mitchell, please will you just go out there, make some runs, take some wickets, and force us all to stop whinging.

The Crowd Says:

2019-09-28T11:27:13+00:00

Jero

Roar Rookie


I’m not sure the selectors feel that they require someone of the ilk of Ben Stokes to fulfill the role. There are plenty of average all rounders getting picked in cricket teams everywhere, but selectors worldwide see benefit in them. We win almost all our home Test series, we have Smith and by and large our number 6 batsman doesn’t play a critical role in home Test series, in terms of providing critical runs which spell the difference between winning and losing. It was always going to count for more in these Ashes though, because our batting has always been wobbly over there agains the moving ball. It made absolute sense to pick six specialist batsmen over there, and do away with the all rounder who couldn’t bat at number six level. Note that once the Ashes were secured at Old Trafford, they immediately reverted to an all rounder at 6. Our quicks do play a critical role though, and I think you’ll find that the selectors are going to listen to them when they say that having a fourth seamer actually helps them. This whole “deserves” to be picked hang up everyone has isn’t actually logical. Someone might be lucky to be getting picked, but it doesn’t collide with the logic which you understand perfectly. Most people on The Roar feel there’s someone who deserves to be picked, but it doesn’t mean that there’s a spot for them in the side. Just because Marsh isn’t Stokes, it doesn’t invalidate the logic. We’ve had an all rounder as a constant presence in the team since the third Test at the WACA in the 2006/7 Ashes series, barring the first four Tests in this recent Ashes series. And there’s invariably always been a better batsman scoring runs in the Shield who probably “deserved” to be in the Test team on ability, whether it was Watson or Mitch in the team. Maybe they will go with just three specialist bowlers on occasion, if the conditions warrant it. But 90 overs in a day is asking a lot from four bowlers on flat wickets, no matter how good they are, or who can replace them in the next Test. This whole “deserves to be picked” thing seems to be largely a “reason” for people to get on their high horse about Mitch Marsh, over and over.

AUTHOR

2019-09-28T10:50:28+00:00

Samlaurence26

Roar Rookie


I understand the logic perfectly. They want player who can provide proper support to the bowlers and prevent them from getting injured. Believe me, I wish Marsh was as good as Ben Stokes is. But I know what I want from my number 6, and first and foremost I care about runs, not how well he can support our bowlers. Australia has Cummins, Hazlewood, Starc, Pattinson and don't forget about Richardson. If the selectors are worried about injuries, rotate the bowlers. That worked well enough in the first four Tests of the Ashes. I really don't buy this argument that Marsh is deserving of selection because of his support and the boost it gives to the rest of the bowlers. That's not a good enough reason.

2019-09-27T22:27:51+00:00

Jero

Roar Rookie


It's not complicated. They want a fourth seamer on flat wickets where there's little sideways movement, so that Cummins, Hazlewood and Starc don't bowl themselves into the ground. We have condensed Test series, with 5 or 6 matches completed between mid November and the start of January. We all know that Mitch Marsh hasn't established himself as a Test no 6 batsman, but it doesn't mean that the selectors don't want a fourth seamer who can also bat when there's a flat pitch and a lot of bowling to do. Bear in mind that the selectors picked Marsh for a very flat MCG last year then dropped him for the SCG Test, which historically has some turn. His replacement, Labuschagne, bowled plenty of overs there. It's all about having four specialist Test bowlers and a fifth bowler to help carry the load. We can all get upset about Marsh getting picked if we choose to, but unless there are conditions like Tests 1 to 4 of these Ashes when there's plenty on offer to help the three specialist quicks, or unless you have Warne and McGrath in your team and Gilchrist at 7 the selectors will always be looking for someone like him. It's also helpful when you have a batsman of Haddin's quality at seven and someone like Watson in the team who's a better batsman, but it's all about the current crop of players. They'll have their eyes set on Will Sutherland, hoping that he develops into a Test standard player in the near future to fulfill the role. Hopefully he has superior batting skills to Marsh, but it's early days.

AUTHOR

2019-09-27T15:32:46+00:00

Samlaurence26

Roar Rookie


He scored two centuries last Ashes but couldn't perform past those five tests. I doubt he lasts for long this time around either

AUTHOR

2019-09-27T15:32:07+00:00

Samlaurence26

Roar Rookie


I agree with the sentiment Akitas

AUTHOR

2019-09-27T15:31:48+00:00

Samlaurence26

Roar Rookie


So he got some wickets but made no runs. So what happens next? Do they use his wickets as a reason to pick him in Aus, despite the fact that the ball will do so much less on Aussie pitches. I still feel like they've worked themselves into a position where they can justify picking him again, even though I don't think his next few performances will be up to scratch. If Aus aren't going to play Head, it's far more logical to pick Kurtis Patterson to play at 6 than Marsh. Ironically I think winning the last test has made the English even more annoyed that they couldn't get the Ashes back. That has been satisfying to say the least.

AUTHOR

2019-09-27T15:28:21+00:00

Samlaurence26

Roar Rookie


Well he definitely bowled much better than I thought he would. But he didn't get any runs, and that's what we needed to win. So suffice to say it was a bad selection.

2019-09-13T00:03:24+00:00

TheGeneral

Roar Rookie


Akitas, Wicketless?. Four is pretty good. And for our sake lets wait and see re runs scored. A bit of humble pie would be good.

2019-09-12T04:43:00+00:00

TheGeneral

Roar Rookie


Akitas, I expect us to win the test. I do not think Marsh should have picked, but if the workload is big for our main bowlers, he will come in handy. As I stated in another post to you, the selectors have done a great job so far, so stop calling it crap. You can crow all you like after the test and if it goes wrong.

2019-09-12T04:31:30+00:00

Akitas

Roar Rookie


I would expect runs conceded to be far in excess of runs scored, and probably wicketless too. A ridiculous selection, and this crap really has to stop.

2019-09-12T04:30:03+00:00

Jero

Roar Rookie


Yep, there's every chance. The selectors will be perfectly happy with that. If it means that Cummins is fit and firing having a similar impact to how he usually performs, bowling fewer overs.

2019-09-12T04:16:23+00:00

Jero

Roar Rookie


Unless unfit, they were never going to drop Cummins. Siddle and Pattinson need not apply. But they want to manage Cummins' workload on a flat wicket, hence the Marsh Compromise. When you work backwards from there, it all falls into place. It's not about Head, even less so about Marsh. It's all about Cummins. As much as it pains many, there's a rationale for it. If Marsh bowls enough overs and scores around about what Head has over the last few Tests the selectors will be happy enough. Even more so if he gets some wickets and runs. Just lie back and think of England, Samuel. You're used to it, after all.

2019-09-12T00:50:33+00:00

maccaa62

Roar Rookie


I bet he doesn’t get more runs than Head and I get he doesn’t bowl more than 10 overs. He will get 1 lower order wicket

Read more at The Roar