Devin had a corner of the third floor that was almost a real office. Not walls, but the good kind of open, the kind with a window behind him and enough distance from the pod that people knocked before they spoke. On Monday mornings he got there early. He would pull up his team’s board, read the weekend commits, skim the support queue, and start turning all of it into the thing the executives actually wanted: a page and a half of where we are, what slipped, what to watch.
He managed twelve people. But that Monday page was the job. Or it was the part of the job that had a name.
For nine years the shape of his week stayed the same. Pull status from below, repackage it for above. Take the strategy from above, break it into tasks below. He was good at it, and good at it in a way that hid what it was. When Devin did it, it looked like coordination. Underneath, most of it was translation. Engineers spoke one language, executives spoke another, and he stood on the stairs between them turning one into the other all day long.
Two things happened in the same quarter, and neither one was aimed at him.
The executives started getting a weekly AI briefing. It pulled from the same systems Devin pulled from, and it answered most of what his Monday page answered. Where delivery was slipping. Which accounts had gone quiet in the weeks before a renewal. It arrived Sunday night, before he had opened his laptop.
That same quarter his engineers picked up AI coding tools. A vague request that used to need Devin in the room to unpack, to ask the three clarifying questions that turned a sentence into a spec, now turned into a working draft on its own. The engineer typed the vague thing, read what came back, fixed it, and kept moving. The three questions still got asked. They just did not get asked to Devin.
The information he carried between floors started moving without him.
Nobody planned this. I want to be fair to the people who rolled these tools out, because I have been one of them, and the logic was sound. You put AI where the leverage is highest. That means the top, where a handful of expensive decisions steer everything, and the bottom, where the volume of work lives. The middle was the part everyone assumed was structural. Load-bearing. Permanent. It turned out that a large share of it was forwarding, and forwarding is the first thing a machine is good at.
I have watched a lot of managers find out their value was the relay, and it never arrives as an announcement. There is no meeting. The proposals that used to reach you as a conversation start reaching you as three bullets in someone else’s deck. You get added to the thread instead of asked in the room. One quarter you are consulted and the next you are copied, and if you are busy you might not notice the difference for a while.
Here is the part I want to sit with, because it is the whole thing.
A floor up from Devin, a manager named Priya went through the same quarter and came out the other side larger, not smaller. Same tools. Same briefing landing in her leadership’s inbox on Sunday. The difference was what her week had been made of before any of it showed up. Priya spent very little of her time moving information. She spent it on the calls that do not fit on a page. She knew which of her engineers was three weeks from quitting before he knew it himself, and she moved him to a project that changed his mind. She had killed a launch the previous spring that every dashboard said was healthy, because she could feel the customer conversations turning and the numbers had not caught up yet. When the AI briefing arrived on her floor, it did not replace her. It just did the reading she used to do before the part that mattered started.
The briefing could tell her leadership what happened. It could not tell them what to do about the engineer, or the launch, or the account manager who was quietly checking out. Those were judgments, and judgments were most of Priya’s job. The relay had never been a big share of it.
It took Devin a few months to see this line clearly, and to his credit he did not spend those months defending the Monday page. He let it go. He wrote far fewer updates, because the update wrote itself now, and he took the reclaimed hours and pointed them at the decisions that had always been sitting just outside his week. Reading the room in a tense planning meeting. Making the call on a project the floors above and below could not yet see the need to stop. Learning which engineer was restless before the exit interview.
None of that had ever appeared in his status summaries. It was the work he did between them, in the minutes he had not been counting.
The effect I did not expect showed up on his team, not on him. When Devin stopped being the bottleneck that every question had to route through, his engineers stopped waiting. They brought him harder problems, because the easy ones no longer needed him and the hard ones finally had his attention. Two people who had been drifting stayed. The team got faster, and the reason was not the coding tools, or not only them. It was that their manager had been freed to do the thing they had actually needed a manager for, which was almost never a translated status and almost always a judgment nobody wanted to own alone.
I should say plainly that early in my own career, I was the relay. I built a reputation on being the person who could sit between the engineers and the executives and make each side legible to the other, and I was proud of it, and it was genuinely valuable at the time. It also would not have survived this. If someone had handed my old employer a tool that did the translation on its own, a real part of what I sold would have thinned out overnight. I did not know that then. I thought the translating was the value. It was the visible value. The real value was the handful of times a year I told a leader something true that the reports were too polite or too slow to say, and I did not learn to weigh those two things correctly until much later than I would like to admit.
That is the uncomfortable center of what AI is doing to the org chart, well past the headlines about whose job is next. It is not coming for the manager who manages. It is coming for the manager whose week is mostly moving information from one floor to another, and it is quietly rewarding the one who was already spending that time on the calls a machine cannot make. The squeeze is real. It just lands on a narrower target than the panic suggests.
Devin still runs his team. He is, by any honest measure, more of a manager now than he was when he was writing the Monday page, and he is doing less of what he used to think the job was.
The relay was never the job. It was just the part of the job you could see.
The hard part is knowing, before the tools force the question, which of your managers is doing the judgment and which is doing the forwarding. That is the map we build with clients at Kennesys: reading where the real decisions live in an org before you automate the layer around them.