Home > Sectors > Professional Knowledge > Scaling Technology Companies Without Losing Focus

Scaling Technology Companies Without Losing Focus

Watch the short film

Play Video
Scaling technology companies without losing focus: how the shared context of a small founding team fades as the company grows.

What it means in practice

A small founding team typically operates with near-total shared context — everyone in the room knows what the product is trying to do, why, and for whom, because that understanding was built together, in real time, through the company’s earliest and most formative decisions. As the company scales, this shared context does not automatically travel with new hires. Each new person joins with a slightly less complete version of the original “why,” absorbed secondhand from documentation, onboarding conversations, or simply observing what the team currently does rather than understanding the reasoning that produced it. Individually, none of these gaps are large. Collectively, across dozens of new hires, the company’s sense of its own focus becomes a composite of increasingly diluted versions of the original, rather than the sharp, shared understanding it started with.

Donald Sull, Rebecca Homkes and Charles Sull’s research on strategy execution offers a directly relevant complementary finding: across more than 250 companies, only 9% of managers believed they could reliably rely on colleagues in other functions and units, and the central execution problem their research identified was horizontal coordination — not, notably, the quality or clarity of the original strategy. A technology company’s loss of focus during scaling is rarely a failure of the founders’ original vision; the vision itself typically remains sound and is usually still stated clearly in company materials. What breaks down is the coordination needed to keep that vision consistently translated into decisions across a rapidly multiplying set of teams, each interpreting the same stated priorities slightly differently as shared context thins.

Why it happens

Jay Galbraith’s research on organisation design describes this as a natural consequence of rising information-processing demand: a growing organisation has more decisions to make, more people needing context to make them well, and informal, proximity-based coordination — the kind a small founding team relies on without even noticing it is a mechanism — simply cannot carry the same volume of shared understanding once the group has grown past a certain size. Unless a company deliberately builds an explicit way of carrying and refreshing its sense of focus, the informal mechanism erodes quietly, and focus fragments not through any bad decision but through the simple mathematics of more people holding less complete context each.

Where this varies

The erosion is sharper in companies growing primarily through hiring rather than through acquiring already-aligned smaller teams, since hires joining individually absorb context one relationship at a time, while acquired teams at least arrive with a coherent internal understanding of their own, even if it differs from the parent company’s. It is also sharper in companies expanding into multiple product lines simultaneously, since each new line adds its own version of “why,” multiplying the number of distinct contexts a growing organisation needs to hold coherently at once.

It is worth noting that this fragmentation is largely invisible in the metrics a growing technology company typically tracks. Revenue, headcount, and product velocity can all look healthy while the organisation’s shared sense of why it is doing what it is doing quietly thins out across an increasing number of people, which is part of why the erosion tends to be recognised only in hindsight, once a genuinely costly misalignment has already occurred.

A recognisable early symptom is two teams independently building solutions to the same underlying problem, each unaware of the other’s work, because neither had a clear enough shared picture of the company’s actual priorities to recognise the overlap in advance. Neither team is at fault; both are behaving reasonably given the incomplete, secondhand version of company context each happens to hold.

Where this shows up

People working in technology companies will probably recognise this pattern first. The wider Professional and Knowledge-Based grouping and the other sectors page show how it presents elsewhere.

Questions worth considering

  1. How much of this company’s original sense of focus is currently held by people who were present when it was first established, versus people who absorbed it secondhand?
  2. If the founding team were unavailable for a month, would the company’s current priorities look the same as they do today?
  3. What deliberate mechanism, if any, currently refreshes shared understanding of the company’s focus as new people join?

Your team is facing similar challenges?

We Became a Different Company Without Deciding To — without losing focus
The Riddle Ledger, a brand of Zoom Riddle

Subscribe to The Riddle Ledger

Perspectives are sent as they are published, with no promotional email, and you can unsubscribe at any time.

Sources

Jay R. Galbraith, “Organization Design: An Information Processing View,” Interfaces, 4(3), 1974, pp. 28–36.

Donald Sull, Rebecca Homkes and Charles Sull, “Why Strategy Execution Unravels — and What to Do About It,” Harvard Business Review, Vol. 93, No. 3 (March 2015), pp. 57–66.

You need a PDF version for a meeting?

Frequently Asked Questions

Some dilution of shared context is a structural consequence of growth, but the pace and severity of it varies considerably depending on how deliberately a company works to carry that context forward.
Documentation helps transfer explicit information, but the original founding team’s shared understanding often includes a great deal of context that was never fully explicit even to them, which documentation alone cannot fully capture.
Because technology companies frequently add headcount and complexity at a pace that outstrips the rate at which informal coordination and shared understanding can naturally travel to new people.
Usually not — the vision itself typically remains sound and clearly stated; what breaks down is the cross-team coordination needed to keep it consistently translated into everyday decisions as the company scales.
A small founding team builds its understanding of what the product is for together, in real time. New hires tend to absorb a slightly thinner version second-hand, from documentation, onboarding or observing what the team currently does. The page suggests the gaps are small individually but, across dozens of hires, leave a composite of increasingly diluted versions of the original.
The page cites their research across more than 250 companies, in which only 9% of managers believed they could reliably rely on colleagues in other functions and units. The central execution problem they identified was horizontal coordination rather than the quality or clarity of the original strategy.
The page notes that the fragmentation is largely invisible in metrics a growing technology company typically tracks. Revenue, headcount and product velocity can all look healthy while shared understanding of why the company does what it does thins out. It tends to be recognised in hindsight, after a costly misalignment has already occurred.
One recognisable symptom on the page is two teams independently building solutions to the same underlying problem, each unaware of the other’s work. Neither team is described as at fault. Both behave reasonably given the incomplete, second-hand version of company context each holds.