OPERATIONAL INFRASTRUCTURE

OPERATIONAL INFRASTRUCTURE

The Document That Let Me Stop Being The ANSWER
The Document That Let Me Stop Being The ANSWER
The Document That Let Me Stop Being The ANSWER

A single execution packet made one person optional on the day of a major event, proof that "I don't know what we'd do without you" is a diagnosis, not a compliment. This issue covers the three artifacts (decision log, operating doc, relationship map) that build the thing that runs without you, because the goal was never to be needed.

A single execution packet made one person optional on the day of a major event, proof that "I don't know what we'd do without you" is a diagnosis, not a compliment. This issue covers the three artifacts (decision log, operating doc, relationship map) that build the thing that runs without you, because the goal was never to be needed.

Before a large public health expo last month, I sent a ten-person team a single document. 

Not talking points. An execution packet: pre-event checklist, day-of run of show, post-event checklist, the whole thing end to end. Load-in times, assignments, sequence, what happens when. 

I could have carried most of that in my head. I've done enough of these. Carrying it in my head would have felt efficient right up until 6:40am on a Saturday, when nine people are looking for one person to ask, and that person is parking a truck. 

The packet wasn't documentation. It was the thing that made me optional on the day. Which is the actual goal, and it's the opposite of what most of us are quietly optimizing for. 

"I don't know what we'd do without you" is a diagnosis It's a lovely sentence. The prognosis isn't great. 

Every hour of work only you can do is an hour you can never raise the price on, never hand off, and never stop doing. Indispensability doesn't feel like a trap because it arrives dressed as appreciation. But look at what it does: caps your rate, fills your calendar with your oldest and cheapest work, makes the organization fragile, and — the part people miss — makes you impossible to refer, because you have no room. 

The consultants and Chiefs of Staff with the longest, best-paid tenures are almost always the ones most visibly willing to leave. Not because they're bluffing. Because being ready to go is what lets you do the hardest part of the job: telling the truth to someone who could end the arrangement. 

Three artifacts, built as you go 

Every recurring thing you own should have an owner-in-waiting and a document. If it has neither, that's not a responsibility. That's a hostage. 

1. The decision log. Not what happened — why. "We went this direction in March because the board wanted country-level visibility before the raise." Two sentences. Six months later someone will propose reversing it, nobody will remember the reason, and three weeks will disappear re-litigating it. Four minutes a week.

2. The operating doc. What meetings exist, who's in them, what each is for, what gets decided where. Most organizations have never written this down, and writing it is itself a diagnostic — you'll find two meetings doing the same job and one decision with no home. 

3. The relationship map. Who to call for what, and how to ask. "Finance says no to anything arriving after the 15th — ask before." "Legal is fast with a draft, slow with a question." Nobody writes this one. Everybody needs it. Your successor will think you're a genius, and your successor talks to people. 

Leaving well is business development 

Every consultant has a client they drifted away from. Final invoice, a couple of unanswered messages, a slow fade. That client will never refer you — not out of anger, but because there's no clean story to tell about you. Endings are what people remember and what they retell. 

So end on purpose. A closing session walking the team through the three artifacts. An honest list of what you didn't get to. A short note to the principal on what to watch for over the next two quarters. A named handoff to a specific human being, in a meeting, with everyone present. 

Six hours. Highest-ROI six hours of the engagement, and almost nobody spends them. 

Chiefs of Staff: same test, pointed inward. If your principal can't run their own staff meeting without you, that isn't job security. It's a ceiling you spent two years building. The goal was always to make them effective when you're not in the room — which is, conveniently, the exact skill that gets you the operating role you want next. 

The thread through all five 

Diagnose the real problem. Move without authority. Define the relationship, then price it. Land before you swing. Build the thing that runs without you. 

None of those five require anyone to report to you. All five are harder than having people report to you. Which is why the work pays what it pays. 

One thing to try this week: List everything only you can do. Pick the most boring one. Find its next owner by Friday. 

That's the first five. If any of it was useful, forward it to the one person you know doing this job without a title for it. 

— Michael J Washington, Ocean Stride Advisory

Issue 005
Issue 005