The ‘one‑run loss’ moment
In a tense IPL 2026 encounter, Delhi Capitals narrowly lost by just one run, with the narrative quickly turning to veteran batter David Miller after his decision not to complete a single on the penultimate ball reportedly became the focal point of criticism. The middle‑order south‑paw, widely expected to rotate strike in the final overs, instead stayed put on a risky ball, leaving the tail batting and the team just short of the target.
Gavaskar’s defence of Miller
Legendary former captain Sunil Gavaskar, however, has argued that blaming Miller alone is unfair and that the broader setup and game‑management bear more responsibility for the marginal loss. Gavaskar pointed out that the required run‑rate and the state of the pitch, the strength (or weakness) of the remaining batters, and the pressure‑build‑up in the middle overs all shaped the situation, not just Miller’s final judgment. In his view, focusing narrowly on one decision obscures the cumulative impact of earlier planning and field‑setting that led to the 1‑run cliff‑hanger.
Why context matters more than blame
The former India opener stressed that in high‑pressure, low‑margin finishes, “no single decision operates in isolation,” and that a team’s structure—such as the order of finishers, backup plans, and captain’s on‑field choices—should be scrutinised first. He also warned that singling out a senior player like Miller after a tight loss can damage team confidence and set a bad precedent, at a time when the league needs to balance accountability with constructive post‑mortems.
