Read this online Was this forwarded to you? Subscribe to Pressure Patterns and get the next one in your inbox.

PRESSURE PATTERN #6

Snowshoe Weather

On the force that breaks what it touches, why the fix is rarely shrinking the weight, and what it takes to widen the surface that carries it.

Pressure: Sinking isn’t proof the load is too heavy. It’s proof the surface is too small.

Behind my house in Minnesota there are several acres I have crossed more times than I can count, part farmland, part marsh. In deep winter it turns into one smooth white field. But that smoothness is deceptive. The ground underneath keeps rising and dropping, so the depth changes step to step without telling you.

One stride holds. The next finds two feet of loose powder over a low spot, and in you go. Boot, shin, thigh. There is a name for this effect: post-holing. In boots, even good warm ones, it had me winded a hundred yards into my own back yard.

Then I got a pair of snowshoes, and the same ground stopped fighting me. Same person. Same weight. Same snow. I easily walked several miles over drifts that had been swallowing me whole. Nothing about me had changed. The only thing that changed was the span of the surface under my weight. It is not a trick. It’s physics.

For years I got this exact lesson wrong at work. When someone on my team was sinking, I reached for the only two tools I could see: lighten the load, which I couldn’t always control, or encourage them to take a short vacation and then grind it out until the end of the surge. Neither of those approaches touched the real problem, which was how few square inches sat under the load.

Pressure = Force / Area

In physics, pressure is defined as force per unit area. That’s only two variables, so pressure rises in two ways:

1. The force stays the same, but the surface shrinks: a resignation, an unfilled role, ten people become seven and the roadmap doesn’t.

2. Or the surface stays the same, but the force grows: a tightening economy, a new competitor, a launch window that won’t move.

Teams are not physics problems, but this formula has changed my first question about any hard season for a team. Not how heavy. How wide.

Pattern: Pressure isn’t how much a team carries. It’s how few are carrying it.

Snowshoe weather is my name for the seasons most teams actually work through: the load is deep, there is no route around it, and the formula’s two variables are the whole diagnosis. When a heavy force lands on a team and the surface is a few people, it becomes acute pressure on those few. Kept connected and spread wide, the same force becomes a weight the whole team can carry together.

A snowshoe is not a plank. It is a frame laced with webbing, dozens of small connections sharing every step, and a team is the same: the tight network of people and processes is what makes the area wide. A load carried that way is not just lighter per person. It is steadier, higher quality, and much harder to drop.

But load does not spread itself. Under strain, work flows toward whoever can carry it: escalations route to the person who fixed it last time, knowledge pools in whoever has been there longest, approvals queue behind the one name everyone trusts. Competence attracts load, so the reward for carrying well is more to carry.

From above it looks like efficiency; the org chart reads smooth, like the field behind my house. The tell is where work waits: progress queued behind one calendar, a vacation that requires a war plan, “only one person knows how” said as a fact instead of a warning. The one carrying the most is the first to punch through.

Most of us inherited instincts that aim at the wrong variable. Reduce the force: sometimes possible, rarely ours to decide. Toughen the person carrying it: that is buying stiffer boots for deep snow. The boots don’t change what the snow does. Only the snowshoe does, because it never argues with the weight. It simply spreads it out.

The real barrier is that widening looks wasteful up front, one person too many in the budget review, right up until the week it isn’t. And the person under the point rarely asks for help, because carrying a heavy load alone can be attached to identity, pride, sometimes job security.

But you rarely control the force, and you almost always control some of the area: who else can do this, who else knows this, who else can support the person carrying the heaviest load? If force is what happens to you, area is what you can build in response.

Four moves, none needing permission from the level above you:

• Map the point loads. Make a list of the things that only one person can do and where work naturally concentrates. You cannot widen what you cannot see.
• Widen the surface. Delegate the heaviest work across more people, ask for help, stretch a work stream across more time, put a second trained hand on the critical system.
• Stay connected while you carry. Watch each other for the early signs of burnout, step in or advocate for relief, and raise your own hand when you are the one sinking. It can feel like weakness, even shame. It is neither. Asking for help is what a high performing system does. This is not a character test.
• Reward the spread, not the save. Great collaboration under pressure with clean handoffs deserve the applause way more than the heroic all-nighter.

What you celebrate, you concentrate. So celebrate the spread.

Shift: If I can’t lighten the force, how do I widen the area?

One question to carry this week: where is the work concentrating most acutely and what can you do to help spread the load?

The full piece goes deeper on the research behind widening, the questions to put in front of your team, and the habits worth stopping. Read the full version.

This pattern is part of the library of leadership content at Resonant Vector published by Mark Benson to help leaders and teams thrive under pressure.