The Weight Before the Words

It’s Tuesday morning. You’re in a 1:1. One of your direct reports is asking about leading the API redesign next quarter. Is it a good growth opportunity? It’s a reasonable question. You give a reasonable answer.

What they don’t know is that you spent an hour last night on a call with HR, finalizing the conversation that will change everything for them by the end of the week.

Every engineering leader eventually carries this weight: the gap between what you know about someone’s future and what they know about their own. The conversation itself gets all the attention: what to say, how to be direct with empathy. That part matters, but it’s thirty minutes. The carrying period can last weeks or months of parallel operation. That’s where outcomes are actually shaped. How you manage it strongly shapes whether the person lands well, the team stays stable, and the organization stays clean.

The Bureaucratic Reality

Let’s be honest about the timeline. Sometimes it’s a PIP that HR and legal require before anything moves forward. Sometimes it’s a reorg that’s been approved but not announced. Sometimes it’s a client-driven rolloff where the decision originates entirely outside your org. The trigger varies. The carrying period doesn’t.

Each version has its own mandated timeline, and those timelines exist for good reasons, though not every one is as long as it needs to be. The failure mode isn’t the mandated timeline. It’s the discretionary delay you add on top of it. The process is complete. The path is clear. And you push it one more week because the timing feels off, or you want one more data point, or Friday just seems too soon. That padding isn’t diligence. It’s the discomfort of acting disguised as thoroughness.

Every day of discretionary delay is a day the person keeps investing in a reality you’ve already decided to change. They commit to projects, turn down recruiter calls, and make plans based on the absence of bad news.

Where the Time Goes

But before the carrying period even starts, most leaders have already lost weeks to a quieter failure mode: hope as strategy. “One more quarter.” “Let’s see if the new support structure helps.” “I don’t want to overreact.” By the time you’ve committed to the decision, you’ve spent more time convincing yourself to act than the process itself requires. The carrying period doesn’t start when the decision is made. It starts when you first suspected and chose not to force clarity.

Once you’re in it, the carrying period has failure modes that show up in your day-to-day behavior. Each one is well-intentioned. Each one makes the outcome worse.

Unconscious withdrawal. You pull back without realizing it. Your 1:1s get shorter. You stop engaging with their proposals. You stop asking about career goals because it feels dishonest. They notice the shift before they understand it, and by the time the conversation happens, it lands as confirmation of something they already sensed. That turns a recoverable transition into a betrayal.

This is different from a deliberate strategy. Some leaders intentionally create space for someone to read the room and self-select out. A calculated move with a defensible—if uneven—rationale. But unconscious withdrawal isn’t strategy. It’s leakage. Know which one you’re doing.

Overcorrection. Guilt pushes you the other direction. You’re warmer, more available, more encouraging than usual. When the conversation arrives, the prior weeks become evidence against your credibility. They replay every positive signal and wonder what was real. The dissonance is worse than the news.

Performative normalcy. It sounds noble. But maintaining your exact normal rhythm can become its own kind of dishonesty. If you know someone is rolling off the project in ten days, a deep-dive architectural review on Wednesday isn’t respect. It’s theater. Letting them take ownership of a complex initiative that someone else will inherit next week isn’t kindness. It’s an organizational liability.

Operational pragmatism isn’t the opposite of respect. Shifting someone toward lower-risk work during the transition window protects the team, the organization, and the person from owning a mess they won’t be around to resolve. The line is intent: adjusting scope to reduce blast radius is leadership. Disengaging because you’ve already written them off is negligence.

Managing the Window

A few things keep the carrying period from degrading the outcome.

Have an operational partner. Not a therapist—someone who shares the coordination load and keeps your judgment honest. An HR partner managing timing and preparing assessments. A peer or skip-level leader who owns the backstory. The loneliness of carrying it alone is what drives most of the failure modes above. When you have no one to calibrate with, you either withdraw or overcorrect.

Separate the emotional timeline from the operational one. You can feel conflicted and still execute cleanly. Discomfort isn’t a signal that you’re moving too fast. It’s a signal that you take the human cost seriously. But it’s a variable in the equation, not the equation itself. The equation is: does the person land well, does the team maintain velocity, and does the organization stay healthy.

Know when the carrying has to end. Extending it doesn’t protect anyone. It converts your discomfort into their uncertainty and the team’s instability. Once the process is approved and the path is clear, move.

The Thirty Minutes and the Weeks

You’ve done this before. You’ll do it again. And the thing that will test you next time, same as last time, isn’t what you say in the room. It’s whether you managed the weeks before it well enough that the person has options, the team has continuity, and the organization doesn’t have a crater where a key person used to be.

That’s the harder part of the job. Not the conversation. The carrying.