Bowling to a Specific Batsman: Tailoring the Attack
How bowlers and captains design a bowling strategy specifically calibrated to an individual batsman's weaknesses, preferred scoring zones, and technical vulnerabilities. The information sources used (video analysis, ball-tracking data, historical dismissals, in-match observation), why the same pitch and conditions demand a different plan for different batsmen in the same innings, how a bowling plan for an opener differs from one for a lower-order batsman, and the judgement calls required when a pre-match plan stops working.
Information Sources for Batsman-Specific Plans
Modern bowling plans draw on multiple data streams. Pre-match analysis teams produce heat maps of where a batsman has been dismissed across their career — specific delivery types, lengths, and lines that have proven effective. Ball-tracking data (Hawk-Eye or equivalent) shows precisely where each delivery pitched in a batsman's career, distinguishing which lengths in which zones produce scoring shots, plays-and-misses, or dismissals. Video analysis highlights specific technical vulnerabilities: a batsman who dips their head toward off stump as they play certain shots, a left-hander who plays away from their body at balls angled across them, a middle-order player who struggles against balls pitched full and moving in. These are not intuitive judgements — they are measurable patterns extracted from hundreds of deliveries.
Why Plans Differ for Different Batsmen in the Same Innings
On the same pitch, with the same bowlers operating, the optimal plan changes entirely when a new batsman arrives. An opening batsman who has played 100 Tests on the pitch type faces a different plan from a specialist number seven who has played 15. A left-handed batsman changes the angle at which the outswing travels relative to the body, requiring fielding adjustments and potentially different bowling angles. A batsman in excellent recent form may receive a more defensive plan — a captain might bowl to dry up scoring and frustrate rather than hunt the wicket immediately — while a batsman in a run of poor form facing a type of bowling that has repeatedly dismissed them receives an aggressive plan targeting that established weakness immediately. The art of captaincy includes reading which batsman in the current partnership is more vulnerable and directing the bowling attack accordingly.
When the Pre-Match Plan Stops Working
A fundamental problem with data-driven bowling plans: batsmen evolve. A weakness identified from dismissals two years ago may have been entirely addressed in practice. When the pre-match plan fails (3 overs of the planned delivery type have produced no wicket and the batsman is scoring freely), the captain faces a decision: persist with the plan (perhaps the plan needs more time to 'set' the trap) or adapt to what the batsman is showing in the current innings. The most common failure mode is over-commitment to the plan: continuing to bowl short outside off stump because historical data showed the batsman had been caught at gully five times, while the batsman in front of them is pulling those deliveries for four repeatedly. In-match observation must override pre-match data when the contradiction is sufficiently clear.
Frequently asked questions
Do batting teams also develop plans against specific bowlers?
Yes — batting plans against specific bowlers are equally data-driven. Batsmen and coaches analyse which deliveries from a specific bowler they can score from (scoring zones against this bowler's bowling types), where they should leave (the bowler's dangerous deliveries that have dismissed them or similar batsmen), and which phases of a spell to attack (bowlers who tire toward the end of long spells may offer different options than at the start). The batting plan for facing a bowler like Jasprit Bumrah — whose bouncer, yorker, and inswing all need different responses — involves specific shot selection against each delivery type, practiced in the nets specifically to face that bowler's variety. The better-resourced international teams now replicate specific bowlers' styles in nets before touring.
Is it unethical to target a batsman's known weaknesses?
No — identifying and exploiting a batsman's technical or psychological weakness is a core part of the competitive game. The Laws of Cricket place no restriction on targeting weaknesses (as long as the actual delivery is legal). What is restricted is intimidatory or dangerous bowling — specifically, bowling deliberately at a batsman's head with intent to cause injury (rather than to dismiss them). The ethical boundary is safety, not competitive strategy. Targeting a batsman's technical weakness (the ball on their legs, the short ball they hook riskily, the outswinger they drive at too early) is considered legitimate competition. Targeting the same batsman's psychological vulnerability — by sledging, using personal information, or unsettling them off the field — is subject to the ICC's Code of Conduct.
How does the plan change when a new ball is taken?
The new ball fundamentally changes the bowling plan because it offers pace, carry, and swing that the old ball cannot provide. When a team takes the new ball (available after 80 overs in Tests), they typically return to a more aggressive plan: pace bowlers replace spinners, the field shifts more aggressively toward catching positions, and the plan targets different batsman weaknesses (the new ball exploits edges to slip rather than the flat-bat dismissals the old ball and spinners produce). The arrival of the new ball is also a psychological moment — batsmen who have settled into a rhythm against old-ball spin must reset against pace and swing. The bowling team specifically plans what to do with the new ball against whichever batsmen are at the crease in that moment.