The System That Ran Without You

I started leading people at twenty, and for most of the years since, my instinct in the moments that mattered was to reach straight for the commitment. Lay out the plan, ask for the yes, sort out the details after.

It backfired in a specific, repeatable way. The sharpest people on my teams — the ones whose buy-in I most needed — would answer a request for commitment by listing every reason the thing couldn't be done. In order. Airtight. I used to hear that as resistance. It wasn't. It was the predictable output of handing someone a how before I'd given them a why — and delivering it the same way I delivered it to everyone else.

I didn't sit in that mistake. I inverted it. But it took me an embarrassing number of years to see what the mistake actually was.

For four weeks — all of Act I — the system we built lived inside one person. Yours. Energy, prioritization, focus, and emotional regulation, wired together so your own operating system runs without willpower. This week the system leaves your calendar and meets other people. And the first thing you learn is that a system running clean inside your own head can read as chaos to a team — not because the system is wrong, but because you're running it on people who need it delivered in opposite ways.

That gap is what this week's pairing closes. Two of the foundational frameworks in The Resilience Engine: Situational Leadership II and the "Clear is Kind" Protocol. Each is well known on its own. Run together, they cover a problem neither can cover alone.

THE MECHANISM

Situational Leadership II, from Ken Blanchard and Paul Hersey, starts from a claim that sounds obvious and that almost nobody actually operationalizes. As the book puts it: "there is no single best leadership style." You diagnose each person's development level for the specific task in front of them, and you adapt your style to match — directing, coaching, supporting, or delegating. The same person can be a self-reliant expert on one task and an anxious beginner on the next. You lead the task, not the résumé.

"Clear is Kind" comes from Brené Brown's research, and it fits on a bumper sticker: "Clear is kind. Unclear is unkind." Vagueness feels gentle and is actually cruel — it leaves people to fail in confusion while you protect your own discomfort. The book turns that principle into a repeatable format — Situation, Behavior, Impact, Request, Support — so "be clear" stops being a personality trait and becomes a structure anyone can run.

Here's what makes them a pair rather than two good ideas filed separately. Situational Leadership II governs how you deliver — the style, tuned to the person. "Clear is Kind" governs what you deliver — the standard, held identical for everyone. One rail flexes. The other holds. They run in parallel, and each fails in a specific way the moment the other goes missing.

WHY EACH RAIL FAILS ALONE

Adapt your style without an explicit shared standard, and the adaptation stops reading as responsiveness. It starts reading as inconsistency — and to the person on the receiving end, as favoritism. The book names this failure directly: if "you roll out SLII but don't combine it with 'Clear is Kind' communication," it warns, "your adapted leadership styles come across as inconsistent and confusing." I have done exactly this. I gave one person room and another person structure — both correct for who they were — and never said out loud that the objective underneath was identical. From the outside, it didn't look like tailoring. It looked like I was running two different rulebooks.

Now run the other rail alone. Hold one crystal-clear standard, but deliver it in a single uniform voice to everyone. It lands for your self-reliant people — they were going to be fine anyway — and it sails straight past the person who's quietly struggling and won't say so. Clarity that only reaches the people who already had it isn't clarity. It's a broadcast. This is the exact failure Situational Leadership II exists to prevent: one-size-fits-all management, the book notes, "creates one-size-fits-nobody resentment."

One rail alone reads as favoritism. The other alone reaches only the strong. Together — and only together — you get a standard that's the same for everyone, delivered in the one form each person can actually receive.

THE EVIDENCE

If this feels like a small refinement, look at what its absence costs at scale. Gallup's 2024 State of the Global Workplace report found that only 30% of US employees are actively engaged. 62% are not engaged. 15% are actively disengaged.

That is not a motivation shortage in the workforce. It's the visible output of teams run on one rail — style without standard, or standard without style. Seven in ten people showing up to systems that were never wired to hold them.

RUNNING BOTH RAILS

You don't need a program. You need one turn of both rails at once.

Pick two people who need opposite things from you — one who wants room, one who wants to be in the room. Name the single shared objective they are both working toward, and say it to each of them in the same words. That's the standard rail: explicit, identical, spoken out loud. Then deliver it to each in the style their situation actually needs — the why first, for the one who has to own it before they'll move; continuous inclusion, for the one who does their best thinking inside the conversation. One standard. Two deliveries. Held on purpose.

That is the whole mechanism in a single interaction: the objective doesn't bend, the delivery does.

OPENING ACT II

Act I asked whether you could install a system inside yourself. Act II asks the harder question: whether it survives other people. The answer the next six weeks keep returning to is that it isn't charisma that makes a team hold — it's structure. The leaders who don't need to be in the room to keep the standard high didn't find more charisma. They built a better design.

There's a popular version of this week's idea that stops halfway: "great leaders just flex their style to each person." It's half right, and the missing half is the one that matters. I'll take that up this weekend — along with a stance I hold that cuts against a lot of what gets said about leadership: the job is to extract what's already in each person, not to install what you wish were there. But that's Saturday.

For now: one objective, said the same way to two people, delivered two different ways.

— Oscar

Want to see where your team's operating system actually holds — and where it's running on one rail? The Resilience Engine Systems Audit maps it: myresilienceengine.com/systems-audit