Wicket Preservation Strategy: When to Attack and When to Protect
Wicket preservation is the strategic principle that batting teams must balance scoring rate with survival — a wicket lost is irreplaceable, and losing wickets in clusters (collapses) often leads to insufficient totals. The optimal approach varies by format: Test cricket heavily weights wicket preservation; T20 cricket accepts more risk per delivery. Understanding when to sacrifice scoring for survival — and when to attack aggressively — is central to elite batting strategy.
Wicket preservation as a batting concept: in Test cricket, each wicket is 10% of a team's batting resource. A top-order wicket (numbers 1-5) is particularly valuable because it represents not only runs from that batsman's innings but also the platform from which the partnership behind them can build. When the first 3 wickets fall cheaply, the remaining 7 wickets must score more to compensate — statistically, teams with their first 5 wickets averaging 60+ per partnership have a much higher probability of setting competitive Test totals than teams where early wickets fall for 0-10 runs per partnership.
Format Comparison
Wicket preservation by format: Test cricket — wicket preservation is the primary goal for the first 30-40 overs of a new innings; the batting team should accept slow scoring (3-4 per over) in exchange for keeping wickets in hand for later sessions; the strategy: survive the new ball (overs 1-25), establish (overs 25-60), accelerate (overs 60-90). ODI cricket — wicket preservation is balanced against run rate from ball one; the powerplay (overs 1-10) allows some risk because the scoring opportunity is high; wickets should be preserved in overs 15-35 (the 'middle wicket preservation phase') to enable a death-over acceleration; T20 cricket — wickets are the least-preserved resource; teams accept losing 4-5 wickets for a fast total because 6-7 quality batsmen can score 150+ even with early loss.
Batting Collapses
Batting collapses (3+ wickets for 10-15 runs) occur from specific triggers: (1) The new ball — the freshness of the new ball (increased swing and seam) at the start of an innings or when the second new ball is taken creates conditions where several wickets can fall in a cluster if the batting team does not adjust their approach for the increased movement; (2) Pitch deterioration — on spinning or wearing pitches (days 4-5 of Tests), the increasing turn and uneven bounce makes batting progressively more difficult; (3) Psychological transmission — when one wicket falls in unusual circumstances (a bad shot, a good ball), remaining batsmen become anxious and make more errors; research shows wickets cluster because subsequent batsmen face a combination of a still-good bowling attack AND heightened anxiety.
Partnership Building
Partnership building between two batsmen: strong batting partnerships survive through explicit communication (the two batsmen speak between overs about pitch conditions, bowler plans, and target scores), technical complementarity (a left-right batting combination disrupts the bowler's line by forcing them to change their angle after each delivery), and psychological support (a batsman going through a difficult patch benefits from their partner maintaining calm). The 2001 Kolkata Test partnership between V.V.S. Laxman (281) and Rahul Dravid (180*) — 376 runs — is the definitive example of partnership building under extreme pressure: India were following on and needed to bat for 2 full days to survive; the two batsmen rotated strike, communicated constantly, and built their partnership across a full day of play.
Frequently asked questions
What is a batting collapse in cricket?
A batting collapse in cricket is a rapid loss of multiple wickets for very few runs — typically 3 or more wickets falling within 15-20 runs. Famous examples: England collapsed from 121/5 to 123/10 (all out for 123) in the 2013 Ashes at Edgbaston; Australia collapsed from 369/2 to 408 all out (losing their last 8 wickets for 39 runs) at the 2019 Ashes. Collapses typically occur when: the pitch conditions deteriorate (new ball, wearing surface, swing conditions suddenly increase); one bowler finds their rhythm and puts together a spell that is practically unplayable; or psychological anxiety transmits between batsmen after an unexpected dismissal. Modern sports psychology emphasises teaching batsmen to 'reset' after a wicket falls to avoid the psychological transmission of a collapse.
What is a good batting partnership in cricket?
In Test cricket, a 50-run partnership (any combination of runs between two batsmen) is considered solid; a 100-run partnership is excellent; a 200+ run partnership is exceptional; and a 300+ partnership is record-territory. In ODI cricket, a 100-run partnership can be match-winning if scored in 80-90 balls (run rate 7+); a partnership of 60-80 runs at 7+ per over from the middle-order (overs 20-40) is considered good. The highest Test wicket partnership ever: 576 by Kumar Sangakkara and Mahela Jayawardene for Sri Lanka vs South Africa in Colombo in 2006 (for the 3rd wicket). The highest ODI partnership: 258 by Rohit Sharma and Ambati Rayudu for India vs West Indies in 2014.
What is a batting average in cricket?
Batting average in cricket is calculated as: Total runs scored / Number of times dismissed. A batsman who scores 1,000 runs and has been dismissed 20 times has an average of 50.0. Importantly, not-out innings do not count as dismissals — if a batsman is not out at the end of an innings, that innings' runs are added to the total but the dismissal count does not increase. This means batsmen who frequently bat at number 8-11 (lower order, often not out) can have inflated averages relative to their true batting quality. Test batting average benchmarks: 50+ is elite; 40-50 is very good; 30-40 is solid; below 25 is considered a batting weakness for a specialist batsman.