Why the Same Pressure Feels Different Everywhere

This current series explains the 6 questions to ask when you have problems that have already been “fixed” once… or twice… and are somehow back again.

We’ll spend our time looking at what your organizational pressure is revealing, where things are straining, and what actually has to change so the fix sticks.

The goal isn’t more activity. It’s fewer repeats.

Thanks for being with us for the fifth question! -Tate

It’s disorienting leading through a hard stretch. The same year doesn't feel the same across the organization. You’re in the same building. Same numbers on the same dashboard. The team down the hall is having a different experience than yours.

Some teams seem to absorb the load. Others are visibly cracking. And when those two groups have to work together, which they almost invariably do, the friction can read as personal even when it isn't.

There's a reason for this. It has little to do with the idea that some teams are stronger or better led than others. Work behaves differently under pressure depending on what kind of work it is.

Some work is built to move fast. It needs quick decisions, short cycles, room to try something and adjust. The cost of being slow is higher than the cost of being wrong, because you can correct a wrong answer but you can't get the time back. A sales team works this way. So does a product team in an early market. Or an incident response team. For these teams, pressure can sharpen things up to a point. The urgency fits the work. Load, for them, can actually be useful.

Other work is built to be stable. It needs consistency, accuracy, or careful coordination. The cost of being wrong is higher than the cost of being slow, because errors compound. They hit downstream processes, customers, compliance, or trust. A finance team works this way. So does a regulatory affairs team, a supply chain operation, or client relations. On these teams, the same pressure that helps the fast-moving team puts them on edge. Rushing is the enemy. When they're pushed to move faster than the work safely allows, they don't just get frustrated. They get less effective and more anxious. The errors begin to stack up. 

When these two teams have to work together, the difference can show up as conflict. The fast-moving team thinks the stable team is slow, blocking, scared of risk. The stable team thinks the fast-moving team is reckless, sloppy, and doesn't understand the consequences. (Both right about what they need. Neither right about each other.) The conflict has nothing to do with attitude or culture or whether people are team players. They're doing different kinds of work, and the pressure is surfacing that difference in the most visible and personal way it can.

There's a second cut that matters about as much.

Some work needs to act and then learn from what happens. The information you'd want before moving doesn't exist until you've moved. Waiting is itself the wrong answer. Other work needs to understand the situation before acting, because the cost of a wrong move is too high to absorb. Neither of these is a personality type or a culture preference. They're requirements of the work itself. A marketing team testing a new channel needs to run experiments. A surgical team preparing for a procedure needs to know what they're doing before they start.

Most organizations don't build their structures around these differences. They build one structure and ask everyone to work inside it. When load goes up, the gap between what the work needs and what the structure gives it becomes friction. That friction usually gets read as a people problem.

The team that needs to move fast is stuck in an approval process built for work that needs to be stable. The team that needs to think carefully before acting is being pushed into sprint cycles built for work that benefits from moving fast. Each of them is working against the structure rather than with it. Under normal load that's a manageable annoyance. Under higher load it's the thing that's breaking everything.

Understanding this changes how you read what you're seeing.

When a team is consistently slow, the first instinct is to ask whether they're working hard enough. The more useful question is whether the structure they're working inside fits the kind of work they're doing. Same logic for two teams that keep clashing. The instinct is to fix the relationship: better communication, clearer roles, a teambuilding or alignment session. The more useful question is whether they're doing fundamentally different kinds of work that are being asked to move at the same pace, through the same process, toward the same kind of decision. If that's what's going on, communication training is the wrong tool. Train all the communication and teamwork you want, the structure keeps producing tension.

The practical bit. When you're trying to figure out where the load is hitting hardest, looking at which teams are struggling isn't enough. You have to look at whether the structure those teams are working inside fits the work itself. A team doing stable, accuracy-dependent work that's being pushed to move fast isn't struggling because they're weak. They're struggling because they're being asked to do their work wrong. A team doing fast, experimental work that's buried in process and approvals doesn't have a discipline problem. The structure is slowing them down in ways the work can't afford.

Two teams cracking under the same pressure aren't telling you the same story. The difference between the stories is the diagnosis.

Get The Load directly in your inbox