Vanished Edges

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. I stopped saying “a few more months” at home after that. Not because I decided to stop. Because nobody in my house believed it anymore, including me.

For a long time I treated that as a planning failure of my own. If I sequenced better, delegated better, said no better, the calm would arrive. 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. A crisis hit, everyone ran hard, and it passed. The weeks afterward were slower on their own, and people caught their breath without anyone planning for it. 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 hard stretch blends into the next one, and the load is simply there, all the time, on the good days and the bad ones, at the office and at home. 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.

Identify the Pattern

Vanished edges describes the pattern of pressure that used to be episodic, but has become ambient and constant.

This 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.

Our bodies and minds are built for the old shape: a spike of stress, a response, a return to normal. There is a large body of research on what happens when margin never comes, and none of it is about weakness. A system that stays switched on pays a rising cost the longer it stays on.^[1] Inside a team, I have watched that cost arrive 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. Decisions that used to be routine start getting escalated. Work comes back to be redone because it was done tired the first time, and the same problem returns a second and a third time. From a distance, the team looks fully committed. Up close, the quality of decisions and the effectiveness of the work have been slipping for months.

The uncomfortable part is that a strong team hides this the longest. Strong teams carry reserve, and they spend it covering the early losses. Someone absorbs the extra load, someone catches the rework before it reaches a metric, and none of it shows up in a number you track. So the team you worry about least gives you the faintest warning, and by the time sustained load is impossible to miss, it is showing up in your best people. That is the most expensive place for it to surface, and the last place you were looking.

One more piece, from the physiology: for a single person, duration beats intensity. The body is built for acute stress followed by recovery, not for chronic activation.^[2] The teams I have led worked the same way. They survived brutal sprints that had an end date, and cracked under moderate load that never ended. A sprint with no finish line is not a sprint. It is a new baseline no one agreed to.

Reframe the Mindset

The tools most of us inherited assume the edges still exist. Work harder assumes there is a far side where you will recover. Time management assumes the problem is how the hours are arranged. Resilience training assumes the recovery is coming and you just need to hold on until it arrives. None of these are bad tools, and when pressure still comes in waves, they still work. But pushing through only works when there is something to push through to.

Losing the trough between waves costs more than it first appears, because the trough was doing two jobs. It was the recovery, and it was also the warning. When a team crashed after a hard push, the crash itself said, in plain terms, that everyone had been running too hot, and the slower weeks that followed gave them room to cool down. Continuous load takes away both at once. It never crashes hard enough to sound the alarm, so the moment that used to say “now, recover” never arrives. Nobody decides to skip recovery, and it is not neglect when it stops happening. Recovery did not get skipped. It lost its trigger.

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. Wanting the team to win. Nobody defends a punishing baseline more loyally than the person who built it for the people it is costing.

And you probably do not control the load. Most leaders cannot cut the roadmap in half or reverse external forces. So the useful reframe is not “reduce the pressure.” It is narrower. Recovery used to happen on its own, in the spaces the work left open. Those spaces are gone. Now recovery only exists where someone deliberately builds it, the same way staffing and budget only exist where someone plans them. If it is not built, it does not exist. And building it is available at every level, whether or not the workload is yours to set.

Transform the Tension

Three moves, none requiring authority you do not have.

Stop promising it settles. If the settling is not coming, say so. Your team already knows the calm quarter keeps not arriving, and every time you promise it anyway, they trust the rest of what you say a little less. Naming the real baseline costs you one uncomfortable conversation. It buys back the credibility you will need for everything else.

Build edges back in on purpose. Give the current push a real end, and say out loud what the first week after it looks like, even if the next project starts anyway. Then rotate the weight that never stops: the escalations inbox, the on-call phone, the meeting that eats a day. The work still gets done. What changes is that no one person carries an always-on load with no break in sight. Rotation gives one person their edges back without dropping anything.^[3]

Watch judgment, not hours. Hours and effort will lie to you; the work will not. Look for decisions getting escalated that used to be routine, rework coming back, meetings multiplying while output shrinks. And look hardest at your strongest team, where the reserve runs deepest and the strain shows last. Those signals appear in the work long before anyone says a word about being tired.

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

Reflection (Questions to Ponder)

• When did I last promise my team, or my family, that it settles after this push? Did it?
• Which of my decisions this month were made worn down, and which would I make differently on a clear Tuesday morning?
• What in my team’s rhythm creates recovery on purpose, and what just assumes it will happen?

Connection (Questions to Discuss)

• Where has our judgment slipped ahead of our effort: decisions bouncing upward, rework, the problem that keeps returning?
• If the load is not dropping this year, what edges could we build inside it: real finish lines, rotations, recovery that is scheduled instead of hoped for?
• Which commitment are we still carrying that made sense in a crisis and never got retired?

Subtraction (Things to Stop)

• Stop promising things will slow down. Every time it fails to arrive, it spends credibility you will want later.
• Stop reading endurance as health. A team can run hard long after its calls have started degrading. The effort is the camouflage, and the better the team, the better the camouflage.
• Stop treating recovery as an individual perk while the load is structural. A rested person returning to an unchanged system drains on the same schedule as before.

Action (Things to Try)

• Put one real edge on the current push, out loud. Name its end date, and name what the first week after it looks like. If you cannot name an end, that is not a push. It is your new baseline, and it deserves a different conversation with your team and with the level above you.
• Rotate one always-on weight this month: the escalations inbox, on-call responsibilities, the standing report. Duration is what wears people down; rotation returns someone’s edges without dropping the work.
• For two weeks, keep a private tally of decisions that come back a second time and work that gets redone. That number is your team’s judgment under load, measured in the work instead of the mood.