Skip to content
Foundation5 min

Bowling as a Unit: How Teams Take 20 Wickets to Win a Test

In Test cricket, a team must take 20 wickets to win — 10 in each of the opposition's two innings. This article explains how bowling attacks function as coordinated units rather than individual efforts, the role of each bowler type in a complete attack, how captains rotate bowlers and manage loads, and what separates winning bowling attacks from good individual bowlers.

Written by GeoCric EditorialUpdated Invalid Date
ShareShareWhatsAppFacebook

The 20-Wicket Challenge

In Test cricket, no lead or total guarantees victory unless the bowling team can dismiss all 11 opposition batsmen twice. This means taking 20 wickets across a 5-day match — an average of 4 wickets per session, or more realistically, concentrating wicket-taking in sessions when conditions are most favourable. Teams that are unable to take 20 wickets draw matches regardless of their batting performance: Australia's 2011 series against India saw Australia post competitive totals but failed to take enough wickets to win Tests. The inability to take 20 wickets in conditions that don't assist bowling is the primary challenge for all-format teams competing in subcontinental conditions (slow, turning pitches that are harder for pace bowling attacks).

The Roles Within a Bowling Attack

A complete Test bowling attack typically includes: a new-ball pacer (takes wickets with swing and seam when the ball is fresh), a supporting fast bowler (maintains pace and pressure while the primary bowler rests), a spinner (exploits pitch deterioration on days 3-5 and takes wickets in conditions where pace bowlers can't), an all-rounder who can bowl medium pace (adds overs when the primary bowlers are rested), and optionally a second spinner in subcontinental conditions. Each bowler's contribution is interdependent: the spinner's wickets on day 4 are made possible by the openers' batting contributions that gave the team a lead worth defending; the pace bowler's first-session wickets create pressure that the spinner exploits in the afternoon.

Managing the Bowling Group

The captain manages the bowling group across 5 days: monitoring workloads (a fast bowler bowling 30+ overs in conditions that don't assist them may carry a stress fracture risk); maintaining morale when wickets aren't falling (a bowler who has bowled 20 wicketless overs still needs encouragement and tactical support rather than public criticism); and sequencing bowlers to maximise the impact of conditions (using the pace bowlers in the morning when the pitch has overnight moisture, then the spinner after lunch when the pitch is dry and the ball older). The captain's bowling management is one of the most complex aspects of Test captaincy because it requires simultaneous management of physics (conditions), physiology (bowler workloads), and psychology (team morale).

Australia's 2021-22 Ashes attack: Australia's bowling attack in the home Ashes of 2021-22 — Pat Cummins, Mitchell Starc, Josh Hazlewood, and Nathan Lyon — demonstrated perfect bowling unit function. Cummins provided control and wickets from one end; Starc's left-arm angle and swing took wickets with the new ball; Hazlewood's accuracy and seam exploited any movement; Lyon's spin attacked in the dry conditions of days 3-5. No single bowler was exceptional; together they took 50 wickets in the series to win 4-0. The unit was greater than its parts — each bowler's role was clearly defined and each executed their specific function without overlap or confusion.

Frequently asked questions

What if a bowling attack runs out of bowlers who can take wickets?

When a bowling attack cannot take wickets — often called being 'toothless' — the result in Tests is a draw or defeat. Teams without a wicket-taking option (every bowler is being played comfortably) can resort to: bowling wide of off stump to frustrate the batsmen into errors; bowling extremely short or full to create mis-execution; setting highly attacking fields to pressure batsmen into risky shots; or using a part-time bowler who the batsman doesn't know as well (surprise value). None of these reliably produce wickets against competent batsmen on a flat pitch. The most extreme example: England's 2015 series against New Zealand saw Steve Harmison-era-like tests of whether varying the bowling ever produces wickets when conditions don't assist — they rarely do consistently.

How does an injury to the primary pace bowler affect the unit?

A primary pace bowler injury mid-match creates a significant bowling unit disruption: overs must be reallocated to other bowlers who may not have the pace, accuracy, or swing capacity of the injured bowler. The spinner and all-rounder typically absorb the extra overs. Captains also adjust field settings — a replacement bowler who lacks the primary bowler's pace may need more fielders inside the ring to compensate for batsmen playing more confidently. At international level, squad selection now explicitly considers bowling unit resilience: a squad of 15 that includes 5 genuine bowling options (in case 1-2 are injured during a match) is more robust than a 4-bowler unit where one injury breaks the team's ability to take 20 wickets.

Is it possible to win a Test with just two quality bowlers?

Yes, historically — particularly if two bowlers are exceptional and conditions assist them. England's mid-2000s reliance on Andrew Flintoff and Steve Harmison at pace, with Ashley Giles providing spin, won an Ashes with only two primary wicket-takers. India's spin-dominated attacks of the 1970s-80s (Bedi, Prasanna, Chandrasekhar, Venkataraghavan) used four spinners with minimal pace, winning Tests by overwhelming spin on subcontinental pitches. The minimum viable bowling unit differs by conditions: in England (swing and seam), two pace bowlers plus one spinner can take 20 wickets; in India (dry, turning), two quality spinners plus one pace can take 20 wickets. The absolute minimum across all conditions — two genuinely good bowlers with the right conditions — is achievable but fragile.