Cricket in the Data Age: A Third Player Between Bat and Ball

The last over of a T20 match. The bowler walks back to his mark, and before he turns, a signal arrives from the dugout. The captain stands with a small card in his hand, printed with a pattern of the batter's shot selection from recent matches, while an analyst in the stands is calculating the average line and length of the last three deliveries. This is the most ordinary sight in modern cricket — and it announces that a third player has walked onto the field: data. The idea of measurement is not new to cricket. The traditional scorebook was itself a database: who faced how many balls, how many runs came in which over, which bowler dismissed which batter. Until the end of the twentieth century, that was the information teams had, and it was used mostly for review rather than planning. The change came when technology turned that scorebook into live data in real time. The first major turning point was the arrival of the review system. When referrals entered the game, cricket acknowledged for the first time that human sight and machine sight could differ, and that the difference would be recorded publicly. Ball tracking, edge detection and heat-sensing cameras followed. Their impact was not limited to decisions. They put a new question in front of players: if the path of every ball, the angle of every shot and the moment of every catch is being recorded, should the method of practice change too? The answer has become clearer over time. A fast bowler today does not only check where his yorker landed; he checks the height at which it arrived, how far it passed from the bat, and how much the speed changed on that delivery. For a spinner this information matters even more — revolutions, drift and the behaviour of the ball after pitching are no longer matters of guesswork but of measurement. Bowlers like Rashid Khan are commonly described as masters of subtle changes of pace; what was once called pure art can now be measured as well. Batting tells the same story. Coaches once said a batter must 'wait for the ball'. Analysts now show how a batter's strike rate changes against a particular bowler in a particular phase, on which line he becomes more aggressive, and in which over his scoring rate drops. For a captain this is a new kind of power — he can now decide not just who bowls, but when. The sharpest impact has been in T20 cricket, where every ball carries a different value and the margin for error is small. 'Match-up' has become a common word, meaning the study of which bowler is naturally better against which batter. This analysis rests not only on numbers but on shot direction, footwork and release point. As a result, field settings have changed. A fielder was once placed where the batter hit the ball; now he is placed where data says the batter may hit the next one. But one side of this story is often ignored — the player's body. The modern calendar is far denser than before, and teams now have tools to measure how far a player ran, how his heart rate changed, how he slept and how much load his muscles carried. Workload management is no longer simply 'giving rest'; it is a calculation. The fitness culture associated with players like Virat Kohli is partly connected to this measurement mindset — treating the body as a system that can be regularly tested. This matters even more for fast bowlers, whose trade is the most injury-prone. Jasprit Bumrah is widely described as a bowler whose strength lies in an unusual action and extraordinary accuracy; maintaining such an action brings biomechanics into the picture. Technology now intervenes before injury, not only after it, and that is a significant change in how cricket is managed. On the other side, data has reshaped the coaching staff. Teams once had a coach, an assistant and a physio. Now the list includes throwdown specialists, batting and bowling analysts, fielding coaches and data scientists. This is a shift not only in numbers but in authority — in many teams a large part of the pre-match plan comes from analysts' reports, and coaches translate it through the player's mindset. A delicate balance follows: how rigid should the plan be, and how much freedom should the player get? This is where the limits of data appear. Cricket is a game in which wind direction, pitch behaviour, crowd pressure and a player's confidence are decisive, and none of these can be measured directly. Data can show that a short ball has worked against a certain batter; it cannot show whether that batter is full of confidence that day. The captain's real job is to decide between these two kinds of information. Captains like Rohit Sharma and Kane Williamson are often praised precisely for balancing plan and instinct — neither slaves to data nor dismissive of it. Blind adoption of data creates another risk: the homogenisation of the game. If every team builds similar plans from similar numbers, variety declines. T20 batting offers an example, where many batters now repeat the same shots — the ramp, the reverse scoop, the lofted hit — because data says these produce runs. But when everyone plays the same way, bowlers prepare for exactly that, and new tricks must be found to break it. Data accelerates innovation and shortens its lifespan at the same time. Another recurring debate concerns the spirit of the game. When technology overturns decisions, spectators ask whether cricket has become too much mathematics. It can be seen differently: technology has reduced injustice. In an era when every decision is captured by thousands of cameras, playing without technological assistance was itself unfair to players. The question is not whether technology should exist, but what its limits are and how transparently it is used. A further extension concerns player data and privacy. When a player's biometric data, injury history and mental state are held by a team, whose information is it? Does the player own his own data? These questions are new for cricket boards worldwide, and they need answers quickly, because technology has already moved ahead of them. Now the least discussed side — the spectator. Data has changed the viewing experience. Pitch maps, wagon wheels, speed graphics and win-probability percentages are now routine. The viewer understands the game more deeply, but a new problem arises: when a probability figure flashes after every ball, does the game lose some of the appeal of uncertainty? Cricket's beauty lies in the fact that no number can guarantee the final result — and that is its greatest strength. The road ahead is visible. Machine learning and computer vision are no longer limited to adding up numbers; they can read a bowler's action from footage and flag signs of fatigue. Real-time decision-support systems may one day suggest to a captain who should bowl the next over. But when the suggestion comes from a screen, a further question arises: whose decision is it? If the captain follows the suggestion and the result goes wrong, who is responsible? Cricket has not fully answered that. The true value of any technology is measured not by how powerful it is, but by how it is used. The best use of data in cricket is not where it replaces the player, but where it sharpens preparation and then leaves room for the player's judgement on the field. A good bowler arrives with a plan, but when he takes the ball and sees the batter move, he can change it — that moment lies beyond technology. Finally, data and human intuition are not opposites. Data informs intuition, and intuition gives data human context. When the two move together, the game improves — better planning, fewer injuries, longer careers and a game that spectators can understand more deeply. When either is treated as everything, some part of the game pays the price. The next decade of cricket will be spent searching for that balance.