Scaling, replicating, and the difference nobody makes you state
Am I trying to scale an organization or replicate an idea, and do I know the difference?
Question 11 of the Index
You have a plan with numbers in it, and the numbers are probably fine. What the plan does not say, because nobody made you say it, is which of two quite different projects you are running. The word growth covers both, which is how a plan can look finished and still point at nothing in particular.
Scaling an organization means the thing that gets bigger is the entity: more staff, more budget, more sites reporting to a centre that holds the standard. Replicating an idea means the thing that gets bigger is the practice, and the entity may stay small on purpose, because what travels is a method other people run under their own name and their own funding. Both are legitimate. Neither is a version of the other, and they fail in opposite directions.
It matters early because the two ask opposite things of you. Scaling rewards control: one quality bar, one name, hiring that protects the standard. Replicating rewards giving the thing away: documentation, a name other people are allowed to use, and tolerance for versions you would not have built. Organizations that mean to replicate but manage as though they were scaling end up with a franchise nobody asked for, and the founders are usually the last to see it, because from the inside it feels like caring about quality.
There is a quick way to find out which one you are actually running. Picture the practice spreading widely and well under other people’s names, with your organization staying exactly the size it is now. If that reads as success, you are replicating. If it reads as loss, you are scaling, and the honest version of the plan says so out loud, to your board, in those words.
Bring the plan and the discomfort. The question is not which one is better. It is which one you are already doing.
No account, no card, one exchange. Yours to keep.