The Culture Was Real

What Zappos built in Las Vegas, why it worked for a decade, what made it vulnerable, and what every organization can learn from both sides of the story

A shoe company that was not about shoes

In 1999, a small online retailer in San Francisco began selling footwear. It was not the first company to sell shoes online. It was not the best funded. It did not have the widest selection. What it had was a conviction, stated clearly and lived consistently from the beginning, that would eventually make it one of the most studied organizations in American business.

The conviction was simple: Zappos was not a shoe company that provided customer service. It was a customer service company that happened to sell shoes.

That distinction mattered more than it might initially appear. A shoe company optimizes for selection, price, and delivery speed. A customer service company optimizes for the experience of the person on the other end of every interaction. These are not the same optimization. They produce different decisions, different priorities, and different organizations. Tony Hsieh, who became CEO in 2000 and shaped the company's direction across the following decade, understood this clearly. The product was footwear. The mission was something else entirely.

Zappos relocated to Henderson, Nevada in 2004 to be closer to its warehouse operations and to build an organizational culture without the distractions of a major city. By 2008, it had surpassed one billion dollars in gross merchandise sales. In 2009, Amazon acquired the company for approximately 1.2 billion dollars. At the time of its acquisition, Zappos had a 75 percent repeat customer rate and a Net Promoter Score reported to exceed 85. These were not the numbers of a shoe company. They were the numbers of an organization that had built something into its daily operations that most retailers had not thought to build.

This article is about what that something was, why it worked, and what happened when the conditions that had produced it began to change.

Zappos was not a shoe company that provided customer service. It was a customer service company that happened to sell shoes. That distinction produced a different organization, not a different marketing strategy.

The vision that was actually a commitment

Most organizational vision statements are sentences that could belong to any organization in a given industry. Aspirational. Broadly positive. Immediately forgettable by the people who were present when they were written.

Zappos' founding purpose, to deliver WOW through service, was three words with a specific and verifiable meaning in every customer interaction. WOW was not a metaphor. It was a performance standard. It described the experience the organization was committed to producing, stated in language that any customer service representative could apply immediately to the conversation they were in.

The test Hsieh applied to any decision was direct: does this produce a WOW experience for the customer? Not: does this reduce cost? Not: does this improve efficiency? The question that oriented decisions was the customer's experience. Cost and efficiency had to serve that question, not the other way around.

This produced decisions that looked irrational by the standards of conventional retail. Zappos offered free two-way shipping at a time when most online retailers charged for both. It maintained a 365-day return policy. Its customer service representatives operated without scripts and without time limits on calls. A call that lasted four hours, if it was the call the customer needed, was the right call.

In 2012, a Zappos customer service representative spent 10 hours and 29 minutes on a single phone call, setting what was reported as the company's record for the longest customer service call in its history. The representative did not consult a manager before spending that time. The vision had made the decision for her: a WOW experience was what the call required, and that was what Zappos delivered.

A vision that produces that kind of autonomous decision, in a representative who does not need to escalate, confirm, or apologize for the time invested, is not a vision statement. It is an operating system.

The values that were not on the wall

Zappos developed its ten core values through a process that took approximately one year and involved genuine input from employees across the organization. This is worth noting not as a procedural detail but as an organizational signal. Most corporate values are written by a small group of senior leaders and then communicated to the rest of the organization. Zappos built its values from the ground up, collecting input, testing language, and revising until the final ten reflected what people throughout the company actually believed rather than what leadership wanted them to believe.

The resulting values included commitments that most organizations would not name publicly: Create Fun and a Little Weirdness. Be Humble. The list acknowledged that the organization was made of human beings who brought energy, personality, and individual character to their work, and that those qualities were not distractions from the mission but essential to it.

More important than the wording was the connection between the values and the operational system. Zappos used its values as a filter at every stage of the employment relationship. Hiring decisions were made partly on cultural fit alongside technical competence. Performance reviews explicitly assessed value alignment. Promotions and recognition reflected how people lived the values, not only what they produced. The values were not hanging on the wall. They were embedded in the processes that determined what happened to people inside the organization.

The most vivid expression of this was the offer made to every new employee after completing the initial training period. Zappos would pay any new hire to leave, initially one thousand dollars and eventually rising to five thousand, if they chose not to continue after experiencing the culture firsthand. The offer was not a severance package. It was a self-selection mechanism. The organization was saying: if this is not genuinely right for you, we will make it easy to leave. The people who stayed after the offer had chosen, explicitly, to be part of what Zappos was building.

"We wanted to make sure that we weren't hiring people who just needed a job. We wanted people who really believed in what we were doing and thought it was an opportunity to be part of something special."     Tony Hsieh

The brand promise that held

For the first decade of the company's growth, Zappos delivered on a set of promises that its customers, employees, and vendors experienced consistently.

For customers, the promise was simple and precise: what was described was what was delivered, faster than expected, with a return policy that removed any risk from the purchase. Customer service representatives were empowered to do whatever the customer needed, including recommending a competitor's website if Zappos did not carry what the customer was looking for. That last practice, the willingness to send a customer elsewhere when Zappos could not serve them, was the clearest expression of an organization that genuinely believed its purpose was to serve the customer rather than to extract value from the customer relationship.

For employees, the promise was an environment in which personal growth, genuine belonging, and work that felt meaningful were available to anyone who chose to invest in the culture. The company's customer service center was designed to be a place people wanted to work rather than a place they tolerated. Employees decorated their own spaces. Unusual requests were accommodated. The culture was deliberately and visibly different from the standard call center environment, and that difference was experienced by the employees who worked in it as a genuine expression of the organization's values.

For vendors, the promise was a partnership built on shared interest in the customer's experience. Premium footwear brands that had initially been reluctant to sell through an online channel became Zappos partners because the organization's approach to the customer relationship protected rather than diminished their brand. Zappos earned vendor trust by treating the customer with the same care the vendors would have chosen to provide directly.

This was not marketing. It was the accumulated result of thousands of individual interactions in which people inside the organization had acted according to the values and purpose they had been given, and in which those values and that purpose had proven to be genuine commitments rather than aspirational language.

Zappos' brand promise was not a marketing campaign. It was the accumulated result of thousands of individual interactions in which people acted according to values that were real, not decorative.

What the Amazon acquisition tested

Amazon acquired Zappos in November 2009 in a transaction valued at approximately 1.2 billion dollars. The circumstances of the acquisition matter to understanding what followed.

The 2008 financial crisis had placed significant pressure on Zappos' credit facilities. The company's model required substantial working capital: large inventory holdings, free two-way shipping, and a 365-day return policy were not inexpensive to maintain. When the credit markets tightened, the financial runway that had supported the model became less certain. Hsieh chose to sell to Amazon rather than modify the business model or seek alternative financing.

Amazon's stated intention was to allow Zappos to continue operating independently, preserving the culture and customer service philosophy that had produced the company's value. For several years, the arrangement functioned as described. Zappos operated with significant autonomy. The culture remained recognizable. The customer experience continued to reflect the values the company had built.

The first significant test came not from Amazon but from within. In 2013, Hsieh announced that Zappos would adopt Holacracy, a management framework designed to replace conventional hierarchical structures with a system of self-organizing circles and distributed authority. The stated intention was to build an organization in which people had genuine autonomy over their work without depending on a manager's approval to contribute, innovate, or grow.

The concept was consistent with several things Zappos had always valued: trust in people, distributed decision-making, and an organizational environment that treated employees as capable adults. The execution proved considerably more complicated.

By 2015, approximately 14 percent of Zappos employees had accepted a buyout offer to leave rather than continue under the new structure. The departures included experienced people who had helped build the culture the restructuring was intended to preserve. The self-organizing circles that were supposed to replace hierarchical management created their own complexity, and the clarity of purpose and role that had allowed Zappos' customer service representatives to make autonomous decisions without escalation was harder to maintain in a structure that had removed the management layer without fully replacing what that layer had provided.

The lesson the second chapter teaches

The standard reading of Zappos is a culture success story. Build the right values. Hire for fit. Trust your people. The customer experience will follow.

That reading is accurate as far as it goes. Zappos did build genuine values. It did hire for cultural fit. The customer experience did follow. For a decade, it was one of the clearest examples in American business of an organization in which the connection between internal culture and external experience was deliberate, measurable, and real.

The more complete reading, which the second chapter of the Zappos story makes available, is about what culture requires in order to sustain itself when the conditions that produced it change.

Zappos' culture was inseparable from a specific set of conditions: a founder who embodied and personally maintained the values, a customer service model that made the culture's expression immediate and visible in every interaction, an operational philosophy that placed the customer experience above cost efficiency, and a talent system that continuously filtered for people who wanted to be part of what the organization was building.

When those conditions changed, the culture did not simply continue by inertia. Amazon's operational requirements, Prime's two-day delivery standard, the pressure on margins from a retail market that was increasingly commoditized, the structural disruption of Holacracy, and eventually the loss of the founder whose personal conviction had anchored the culture's daily expression: each of these changes placed pressure on a culture that had been real but that had not fully become institutional.

The distinction is important. An institutional culture is one that can reproduce its own standards without depending on the people who created it. The values are embedded in hiring, training, operational systems, and leadership development deeply enough that new people absorb them and the culture continues. A founder culture is one that depends on the founder's presence, energy, and daily modeling to maintain its intensity. Founder cultures produce remarkable organizations. They are also more fragile than they appear from the outside.

Recent customer and employee feedback about Zappos reflects the consequences of this fragility. Customer reviews describe inconsistency in the experiences that were once reliably remarkable. Employee reviews acknowledge that the environment of the early years is less fully present. The brand promise that was once the clearest competitive advantage in online retail has become, in the language of those who encounter it today, uneven.

A culture that depends on the founder's daily presence to maintain its standards has not yet become institutional. Zappos built something genuine. The harder question it eventually faced was whether the values were embedded deeply enough to outlast the conditions that had produced them.

What the full story reveals

Zappos is not a cautionary tale. It is a complete one.

The first chapter demonstrates that vision, values, and a genuine brand promise can become a competitive advantage when they are built into the organization's operational systems rather than posted on its walls. A 75 percent repeat customer rate, a Net Promoter Score above 85, and a talent culture that attracted people who wanted to participate in something larger than a job: these are the documented results of an organization that took its own convictions seriously for a sustained period.

The second chapter demonstrates that the same convictions, unless they are embedded deeply enough to be reproduced without the people who originally held them, become vulnerable to the changes that every organization eventually encounters. Leadership transitions. Acquisitions. Structural redesigns. Market shifts. The culture that was real in 2008 remained real through the first years after the Amazon acquisition. It became progressively less reliable as the conditions that had sustained it changed without the organizational infrastructure to reproduce it.

The question the Zappos story asks of every organization is not whether its culture is genuine today. The question is whether the values that feel alive in the room where leadership is sitting are embedded deeply enough in the systems, the hiring, the training, the performance management, and the daily operating decisions that they will continue to govern behavior when the people who built them are no longer present to model them.

Culture is not the engine. Culture is the result of the engine. The engine is the connection between what the organization says it is, what it rewards, what it hires for, what it trains toward, and what it holds people accountable to. When that engine runs consistently, culture is the natural output. When it stops running, culture becomes memory.

What Working As 1 takes from this

Working As 1 uses four elements as the foundation of organizational performance: vision, mission, core values, and beliefs. The Zappos story illustrates all four, in both their presence and their eventual erosion, with unusual clarity.

The vision that oriented Zappos, a customer service company that happened to sell shoes, was not a statement of aspiration. It was a working answer to the question that every person in the organization could apply in real time: is what I am about to do consistent with who we are? A vision that answers that question in the moment of a 10-hour customer service call, without consultation or approval, has become something more than a declaration. It has become a decision-making tool.

The core values that Zappos developed through a year of genuine organizational involvement were not aspirational language. They were a social contract: the shared agreement about how people would treat each other, the customer, the vendor, and the work itself. The offer to pay new employees to leave was the values being tested in real time. The people who stayed had chosen the contract. The organization that paid people to leave had honored it.

The beliefs Zappos built around the customer experience, the employee experience, and the vendor relationship were, for a decade, the clearest expression in American retail of what it looks like when an organization genuinely delivers on what it says it stands for. The 365-day return policy. The four-hour calls. The willingness to send customers to a competitor. These were not customer service tactics. They were beliefs made operational.

What the second chapter of Zappos adds to the Working As 1 understanding is the distinction between a living culture and an institutional one. A living culture is present and felt and genuine. An institutional culture is all of those things, and also embedded in systems that reproduce it when the people who created it are no longer in the room. Working As 1 works with organizations on both: on building the vision, values, and beliefs that make a culture genuine, and on embedding them in the operating systems, the hiring, the development, and the accountability structures that make them institutional.

The Zappos story does not end badly. It ends honestly. It demonstrates that the work of building an organization in which vision, values, and beliefs are real is valuable, consequential, and genuinely difficult to sustain. And it provides the clearest available illustration of what that difficulty looks like when the conditions that made a culture possible change faster than the infrastructure designed to reproduce it.

The question Zappos eventually faced is the question every leader of every organization is always facing, regardless of whether they know it: are the values we are living today embedded deeply enough to be the values we live tomorrow, without us?

Culture is not the engine. Culture is the result of the engine. Build the engine.