What Growth Erodes Isn't Direction. It's Proximity.

Direction doesn't disappear on day one. It starts drifting at the first new layer.

In a ten-person company, nobody talks about direction, because nobody has to. The founder turns down the same kind of deal in front of everyone, fires the same kind of client in front of everyone, delays the same kind of project in front of everyone. Direction isn't a sentence there. It's a habit, watched in real time by everyone close enough to see it.

A layer arrives before a conversation does

Growth changes this picture in a headcount list before it changes it in a strategy deck. A layer of managers appears between the founder and the work; a team forms that the founder no longer sits in on; a second office opens, then a second country. The founder's intent usually survives intact. What changes is how many people it now has to pass through before it becomes someone else's decision.

Direction doesn't get lost. The distance between it and the decision gets longer, and every added person carries a little less of it forward. That is not the same claim as saying the sentence written on an offsite whiteboard was wrong. The sentence can still be exactly right. What shrinks is how far it reaches.

This tends to move without anyone noticing it day to day. The founder still decides on the same principles; the team still repeats the founder's sentences. What's changed is only how many hands that sentence passed through before reaching today's decision-maker — and no report tracks that number, because the numbers that get tracked are revenue, growth, and headcount, not distance.

This is a different problem from the question behind setting direction: there, the question was aimed at the wrong person. Here, reaching the right person is what keeps getting harder.

Every layer moves direction one generation further from its source.

A manager hired eighteen months into a company's life rarely hears the direction from the founder directly. She hears it from someone who heard it from someone else. Three layers down, what's left isn't the original sentence but a summary passed through memory more than once — not wrong, just thinner, and the thinning doesn't show because it's still delivered in roughly the same words.

A photocopy of a photocopy

A photocopy of a photocopy looks fine at first glance — the letters still read, the page is still a page. The degradation doesn't show in any single copy; it accumulates as the chain lengthens. Direction works the same way: what's lost at one layer is too small to notice, but five layers on, the surviving sentence has drifted from what the founder meant in ways nobody can point to.

What's actually lost isn't the direction itself — it's the proximity of having heard it firsthand. That proximity isn't earned by repeating the sentence. It's earned by having been in the room when the sentence was first said, and in a growing company, fewer people are in that room every year.

A salesperson turning down a deal today may never have heard why the founder turned down something similar three years ago. What's left in her hand is a rule — 'we don't take deals like that' — with the reasoning gone. The rule is true; the reasoning is missing, and a rule with no reasoning is the first thing to bend under real pressure.

The gap shows up most sharply in a conflict: two managers, two layers down, reach opposite decisions on the same question, each entirely faithful to what their own layer taught them. The meeting that follows argues about who's right. The real question is why the two of them carry such different sentences from the same source — and that isn't a competence problem in either manager. It's a sign the chain already broke somewhere upstream.

This is one step past vision spreads through translators, not talk: that piece was about direction never being repeated enough. This one is about repetition itself losing something with every pass.

Three ways to tell whether direction still reaches the edge.

Checking whether direction is still running on its original source doesn't require asking for a new strategy deck. The deck will always come back looking right, because the founder — or whoever sits closest to the founder — is usually the one who wrote it. That's not where the real question lives.

Three questions, asked two or three layers down

Instead, it helps to ask someone two or three layers removed from the founder about one ordinary decision they made last week:

• Why did you decide it that way? If the answer is the founder's own sentence, direction is still reaching that far. If the answer is 'that's just how we do things here,' it isn't.
• Who did you learn that from? Count how many people stand between that answer and the founder — that's the actual distance direction has to travel.
• What would you have done differently? No answer usually means the rule has been memorized, and the reasoning behind it is already gone.

These three questions don't measure direction — they show which layer it turned into a copy of a copy. The point where that happens is almost always earlier than anyone expects, because the first loss is always the quietest one.

None of these three questions is a test, and none is meant to catch anyone out. A manager who gets defensive usually isn't hiding the answer — the question just feels like a verdict on her rather than on the chain that fed her. The weak link is rarely the most capable manager in the company. It's usually the one furthest from the founder, and talent doesn't close that distance; it only delays anyone noticing it.

Reconnecting is a threshold problem, not a calendar one.

Most companies tie re-stating direction to a calendar: a quarterly kickoff, an annual offsite. The calendar is the wrong measure, because drift doesn't move with time — it moves with layers. A company that adds no new layer for six months hasn't drifted at all; one that adds two layers in a month has drifted before six weeks are out.

The right moment shows up on the org chart, not the calendar

The right moment to reconnect is a threshold: a new management layer opening, a meeting existing that the founder doesn't sit in on, a team hired in a second city. Each stretches the chain by one more link, and every stretched chain asks, almost immediately, to be shortened again.

Reconnecting isn't repeating the sentence. It's letting the person at that layer live the moment the sentence was first said, one more time. That happens less through a company-wide meeting and more through an hour alone with the founder, with no agenda beyond that.

A company that skips this threshold doesn't lose direction all at once — it quietly splits in two. The upper layer keeps telling the original sentence; the lower layer keeps working from its own summary of it. The two versions usually only meet in a crisis, where two decisions collide head-on — and until then, both sides are certain they're right, each faithful to the sentence it was actually given.

This is the overlooked half of delegation is a sequence, not a moment: what gets handed down there is the decision. What gets handed down here is the reasoning behind it — and without it, all that's left is the rule.

From the room

Working with growing companies, most founders who arrive describing a lost sense of direction are still saying the right sentence. The problem was never in the sentence — it's in how many people it passes through before reaching the farthest edge of the team.

Saying it again isn't enough. Someone has to live it again.

Our own work here isn't handing a founder a better sentence to write. It's showing which layer the copy started to degrade, and putting the founder back in the same room as the person at that layer. A single hour there usually does more than months of strategic-clarity work — because what was missing was never information. It was proximity.

One more observation: the founders who lose this proximity fastest are the ones who feel busiest. Busyness is a natural result of growth. But the first thing a busy founder gives up is usually time with the farthest layer — exactly where direction goes missing first.

The founders who notice this tend to change the same thing on their calendar: not another meeting, but the time actually spent with the farthest layer. An hour not spent there costs more, months later, than the procedure someone eventually has to rewrite because of it — and that cost is almost always noticed too late to be cheap.

How we work treats noticing these thresholds early as part of the job — before the strategy document ever needs rewriting.