Uber’s 2017 collapse into public scandal is usually told as a culture story. A toxic workplace, a founder who tolerated harassment, a leadership team that rewarded aggression and looked away from misconduct. All of that is true.
But it is an incomplete diagnosis. What the culture expressed, the architecture permitted. And what the architecture permitted, it eventually required.
The underlying condition at Uber was structural: a company that scaled from a few hundred to tens of thousands of employees across dozens of countries in less than a decade, without building the governance, accountability systems, or organizational design capable of managing that scale. The cultural failures were real. They were also symptoms. Growth does not create culture problems. Growth reveals architectural ones.
That distinction matters for every founder who is growing a company right now.
Greiner’s growth model and the crisis Uber could not outrun
Larry Greiner’s 1972 model of organizational growth describes a recurring dynamic: each phase of growth eventually produces a crisis that the existing structure cannot resolve. The crisis is not a failure of will or talent. It is a structural mismatch between the demands placed on the organization and the architecture available to meet them.
Greiner identifies a crisis of control as one of the most common inflection points in rapidly growing organizations. At small scale, founders and early leadership can coordinate through direct supervision and informal communication. As headcount, geographic distribution, and operational complexity grow, informal coordination degrades. Decisions that once moved quickly through a small team begin requiring navigation through ambiguous authority, competing priorities, and organizational layers that were never formally designed.
Uber hit every dimension of that crisis simultaneously. Between 2014 and 2017, the company expanded into more than 70 countries, grew from approximately 1,000 to over 14,000 employees, and was managing regulatory battles, driver relationships, competitive pressures, and product development across markets with radically different legal and operational contexts. The architecture did not grow with the company. Governance structures were informal. Accountability for outcomes was diffuse. HR systems were inadequate for the scale they were serving. The crisis was not an accident. It was a structural inevitability.
Mintzberg on coordination and what happens when it fails
Henry Mintzberg’s work on organizational structure distinguishes between coordination mechanisms: direct supervision, standardization of work processes, standardization of outputs, standardization of skills, and mutual adjustment. At small scale, founders coordinate through visibility and direct involvement. At scale, organizations require systems that coordinate behavior even when leadership is absent. When those systems are not built, the coordination function does not disappear — it degrades into ambiguity, escalation, and inconsistency.
In mature, well-designed organizations, these mechanisms overlap and reinforce one another. In rapidly scaling organizations, the informal mechanisms that worked at small scale — primarily direct supervision and mutual adjustment — degrade before formal standardization has been built to replace them.
At Uber, the coordination failure was visible across every organizational layer. Managers operated with significant autonomy because centralized process standardization had not been established. HR escalation paths were unclear or inconsistently followed because the systems for standardizing those processes had not kept pace with headcount growth. Leaders in different regions made consequential decisions with little coordination because the governance architecture for cross-functional, cross-regional accountability had not been designed.
The result was an organization that looked unified from the outside — one brand, one app, one market position — but was operationally fragmented at every level below the founding team. That fragmentation is not a cultural phenomenon. It is what Mintzberg’s model predicts when coordination mechanisms fail to develop in proportion to organizational scale.
The founder’s dilemma and the cost of maintaining control
Noam Wasserman’s research on founder transitions, developed in The Founder’s Dilemmas (2012), identifies a structural tension that becomes critical at scale: the founder who is most suited to starting a company is often the least suited to running it once it has grown past a certain threshold of complexity. The qualities that drive early growth — speed, conviction, tolerance for risk, unwillingness to be constrained by process — become liabilities when the organization requires governance, accountability infrastructure, and the kind of institutional discipline that constrains individual behavior.
Travis Kalanick’s leadership at Uber is a precise illustration of Wasserman’s thesis. The competitive aggression, the bias toward speed, the resistance to regulatory constraint — these were features in Uber’s early market-building phase. They became structural liabilities once the organization needed to build the internal governance capable of managing tens of thousands of employees and the legal, ethical, and operational complexity that came with them.
Wasserman’s framework does not assign blame. It describes a structural condition. Founders who do not recognize the transition point — or who resist building the architecture that the transition requires — create organizations that will eventually produce the kind of failures Uber became known for. Not because they are bad leaders, but because the structure they maintained was no longer appropriate for the organization it was supposed to govern.
The operational scene: a 34-person logistics company at velocity
A 34-person logistics company had grown from 11 employees to its current size in 18 months, driven by a regional contract win that more than tripled its operational scope. The founder was described by every member of the leadership team as brilliant, decisive, and indispensable. He was also the single point of authorization for every significant operational decision, the primary relationship holder for every major client, and the informal resolution mechanism for every internal conflict.
The stated organizational identity was one of empowerment and team ownership. The actual incentive structure rewarded proximity to the founder — those who could get his attention moved faster, regardless of formal role. Decision authority was undefined below the top two levels of the organization. When the founder was traveling — which was frequent — the organization slowed measurably. Client escalations waited. Operational adjustments stalled. Staff described the experience as working inside a structure that existed only when he was in the room.
The friction consequence was visible in the data: client satisfaction scores had declined over the growth period despite increased headcount. Onboarding failure rate had risen. Two senior operations managers had left in a six-month window, both citing ambiguity about decision authority and the impossibility of building their functions without founder involvement in every material choice.
The architectural correction was not a leadership development program. It was a decision authority map that defined what each role could authorize without escalation, a client relationship protocol that distributed ownership across the operations team, and a governance cadence that replaced informal founder access with structured weekly alignment. Four months later the founder described his own role differently: he had moved from being the organization’s operating system to being one of its inputs.
What growth velocity actually exposes
The Uber story and the 34-person logistics company share a structural logic, regardless of scale. Growth velocity does not create organizational problems. It accelerates the visibility of architectural ones that already existed. The governance gaps, the undefined decision authorities, the informal coordination dependencies, the accountability structures that never got built — these exist at 15 employees and 150. Growth makes them impossible to manage around.
Chandler’s foundational argument in Strategy and Structure (1962) — that structure must follow strategy — is often cited in business literature as a design principle. It is equally a warning. When strategy outpaces structure, the organization operates in a condition Chandler describes as structural lag: the demands placed on the organization exceed the architecture available to meet them. That lag has a cost. At Uber, the cost was measured in regulatory sanctions, board intervention, and reputational damage that took years to reverse. In founder-led companies at smaller scale, the cost is measured in operational friction, talent loss, and growth ceilings that feel like market constraints but are actually internal ones.
Growth is not the problem. The absence of architecture that grows with it is.
What founders can actually learn from this
The Uber case is not primarily a cautionary tale about toxic culture. It is a structural lesson about the architecture required to govern growth — and the cost of treating that architecture as secondary to the velocity of expansion.
The diagnostic question for any founder who is growing is not whether the culture is healthy. Culture is an output. The diagnostic question is whether the architecture is capable of governing the organization that currently exists — not the organization that existed 18 months ago.
That means examining decision authority as the organization currently operates: who can authorize what, at what threshold, through what process. It means examining accountability structures: when something goes wrong, is there a defined path for resolution that does not require founder involvement? It means examining coordination mechanisms: as the team grows, are the informal dependencies that used to work being replaced by formal ones that can carry the load?
Organizations answer architectural neglect eventually. The only question is whether the answer arrives internally as friction or publicly as failure.
Growth does not outpace a company’s culture. It outpaces its architecture. And architecture, unlike culture, can be deliberately built before the cost of its absence becomes the story.
References
Chandler, A. D. (1962). Strategy and Structure: Chapters in the History of the Industrial Enterprise. MIT Press.
Greiner, L. E. (1972). Evolution and revolution as organizations grow. Harvard Business Review, 50(4), 37–46.
Isaac, M. (2019). Super Pumped: The Battle for Uber. W. W. Norton & Company.
Mintzberg, H. (1979). The Structuring of Organizations. Prentice-Hall.
Wasserman, N. (2012). The Founder’s Dilemmas: Anticipating and Avoiding the Pitfalls That Can Sink a Startup. Princeton University Press.
Legacy Line Operations works exclusively with founder-led companies between 10 and 75 employees.
This article is part of the Case Study Series — comparative analysis of operational architecture decisions in high-growth companies.
legacylineoperations.com