Scale Changes the Problem
What would break if this worked ten times better?
The idea
Approaches that work at one size often fail at ten times that size, because the constraint moves.
In the real world
Personal service to every customer stops being possible past a few hundred.
Going deeper
Systems have operating ranges. An approach that works at one volume usually fails at ten times that volume not because it degrades gradually, but because the binding constraint moves somewhere else entirely.
Founder-led onboarding is the clearest example: it is often genuinely the best thing about a young company, and it is bounded by one person's hours. Nothing about it degrades as you grow — it simply stops being available, and the differentiator becomes the ceiling. The useful exercise is to ask what breaks first at ten times, then to notice that the answer is frequently the thing currently working best.
Where it stops applying
Prematurely engineering for scale you do not have is the more common error and kills more companies than hitting a ceiling does. Knowing where the ceiling is matters more than removing it early.
Why it matters
It warns you that the thing currently working is not automatically the thing to do more of.
Try this today
Ask what would break first if your volume multiplied by ten tomorrow.
Test yourself
A founder personally onboards every customer, and it is the company's strongest differentiator. What happens at ten times the volume?
Show the answer
The differentiator becomes the constraint. It cannot be multiplied without either the founder's time or a different mechanism that reproduces the effect, and the strength turns into the ceiling on growth.
Learn this in the feed Answering from memory, then again days later, is what makes it stick.