Operational Learning: Hands Stilled

I sat in a CAB call last quarter where I almost made the kind of mistake that takes years to unlearn.

The change in question was a routine release. Something simple at first glance, but with one dependency I knew from a previous incident could cause real downstream pain if it shipped without a specific safeguard. The owner of the change hadn't worked through that incident with me. They had walked into the role two months earlier, after I'd moved laterally into a different part of the org.

I was in the call as an observer. The room ran on a half-hour cadence, structured tight. Five minutes for context, ten for risk classification, ten for the call, five for documentation and routing. Standard. It was the third CAB I'd sat in on in this format, and I still wasn't used to how short they were.

The change came up. The owner walked through the risk profile. I felt my mouth open before I had a thought formed. I was going to redirect. Going to ask whether they'd checked the dependency. Going to surface the prior-incident pattern. Going to say what I thought they'd missed.

I caught it half a syllable in.

Because the next thing the owner said, without any prompt from me, was the dependency. They'd flagged it. They had the safeguard already in the change package. They named the prior incident by ticket number, not by the war story I would have told. They'd read the post-mortem.

The call moved on. Decision logged. Routing automatic. Twenty-six minutes total.

I closed my mouth. Sat with my hand still half-raised against the desk, ready to point at something. Nothing to point at.

I sat with that for a long minute after the call ended. Something had just happened in that room, and I wasn't sure I'd ever been on this side of it before.

I have spent the better part of twelve years trying to get rooms like that to run.

Different sectors, different scales, different vocabularies. A plant where the daily ops call had been a 90-minute rehash of yesterday's blame. A change board that ran on tribal memory and hero sweat. A program governance forum where every escalation was a personal favor. I have sat in dozens of these rooms over the years and pushed pieces of structure into each one. A cadence that holds. Triggers that earn the reopen. Ownership that lives in a role rather than in a name. Exceptions classified instead of accommodated. A documentation discipline that means the next person doesn't have to find the institutional memory in a hallway conversation.

The pieces don't look the same in any two operations. I have watched the same underlying architecture take different shapes in different rooms, with different vocabulary attached to it, and each time it took years of pushing for any of it to start holding.

What I had not done, until that CAB call, was sit in a room where it was running without my hands on it.

The hardest part wasn't the recognition. The recognition was almost easy. My nervous system noticed before my analytical brain did. The hardest part was the next twenty seconds.

The hardest part was the discipline of letting the owner make a call I would have made differently.

Not wrong. Differently. They sequenced the conversation in an order I wouldn't have chosen. They named the risk in language I wouldn't have used. They closed the call faster than I would have closed it. By the time I had cycled through my own version of how that conversation should have gone, the room had already moved past it. Cleanly.

If I had spoken, I would have made the system worse. Not because my redirect would have been wrong, but because the structure only holds if the owner gets to own. The moment I become the redirect, the room re-trains itself to wait for me. The cadence loosens. The triggers degrade. The role becomes a name again.

• • •

In that twenty-six-minute meeting, five things were running at once, in vocabulary I have been using for years without always being able to point at any of it holding this cleanly.

Cadence held the decision. The meeting didn't expand to fit the conversation. The conversation contracted to fit the meeting. The cadence wasn't a calendar entry. It was a control structure.

Triggers earned the reopen. Nobody asked to revisit a prior decision out of nervousness or political weight. The change package referenced specific prior decisions only where the conditions had crossed a documented threshold. The reopens were quiet because they were earned.

The owner owned. Nobody asked who they reported to. Nobody routed the decision up the chain to make sure a more senior person had blessed it. The role had decision rights and the rights were respected by the room.

Exceptions were classified instead of accommodated. One change in the queue ahead of mine was non-standard. It wasn't waved through with a verbal apology and a promise to document later. It was classified, the deviation captured, the learning routed to where the standard would be re-evaluated. The exception was a learning input, not a one-off.

The documentation worked. The new owner had read the post-mortem. They knew the dependency by ticket. They didn't need me to tell them the war story because the war story had already been written down by people whose job it was to write it down.

Five things, all running at once, in a room where nobody used the words operating model.

That is what an operating architecture looks like when it is actually installed. It runs the room, in twenty-six minutes, because every piece is doing its job quietly. The people inside the room have stopped noticing it. They have stopped narrating it back to themselves. They are just working.

• • •

There is a real tension here that the capstone of any operational architecture has to face.

You need to be able to explain the system. To a board. To a new hire. To a stakeholder asking what the operating model is. The vocabulary matters. The naming matters. Without it, the architecture is unteachable and unprotectable, and the next reorganization will dismantle it without realizing what it dismantled.

But the moment the people inside the room start narrating the architecture back to themselves as an operating model, something shifts. The cadence becomes a thing they're doing rather than how they work. The triggers become a process to follow rather than a discipline that has been internalized. The owner becomes someone executing a role description rather than someone owning a decision. The system begins performing itself, which is the register decay arrives in.

If I had spoken in that CAB call, I would have started exactly this kind of decay, and I would not have known I had done it. The meetings would have stretched. The owners who had been making clean calls would have started waiting for permission. The escalations would have routed back up to me. The senior person who built the system would have become the bottleneck the system was built to remove.

I have seen that decay arc before. From the other side. In rooms where I was the redirect, and could not understand why the system kept needing my hands on it.

I do not have a clean resolution for this tension. I do not think one exists.

The leaders I respect most have learned to speak the operating model fluently outside the room and to almost never speak it inside the room. They protect the invisibility of the architecture from the people who are running it, while making the architecture visible to the people who need to understand or fund it. That is not a resolution. That is a working practice.

The discipline is restraint. Recognition is the part that makes restraint possible.

The CAB call that ran in twenty-six minutes ran that way because nobody in the room was performing the operating model. They were running it. My job, in that moment, was to not become the thing that interrupted that. To not narrate. To not redirect. To not insert the war story they did not need.

To still my hands.

Most of you reading this have spent a long career pushing pieces of an operating architecture into rooms that did not have one. A cadence somewhere. A trigger discipline somewhere else. An ownership map you fought to get role-based. A post-mortem habit that took two years to stick. Different rooms, different sectors, different scales. The pieces rarely look the same twice.

The work this week is not to install anything new. The work this week is to look.

Walk into your next operations review and ask one question. Which of the pieces you have been pushing, for years, has finally started running without you?

If you can find one, the discipline that follows is harder than the building was.

Keep your hands off it.