Print

[TangoWhiskey]

I skippered a 2nd XI for a couple of seasons (2012 & 2013) and on reflection I don't think whether we batted or bowled first actually made much a difference to the result. However given that we had sometimes 8 players who all considered themselves bowlers, I regularly chose to bowl first as it gave me control in terms of making sure everyone got involved. I did win more matches batting first because I knew if we could put 100+ on the board, we had the bowling to knock over most sides in our division. I was also far more ruthless as a fielding captain with a total to defend.

My one rule of captaincy was never take off a youngster after he had a bowled a bad over (or gone for a lot of runs), I always made them bowl another over. It makes the kid both believe in you and more importantly believe in himself.     

Blimey. Eight players who consider themselves bowlers? Lucky boy! We're lucky to get 3 bowlers in our side. Mind we have a lot who consider themselves as all rounders but in all honestly the closest they get to that classification is with their waistband.

[uknsaunders]

Ultimately you have to play to your teams abilities and the conditions. If your pitch is a batting paradise then batting first, getting a total and using scoreboard pressure is the way to go. If you have a deck that nibbles around maybe a bit damp to start with and you have a decent bowling line up then it's a bowl first job.

I remember winning a 2nd XI league with a weak bowling line up and a strong batting line up. Our pitch was a road but the ball swung around early on. We simply had a line up of swing bowlers who could take wickets first up. We weren't quick enough to stop runs when it didn't swing but we hoped to do enough damage before the oppo got on top and restrict the score. Then once we had a below par target we'd leave it to the batsman to chase down. Plan worked very well for a number of years. I remember doing something similar a few years later with a stronger bowling unit, essentially heap loads of pressure on them first up and hope they crumble. In that instance we had a deck that moved around a bit and generally got better as the game went on. We were just as good setting targets and really you want to be flexible in your game plans according to conditions.

[Akewstick]

Depends what the side is for? I skipper the development team we usually loose. If possible I will always bowl first so I can give the lads a bowl without them feeling that one poor over will loose the match. If you bat first and get skittled for 70-80 you have no leeway in giving your bowlers experience. As for batting all our lads will probably get a bat anyway. And I don't want to be finished by 4.

This is the logic at the level I play at as well, bowl first, everyone gets a bowl, if we get rolled for 50 we've still got a decent game, as a batsman though against a superior side on a hot day, when I know I'm going to fry in the sun for 3 hours at deep midwicket for the chance to come in with the team on 9-4 in the third over... I still know it's right but selfishly, I really wish we'd bat first.

[Lumsden]

Blimey. Eight players who consider themselves bowlers? Lucky boy!

I think perhaps more accurately is that they could no way be described as batsmen !!!