PRESSURE PATTERN #9

Empty Station

On the morning after a key person quits, what their leaving does to everyone else's load, and the 48 hours that teach a team who they are.

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

Pressure: The resignation takes a day. What follows belongs to the people who stayed.

Ray resigned on a Tuesday.

He did it the way you would want someone to do it. Weeks of notice. A written handoff for every account he owned. He sat down with the two people picking up his territory and walked them through which customers needed a call in the first month and which ones would hold until the quarter turned. He was in sales, he had been with us for years, and he left the way he had worked.

A few days later, in a room with a lot of other people in it, a boss of mine said that Ray had never really been a committed member of the team.

It was not rage. It was said evenly, almost in passing, folded into a longer conversation about pipeline. And it was not true. I had been in the trenches with Ray. He had carried quarters that would have flattened other people, and the person saying it had been in the room for most of them.

I said so. Not well, and not at length. The conversation moved on inside of a minute.

What I remember is the room. The room did not argue with me and it did not agree with me. People looked at their laptops. It took me a long time to understand that my correction had not mattered much, because the sentence had already done its work. Every person in that room had just learned something, and it was not about Ray.

What a team learns in the days after someone leaves is not about the person who left. It is about what happens to your record here when you go.

I believed at the time that I was watching a bad moment. A leader under pressure, saying something he would not say again. I filed it that way for years. Then I left, and he said the same kind of thing about me.

Meanwhile the actual work Ray had been doing did not go anywhere. It sat unowned for about a week, and then it went somewhere. Not by decision. By gravity.

Pattern: A load left unassigned still gets assigned. It settles on whoever is nearest and least likely to say no.

Two things happen when a key person leaves, and organizations usually only manage one of them.

The first is the staffing problem. A seat is open, a requisition gets written, somebody starts interviewing. It takes months, the months are understood as a given, and so it gets treated as the hard part.

The second is the load problem, and it resolves itself in about two days whether anyone attends to it or not. The work does not wait for the req. Absent a decision, it moves along the path of least resistance: to the person physically closest to it, to the person who already knows the system, to the person who has historically said yes. Conscientiousness is a selection criterion here, which is why the people who absorb an empty station are frequently the ones least able to afford it.

It travels below the level of anything written down. Three extra approvals in someone’s week. A standing meeting they now run. A customer who now calls them. It carries no end date, and because the output holds for a while, the arrangement looks like it worked.

Coworkers watching someone leave are not neutral observers. Felps and colleagues found that a person’s likelihood of quitting is shaped by the job search behavior of the people around them, over and above their own satisfaction with the job. Departures are informative, and people update on them. The first person to leave changes the arithmetic for the people who watched them do it.

In the days after a departure a team is doing something more careful than gossip. They are collecting evidence about what this place does with your history once you are gone. They get it from how you describe the person, from whether you say anything at all, and from whether your version matches the one they lived through.

What it costs

None of this stays in the register of how people feel. Four places it lands, none of them soft:

• Decision quality and speed. A team that concludes leaving gets your record revised stops telling you early. There is no upside in signaling that you are looking. The next departure arrives as a resignation rather than a conversation three months out, and every retention decision after that gets made later and with worse information.
• Cross-functional throughput. The load moves to whoever is nearest, and nearest usually means inside a function. The parts of the role that crossed boundaries are the least likely to get picked up, because they belonged to no job description and were visible to few people. Work at the seams degrades first and reports last.
• Organizational prioritization. Interim coverage with no end date commits real hours against nothing on paper. Next quarter you plan against a model that assumes those hours are available. You prioritize with confidence against a number that is wrong, and the gap surfaces later as slipped commitments blamed on estimation.
• Trust, which compounds the other three. Trust governs how much people give beyond what was asked, and most of what an organization calls excellence lives in that margin: the catch that was not assigned to anyone, the second look at something that already passed review, the hard conversation someone starts because they care about the outcome more than the awkwardness. When trust drops, compliance holds and discretion goes. Output looks stable for a quarter or two, which is exactly why this is easy to miss until it is expensive.

What moves into the space discretionary effort leaves is cynicism. And a person who watched a good colleague get written out of the record, and drew a conclusion about the place, is not being cynical. They are reasoning correctly from evidence you supplied. That is the part a message cannot reach.

What to do about it

Two readings get in the way. The first treats a departure as simply a resourcing event: post the role, restore the headcount, problem closed. That reading is not wrong so much as slow, because it attends to the thing that takes three months and ignores the thing that resolved on Thursday. The second treats it as a verdict, on the company or on the person. Both versions are satisfying and both stop useful inquiry, because once you have a verdict you no longer need the facts.

Three moves, none of which require you to feel good about the person leaving:

• Say the true generous thing in the first two days, out loud, in front of the team. One accurate sentence about what they contributed, said in a room, early. Losing someone good hurts, and the hurt does the editing before you notice it happening. The version that comes out is rarely a lie. It is a true account with the best parts left out. The work is not being generous. It is being accurate while it still stings.
• Redistribute on purpose, with names and an end date. Write down what the person was holding, including the parts that were not in their job description, assign each item to a named person, and say the period out loud. Pay particular attention to whatever crossed a boundary, because that is the part your own function will not think to claim. Absorbing for a defined stretch is a plan. Absorbing with no end date is a role change in disguise.
• Ask the people who stayed a specific question. “How are you holding up” gets a polite answer. “What landed on your plate this week that was not there two weeks ago” gets an inventory. The sum across four people is usually larger than any one of them realizes, and that sum is the correction to next quarter’s capacity model.

Shift: Who picked up what this person was carrying, and was it intentional, or was it gravity flowing in the path of least resistance?

One question to carry this week: when the person who left was someone you counted on, did the account you gave of them survive your own disappointment?

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

P.S. Years after that meeting I left too, and I got the same treatment Ray had. Mostly it taught me that the reflex is common and it is not personal, which is a smaller lesson than I wanted and a more useful one. What I do differently now is narrow. When someone leaves, I write down what they were carrying before I write the requisition, because the second thing is easier and I will do it first if I let myself. And I say one true thing about them in the first forty-eight hours, while people are still listening. Not for the person who left. They are gone. It is for the people who stayed.

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.