The Relay Was Never the Job. The Timing Was.

November 19, 2026

Watch the video version:

During an acquisition, the newest person on my team came to me with the question the newest person always asks: "Am I going to be the first to go?"

I knew more than I could say. I had done my own reading on the company that might be buying us, and I had reached real conclusions about what was coming. None of it was inside information; all of it was pattern recognition, research, and professional judgment. I could not separate what I had concluded from how I had concluded it without putting things in motion that were not mine to put in motion.

Looking at him, I felt two things at once. I wanted to give him more than I could, and I held the line anyway. I also carried the weight of knowing more than I could say while looking at the person most exposed to it. So I separated what I knew as fact from what was research and rumor, and I handed him only what I could stand on. The positions on my team had been approved by a board that had been working on the acquisition for six months, and you do not approve expansion for a group you plan to cut. The team was profitable. The acquiring organization had told us directly that it was interested in our core software.

It didn't settle. I knew three facts would not make the question go away for him. Had I passed along my own read as I had it, he would have acted on a guess dressed as a fact, and my read would have spread past him and become the team's version of events, one I could never take back.

I am making the same call right now. A new partner for our API product has asked for six significant changes. I have accepted two, and only one of those is designed. If I let the other four through, it would derail everything. It wouldn't matter if I told my team I wasn't sure we would even do them; they would still start thinking them through and formulating questions, and it would derail things.

From the outside, both look like routing. Something comes in from one side, something goes out the other, and a manager sits in the middle. That is the work many organizations are now cutting. Xbox's leadership told staff in July that organizations with up to 14 layers of management would come down to no more than five, and three where possible, according to the memo as quoted across multiple outlets. Some leaders hold three views of those layers at once: managers who only route information are overhead, and tools move it faster and cheaper; transparency beats gatekeeping, so a layer that holds information back is the problem; and an AI summary now does what the messenger did.

I make no prediction about Xbox. Plenty of managers really did only forward email, and when a cut removes one of them, nothing changes. The test is what happens after the role is gone: whether anything starts arriving too early or too late.

The judgment only shows when it is missing. From the outside, the role looks like forwarding, because the visible output is the same: a message passed along. The judgment lives in what passes and when, and nobody sees the message that was held until it was ready. Cut the role, and information still moves. It moves the moment it exists, before it is stable. Signal Staging is my name for that judgment: the call on when information from one part of the organization has matured enough to pass to another without generating rework. It cannot be separated from the act of passing, which is exactly why it looks like routing.

Unstaged information is rumor with a timestamp. Passing everything along at once feels like transparency, but the people receiving it cannot tell analysis from fact, so they treat all of it as fact. A label stages nothing: "we may not do this" still lands as something to think about. Some act on it: they re-plan, or they start looking. Others learn to discount everything and wait to see what sticks. Either way, your team loses the one signal it used to have: this is ready. Faster tools make that worse. They move everything sooner, and none of them decides whether it is ready to move.

Leadership reads the quiet as transparency working, because nobody brings the worry upward. The missing judgment never shows up on a report; it shows up as rework, reversals, and people leaving early over a guess. The cost lands first on the people most exposed and least informed, like the new hire who asked me his question. Then it lands on the senior people who start doing the staging informally, with no title and no time set aside for it. Then it lands on the leader who has to walk back what spread. I wrote in July about the coordination work that moves to whoever absorbs it. Timing is the one part that cannot move, because it is a judgment, not a task.

This is what I call The Redundancies: two identical consultants and one sincere question, "What would you say you actually do here?" They keep the one deliverable anyone can see. The judgment about when information should arrive was never on a line item, so it leaves with the person who carried it. They are beaten by one thing: a written account of that work, prepared before they arrive.

The leaders who come through a flattening with their timing intact don't have better instincts than you. They wrote the call down while the person who made it was still in the room.

Before you cut a role that looks like routing, find the decision inside it. The role was never the forwarding; it was the call on what is ready to pass, and when. Write that call down while the person who makes it is still there, and name who makes it afterward. If nobody owns "is this ready?", the information still moves, only at the wrong time.

Take one role on your team that the next reorg could read as a relay, and if it is yours, take your own. List three things from the last month that the person held, reworded, or timed before passing them on, and next to each, write what would have happened if it had gone straight through. If you cannot fill in the list, you don't know what the role does yet; ask the person who is in it. Then name who will make that call if the role goes away.

The Edge Case tells the full story of that quiet period in Chapter 1, under Read Access: knowing precisely what needs to happen without the authority to act on it, and how to hold that gap well for the people on either side of it: https://TheEdgeCaseBook.com

The fight between your roadmap and your sprints was built in on purpose, and no process change will end it. What it is, and how to stop losing to it. (Clock Drift)

Anthony S. Jackson

Anthony S. Jackson

Anthony S. Jackson has spent 30 years inside technical organizations. He is the author of the Architecture Protocol Series: three books on the structural problems technical leaders were never told they would face. He writes the LeadershipOS™ Inner Circle, a monthly printed newsletter for CTOs and engineering managers who design teams that hold under pressure.

LinkedIn logo icon
Back to Blog