The Other Channel
and Who Owns the Queue

It was my day off. I was on speakerphone with my wife. She had asked me a question and I was about to answer it.

The screen changed. An incoming call. A partner's name.

My first thought was not about him at all. It was blunt: I am overloaded. One more incoming request, and this one had just jumped over everything else, including the question my wife was still waiting on.

I told her to wait, said I would answer later, and picked up the work call.

We spoke for about twenty minutes. Several times I explained that I had a day off, that I could not go into details. He did not let go. And still, the conversation was fine. He is direct, he is engaged, and I told him so. I said I valued his openness. By the end, I think he understood me better, not worse.

But before we hung up, I said something out loud for the first time. Email is our official channel. If we do not respond within a day or two, then call. He had also asked for our executive director's mobile number. I told him not to try that experiment. The same logic applies there: email first.

There was no conflict in any of this. The episode just stayed with me, and later, turning it over, I saw why.

My phone had become a territory without me ever deciding it. My mother calls this number. My wife. My son. The people who reach me instantly, without a queue, without a subject line. Work lives somewhere else. Work lives in Teams and in email, where messages wait until I open them.

Nobody wrote this rule down. Nobody agreed on it in a meeting. The tools sorted it out themselves, quietly, over years. He had already surprised the whole team this way. After years of Teams and email, a plain call to a mobile phone felt like an event. People mentioned it to each other. Someone is calling. On the phone.

He was not breaking a rule. There was no rule. And his logic was sound. He said it himself: this is how he gets results. He is right. A call cannot sit unread. A call does not wait in a queue behind forty other messages. A call takes the front of the line by force.

That is exactly the point.

Email and chat carry a specific right, and that right is the reason they won. The right to decide when another person's task enters my head. I open the inbox when I am ready. I sort. I sequence. A phone call removes that right. It demands the answer now, in the middle of whatever was already happening.

This is the real insight, and it is smaller and sharper than it first looks. Channels do not just move messages. The channel decides who controls the incoming line, the sender or the receiver. Asynchronous tools give that control to the receiver. A call gives it back to the sender.

Everything else follows from this. The family territory on my phone is not sentiment. It is the one group of people I have given permanent control over my line, and the tools enforced that decision before I ever made it consciously. The team's reaction to his calls was not about manners. It was the feeling of control changing hands without agreement.

And inside a company, the official channel is not bureaucracy. It is the agreement about who owns the queue. When someone bypasses it, they are not choosing a faster tool. They are moving their request from your schedule to theirs.

The partner was not wrong. The channel he used really works, and it works for exactly the reason it costs the receiver something. He taught me where the border was. I had been overloaded for a while. I only saw who was managing the overload, and through which doors it arrived, when one request came through the door I had reserved for family.