Large organisations are impressive machines. They coordinate thousands of people across continents, keep regulators satisfied, and deliver the same product a million times. The practices that make this possible, the approval chains, the tooling standards, the change processes, the layered reporting, are genuine achievements. They are also specific solutions to a specific problem: how do you keep a very large number of people from working against each other?
The trouble starts when those practices travel. A growing business hires someone from a large company, or reads what large companies do, and adopts the machinery without the problem it solves. A team of thirty acquires an approval process designed for three thousand. It gains none of the coordination benefit, because thirty people can coordinate by talking, and all of the cost.
Three imports that hurt
The platform before the need. Large organisations standardise on platforms because a thousand teams using a thousand tools is chaos. A small business that buys the enterprise platform gets a system built for someone else’s complexity, configured by consultants, and used at a fraction of its capacity. The licence is the small part of the cost. The large part is bending every process to fit a tool designed for a different company.
The approval chain. In a large organisation, approvals exist because the person deciding cannot know the whole picture. In a small one, they usually can. An approval chain in a business of thirty mostly adds waiting: work stops until someone who already agrees signs to say so.
The reporting layer. Enterprises need dashboards because nobody can see the operation directly. A small business can, if its records are in one place. Building a reporting layer on top of scattered tools produces a slow, partial copy of what the owner could have seen by looking at the system itself.
A small business does not need to know what it is doing at a distance. It needs to be able to see it up close.
What the machine gets right, and how to take only that
None of this means large organisations have nothing to teach. Some of what they do is worth importing, stripped of its scale:
| Enterprise practice | The idea worth keeping | The scale to leave behind |
|---|---|---|
| Single source of truth | One record per customer, per job, per invoice | The data warehouse and the team that runs it |
| Defined processes | Named transitions with a clear owner | The change board that approves every edit |
| Security discipline | Access control, backups, least privilege | The compliance department |
| Measured operations | A few numbers read straight from the system | The dashboard programme |
The pattern is the same in each row. The principle is sound. The apparatus around it exists because of size. Take the principle, build it into a small system, and skip the apparatus.
Where small scale is an advantage
A business of thirty can do things the big machine cannot. It can change a process in an afternoon. It can build a system around exactly how it works, because there is only one way it works. It can put judgment where the information is, instead of routing information to where the judgment sits. It can automate the handoffs the enterprise still does with tickets, because there are five of them rather than five hundred.
That advantage is thrown away by importing the enterprise’s coordination machinery. It is kept by building an operation that fits the business it is in: specific, connected, owned, and small enough to see whole.
The irony is that large organisations spend enormous sums trying to recover exactly this. The internal start-up, the autonomous team, the “two-pizza” unit: each is an attempt to recreate, inside the machine, the directness a business of thirty has for free. A small business that adopts the machine’s habits gives away the thing the machine is trying to buy back.
The test
Before adopting any practice from a large organisation, ask what problem it solved there, and whether that problem exists here. If it solved coordination among thousands, and there are thirty, the honest answer is that it will not solve anything. It will only make thirty people work like a much larger and slower company, without any of the reasons a larger company has for being slow.