A technology company can move from a handful of founders to several hundred people in a few years, and the organisation has to be redesigned while the product is still being built. Decisions that once happened in a single conversation now cross functions that each see the company differently. This page collects the Perspectives on how growing technology companies experience focus, strategy execution and performance, and why the pace of growth changes the problem.
Technology company growth challenges: why growing technology companies outgrow their processes faster, and where priorities drift as headcount rises.
Larry Greiner’s research on organisational growth describes companies passing through distinct stages, each ending in a crisis that the previous way of organising cannot resolve. In more traditional industries those transitions often unfolded over a decade or more. In technology, the same transitions can be compressed into a few years, sometimes less, leaving little time to build the coordination mechanisms a slower-growing organisation develops almost without noticing.
The result is a company that is successful by most visible measures and under strain internally. A founding team that once shared context by default is now several functions — product, engineering, sales, customer success — each with its own priorities and its own read of what the company should do next. Decision rights that were never written down are now being exercised by people who joined last quarter.
Four places where the organisational pattern is often first noticed in technology companies. They describe what tends to happen, not a list of faults.
Product, engineering and sales each hold a legitimate view, and nothing resolves the disagreement between them.
Two accounts of what matters are maintained by different teams, and the gap between them grows without anyone choosing it.
What worked because everyone sat together no longer works at scale, and nothing has yet replaced it.
The founding team remains the bottleneck for choices that others could make if the decision rights were clear.
Four pressure points where growth outruns the processes built for the last stage.
A small founding team typically operates with near-total shared context.
In a technology company the product roadmap and the business plan are two descriptions of the…
In an early-stage technology company, performance is often judged by output that everyone can…
The skills that build a company from nothing are not always the skills that run it at several…
Open any heading to read the full discussion.
A small founding team typically operates with near-total shared context. Everyone knows what the company is trying to do, who decides and why. As the company grows, that context does not scale automatically; it has to be created deliberately, and the founders are often the last to notice it has thinned.
Focus is the early casualty. Opportunities multiply faster than the capacity to pursue them, every new function has a case for its own priority, and saying no becomes a decision that nobody in particular owns. The Perspectives look at how growing technology companies experience this, and why more effort is rarely the answer to a question of focus.
In a technology company the product roadmap and the business plan are two descriptions of the same intent, written by different people. At small scale they are reconciled in conversation. At larger scale they are maintained by different functions with different pressures — customer commitments, technical constraints, revenue targets — and they can drift apart without anyone deciding that they should.
When they do, the organisation sends mixed signals. Engineering optimises for one definition of what matters, sales for another, and the people in between spend a growing share of their time translating. The pattern is usually invisible in any single decision and obvious in the accumulation of them.
In an early-stage technology company, performance is often judged by output that everyone can see: a feature shipped, a deal closed, an incident resolved. That works while the team is small and the work is shared. As roles specialise and the company adds layers, it becomes harder to tell what good looks like for any individual, or how one person’s result relates to another’s.
Performance management in this setting has to adapt to work that changes quickly and is often interdependent. Measures designed for one stage can quietly reward the wrong behaviour in the next, which is why the articles treat performance as an organisational question as much as an individual one.
The skills that build a company from nothing are not always the skills that run it at several hundred people, and Greiner’s research suggests that the nature of the leadership challenge changes at each stage. Founders who once made every important decision find that the volume exceeds what they can handle, and that the decisions they still make are the ones nobody else was sure they could take.
Moving beyond the founding team means distributing decisions, clarifying who owns what, and trusting people who were not there at the start. None of that is automatic. The Perspectives describe the tensions it creates for founders and for the people who join them.
These are the questions the Perspectives keep returning to. They are offered as a way of looking at the organisation, not as a checklist.
Reflections from real work on organisations growing beyond their founding design.
GROWTH EXPOSES DESIGN
Building commercial infrastructure for an industrial manufacturer preparing for expansion shows that growth does…
READINESS UNDER UNCERTAINTY
Working with a specialist data-recovery and cyber-incident response business shows what marketing looks like when…
THE SYSTEM SHOULD OUTLIVE THE FOUNDER
Preparing a fast-growing property network for franchising shows that a business can outgrow its founder’s…
Evidence-led reading for technology companies.
Software, platform, IT services and other technology businesses, among others. The page is organised by how the organisation grows — fast, across functions that each see the company differently — rather than by technology.
Because headcount, functions and customers can grow within a few years what other industries add over a decade. Information-processing demand rises almost as fast as headcount, leaving little time to build shared systems, decision rights and formal communication.
No. It is most visible during rapid growth, but it can recur at each stage, including in established companies that add products, markets or acquisitions.
Founders usually shape the early organisation without designing it. As the company grows, the decisions that route through them can become a constraint. The articles describe the tension without prescribing a response.
No. Scenarios are invented composites. They describe no actual organisation and are not accounts of client work.
The articles on scaling without losing focus and on strategy execution during rapid growth are a good starting point. Each article stands alone.
Illustrative scenarios on this site are invented composites. They describe no actual organisation and are not accounts of client work.
Related: Professional Services · Recruitment · Professional & Knowledge-Based Organisations · Other Sectors · Markets: London · Zurich · Dubai · Singapore
Services can be delivered remotely, and we accept requests from organisations wherever they are located.
