Why a process that lives in one team’s heads does not survive the second site.
A receiving team that has worked together for years develops an unspoken way of doing things: how a damaged carton is flagged, how a short shipment is recorded, when a supervisor is pulled in. It works because everyone shares the same memory. Move that same volume to a new distribution warehouse staffed by new people, and the memory does not travel with it.
What scales is not the team. It is the part of the team’s knowledge that has been made explicit.
Variability is the natural state of a growing operation. The moment a second facility opens, the same task starts being performed two slightly different ways, and the gap widens with every site added. A home and lifestyle line packed to one standard in Asia-Pacific and a looser one in the Americas does not announce the divergence; it surfaces later as a return rate that is quietly higher in one region than the other.
The point of a standard is not uniformity for its own sake. It is that a customer ordering the same product into two markets should not be able to tell which facility fulfilled it. Holding that line across 18 distribution warehouses means the standard has to be specific enough to act on and stable enough to train against — not a slogan, but a checklist that a new hire on their first week can follow and a supervisor can audit.
FMC aligns these procedures with ISO standards so the reference point is external and fixed, rather than re-litigated at each site by whoever happens to run it.
Consistency is also what lets a network absorb a shock without improvising. When a supplier slips or a route closes, a facility running a defined process can reroute volume to another that runs the same one, because the receiving end already knows how the goods are labelled, staged, and recorded. Without that, every contingency is a fresh negotiation between sites that do things differently.
Growth tends to get credited to ambition. More often it is the dividend of having decided, once and in writing, how the ordinary work is done — and then refusing to let each new site reinvent it.
Scale rewards the boring decisions made early: what to standardise, and what to write down.