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

PRESSURE PATTERN #5

Vanished Edges

On pressure that no longer arrives in waves, what a team loses when recovery disappears, and why judgment erodes before effort does.

Pressure: A sprint with no finish line is not a sprint. It is a new baseline no one agreed to.

For years, every surge arrived with the same story attached, the one I told myself and everyone around me: it gets better in a few months, once we are through this one. There was always a reason to believe it. A launch would ship, a reorg would finish, an escalation would close. And part of the story was true. Each surge did end. But the settling never came, because the next one was already building while the last one receded.

I learned the story had stopped working the way these things usually go: at home, mid-sentence. I was explaining a business trip to my son, walking him through the familiar math, this one trip and then home for a while. He was seven. He said, “Dad, you travel all the time.” No anger in it. Just a boy reporting what he saw. And he saw it more clearly than I did: the trips and the surges were not exceptions anymore. They were the schedule.

For a long time I treated that as a planning failure of my own. It took me longer than I want to admit to see what had actually happened: the work itself had changed shape underneath me. Pressure used to arrive as an event, and the weeks after it were slower on their own. That rhythm is what I mean by edges: hard stretches with clear starts and ends, ordinary time in between. Most teams I know do not have that rhythm anymore. The waves, as I learned, weren’t waves at all. They were part of a rushing river that had no end.

Pattern: Sustained load doesn’t take a team’s effort first. It takes their judgment.

Vanished edges describes the pattern of pressure that used to be episodic, but has become ambient and constant. It matters because of where recovery used to come from. No one scheduled it. The gap between one crisis and the next did that work automatically. When the load became continuous, those gaps disappeared, and rest became something that only happens if someone deliberately makes room for it. In most organizations, nobody owns that job.

The cost arrives in a particular order, and the order is what makes it easy to miss. Effort is the last thing to go. People keep working hard, often harder than before, and all that visible effort makes everything look fine. What goes first is judgment: tradeoffs get sloppier, routine decisions start getting escalated, work comes back to be redone because it was done tired the first time. And a strong team hides this the longest, because strong teams carry reserve and spend it covering the early losses. By the time sustained load is impossible to miss, it is showing up in your best people. The most expensive place for it to surface, and the last place you were looking.

Here is the part that took me longest to see. The trough between waves was doing two jobs. It was the recovery, and it was also the warning. Continuous load never crashes hard enough to sound the alarm, so the moment that used to say “now, recover” never arrives. Recovery did not get skipped. It lost its trigger. And you probably do not control the load, so the useful reframe is not “reduce the pressure.” It is narrower: recovery now only exists where someone deliberately builds it, the same way staffing and budget only exist where someone plans them.

Part of why the missing edges are so hard to rebuild is that the load is attached to good things. Providing for a family. Building something that matters. Nobody defends a punishing baseline more loyally than the person who built it for the people it is costing.

Three moves, none requiring authority you do not have. Stop promising it settles; your team already knows the calm quarter keeps not arriving, and every empty promise spends credibility you will want later. Build edges back in on purpose: give the current push a real end, and rotate the weight that never stops, the escalations inbox, the on-call phone, the meeting that eats a day. And watch judgment, not hours. Hours and effort will lie to you; the work will not.

Shift: If the load has no finish line, what do I build to last inside it?

One question to carry this week: where have you convinced yourself the load is episodic, one more push before it settles, when it is actually continuous? And if that is true, what will you do differently, starting this week?

If this one landed, the full piece goes deeper: the research on why duration beats intensity, what to watch for in the work itself before anyone says they’re tired, and the full sets of questions to reflect on and discuss with your team, plus the specific things to stop and to try. Read the full version.

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