Pressure gets blamed for a lot of things it didn’t cause.
A deadline slips and a team turns on itself, and the deadline takes the fall. A launch goes sideways, people stop talking to each other, and it all gets filed under stress. But pressure doesn’t break teams. It just stops hiding the ones that were already breaking.
I’ve watched two teams hit the same impossible week. One pulled together and shipped something better than it had any right to be. The other came apart, went quiet, and limped across the line with everyone privately furious. Same deadline, same stakes, roughly the same talent.
The difference wasn’t resilience. It was decided long before the pressure showed up.
The pressure isn’t the problem
Every agency runs into the same moments. The client who rewrites the scope on Thursday for a Monday deadline. The launch date that holds even though the work slipped two weeks ago. The month two people give notice in the same week, and the work doesn’t pause to let you feel it.
Most leaders read those moments as a test of the team’s character, or as evidence they hired the wrong people. So they respond the way instinct tells them to. More check-ins, tighter oversight, a standup that quietly turns into an interrogation.
And the next crisis goes worse, because now the team is managing you on top of managing the work. You end up treating the symptom and never touching the thing underneath it.
The team that holds isn’t tougher
Under pressure, people don’t rise to the occasion. They fall back to whatever they can rely on. Nobody invents a new way of working at the worst moment of the quarter; they reach for whatever solid ground is already beneath them.
You can usually tell which kind of team you’re leading long before a crisis arrives. Watch what happens when someone makes a small mistake on a normal week. Do they raise it right away, or do they show up with the explanation already built? That quiet moment predicts far more than whatever happens during launch week.
So the real question isn’t how much pressure a team can take. It’s what’s under their feet when it arrives. Two things decide that, and both get built on the calm days, long before anyone is under the gun.
The first is stability
Stability is the least glamorous thing a leader provides, which is probably why it gets so little credit. It’s just predictability. Expectations that hold, standards that don’t shift with the mood in the room, priorities that mean the same thing on Friday that they meant on Monday.
When that predictability is there, a team can spend a whole crisis on the crisis. They’re not also trying to work out which rules apply this week.
When it isn’t, pressure just speeds up a wobble that was already there. If the ground moves on an ordinary Tuesday, it moves a lot faster on the worst day of the quarter. A team can be perfectly capable and still come apart, because what it’s standing on won’t hold still.
The second is trust
Stability is what makes the second thing possible, and that second thing is what really gets tested when the pressure is on.
Go back to that small mistake. Whether someone puts it on the table early or arrives armoured with explanations isn’t really personality. It’s a track record, built one quiet day at a time. People surface bad news early when they’ve learned, over many uneventful days, that doing so is safe. They hold onto it when they’ve learned the opposite. By the time the deadline arrives, the lesson is already taught. You’re just finding out which one you taught.
Trust is what lets a team move fast without checking over its shoulder. It’s the difference between a group that gets quicker and more honest under load, and one that gets slower and more guarded because everyone is protecting themselves first. I wrote about how that erosion actually happens in what actually breaks trust inside growing teams, and the short version is that it almost never breaks in the moment you’d expect. It breaks earlier, in how the small stuff gets handled.
There’s an order to this worth naming. Trust can’t carry weight that stability hasn’t set up first. A team standing on unsteady footing never gets the repetitions it needs to learn that the people around it are reliable. You can’t build the second floor before the foundation is ready. Leaders who try to manufacture trust on top of instability usually end up disappointed, and they tend to blame the people instead of the ground.
What it actually looks like in the wild
The tell isn’t how loud a team gets under pressure. Loud is fine. Loud can be a team arguing its way toward a better answer. The tell is where the energy goes, toward the problem or toward self-protection.
Over 16 years and 600+ websites at Forge & Smith, the projects that came apart under a deadline were almost never the technically hard ones. A good team will usually rally around hard work. The ones that fell apart were the ones where the brief changed three times in a week, or where everyone quietly doubted the direction but nobody wanted to be the first to say so. Every hour of pressure landed on a crack that was already there. The deadline didn’t open the crack. It found it.
You can run this read on your own team without waiting for the next crisis. Think back to the last genuinely high-pressure stretch you went through. The useful detail isn’t whether you hit the date, it’s whether people owned the mess as it happened or quietly started building a case for why it wasn’t their part. The same stretch tells you whether the hard conversations were about the work or about who would carry the blame.
Whatever the answer is, that’s the culture you actually have, not the one written down anywhere.
You can’t install this during the crisis
Here’s the inconvenient part.
The stability and trust a team draws on under pressure can’t be built under pressure. There’s no time. The crisis is when you find out what’s already there, not when you put it there. By the time the hard week arrives, the work that decides how the team handles it is already done.
Which means the most important work you do for your worst weeks happens during your most ordinary ones. It’s holding the direction steady on a quiet Tuesday instead of redrawing it because you had a new idea in the shower. It’s meeting a small problem calmly instead of making the person who raised it wish they hadn’t. That’s the work nobody schedules, and it’s the work your hardest week runs on.
None of it feels urgent. That’s exactly why it’s easy to skip, and exactly why skipping it shows up later, at the worst possible time.
So if you want a team that gets better under pressure, stop trying to get better at pressure. The team that holds isn’t reacting well when it counts. It’s drawing on something you built months earlier, on a day nobody thought mattered.
