StarkPitch

Conceptos

8 min · 2026-08-12

Errores comunes al interpretar PPDA y números de presión

El PPDA es un proxy útil para la altura e intensidad del compromiso defensivo, pero es fácil de malinterpretar si se ignoran la muestra, el rival y el estado del partido.

Título y resumen están localizados. El cuerpo del ensayo permanece en inglés por calidad.

What PPDA approximates

PPDA (passes allowed per defensive action) estimates how many opponent passes occur before a defensive action such as a tackle, interception, or foul in a defined area of the pitch. Lower PPDA usually indicates more aggressive engagement; higher PPDA usually indicates a deeper or more passive block.

It is a proxy constructed from event data, not a direct count of “presses” as a coach would mark them on video. Definitions of the defensive third or midfield band vary between analysts.

Mistake 1: treating lower as always better

Aggressive engagement can be a deliberate plan — or a symptom of being stretched after turnovers. A low PPDA without territorial or chance control may simply mean a team is chasing.

Conversely, a higher PPDA can be intentional: a mid-block that concedes sterile circulation and defends the box. Style and success are different questions.

Mistake 2: ignoring opponent and game state

PPDA is interactional. Facing a side that circulates patiently under low pressure will produce different numbers from facing a direct team. Leading late often changes pressing intensity. Aggregating without context hides those shifts.

Single-match PPDA is especially fragile. Prefer ranges, opponent-adjusted reading, and phase splits (first hour vs closing stages) before strong claims.

Mistake 3: equating PPDA with a full pressing model

Pressing involves triggers, cover shadows, rest-defence, and coordinated jumps. Event-data PPDA collapses much of that into a rate. It can flag intensity and height; it cannot narrate the press structure alone.

When you write about pressing, state what PPDA can support (“more frequent defensive actions relative to opponent passes in zone X”) and what still needs video (“who jumped, who covered, whether the trap was on”).

A cautious workflow

1. Define the PPDA formula and pitch zone you are using.

2. Note match state and opponent style.

3. Cross-check with territorial metrics, shot prevention, and at least one video sequence.

4. If layers disagree — for example low PPDA with many shots conceded — treat the contradiction as the analytical finding, not an inconvenience.

Puntos clave