For over a century, batting average has served as cricket's supreme measuring stick. In Test cricket, where wickets are the finite currency and balls are theoretically infinite, dividing total runs by completed dismissals remains an elegant and meaningful metric. But applying batting average to Twenty20 cricket is not merely outdated — it is mathematically deceptive and actively incentivizes losing tactical behavior.
The Finite Currency Paradox: Balls vs Wickets
In a 20-over innings, a batting side possesses 120 legal deliveries and 10 wickets. In the vast majority of competitive modern T20 matches, a team uses only 5 to 7 wickets before the 120 balls expire. Therefore, the primary limiting constraint is not wickets — it is legal deliveries. A batter who consumes 45 balls to score 50 runs has consumed 37.5% of their team's entire delivery budget. If the remainder of the team scores at a healthy 150 strike rate, the team total reaches only 162 — well below modern par on true batting surfaces.
Yet, traditional scorecards celebrate the 50 as a personal milestone and inflate the player's seasonal batting average. If the batter remains not out, their average spikes artificially, rewarding them for failing to sacrifice their wicket in pursuit of maximal acceleration in the final overs.
The Contextual Batting Index (CBI) Alternative
CricRover's Contextual Batting Index (CBI) was constructed specifically to replace this archaic measurement. Rather than evaluating raw volume, CBI assigns a benchmark expected scoring rate for every ball faced, calibrated by three continuous parameters:
- Innings Phase Baseline: Powerplay baseline expected strike rate is calibrated at 135. Middle overs (7–15) baseline is 122. Death overs (16–20) baseline is 175.
- Required Run Rate Multiplier: In run chases, scoring runs below the required rate degrades the player's CBI score regardless of personal aggregate.
- Wicket Equity Context: Consuming dot balls when only two wickets are down is penalized far more severely than batting prudently when five wickets have fallen inside the Powerplay.
The Tale of Two Innings: Raw Stats vs CBI
52 runs (44 balls) • Not Out
• Traditional Average: Infinite
• Raw Strike Rate: 118.18
• Balls Consumed: 36.6% of innings
CricRover CBI: 68 (Underperforming Par by 32%)
32 runs (14 balls) • Caught at Deep Midwicket
• Traditional Average: 32.00
• Raw Strike Rate: 228.57
• Balls Consumed: 11.6% of innings
CricRover CBI: 154 (Outperforming Par by 54%)
Boundary Percentage as the True Leading Indicator
Statistical regression analysis across 2,400 domestic and international T20 matches confirms that team Boundary Percentage (the percentage of total runs scored exclusively via fours and sixes) has an $R^2$ correlation of 0.74 with match victory, compared to only 0.22 for batting average. Teams that win the boundary count win 82.6% of T20 fixtures.
When selectors evaluate recruits through the lens of CBI and boundary generation rates rather than batting averages, squad composition shifts dramatically. Teams stop recruiting accumulators who shield their wickets and begin populating their lineups with fearless boundary-strikers who treat every delivery as an opportunity to pressure the opposition's defensive field placements.
