In Search Of Excellence Peters And Waterman

What Actually Made In Search Of Excellence Peters And Waterman Worth Reading

I picked up that book back in 1983, right when everyone at my firm was treating it like gospel. We had a strategy offsite where someone projected the eight attributes on a whiteboard and we spent three hours checking whether our department matched. I remember thinking most of it was obvious once you laid it out, but the packaging was what made it stick. The core idea is straightforward: they studied eight companies that outperformed the market for extended periods — IBM, Hewlett-Packard, McDonnell Douglas, 3M, Xerox, AT&T, McDonald's, and Johnson & Johnson — and eight similarly situated companies that didn't, and then looked for patterns in what separated them. The eight attributes they identified are things like staying close to the customer, being hands-on and value-driven, operating through autonomy rather than tight control, pushing decisions to the people closest to the actual work, having a bias for action instead of endless analysis, sticking to the core business, getting simplicity into the org structure before it gets complicated, and balancing stability with flexibility. Each one sounds reasonable until you try to actually implement it in a company that's already six layers deep and managed by committee. Here's what nobody tells you reading the popular version: the book was really a study in how to observe organizational behavior systematically, not a management cookbook. Peters and Waterman's methodology was genuinely useful. They went into these companies and watched how decisions actually got made, not what the mission statement said. That fieldwork angle is what separates this from the typical business book that gets written by someone who interviewed five CEOs over lunch. The data came from site visits, document reviews, and structured conversations across multiple levels of each organization.

I ran into a specific problem about two years ago when a client asked me to use the eight attributes as an audit framework for their expansion into European markets. Attribute four — autonomy and entrepreneurship — sounded great on paper, but their middle management structure was built around approval chains that required three sign-offs for any budget over twenty thousand dollars. You can't have decentralization when the organizational design physically prevents anyone from making a decision without escalation. What I ended up doing was mapping each attribute against their actual decision rights matrix rather than their stated values, and the gap between the two was enormous. The exercise still helped, but only after I stopped treating the attributes as checkboxes and started treating them as aspirational targets with known implementation constraints. There's a counter-intuitive point most people miss about the research. Xerox was one of their success cases, and by the late eighties that company was essentially collapsing. The book captured a snapshot, not a trajectory. Peters and Waterman themselves acknowledged this later, and in the revised edition they added a whole section on what happens when the environment changes faster than the culture adapts. The companies they studied were excelling at something specific in a specific era.IBM was dominating mainframes in 1980. That doesn't mean those eight attributes automatically translate to succeeding at cloud computing thirty years later. The framework describes how to excel at your current business, not how to pivot when your current business becomes irrelevant. Another thing that gets overlooked is how much the attributes reinforce each other, or how much tension exists between some of them. You can't really have both attribute seven — simplicity and a lean organization — and attribute one — being close to the customer — in a large multinational without creating real structural contradictions. Customer closeness requires investment in local presence, relationship management, and customization. Simplicity and lean operations push the opposite direction. The best companies they observed found temporary equilibriums between these tensions, not permanent solutions. That's an important distinction because it means the framework is descriptive rather than prescriptive. It tells you what excellence looked like in those specific organizations, not a recipe you can follow universally.

The book's actual lasting contribution, in my view, has less to do with the eight attributes themselves and more to do with popularizing the idea that you can study high performance empirically rather than deriving it from theory. Before this kind of work became common, management advice mostly came from academics writing about what should work based on economic models or from consultants with frameworks they'd developed internally. Peters and Waterman went the other direction: they looked at what actually worked and tried to reverse-engineer the pattern. That inductive approach had real methodological value even if the specific findings aged poorly. I'll be blunt about the limitations. The sample size was small — eight plus eight companies is not a statistically meaningful dataset. The selection criteria weren't fully transparent, which means there could have been survivorship bias built into the whole exercise. Several of the so-called failure companies later recovered — GE, for instance, was considered a laggard in the original study but became the benchmark for the next two decades. The book also has a strong West Coast California sensibility that doesn't translate cleanly to every industry or culture. Being hands-on and value-driven means something very different in a Japanese manufacturing company than it does in a Silicon Valley startup. If you're actually going to use this, here's what I'd suggest. Read the original for the methodology and the observational detail, not as a manual. Then pick two or three of the attributes that create the most tension in your organization and dig into how other companies in your sector have actually resolved those tensions. The attribute about bias for action is almost universally recommended, but in regulated industries like pharmaceuticals or aviation, that bias needs to be carefully bounded or you get the wrong kind of speed. Staying close to the customer sounds simple but requires actual investment in feedback loops, not just periodic surveys. I've seen companies implement Net Promoter Score tracking and call it customer closeness when they'd actually reduced their direct customer contact by forty percent through digital channels over the same period.

The book is available in multiple editions now. The original 1982 version has the cleanest presentation of the eight attributes before later revisions added caveats and updates. You can find it through standard book retailers, and many university libraries have copies. If you want the more rigorous academic treatment of the same questions, look at the follow-up work that Peters and Waterman did with the McKinsey quarterly and the later Harvard Business Review articles where they addressed some of the criticism directly. Those pieces are more honest about what the research actually showed versus what the marketing department wanted you to believe. My take after twenty-five years of dealing with organizational strategy is that the book remains worth reading, but primarily as a case study in management thinking from a particular moment rather than a timeless guide. The eight attributes are useful heuristics if you treat them as starting points for diagnosis rather than endpoints for implementation. The real value is in the habit of looking at successful companies systematically and trying to understand why they succeeded rather than assuming it was luck or market position alone. That habit, more than any specific attribute, is what transfers across industries and decades.