The Context They Need Lives Entirely in Your Head
"Should we prioritise the Henderson order or the Bright & Sons one?"
Your ops manager is asking. She's competent. She's been with you two years. She handles a dozen decisions a day without checking in.
But this one landed in your inbox.
You answer in three seconds: Henderson. And you move on.
Here's what you didn't say out loud: Henderson is a new account with expansion potential. They're testing you. Bright & Sons has been with you eight years and will wait two extra days without blinking. You know the gross margin on each account, you know who's price-sensitive and who values reliability, you know that Bright & Sons gave you grace when you messed up a shipment in 2021.
Your ops manager knows none of this. So she asked.
The question wasn't hard. The answer took three seconds. But multiply that by the twelve similar questions she didn't ask this week — because she guessed, or she went with her gut, or she just picked one and hoped.
Some of those guesses were right. Some weren't. You'll never know which, because nothing broke badly enough to surface.
This is the invisible cost of context that lives in your head: not just the interruptions you do get, but the suboptimal decisions made in the gaps where people didn't want to bother you.
Most founders, when they notice this pattern, try to fix it by being more available. Open door policy. Slack DMs. "Just ask me."
This is backwards.
The more available you make yourself, the more you train the team to route through you. You become faster to reach than the knowledge itself. You become a search engine that never crashes and always has the answer.
The real fix is getting the context out of your head and into a place they can access without you.
This is different from an SOP.
An SOP tells someone how to do something. Step one, step two, step three. That's necessary, but it's not the problem here.
The problem is they don't know why one choice matters more than another. They don't have the strategic context, the relationship history, the priorities that sit behind the process.
Henderson vs Bright & Sons isn't a process question. It's a judgment call. And judgment calls require context.
Here's what actually works:
Start a running document — call it Context, or Priorities, or How We Think About Things. Doesn't matter. The format isn't the point.
Every time someone asks you a question that you answer in three seconds, ask yourself: what did I know that they didn't?
Write that down. Not the answer. The context behind the answer.
"Henderson is a new account we're trying to land properly. Treat their first three orders as auditions. Prioritise them over established accounts unless something is genuinely urgent."
That's three sentences. Takes ninety seconds to write. Now your ops manager doesn't need to ask next time. She's got the framework.
Do this for a month and you'll notice patterns.
A handful of contextual frames cover eighty percent of the judgment calls. Which accounts matter and why. How you think about trade-offs between speed and cost. What "urgent" actually means versus what it feels like. Who has authority to make exceptions and when.
This isn't about writing a manual. It's about transferring the mental models that let you make fast decisions, so other people can make them too.
The resistance I hear most often: "But it changes. Priorities shift. I can't write it all down because next month it'll be different."
Fair. But that's not an argument against writing it down — it's an argument for keeping it updated.
A living document that's 80% current is infinitely more useful than context that's 100% accurate but locked inside your skull.
There's a simpler test for whether this is a problem worth solving: look at your calendar and your inbox for the last two weeks. Count the questions that weren't really about process — they were asking you to make a judgment call because the person didn't have enough context to make it themselves.
If that number is north of ten, the context hasn't been externalised. You're still the oracle.
And oracles don't get to take holidays.
If this sounds like something worth untangling, that's the kind of work we do. Not writing your SOPs for you — figuring out what's actually keeping you in the loop, and building the structure that lets you step out.