THE BLOG

Everybody Comes to You and Nothing Moves Without You

the 13 commitments Oct 23, 2026
A narrow, shadowed hallway seen head-on with a single open doorway at the end spilling warm light into it.

It takes you nine seconds to answer.

Someone leans in the doorway with the question, and you already have it — the number, the name, the reason it got decided that way back in March. Nine seconds, and they're gone satisfied, and you're back in what you were doing with a small warm feeling you don't stop to examine.

You have answered that question, or one shaped exactly like it, probably forty times. Different people, same nine seconds. And it has never once landed on you as a problem, because from the inside, being asked feels identical to being valuable.

What that actually is

There's a counterfeit of Always Influence, and it isn't the person nobody asks. You get asked constantly. Your phone is the evidence. Somebody needed you before lunch and somebody else will need you before five.

The counterfeit is being the bottleneck and reading it as being the leader.

Influence and indispensability produce the exact same day. Full, interrupted, consulted, needed. They also produce opposite results, and the difference doesn't show up for about a year. Influence puts something into a person that's still there after you leave the room. Indispensability requires that you don't leave the room.

The tell is uncomfortable and it takes about four seconds to run. What happens where you are not? If the honest answer is that things wait — the decision sits, the work idles, the group circles until you surface — then whatever you have there, it isn't influence. It's traffic. You are not the leader of that room. You are the intersection it drives through.

And the intersection version has a cost the leader version doesn't. Every question routed to you is a question somebody didn't develop the capacity to answer. Forty repetitions of nine seconds each is not just six minutes of your life. It's forty chances to build somebody, spent instead on being needed.

Why the usual fix doesn't take

You know the standard answer. Delegate. Document it. Write the process down so people stop asking.

You've probably even started. There's a half-finished doc somewhere. And it stalled for a reason that has nothing to do with follow-through.

Answering is faster. Every single time, in the moment, it is cheaper to say the thing than to teach the thing — nine seconds against twenty minutes, and the twenty minutes has to come from a day that's already full because of all the nine-secondses. You are not undisciplined. You are optimizing correctly for today and disastrously for the year. Every rational choice you make makes the bottleneck tighter.

There's a second reason, and it's the one worth saying plainly: being needed feels good. Not in a way you'd defend out loud, but in a way that quietly makes you slow to fix this. Any system you build to spread the load will die in three weeks if you haven't admitted that part first.

There's an old scene about this. Moses is sitting from morning until evening judging disputes for an entire nation, one at a time, because he's the one who can. His father-in-law watches for a day and says: "What you are doing is not good. You and these people who come to you will only wear yourselves out, for the work is too heavy for you" (Exodus 18:17–18).

Notice what isn't in that sentence. No accusation. Moses isn't lazy, isn't proud, isn't doing bad work — he's doing the right work in a shape that can only be as large as one man. The correction isn't care less. It's stop being the only door. Appoint people. Give them the small cases. Keep the ones that actually require you, which turns out to be a much shorter list than the day suggested.

This is where the two halves separate.

Always is the measurement, and it doesn't flex: you judge your influence by what holds up when you're absent, not by how often you're needed while you're present. That standard is the same at a desk, on a crew, in a house, with a title or without one.

Style is how the transfer actually happens, and it's not one method. Some people hand it over by explaining — the reasoning out loud, the whole map. Some can't explain anything and transfer everything by working next to somebody for a week. Some write it down once and it holds. Some have to let a person do it badly, watch it not go well, and talk about it afterward. Handing a quiet builder the write-a-playbook method gets you a document nobody reads and a man who concludes he's bad at developing people. He isn't. He was handed the wrong instrument.

The practice

Answer the next one with a question. The next time someone brings you the forty-times question, don't give the nine-second answer. Ask what they'd do. Then let the silence sit, because the silence is where the capacity gets built. If you're wired to move fast: the question costs you ninety seconds, not twenty minutes — you can afford ninety seconds. If you're wired to soften things: resist the urge to rescue them halfway through their answer. Let them finish it wrong, then adjust.

Name the person who should be the answer instead of you. Pick one recurring question and one person who could own it, tell that person, then tell everyone else where to go with it. Out loud, in front of people, so the redirect is public and doesn't quietly revert. If you're wired for structure: put it in writing where the team already looks. If you're wired relational: say it in the room, then back them the first time somebody tries to go around them to you.

Let one thing be done at eighty percent. The reason it all comes back to you is that you keep taking it back when it isn't done your way. Choose one thing this week where eighty percent is genuinely fine and leave it at eighty. If you're wired for craft: pick something with no customer on the other end, so the standard you're relaxing isn't one that matters. If you're wired to avoid conflict: say up front that you're not going to touch it, so you can't quietly redo it at nine p.m.

Write down the one question you've answered forty times. Not a manual. One page, or six bullets, or a two-minute voice memo — whatever you'll actually finish this week. The goal isn't documentation. It's proving to yourself that a thing you thought only lived in your head can live somewhere else. If you're wired to over-build: set a timer for fifteen minutes and ship whatever exists when it goes off. If you're wired to never start: record it as a voice note while you drive and hand it to one person.

The close

Being needed all day is not the same as having built anything, and you'll only find out which one you have on the day you're not there.

Always Show Up As You.

SUBSCRIBE FOR WEEKLY LIFE LESSONS

Practical, faith-grounded lessons on building a life that holds up under pressure. One email a week, short enough to read before your coffee cools.

We hate SPAM. We will never sell your information, for any reason.