One Move Ahead: How Early Intervention Changes the Outcome
In a game of chess, the winner isn’t always the player who sees the most moves ahead. More often, it’s the one who recognises a shift in the board early enough to respond before the position becomes difficult to recover from. Leadership under pressure works the same way.
Once a pressure signal has been noticed and taken seriously, the instinct is to reach for something proportionate to the weight of the problem – a restructure, a formal review, a significant conversation that’s been building for months. But really, the most effective leadership interventions tend to happen much earlier and require far less effort.
The value of acting early isn’t just that it’s easier; it’s that the options available at that stage are considerably better.
Here’s what early intervention looks like in three common leadership scenarios:
A team member’s output starts slipping
The default response: Wait for a performance conversation to become necessary, or to quietly absorb the gap.
The early move: A direct inquiry into what’s getting in the way, not framed as a performance discussion, but as genuine concern for what’s making the work harder than usual.
In practice: A leader at a mid-size firm noticed one of her strongest analysts had missed two internal deadlines in a month. Rather than flagging it formally, she blocked 20 minutes and asked a single open question: “What’s making this challenging for you right now?” The answer revealed a conflict between two project leads over her time that no one had surfaced. One short conversation between the leads resolved it. The analyst’s output recovered within a fortnight.
The intervention cost less than half an hour’s time.
Team energy shifts before a major deliverable
The default response: Roll out a team-building exercise or morale initiative, something visible enough to signal that leadership has noticed.
The early move: Restructure how information flows during high-pressure periods so people have explicit permission to flag problems before they compound.
In practice: A technology company’s engineering lead introduced a two-question end-of-sprint check-in: “What slowed you down this week, and what do you need next week that you don’t currently have?”, during a particularly demanding product cycle. The questions surfaced three resolvable blockers, two of which had been quietly affecting delivery for over a month.
The entire process took less than ten minutes per sprint and surfaced more actionable information than the weekly status meeting it replaced.
Decision-making starts bottlenecking
The default response: Absorb the incoming decisions, or push back on individuals for not showing enough initiative.
The early move: A brief, focused conversation about decision levels, which decisions require escalation, which ones don’t, and what “good enough to proceed” looks like for the latter.
How this might look: An operations director noticed her inbox was filled with decisions that should have been resolved two levels below her. Rather than addressing it person by person, she set aside 45 minutes with her leadership team to map ownership explicitly. Within two weeks, the volume of escalations had dropped noticeably and two team leads reported feeling more confident acting independently.
The mapping conversation took 45 minutes. The time recovered across the team in the following month was estimated at several hours per person.
The thread running through each of these scenarios is that the intervention happened before the situation required a significant response.
The options were still open, the relationships were kept intact, and the cost was low. None of them required a difficult conversation, a formal process, or a restructure.
Consistent performance over time comes down to one thing: getting into the habit of reading pressure early and responding before the position becomes hard to recover from.
Related:
The Cost of Waiting: Why Delayed Response Turns Pressure Into Burnout