McKinsey 7S Framework
The model prescribes checking alignment among strategy, structure, staffing capacity, and systems, while treating style and shared values as a background condition rather than a scored design choice.
McKinsey and Company (Robert Waterman, Tom Peters, Julien Phillips), 1980
The origin of the framework, as the directory records it. The mark grades the origin, not this page.
The directory entry this score was read from. Umbrex is a consultancy network; its summary is the reference, not a primary source.
Scored against the twelve cells, it loads four: Structure, Strategy, Resources, and Flow. The other eight it leaves to you. None of Composition, Evidence, or Mastery is among them, which is the usual result in this directory: the questions an agent in the loop raises first are the ones the literature answers least.
Style and shared values are read as a precondition on fit rather than a designed cell.
This is not a summary of the framework. Umbrex has one; the link under Sources goes there.
What is the smallest unit that can own a customer outcome end to end?
Where on the evolution curve does each capability sit, and does that dictate build, buy, or let go?
What is owned, what is rented, and what is summoned only when needed?
What limits throughput, and what is supposed to happen when the line stops?