Test, ODI, T20 — One Ground, Three Different Geometries

Over the past few seasons, India's grounds have shown a strange duality. In the same city, a few months apart, teams struggle to reach 250 in a Test match; yet in an ODI World Cup, inside those same boundaries, totals climb past 350. Same 22 yards, same boundary distance, same light — yet the relationship between bat and ball feels like two different sports. Sitting by the boundary, it kept striking me that what the scoreboard never says is the real thing: the format itself is a tactical system, and when the system changes, the meaning of every number inside it changes too.

Test, ODI and T20 — all cricket, but their tactical logic is entirely different. In Tests, time is not the enemy but an ally; patience with wickets and the arithmetic of building an innings decide the result. In ODIs, time is limited but sufficient — so risk has a fixed schedule. In T20, time is the only asset, so every ball is a separate decision.

The difference isn't confined to the number of overs. The very design of field settings changes. Tests have no fielding restrictions; a captain can keep all nine fielders deep if he wishes. In ODIs, only two fielders may stand outside the circle in the first ten overs; in T20 that powerplay lasts six overs. These rules aren't just on paper — they control a batter's shot selection, a bowler's line, even the mindset after a dropped catch. DRS and the review system also run on a different rhythm by format, and that too shapes decisions.

One habit from my football analysis transfers directly here. In football I divide the pitch into eighteen zones and count entries into the half-space and Zone 14. In cricket I map powerplay ball-placement, the gaps inside the circle, and the deep fielding ring in exactly the same way. Because in both sports the real question is identical — who occupies which space, and why.

This is where the biggest trap hides. The same number carries three different meanings across the three formats, and comparing statistics without matching formats is the most common error in cricket analysis.

Take a strike rate of 130. In T20 that figure is now almost low — the modern par strike rate has moved past 140, and for a top-order batter 130 means you are slowing the team down. In ODIs, 130 is excellent, especially through the middle overs. Yet in Tests, a strike rate of 130 means the batter is attacking, the ball is old, the field is spread — a deliberate, risky decision. The same 130, three stories in three worlds.

Consider bowling economy of 8 the same way. In T20, an economy of 8 is roughly acceptable; at the death, ten to twelve is normal. In ODIs, an economy of 8 means you are losing the match, because over fifty overs it points toward 400. In Tests, an economy of 8 is almost self-destruction — there the target is to keep it under two. Bowling average follows the same logic: in Tests a 40 average is good, in ODIs 40 is good, but in T20 a 40 average means you are nearly inert.

The rule that emerges is simple but dangerous: the format is a system, and outside the system a number has no independent existence. An analyst who measures a Test batter's value with a T20 strike rate is mixing the arithmetic of two different games.

I learned this systems thinking while working on the half-space. The half-space was not invented in a lab; I first saw it in a U-17 team's match, and then noted, in scattered notes, how it slipped into senior cricket's powerplay geometry and fielding rings. What I see from the boundary is the raw material of analysis — the information points. A specific score, a specific date, a specific name — without hard facts of this kind, no conclusion holds. Every layer of analysis, every conclusion, even every warning, should rest on these information points. Where there is no evidence, guessing is not analysis — it is storytelling.

A real example fits here. Rohit Sharma has scored three double centuries in ODIs — a record possible only within the limited-overs structure of ODI cricket, where the arithmetic of time and wickets follows a fixed mould. By the same logic, Sachin Tendulkar's hundred international centuries are spread across three formats — because when the format changes, the expression of skill changes too, but patience and adaptability remain the same. Records as numbers say nothing on their own; the format's system in which they were achieved is the real information.

A large part of the format-system is rules and governance. The Duckworth-Lewis-Stern (DLS) method for revising a target after rain can completely change a match's result — and that calculation is format-specific, because the weight of overs and wickets differs in each format. Playing in an overseas league requires a board's clearance, or NOC, and in the IPL a former team's retention right, or RTM, changes a player's market value. These mechanisms are not directly technical, but without understanding them, a player's availability and a team's balance cannot be understood.

The commercial side is part of this system too. At auction, a player's price often exceeds his international performance — because the auction's logic is format-specific demand and team need, not just average statistics. So a high salary and international strength are not the same thing — two different systems with two different arithmetic.

And the subtlest area is field geometry. With only four fielders inside the circle during the powerplay, open space appears in front of the batter — that open space is an opportunity like football's half-space, but one that some occupy and others cannot. In Tests that opportunity is absent, because the field is spread; in ODIs it is time-bound; in T20 it is momentary. The most dangerous batter is not the one who finds space; it is the one who understands why the space opened.

Another old habit of mine applies here — fatigue-adjusted analysis. In the 2026 Russia World Cup final, Croatia arrived exhausted after three extra-time matches, and their pressing dropped late. In cricket I watch the same way: after a long tour, a bowler's economy rises at the death, and in the final session of day five a batter's shot selection changes. Fatigue alone explains nothing; but read alongside the format-system, fatigue completes the picture.

Now to the side everyone avoids. As analysis grows more advanced, analysts retreat further into the data room — and drift further from the rhythm of the match. A batter's strike-rate fluctuation is a number on the scoreboard, but behind it lies the state of the innings — how many wickets have fallen, how many overs remain, where the field is open, how tired the bowler is. Without that context a number is just a number, and decisions taken from it often misread the match's tempo.

Another trap — the drama of small samples. If someone declares 'this bowler is a format specialist' from a single innings, that is not information, that is emotion. Test, ODI and T20 benchmarks differ, so making a format-switch decision on one match's data means deciding by breaking the rule. I trust no system until I know how it breaks without a crowd and with heavy legs — in cricket, those heavy legs mean the death overs, the last day's Test session, or the bowling workload of a long tour. When form and fatigue fall together, the strike rate or economy that emerges speaks far more truth than any format benchmark.

In the coming series I will count one thing — how faithfully each team honours its own format benchmark. Dot-ball rate in the powerplay, economy at the death, patience for wickets in the final session. Because the team that plays by the rules of its own system controls the match's true tempo. The question remains open: in the next ODI series, will teams play by their own format-system, or walk out carrying the habits of another format?