And Waterman In Search Of Excellence

Getting Started With Waterman's Framework

I've spent more years than I want to admit looking at business strategy frameworks, and most of them fall apart the moment you try to use them in a real organization. The Waterman and Peters book from the early eighties is one of the few that still has actual teeth when you apply it properly. It is not a quick fix, and it will not save a poorly run company on its own, but it gives you a decent structure for thinking about what actually makes some businesses work better than others.

And Waterman In Search Of Excellence

The core idea behind their research is straightforward. They looked at about forty-three large American companies over four years and identified eight that were significantly outperforming their peers. Those eight companies shared certain habits and practices. The framework is not a step-by-step program you implement next Tuesday. It is more of a diagnostic lens. You take it into your own organization and see which attributes show up and which are missing. The work tends to take most people about two to three weeks to go through properly if they are doing it right, meaning actual interviews with staff at multiple levels rather than just filling out a checklist.

The Eight Attributes Explained

The eight attributes they identified have been rewritten and reinterpreted so many times that the original context got buried. I find it useful to just look at what they actually said and apply them directly without the corporate coaching-seminar gloss. Here is how they break down in practice. A bias for action comes up constantly in my experience, and this is the one people misunderstand the most. It does not mean rush into things without thinking. It means the organization prefers to learn by doing rather than by planning endlessly. In the companies that got studied, you would see decisions made with about seventy percent of the information available. Leadership expected people to adjust course as they went. When I ran a project using this principle on a product launch roughly five years ago, my team wanted a full requirements document before writing a single line of code. I told them to ship a rough version in two weeks and get real feedback. The product we launched was worse than what we originally planned, but we fixed the actual problems customers had instead of the problems we thought they had. The final version took half the time because we stopped guessing.

Being close to the customer is another one that gets watered down into meaningless jargon. The original point was simpler. Management should have regular, direct contact with people who actually buy or use the product. Not quarterly reports. Not focus groups arranged by a third party. Direct contact. I remember a supply chain issue I dealt with a couple of years back where the official metrics said everything was fine. Customers were churning but the retention dashboard showed a stable number because of how the data was being aggregated. I called a random sample of customers who had already churned and asked why. Three of them mentioned a shipping delay that the internal systems had already adjusted for but nobody on the product side knew about. That gap between the data and the reality is exactly what this attribute is supposed to close. Autonomy and entrepreneurship inside large organizations is a tricky one. The companies they studied found ways to keep small-team energy alive even while the overall organization was huge. This usually means spinning off internal teams, giving them budget control, and letting them operate like startups rather than departmental cost centers. I have seen this work and I have seen it fail. The failure mode is when leadership wants autonomy but still demands approval on every decision. That is not autonomy. It is a costume. Productivity through people means treating employees as the main lever for improvement rather than automation or process tightening. This is not a soft HR suggestion. It is a structural choice about where you invest. The original research showed that the best-performing companies invested heavily in training, gave frontline workers more decision-making authority, and shared information more openly than their competitors. The trade-off is that this approach is slower to implement and harder to measure in the short term. You will not see results in a quarterly report. You see them over eighteen to twenty-four months.

Close attention to operations is the attribute that sounds the least exciting but tends to matter the most in day-to-day running. The studied companies had leaders who understood the details of what was actually happening on the ground. They were not disconnected strategists reading slides. I once worked with a mid-level manager who had not visited a production floor in three years. When a quality issue came up, he had no idea why the defect rate spiked because he had no actual knowledge of the process. The people who knew did not feel safe reporting bad news upward. That disconnect is exactly what this attribute addresses, and it is one of the most common failure points I see in organizations of any size. Stick to the knitting means staying focused on your core business rather than chasing diversification for its own sake. The companies in the study tended to avoid acquiring businesses in unrelated fields. They grew by deepening their existing strengths. This is easier to follow when you are small. It gets much harder when you are a large company under pressure to find new growth vectors. My take is that this attribute works best when combined with honest assessment of where your actual competitive advantage lies rather than where it theoretically could lie. Simple form followed by liberal rules is about keeping structures minimal while allowing flexibility. The studied companies had few layers of management, simple reporting lines, and broad guidelines rather than detailed procedures. This is not anti-process. It is pro-clarity. The counter-intuitive part that beginners miss is that simplicity is harder to achieve than complexity. It requires constant discipline to remove layers and rules that accumulated over time. Most organizations drift toward complexity by default.

Form that supports substance means the visible aspects of the company culture should match what the company actually does. This includes how people dress, how meetings run, how decisions are communicated. If you claim to value innovation but your review process requires nine approval signatures, the form contradicts the substance. The studied companies kept their ceremonial aspects aligned with their stated values. I found this one to be the hardest to diagnose because it is easy to miss if you are not looking for it. The misalignment tends to show up in employee cynicism, which is a real metric if you know where to look.

How To Actually Apply This

The biggest mistake people make is treating the eight attributes as a scoring rubric where you aim for a perfect score across the board. That is not how the framework works. Different businesses will emphasize different attributes depending on their industry and size. A software company and a manufacturing company will look very different when you map them against these eight factors. The point is to identify which attributes are strong and which are weak, then prioritize improvements in the weak areas that matter most to your specific situation.

A practical way to start is to pick two or three attributes and interview about fifteen to twenty people across different levels and departments. Ask them specific behavioral questions related to each attribute rather than abstract questions. Instead of asking whether the company is close to customers, ask them to describe the last time they spoke directly to someone who bought or used the product and what they learned. The answers tend to reveal gaps that surveys miss entirely. Budget about two weeks for this phase unless you have a large team helping you. After the interviews, compare what people say with what actually happens. The gap between stated values and observed behavior is usually where the real problems live. Then pick one attribute to focus on for the next six months. Trying to improve all eight at once tends to produce nothing because it dilutes attention and resources across too many fronts. Pick the one that would create the most leverage given your current situation.

When This Approach Fails

I need to be direct about the limitations. This framework was built on data from large American manufacturing and technology companies in the late nineteen seventies and early nineteen eighties. The business environment has changed significantly since then. Service-based businesses, platform companies, and startups operate under different constraints than the companies in the original study. Applying this framework to a twenty-person startup is mostly pointless because the dynamics are entirely different. The framework assumes a certain scale and organizational complexity that small companies do not have. Another issue is that the original research had selection bias. The eight companies they highlighted were already successful when they selected them, which means the study identified characteristics of success rather than causes of success. Correlation does not equal causation, and several of those eight companies had significant problems in the decades that followed. Best Buy, one of the highlighted names, filed for bankruptcy protection in twenty seventeen. Texas Instruments struggled for years after its peak. This does not make the framework useless, but it does mean you should treat it as a set of observations rather than a guaranteed formula. The framework also tends to underweight the role of leadership style and individual talent. Some of the companies succeeded because of specific people in key positions, not because of systemic attributes. If you try to replicate the framework without the right leadership, you may get the structure without the execution. This is a common pitfall I see when consultants try to install these ideas in organizations that do not have the executive commitment to back them up.

For organizations that are smaller, faster-moving, or in highly innovative industries, frameworks like Lean Startup or OKRs might be more practical starting points. The Waterman approach is stronger for established companies trying to understand cultural and operational fundamentals rather than for companies that need to find product-market fit or iterate quickly. If you want the original text, the book is widely available through standard retailers and has been reprinted multiple times. There are also several condensed summaries and case study collections that reference the eight attributes if you want to explore specific examples before committing to the full read. The full version runs about two hundred seventy pages in most editions and moves at a steady pace without unnecessary padding.