What pressure reveals about a team

Calm conditions flatter everyone. When there’s slack in the system — time, budget, attention — even a poorly aligned team can look like it’s working. Pressure removes the slack, and what’s left is the truth about how the team actually operates.

I’ve come to treat hard moments less as problems to survive and more as information to read.

What you actually learn

When a deadline tightens or an incident hits, watch for three things:

The mistake is reacting to the symptom

The instinct in a hard moment is to fix the immediate thing and move on. That’s necessary, but incomplete. The incident is the symptom; the way the team handled it is the signal. If ownership scattered, that’s not a one-off — it’s a structural fact that will repeat under the next bit of pressure.

So after the fire is out, I try to ask a quieter question: what did this just tell me about how we’re built? Not to assign blame, but to find the seam that opened, because it will open again.

Building for the hard case

You don’t make a team resilient by hoping pressure won’t come. You make it resilient by designing for the case where it does: clear ownership decided in advance, decisions that don’t all funnel through one person, and enough psychological safety that people surface problems early instead of hiding them until they’re unavoidable.

Pressure is going to reveal your team either way. The only choice is whether you’ve used the calm periods to decide what it reveals.

← Back to all articles