
Duckworth-Lewis-Stern, explained without the algebra
DLS gets blamed every time rain interrupts a run chase, but the idea behind it is simpler than the reputation suggests: resources, not just overs.
The problem it's solving
If rain cuts a run chase short, you can't just prorate the target by overs remaining — a side chasing 300 in 50 overs isn't in the same position with 25 overs left as a side that was always set 150 to win in 25. Wickets in hand matter as much as overs left. DLS solves for that by tracking a combined resource: how many of a team's 50 overs and how many of its ten wickets are still available at any point in the innings.
How the target actually moves
Every combination of overs-left and wickets-left maps to a resource percentage, built from historical scoring patterns. If the chasing side loses overs to rain, the target is rescaled by the ratio of resources available to each side — not simply cut in proportion to time lost. That's why a rain-reduced target can look higher than expected: the side that got to bat its overs uninterrupted had more resources than the side now getting a shortened chase.
Why it still causes arguments
The model is transparent, but it's still a model — it assumes a 'typical' scoring pattern for a given resource level, and any specific match can deviate from that. When a chase gets reduced mid-innings against an aggressive batting side already ahead of a typical scoring curve, the recalculated target can feel unfair even though the maths is doing exactly what it's designed to do.


