Learning scale at Delivery Hero

Scale makes the invisible visible

At a small company, a strong engineer can carry a surprising amount of operational context in their head. The arrangement feels fast because coordination is informal. At greater scale, the same habit becomes a source of fragility.

Scale exposes every ambiguous boundary: who owns a service, which failure matters first, how a decision is recorded, and what another team can safely assume. More process is not automatically the answer. The useful work is designing interfaces between people as carefully as interfaces between systems.

The shift for me was from solving the problem in front of us to improving the conditions under which many teams could solve related problems without waiting for the same few people.

Local knowledge is a system input

Global organisations benefit from common platforms, but markets remain stubbornly specific. Payment habits, merchant operations, geography and customer expectations do not become uniform because the organisation chart does.

The tension is often described as central versus local. That framing encourages a political contest. A better framing is to ask which decisions gain from shared infrastructure and which require direct market knowledge. The answer can differ for each layer of the product.

Standardisation works when it removes repeated undifferentiated work. It fails when it erases the information that made the local product useful.

Leadership becomes environmental

In a small team, leadership can look like making the decisive call. In a large one, the higher-leverage work is often environmental: making priorities legible, improving the quality of decisions and reducing the cost of collaboration.

Large companies and startups see different failure modes. Working inside both made it easier to recognise when speed was real and when it was merely borrowed from missing safeguards.