Custom Bats Cricket Forum
General Cricket => Your Cricket => Topic started by: KasperRubin on August 12, 2014, 12:34:37 PM
-
Hey Guys
I'm in a bit of a situation here
I'm captain for my club in Denmark.
We have had a good season with our bowling, but our batting really struggles.
We have taken teams for under 130 runs a couple of times (50 overs matches), but struggled to chase. One time we got bowled for 36 runs after bowling them for 124 runs, and it's on atificial pitches, so it havent changed trough the innings. People get them selv bowled out, or get caught on defensive shots.
Should we try and bat first, or stick with the chasing, and try putting preasure on the other team by bowling them out for less than 150 runs?
-
I'm facing almost exactly the same dilemma here.
I've tended to stick to bowling first and hoping the opposition crack under the pressure. Annoyingly we did once score 260 in our 40 overs only to then have it chased down as we fielded like dicks, but otherwise we've been struggling to make more than around 150-180 which just isn't nearly enough in most games.
Recently I've had a go at setting a target which has met with fairly mixed success.
-
Bat first as the pitch won't change. Grind out a total and use scoreboard pressure.
-
Bat first as the pitch won't change. Grind out a total and use scoreboard pressure.
I agree with this. We've had the same problem all year. Batting has not fired but bowling has done really well. Scoreboard pressure can be massive with good bowlers plus you remove the pressure from the batters (who haven't being doing well). We've ended up getting up to the 190-200 mark a few times with batters having ago in their own time rather than chasing a target and those kind of totals are plenty for a good bowling attack. Unless the pitch is going to get significantly better I'd always bat first.
-
Bat first, takes away lot of pressure to perform when batting side is struggling. Plus, you don't want to field full overs and then go out to bat...
-
Depends also whether you have draws in your league. If it's just win or lose, then bat 2nd...
-
bat first , keep your strong ability which is bowling to the second innings.
-
Agree bat first then put pressure on opposition also keep changing the field placings to stop each of the opposition batsman scoring if there's no draw.
-
Am I the only one who enjoys bowling first, simply because I dont have to then dive around behind the stumps with stomach full of tea? :D :D
-
Am I the only one who enjoys bowling first, simply because I dont have to then dive around behind the stumps with stomach full of tea? :D :D
2nd that. Bowl first have a nice bing tea. :)
-
We tend to bowl first, we have a strong bowling attack and we tend to skittle teams fairly cheaply. Our batting is sometimes hit and miss though and we have failed to chase down 72 & 82!!!
-
I keep wicket and open the batting so have to have a light tea either way!
-
As captain I try and Win the toss and have a bat is my main thought! I like the pressure of bowling second and you have 11 men on the field trying to win the game as a unit. Runs on the board too.
-
Depends, how hot is the weather? Don't want a mutiny for fielding first!
-
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.
-
Bowl first and control the game. If it's draw cricket bowl second. Why bowl in win/lose?? Because getting people out isn't the idea, purely restrict runs. Teams batting first don't know the wicket, tend to start slower etc.. So then throw your men out on the fence to stop 4/6's (make 6'ss more risky) and suddenly teams struggle to 200 as many hitters rely on attacking fields to score.m
Then you are only chasing a low total.. Boom. Pressure is then all on the oppo after a poor batting display, hitters are grumpy in the field as they couldn't just smack boundaries and had to score 1's (which those people hate if they are honest)
-
Bizarre
-
Bat first. I'm a batsman these days and there is nothing worse than standing around in the field all day and not getting a bat because we rolled the other team for 50 odd. Bat first and everyone is guaranteed a game.
-
Sunday Cricket in Brisbane ("Warehouse Cricket" - funny name but is outdoors), games start at 10am and is scorchio until about 2pm. All else being equal we tend to bat first given the choice. It's just so darn hot. Winter cricket is more strategic… mostly.
-
Bat first. I'm a batsman these days and there is nothing worse than standing around in the field all day and not getting a bat because we rolled the other team for 50 odd. Bat first and everyone is guaranteed a game.
Or bowl first, if the oops are 50-8 feed runs to make a game of it.. Even more get a game then!
-
Bizarre
Come on then, what's 'bizarre'?
-
Or bowl first, if the oops are 50-8 feed runs to make a game of it.. Even more get a game then!
If the oppo are 50-8 it's already too late...
-
If the oppo are 50-8 it's already too late...
Not really, feed runs, leave gaps in their scoring zones..they can both get 50's and suddenly you have nearly 200 to chase (more if you want to make it harder for your batsmen). They love getting the runs, your guys get more batting. Win win oven it's a friendly
-
Makes it ridiculous if you try to do that to any extent. No point in scoring pity runs for the opposition.
And most tailenders couldn't score runs to people bowling with their wrong arm.
-
Makes it ridiculous if you try to do that to any extent. No point in scoring pity runs for the opposition.
And most tailenders couldn't score runs to people bowling with their wrong arm.
This. If you're playing a friendly usually the blokes batting 9,10 and 11 can be spotted being taught which end of the bat to hold when they are next in.
-
Makes it ridiculous if you try to do that to any extent. No point in scoring pity runs for the opposition.
And most tailenders couldn't score runs to people bowling with their wrong arm.
This happened in a Sunday game a few years back!
The oppo were 6 down for not many so they bought the number 3 on to bowl his "very part time" off spin. He took 3-8 off his one over!
The captain (a right arm seamer) then bought himself on to bowl left arm spin, 3 overs, 3 maidens.
In the end he resorted to not very subtlety giving a few loads of 5 wides away :-[
-
"If you win the toss - bat. If you are in doubt, think about it - then bat. If you have very big doubts, consult a colleague - then bat."
I think you should play to your strengths, you say you don't chase well but can restrict teams. Sounds like you should bat first if given the option. Do you have a new ball per innings? Are your bowlers line and length or rely on pace?
On the other point friendly or not you should aim to bowl teams out, Pointless practising keeping teams in the game. If the game finishes early play a short T20 or something. Youll get more out of that as opposed to engineering a result.
-
I guess it also comes down to what league format you play aswell. In our league you are encouraged to bat first as max points you can get is 30 but only 25 if you bowl first.
-
It really depends on your teams strengths really. I've got two examples from last year:
1. We bowled first in a 40 over game. Knocked em over for 170 odd. We lost early wickets chasing and were about 40 odd for 3 and I came out to bat with my opener and the pitch wasn't the greatest but we managed to time our run chase well and chased it down with a few overs to spare. I suppose if we had batted first we might've thrown our bats around a bit more and gotten bowled out early like the opposition? But batting second meant we always had mini targets all the way along.
2. Another 40 over game, it was a small ground like very small and an artificial pitch. Their captain batted first. We had em down to 14-4 off 8 overs then they had a big guy come out and our captain let the game drift coz he thought most scores will be chaseable on that small ground. They ended up with 300. Our batsmen just collapsed under the pressure of the big score, going for too many extravagant shots and we were bowled out for 180 odd.
Moral of the story I guess is depends on the experience of your team. Only time id really want to bat second if it has rained before the game and I know suns gonna be out so hopefully dry out and harden up the pitch.
Any thoughts?
-
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.
-
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.
-
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.
-
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.
-
Blimey. Eight players who consider themselves bowlers? Lucky boy!
I think perhaps more accurately is that they could no way be described as batsmen !!!