The channels are an example, not the count

Whenever I say four channels — product, architecture, code, QA — someone writes back: mine runs five. They are right. The number belongs to your domain, not to the frame. What matters is the structure, not the count.

I keep getting that note in DMs from CTOs in three different countries, and at first I tried to defend the four. Then I noticed I was defending the wrong thing. The four was an example, not a claim. The claim sits underneath.

The Literal Misreading

The paper §3 uses four channels because that was the cleanest example for software engineering — product, architecture, code, QA map almost one-to-one to roles a CIO already recognizes. It made the diagram readable. It made the table fit on a slide. It let me say something concrete without spending two paragraphs defining terms.

But the actual frame describes N dimensions of judgment that expertise demands you hold simultaneously. N is not four. N is whatever your domain forces on you the moment you operate at the senior level inside it. The four was a worked example, the way a physics textbook uses a frictionless plane — useful, illustrative, not the law.

Reading it as "it has to be exactly four" turns a frame into a checklist. And a checklist of four items is the worst possible misreading, because it implies that anyone working with five or six channels is doing it wrong, or that anyone working with three is somehow lighter. Neither is true. The point was never the count. The point was that expertise does not narrow down to one channel at a time, and the moment you try to pretend it does, you lose the senior in the senior role.

What Dimensions Show Up in Other Domains

A surgeon I talked to last year described her mixer as five channels — technique, hemodynamics, operative time, team communication, and the anticipation of complications. She did not call it that. She said "there are five things I am tracking and if I drop any of them the case gets worse." That is the mixer in another vocabulary.

A proprietary trader friend runs five different ones — position, market regime, risk budget, macro narrative, the day's P&L. He told me that the day he can only track three is the day he should not be at the desk. He has rules for that.

An investigative journalist I worked with on a project a few years back ran four — source health, the angle, the legal exposure, the pace of release, and the implicit audience reading over her shoulder. That is five if you count the audience, four if you fold it into angle. Again the count is a domain artifact.

The pattern is not the number. The pattern is that all three of them, in three completely different crafts, described the same internal posture: several dimensions modulated continuously, none of them parked at zero, all of them feeding the same decision.

What Is Constant

There is a floor below which there is no expertise. One channel does not reach. A surgeon who only watches technique loses the patient. A trader who only watches position loses the year. A senior engineer who only writes code without thinking about product, architecture, or how this fails in QA is not a senior engineer — they are a junior engineer with more years on the resume.

There is also a ceiling above which the mixer overloads. And that ceiling is not a function of how many channels you can technically track — it is a function of self-awareness about which channel is drifting and when. The mixer can hold six channels for a few hours. It cannot hold them for a quarter without explicit recovery design, and the senior who pretends otherwise is the senior who burns out the cleanest.

The channels modulate. None of them drop to zero for long without a cost. The cost might be invisible for a sprint — you can stop thinking about QA for two weeks and ship. The cost shows up the third week. That is the integral I keep talking about: total cognitive load is not the peak of one channel, it is what you carried across all of them over time.

How to Find Your Own

Do not borrow my four. Take a recent decision that felt very you — one where you came out of the room and thought, that was me at my best. Then list which dimensions it touched. Not which steps you took — which dimensions of judgment were live. You will recognize them when you write them down.

Then take a decision that felt that wasn't me — one where you came out and thought, I should not have signed off on that. You almost certainly operated fewer channels than usual. Maybe you were tired, maybe the meeting was too short, maybe one channel had been crowded out by something else. List which one was missing.

The answer — the number plus the names — is your mixer. It is not the paper's. It is not mine. It is yours, and it has been yours all along; the frame just gives you a way to look at it and a vocabulary to talk about it with people who run a different one.

How many channels run in your head on a normal day — and which one is the first to drop when you're tired?

#TechLeadership #FutureOfWork #Engineering #MixerMode