Under pressure, leaders skip the one conversation that would save them time.
The familiar pattern under pressure
When things move fast, a familiar pattern appears. A project starts. Deadlines approach. Everyone is busy, capable, motivated.
So leaders do what feels logical. They go straight to tasks, timelines and deliverables. It looks responsible. It is what the team expects from them. It fits how all comparable projects have started.
And yet this is precisely where most mistakes get built in. Not visibly. Not immediately. But unmistakably once the work is running and the first real tension appears.
What quieter and more costly gets skipped
What gets skipped is quieter and much more costly.
The conversation about how the team will collaborate under pressure. Not the topic of an offsite. Not a separate track. An ordinary conversation, early in the project, about the few questions that make the difference once reality starts to move.
The fact that it is quiet is what makes it costly. No one misses it while it is being skipped, because it is not on an agenda. Everyone misses it the moment it should have happened, because the agreements it would have produced are absent at the moment they are needed.
Four questions that do not get asked
Four questions that usually do not get asked under pressure.
- How will we challenge each other?
- How do we decide when opinions differ?
- What does accountability look like here?
- How do we deal with friction when it shows up?
Under pressure these questions feel like a luxury. Something to sort out 'later'.
But later is precisely when teams pay for them. Because as soon as one of these questions becomes acute, and that almost always happens, there is no shared basis to answer it. The team then improvises under tension, and the improvisation becomes pattern, and the pattern becomes 'how we work here'.
Speed without alignment
In the teams I work with, from project teams to global leadership teams, the pattern is consistent.
Speed without alignment does not create momentum. It creates friction.
Teams initially do not feel slower. They become slower weeks later. Decisions drag. Tensions surface indirectly. Good intentions turn into quiet resistance.
Not one of those symptoms is striking enough to act on immediately. All of them stack up until the moment the leader wonders why a team that started so promisingly takes so much more effort than expected three months in. The answer rarely sits in the people. It sits in the conversation that was not held at the start.
An hour that seemed to miss the brief
A leadership team once asked me to help build a strategic plan to hit their business goals. I agreed and started with behaviour.
They looked at me as if I had missed the brief. To them strategy meant market analysis, goals, priorities. Not how they would treat each other while executing that strategy. They were right that I did not answer their explicit question. And they were wrong about what the brief actually was.
At the end of that hour they told me it was the most useful session they had had in years. Not because we had built the strategy. Because we had agreed on how they would challenge each other, decide, carry accountability and address friction while working out the strategy together. From that point on the strategy work moved faster than they had expected, because the work that would otherwise have stacked up underneath the strategy had been caught.
What fast-scaling leaders counterintuitively do
The leaders who scale fastest do something counterintuitive. They pause early.
Not for a long offsite. Not for therapy. Just one focused hour to make behaviour explicit before the work begins.
The hour is cheap. It costs nothing that would not otherwise be spent. It often saves months of rework, misalignment and energy loss. The ROI is one of the highest in my work, and at the same time one of the hardest to argue, because the effect only becomes visible later and the leader initially feels they are postponing something.
Who we want to be while we hit the goal
I have seen that one hour change teams in how they work under pressure. They align on who they want to be while hitting the goal, not only on what needs to be achieved.
That distinction is not philosophy. It is operational. A team that steers only on the goal uses every means to reach it, including means that undermine the relationship or the culture. A team that also steers on behaviour chooses means that hit the goal and strengthen the relationship. The first form hits the goal faster and pays later. The second hits the goal with less repair cost and at the same time builds capacity for the next project.
The next time a project starts under pressure, take that hour at the beginning. Not to delay the work. To lay the basis on which the work can actually land.