7S was developed at McKinsey in the late 1970s. It's credited to Robert Waterman and Tom Peters. Richard Pascale and Anthony Athos share the credit for the related account of Japanese management. It names seven elements an organization has to move together for change to take. They are Strategy (the plan), Structure (the org chart and reporting lines), Systems (the processes and IT of daily work), Shared Values (the culture at the center), Skills (organizational capabilities), Staff (who is hired, developed, retained), and Style (how leadership actually behaves, as distinct from what it says). The first three are the "hard" Ss. They're visible, and easy to change on paper. The last four are the "soft" Ss, harder to see or change. They're also frequently the reason a hard-S change fails to take, and that's the framework's whole point.
How do you use 7S to diagnose a change effort?
The driver logic is interdependence. None of the seven elements produces change alone, and a mismatch between any two will defeat the effort however well the other five are executed. Announce a new Strategy without touching Structure, Systems, Skills, Staff, Style, and Shared Values, and what you've produced is a memo. Nobody should mistake it for a transformation. The most useful distinction in the whole framework is espoused versus enacted. Espoused is what leadership says the priority is. Enacted is what incentives, promotions, and resource allocation actually reward. The gap between the two is very often the entire diagnosis, and Worked Example 4 measures it with real operating metrics.
Build it correctly by attaching an observable fact to every box: a metric, a named policy, a specific behavior. Never an adjective alone. "Structure: matrixed" describes nothing anyone can check. "Branch managers hold full P&L authority and digital initiatives report through a staff function with no line authority" can be checked. It also lets a 7S diagnosis predict where a change effort will stall before it stalls.
Advertisement
What are the blind spots of the 7S framework?
7S has three blind spots at the mechanism level. First, the framework is a diagnostic checklist and not a sequencing tool. It tells you seven things must move together, but it gives no causal ordering for which should change first. Operating-model design and roadmap sequencing, covered on their own pages, exist to fill that gap. Second, fill it in with adjectives in place of evidence and the result is description without diagnosis. You'll later learn to call that failure the "boxes-and-lines" trap. Third, and most important, 7S has no opinion on whether the Strategy box itself is any good. It diagnoses alignment, and an organization can be perfectly, efficiently aligned around a bad strategy. Several of the "excellent" companies studied in the book that popularized 7S ran into real difficulty within a few years of publication. Alignment around the wrong bet is a different problem from misalignment around the right one.