Jump to content

McKinsey 7S Framework

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Curb Safe Charmer (talk | contribs) at 11:14, 18 January 2020 (Reverted good faith edits by 2405:204:5607:216B:F89:751:B64D:B37E (talk): Unexplained and unhelpful (TW)). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Visual representation of the model[1]

The McKinsey 7S Framework is a management model developed by business consultants Robert H. Waterman, Jr. and Tom Peters (who also developed the MBWA-- "Management By Walking Around" motif, and authored In Search of Excellence) in the 1980s. This was a strategic vision for groups, to include businesses, business units, and teams. The 7 Ss are structure, strategy, systems, skills, style, staff and shared values.

The model is most often used as an organizational analysis tool to assess and monitor changes in the internal situation of an organization.

The model is based on the theory that, for an organization to perform well, these seven elements need to be aligned and mutually reinforcing. So, the model can be used to help identify what needs to be realigned to improve performance, or to maintain alignment (and performance) during other types of change.

Whatever the type of change – restructuring, new processes, organizational merger, new systems, change of leadership, and so on – the model can be used to understand how the organizational elements are interrelated, and so ensure that the wider impact of changes made in one area is taken into consideration.

History

In 1977, McKinsey director Ron Daniel launched two projects. The first and major one, the Business Strategy project, was allocated to top consultants at McKinsey's New York City corporate HQ and was given significant resources. It was headed by Frederick Gluck, and despite promise, the project could not manage to effectively implement the new strategies. The second project was related to the problem of implementation: organizational effectiveness. This project was headed by Cleveland-based James Bennet.[2]

Peters states that directly after graduating with a PhD from Stanford and returning to McKinsey, Daniel handed him a "fascinating assignment."[3] Motivated by the new ideas coming from Bruce Henderson's Boston Consulting Group, Peters "was asked [by Daniel] to look at 'organization effectiveness' and 'implementation issues' in an inconsequential offshoot project nested in McKinsey's rather offbeat San Francisco office."[3] While Daniel's first project was focused on Business Strategy, this second project was concerned with "Organization" which Peters defined as involving "the structure-and-people side.".[4] The "Organization" project was seen by Peters to be less important, according to Peters in a Fast Company interview.

Despite being described as "marginal," the project "had an infinite travel budget that allowed [Peters] to fly first-class and stay at top-notch hotels, and a license from McKinsey to talk to as many cool people as [he] could all around the United States and the world."[4] Peters admits that "There was no carefully designed work plan. There was no theory that I was out to prove. I went out and talked to genuinely smart, remarkably interesting, first-rate people."[4] In addition to Karl Weick and Einar Thorsrud, Peters notes that Douglas McGregor's theory of motivation, known as Theory X and Theory Y, was directly influential on the direction of the project.

In a 1978 article, "Symbols, Patterns and Settings," Peters argued that "shifting organizational structure" and "inventing new processes" - structure and system, respectively - were only two tools of organizational change. Peters then outlined eight "mundane" tools that every manager has at their fingertips. He described this article as a "tentative presentation" and "the first public expression of these ideas."[3]

In 1979, McKinsey's Munich office requested Peters to present his findings to Siemens. That provided the spur for Peters to create a 700-slide two-day presentation. Word of the meeting reached the US and Peters was invited to present also to PepsiCo. However, unlike the hyper-organised Siemens, the PepsiCo management required a tighter format than 700 slides, so Tom Peters consolidated the presentation into eight themes. Each of these eight would form a chapter of In Search of Excellence.

In 1980, Waterman joined Peters, and, along with Waterman's friend Tony Athos and Richard Pascale - both academics - came together at a two-day retreat in San Francisco to develop what would become known as the 7S Framework, the same framework that would organize In Search of Excellence. In June 1980, Peters published an op-ed in the Manager's Journal section of the Wall Street Journal titled "The Planning Fetish."[5] In this article, he "stressed the importance of execution and dismissed the whole idea of strategy."[6] As strategy was McKinsey's main operation at the time, this was seen as a "frontal assault" on the company, leading Mike Bulkin, the head of the New York office, to demand that Daniel fire Peters.

The primary "innovative" theme that undergirded what would become the well-known "In Search of Excellence" book was that "structure is not organization." This also happened to be the title of a 1980 journal article authored by Bob Waterman, Tom Peters, and Julien Phillips in which they argue that the "picture of the thing is not the thing.... An organizational structure is not an organization."[7] This article also introduced what would become the McKinsey 7S Framework.

In December 1981, Peters left the company after agreeing to a fifty percent royalty split with McKinsey. Later, co-author Waterman stayed at the firm for three more years but received no royalties from In Search of Excellence

In Search of Excellence

The work of Peters, Waterman, Athos, and Pascale leading up to the widely successful In Search of Excellence, not only elaborated the eight themes that would form each chapter, but also the 7 S's frame the different ways in which the firms profiled in the book were "excellent."

The Art of Japanese Management

Athos and Pascale, although not named as co-authors of the 1982 publication of In Search of Excellence, published their own study in a 1981 book titled The Art of Japanese Management. This book used the 7S Framework to compare the Japanese firm Matsushita with the American company ITT.[8] Just as Peters emphasized throughout his writing, the important distinction between American and Japanese management was not the so-called "hard" technical aspects of organization, but rather the "soft" cultural aspects.

Objective

(To analyze how well an organization is positioned to achieve its intended objective)

Usage

  • Improve the performance of a company
  • Examine the likely effects of future changes within a company
  • Align departments and processes during a merger or acquisition
  • Determine how best to implement a proposed strategy

The Seven Interdependent Elements

  • The basic premise of the model is that there are seven internal aspects of an organization that need to be aligned if it is to be successful

Hard Elements

  • Strategy - Purpose of the business and the way the organization seeks to enhance its competitive advantage.
  • Structure - Division of activities; integration and coordination mechanisms.
  • Systems - Formal procedures for measurement, reward and resource allocation.

Soft Elements

  • Shared Values
  • Skills - The organization's core competencies and distinctive capabilities.
  • Staff - Organization's human resources, demographic, educational and attitudinal characteristics.
  • Style - Typical behaviour patterns of key groups, such as managers, and other professionals.

Limitations

The framework gives rise to a few vital points, like:

  1. What type of analysis is this? Or what is the action triggered after putting your organization into this drill?
  2. Does this give you real guidelines as to how to proceed further, after the analysis is completed?
  3. Do we treat this as a guideline or checklist and proceed with using other techniques to formulate further steps?
  4. There have been other techniques in vogue which have to be used to arrive at actionable points. Here too, a similar approach may be needed, as a tool, to really put this into action.
  5. The above seems to be an abstract list of generic elements in any organization. It does not spell out which steps are to be initiated to improve each business process, such as Marketing, Finance, Manufacturing etc.

References

  1. ^ Hayes, John (2014). The Theory and Practice of Change Management. London: Palgrave Macmillan. p. 137. ISBN 978-1-137-27534-9.
  2. ^ McDonald, Duff (2014-09-30). The Firm: The Story of McKinsey and Its Secret Influence on American Business. Simon and Schuster. ISBN 978-1-4391-9098-2.
  3. ^ a b c "A Brief History of the 7-S ("McKinsey 7-S") Model - Tom Peters". 8 March 2011.
  4. ^ a b c "Tom Peters's True Confessions". 30 November 2001.
  5. ^ Peters, T. (1980). The Planning Fetish. Manager's Journal," Wall Street Journal.
  6. ^ McDonald, Duff (30 September 2014). "The Firm: The Story of McKinsey and Its Secret Influence on American Business". Simon and Schuster – via Google Books.
  7. ^ Waterman, R. H., Peters, T. J., & Phillips, J. R. (1980). Structure is not organization. Business Horizons, 23(3), 14-26.
  8. ^ "Richard Pascale". The Economist.