Read time: 4.1 min.

{{First Name | My friend}},

I was reading the news a few weeks ago when something caught my attention.

Delta Air Lines was simultaneously transitioning its COO, CFO, and CMO.

The coverage was thoughtful. It focused on the incoming leaders, their backgrounds, what they bring, and what the change signals for the airline's next chapter.

But I kept thinking about something the coverage didn't mention.

When three senior leaders transition at the same time, the visible things get managed.

The org chart updates, responsibilities shift, and onboarding begins. Announcements go out. The organization signals continuity, and in most ways, it means it.

What doesn't get announced is quieter and harder to see.

Every leadership team makes choices, often without realizing it, about how decision architecture gets built. Who holds authority when priorities conflict. What was decided and on what basis. Under what conditions a decision can be reopened. Those choices can be made explicitly, documented, and built into how the leadership team operates. Or they can be left to form on their own, settling into relationships and informal agreements that feel stable because the people holding them are still in the room.

Most organizations choose the second path without ever consciously deciding to.

And let’s be honest. It works, until it doesn't.

Because informal architecture is real. It has the power to govern how decisions move through the organization every day. But it has a fundamental vulnerability built into it. It is entirely dependent on the people carrying it. And when those people leave, it leaves with them.

This is the part I keep coming back to.

In the early weeks after a transition like this, nothing looks broken. Work continues. Milestones are tracked. New leaders are getting oriented. The organization is doing exactly what it should.

But something subtle starts happening at the decision layer.

Settled decisions start surfacing again. Not because the strategy changed. Because the new leader wasn't in the original conversation and doesn't know what was decided, who carries it, or whether it's still standing. Teams wait for re-confirmation before moving. What should be a clear directive slowly becomes a question. Cross-functional decisions stall because no one is certain who owns them and where authorities lie.

You'll recognize it when you hear it.

"I just want to make sure we're still aligned before we go further."

"Let's get the new leader up to speed before we finalize."

Or the quieter version, when people simply stop raising issues across functions because they're not sure who decides anymore.

Nothing is collapsing. But nothing is moving cleanly either.

Here's what I've come to understand about moments like this.

The drag that follows a major leadership transition is rarely a talent problem. The incoming leaders are capable. They were chosen carefully. They will find their footing.

The drag is a decision architecture problem. And in most organizations, that architecture was never made explicit to begin with. Not because it couldn't be. Because the urgency to make it explicit never arrived. The people who held it were still in the room, so the system kept moving.

Let’s be clear. Transitions don’t create the vulnerability. They reveal a choice that has been quietly deferred.

When ownership of decisions lives informally, it feels stable right up until the moment the people holding it leave. The authority boundaries that everyone understood implicitly become genuinely unclear. The decisions that were settled become unsettled. Not because anyone is being difficult, but because the structure that was holding them in place was never actually structural. It was personal.

That's not an organizational inevitability. It's a design gap. And it's one that can be closed before a transition ever forces the question.

The organizations that navigate transitions treat decision architecture as a structural question, not a relational one. They make ownership explicit. They document the basis for major decisions. They define the conditions under which decisions can be reopened, and they assign those answers to roles rather than to people.

When a transition arrives, they still have work to do. But they aren't starting from scratch on the questions that matter most.

For teams that haven't yet done that work, a transition creates a narrow and clarifying window. The questions become unavoidable.

What decisions are currently in motion, and who carries them? What was decided, and what was the basis for it? Where did authority exist informally, and how do we make it explicit before the person holding it leaves? And under what conditions can those decisions be reopened by someone new to the role?

Those questions don't slow the transition down. They protect the execution momentum that the transition would otherwise quietly absorb.

The strongest teams build explicit decision architecture because strong execution requires it. When a transition does arrive, they aren't scrambling. The answers are already there.

Delta will navigate this. Strong organizations with good leadership usually do.

But here’s what stays with me.

Most leadership teams don't know how much of their decision architecture lives informally until a transition forces the question. They find out not in a planning meeting, but in the weeks of quiet drag that follow. In the decisions that keep returning to the agenda. In the coordination that takes longer than it should. In the moment someone says, carefully and professionally, "I just want to make sure I understand what we've already committed to here."

That moment is the system asking a question that should have been answered before the transition began.

So here is what I'd ask you to sit with, not as a hypothetical, but as a real question about your organization right now.

If your three most senior leaders transitioned at the same time, how much of what they carry would actually survive the handover? The decisions in motion? The informal authority? The shared understanding of what was decided, what it cost, and under what conditions it can be reopened?

Most teams don't find out until they're already in the middle of it.

The ones who ask the question early move differently.

If you're looking at your own leadership team and wondering what lives in the informal, the unarticulated, and the assumed, this is landing close to home. I'd genuinely love to have that conversation with you. You can schedule time directly here.

Until Next Sunday,

Shawnette Rochelle, MBA, PCC
Founder, Excellence Unbounded
Decision Systems for Executive Teams

If you’re curious to learn more about my work with executive teams, you can find it here.