Home/Soccer Analytics/Tempo Quantification (Actual vs. Expected Speed)

Tempo Quantification (Actual vs. Expected Speed)

Tactical AnalysisLevel 3 — Advanced

What It Is

Defining tempo as the average difference between actual ball speed and expected ball speed across a set of passes: tempo = mean(actual_speed - expected_speed). A player or team that consistently passes faster than expected given the spatial context plays at a "high tempo." This separates meaningful tempo (quick combinations through tight spaces) from meaningless speed (long clearances that happen to be fast). The chess analogy: tempo is gained when you accomplish an objective with fewer moves (or faster passes) than expected; lost when you take extra time. Accumulating these deltas reveals which players, teams, and pass types consistently play faster or slower than context predicts.

Correct Execution

(1) Compute expected ball speed for every pass using the expected-ball-speed-model. (2) For each pass, compute delta = actual_speed - expected_speed. (3) Aggregate by player, team, match, phase of play, pass type, or any other dimension of interest. (4) Positive mean delta = high tempo (passing faster than context demands). Negative = low tempo (passing slower than context allows). (5) Analyze which situations produce the highest tempo — are there specific pass types, pitch zones, or game states where a team plays significantly faster than expected?

Key insight: this is NOT possessions per game (basketball tempo). Stoke City under Pulis topped raw ball speed rankings but wouldn't score as "high tempo" because their fast passes were long clearances into contested space — expected ball speed for those situations is already high. Barcelona's short combinations in tight spaces are "high tempo" because expected speed there is low but they execute quickly.

Progression Levels

Diagnostic Tree

Coaching Cues

  • "High tempo in your own half is just quick recycling. High tempo in their half is what breaks defenses."
  • "Stoke topped raw ball speed. That's not tempo — that's long balls."
  • "Tempo is chess: accomplish the same objective with fewer moves. In football: move the ball faster than the defense expects."

Common Errors

  1. Using raw ball speed as tempo: Long clearances are fast. They're not tempo. Always adjust for context.
  2. Confusing tempo with possession: Barcelona has high tempo AND high possession. They're correlated but not the same — a team can have low possession but play at high tempo in transition.
  3. Not accounting for game state: Trailing teams often increase tempo (desperation passing). Leading teams may decrease tempo (game management). Tempo changes within a match are as informative as the aggregate.

Edges

Conventional Wisdom Is Wrong

The Teams That Top Raw Ball Speed Rankings Are NOT Playing at High Tempo

tactical-analysistempo-quantification

Tempo defined as raw ball speed produces absurd rankings — Stoke City under Pulis topped raw speed because of long clearances. True tempo is actual speed minus EXPECTED speed for each pass's context. Barcelona's short combinations in tight spaces register as "high tempo" because expected speed is low but they execute quickly. Stoke's long clearances register as average because expected speed for those situations is already high.

What most people do
Measure tempo via raw ball speed, possession speed, or passes per minute — all of which conflate meaningless speed (long clearances) with meaningful speed (quick combinations through pressure).
What the best do
Build a context-adjusted tempo metric: mean(actual_speed - expected_speed) across all passes. This separates meaningful tempo (faster than the context demands) from meaningless speed (long balls that happen to travel fast). Slice by pitch zone to distinguish tempo in buildup (less important) from tempo in the final third (more important).
Why it's an edge: Teams with genuinely high tempo in the final third create chances before defenses organize — the 20-second zone dwell principle connects directly. But this can't be measured without the expected-speed model. Raw speed metrics rank the wrong teams at the top.
How to exploit: Build the expected ball speed model, compute tempo scores, and identify which players and teams play faster than context demands in the zones that matter (final third, progression phase). Recruit players with high tempo in those specific zones. For opponents: identify where their tempo drops (likely against organized low blocks) and prepare to force them into that context.
Cross-domain parallel
In chess, tempo is "accomplishing an objective with fewer moves than expected" — the same relative-to-expectation concept.
Devin Pleuler, Toronto FC, StatsBomb Conference, 2021-11-04. Stoke vs. Barcelona example.

Sources

  • Devin Pleuler, Toronto FC, StatsBomb Conference 2021, YouTube, 2021-11-04 — proposed tempo = mean(actual - expected ball speed); contrasted basketball tempo (possessions/game) and chess tempo (moves saved); identified the need for context-adjusted speed measurement