The Uncollapsed Role

Operations is a peculiar word in a title because it describes a condition rather than a craft. A company that is operating is, by definition, doing operations. Marketing points to a function. Engineering points to a function. But operations stretches to cover whatever the organization hasn't quite decided who should own.

That elasticity feels useful until you have to explain what you actually do. I've been in ops roles long enough to know the answer changes depending on who's asking and when. Not because I'm being evasive, though I've been that too. Because the role itself genuinely shifts, and most organizations prefer not to look at it directly.

The question underneath the job title is where, exactly, authority lives when it flows through this role. Not on the org chart. In the room.

There are two stable answers, even if most companies never name them directly.

In one model, authority attaches to the role itself. The operations lead's sign-off changes outcomes. Their decision binds the room. If the forecast fails, it fails on their desk. Accountability is legible because mandate is legible. You can disagree with them, but you cannot ignore them.

In the other model, authority is borrowed. The operations lead works through proximity and trust rather than formal mandate. They smooth, translate, pressure-test, redirect. Their influence depends on the principal's standing and attention. When that standing shifts, so does theirs. If the principal loses credibility, the ops role thins instantly. The work remains real, but the authority is relational rather than structural. These roles can look, from the outside, like they have tremendous influence, because the people holding them are always in the room. What's harder to see is that the room itself is the only thing giving them standing.

Both arrangements can function well. The friction begins when no one quite knows which one they're living inside.

Before anything forces clarity, the role often exists in superposition.

In one meeting it feels decisive, almost command-and-control. In another, the same person defers, nudges, rephrases someone else's argument so it lands more cleanly. The boundaries flex without anyone having to renegotiate them. This can persist for a long time because it reduces short-term tension. The organization gets operational leverage without confronting what it has actually delegated. The ops lead gets access without having to anchor every decision publicly. Everyone moves forward under a workable ambiguity.

There's an intellectual pleasure to moving between modes that I've found hard to explain to people who prefer defined mandates. When you can inhabit both archetypes fluidly, each situation becomes a small act of reading: what does this moment require? What does the person across the table need from me right now, a decision or a cover? I've sat in rooms where I was, depending on the moment, the person with de facto authority and the person running quiet interference for someone else's authority. I've drafted the memo and made sure the right person got credit for it. I've stopped a bad decision and deliberately let a mediocre one proceed because the relationship it would have cost wasn't worth the optimization.

Some of this is just competence. Knowing when to lead and when to serve is a real skill, and organizations benefit from people who have it.

The collapse comes when ambiguity can no longer carry the weight.

Two executives disagree and look for resolution. The CEO is unavailable. A decision has to stick beyond the room. In that moment the question that's been deferred finally surfaces: does this role have authority, or does it only have access?

The answer rarely arrives as a formal declaration. It shows up in how the room reacts. Do people adjust to the call that was made, or do they wait for someone else to confirm it? Does the decision hold next week, or does it quietly unravel?

What's revealed in that moment is not new authority but the shape that was already there.

When an organization assumes it has strong ops and discovers it does not, decision-making grows tentative. When it assumes it has service ops and discovers it has quietly built strong ops, power boundaries tighten and the room reorganizes itself around a clearer center.

Neither outcome is inherently better. What strains a system is prolonged indeterminacy. The same argument returns under different labels. Accountability diffuses just enough that patterns survive intact.

Authority will collapse somewhere. It always does.

Here's what I've been slower to admit: the uncollapsed role is also structurally convenient for the person inside it.

A strong ops person operates with legible accountability. The pipeline broke and they own the pipeline. The org chart says it's their domain, which means failure has a clear address. Service ops is harder to hold to account, because the influence was relational and the wins were attributed to the principal by design. But the person in the genuinely uncollapsed role has it both ways. Credited informally for the smooth quarters, insulated structurally when something fails. There's always some ambiguity about what they were even supposed to do.

I stayed in that state long enough to benefit from it. The intellectual pleasure was real. The cognitive flexibility was real. So was the comfort of being consequential without being fully on record, of being in the room without being the one the room would hold responsible.

The most valuable operations work is the kind that makes itself invisible. Problems that stop happening. Systems that run without heroics. But invisibility cuts two ways. It can be the mark of durable infrastructure or the byproduct of authority that was never fully located, and from the outside, the two can look identical. An organization can operate for years in that ambiguity. Decisions get made, conflicts get resolved, leverage compounds. The room keeps moving.

Authority will collapse somewhere. It always does. The only real question is whether the organization decides where it lives before pressure decides for it.

The uncollapsed state feels like flexibility. For the organization and for the person inside the role, it's also something more comfortable than that: the freedom to keep moving without deciding who's responsible for the direction.