Tony Hsieh did not build a company with good values. He built a company where the values were load-bearing.
That distinction matters more than most founders realize. The difference between a company that talks about its culture and a company that has operationalized it is structural, not rhetorical. Zappos’ culture did not emerge from a set of principles on a wall or an annual values workshop. It emerged from deliberate decisions about hiring, promotion, compensation, workflow design, and organizational governance. Culture was the architecture, not the decoration.
Most founders who study Zappos come away with one takeaway: be customer-obsessed and make your team feel valued. That lesson is not wrong, but it misses the more consequential insight: Zappos built a system in which its values could not easily be abandoned, because they were embedded in how the work actually happened.
When values are not structurally embedded, organizations compensate through escalation, interpretation, and managerial intervention — all of which increase coordination cost as the company grows. Culture, understood this way, is not a morale variable. It is a coordination mechanism. What Zappos built, at its most coherent, was a coordination system that ran on values rather than rules.
Edgar Schein’s three levels
Edgar Schein’s foundational model of organizational culture, introduced in Organizational Culture and Leadership (1985), describes culture as operating on three levels: artifacts, espoused values, and underlying assumptions. Most organizations operate at the first two. They build visible artifacts — mission statements, office aesthetics, recognition programs — and they articulate values in language their teams can repeat. What they rarely do is allow those values to settle into the third level: the unconscious, taken-for-granted beliefs that actually govern behavior when no one is watching.
Zappos operated at the third level. Tony Hsieh’s decision to pay new hires $2,000 to quit after their first week of onboarding was not a gimmick. It was a diagnostic. The offer filtered for people whose underlying assumptions about work aligned with the culture Zappos was building. Anyone who took the money was being paid to reveal that their assumptions did not match. Structural design, not cultural aspiration.
This is where most founder-led companies stop short. They articulate values at the first two levels — they name them, display them, reward verbal alignment with them — without building the structural conditions that allow those values to govern behavior at the third level. The result is a culture that exists in the language of the organization but not in its mechanics.
Galbraith’s Star Model and the Zappos alignment
Jay Galbraith’s Star Model describes organizational design as the alignment of five elements: strategy, structure, processes, rewards, and people. His central argument is that dysfunction occurs not when any one element is poorly designed, but when the elements are misaligned with one another. A company can have a strong strategy and a committed team while still producing operational friction if its processes and rewards are sending different signals.
Zappos is one of the cleaner examples of Star Model alignment in a high-growth company. The strategy — delivering happiness through customer experience — was not a marketing position. It governed structural choices. Customer service representatives had no call time limits. The rewards system compensated for cultural fit and long-term retention, not just performance metrics. The hiring process screened for values before screening for skills. Processes were designed to give frontline employees genuine decision authority over customer outcomes.
Each element reinforced the others. Remove any one and the alignment deteriorates. This is precisely what happened when the Holacracy experiment began to break down the structural layer. The values remained. The language of culture remained. But the architecture that had been carrying them was dismantled, and the culture began to fray.
The operational scene: a 22-person team in the retail sector
A 22-person specialty retail company had spent two years building what its founder described as a people-first culture. They had a set of written values, a quarterly recognition program, and a strong reputation among their staff for flexibility and care. The founder was genuinely committed. The language in the company reflected that commitment.
When an operations review was conducted, the actual workflow told a different story. Frontline staff had no decision authority over returns beyond a $50 threshold. Compensation was tied primarily to individual sales metrics, not to customer satisfaction or peer support. When things went wrong with customers, staff were required to escalate — which in a business where the founder was frequently unavailable meant customers were left waiting.
The values said: we put people first. The architecture said: you need permission to act, your pay depends on your individual number, and escalation is the protocol when judgment is required. Those two systems were in direct conflict. The culture was not dysfunctional because the people were wrong. It was dysfunctional because the structure had never been built to carry the values the founder held.
The fix was not motivational. It was architectural: a tiered decision authority map, a modified compensation structure that rewarded team outcomes alongside individual performance, and a clear handoff protocol that did not require founder involvement for routine customer situations. Six months later the founder described the shift not as a culture change, but as the culture finally becoming real.
The Holacracy rupture and what Greiner predicted
In 2013, Hsieh announced that Zappos would adopt Holacracy — a flat, self-managing organizational structure that eliminates traditional management hierarchy in favor of distributed authority circles. The philosophical alignment with Zappos’ values seemed logical. A company that believed in empowering its people would benefit from a structure that formalized that empowerment.
What the transition revealed instead was that the original architecture had been doing more work than anyone had acknowledged. The transition replaced familiar managerial coordination mechanisms with a system the organization was never operationally prepared to run at that scale. Decision-making slowed. Accountability became diffuse. By 2015, approximately 18 percent of the workforce had taken buyout offers and left. The culture survived in language; it struggled in execution.
Larry Greiner’s model of organizational growth, published in the Harvard Business Review in 1972, describes a recurring pattern in which companies move through phases of growth that each end in a specific type of crisis. One of those crises is a crisis of control: as organizations grow, the informal coordination that worked at smaller scale breaks down, and the absence of formal architecture creates confusion about authority, accountability, and process.
Zappos’ Holacracy period aligns with that pattern. The company had grown past the scale at which its informal, founder-shaped culture could govern behavior without structural support. The lesson is not that Holacracy failed as a concept. It is that values require architecture, and architecture cannot be dismantled without replacing the coordination function it was carrying.
Signs your values are not yet operationalized
Before asking what founders can learn from Zappos, it is worth asking whether the condition applies. These are the observable signals that values exist in the language of an organization but have not yet been built into its mechanics:
– Decisions escalate to the founder or a manager because the alternative is ambiguous or undefined.
– Frontline staff interpret the values differently across departments or locations.
– Culture quality varies depending on who is available — a reliable indicator of non-institutionalized culture.
– Compensation or recognition rewards behavior that contradicts stated principles.
– The culture weakens under growth pressure, leadership absence, or organizational change rather than holding.
If two or more of these patterns are present, the values are aspirational. The architecture has not yet been built to carry them.
What founders can actually learn from this
The lesson most founders carry from Zappos is one of aspiration: be customer-focused, be generous with your people, build a culture you are proud of. These are not wrong. But they are incomplete.
The more useful lesson is diagnostic. Ask whether your values are operational. Can you point to a specific process, policy, decision rule, or structural design choice that carries each value? If your value is responsiveness, what is the decision authority your frontline staff has when a customer situation requires judgment? If your value is team over individual, what does your compensation structure actually reward?
If the answer to those questions is: our values live in how we talk about things, not in how things are built — then the values are aspirational. They are not yet operational.
Zappos understood this, at least during the period when the architecture held. And the distinction holds regardless of company size, industry, or founder intent.
Values that depend entirely on founder presence are not culture. They are personality. Sustainable culture emerges when values are translated into authority structures, incentives, workflows, and operational expectations that survive scale.
References
Galbraith, J. R. (1993). Competing with Flexible Lateral Organizations. Addison-Wesley.
Greiner, L. E. (1972). Evolution and revolution as organizations grow. Harvard Business Review, 50(4), 37–46.
Hsieh, T. (2010). Delivering Happiness: A Path to Profits, Passion, and Purpose. Business Plus.
Mintzberg, H. (1979). The Structuring of Organizations. Prentice-Hall.
Schein, E. H. (1985). Organizational Culture and Leadership. Jossey-Bass.
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