The MECE principle (mutually exclusive and collectively exhaustive) is a grouping principle for separating a set of items into subsets that are mutually exclusive (ME) and collectively exhaustive (CE).[1] It was developed in the late 1960s by Barbara Minto at McKinsey & Company and underlies her Minto Pyramid Principle,[2] and while she takes credit for MECE, according to her interview with McKinsey, she says the idea for MECE goes back as far as to Aristotle.[2]
The MECE principle has been used in the business mapping process wherein the optimum arrangement of information is exhaustive and does not double count at any level of the hierarchy. Examples of MECE arrangements include categorizing people by year of birth (assuming all years are known), apartments by their building number, letters by postmark, and dice rolls. A non-MECE example would be categorization by nationality, because nationalities are neither mutually exclusive (some people have dual nationality) nor collectively exhaustive (some people have none).
Common uses
editStrategy consultants use MECE problem structuring to break down client problems into logical, clean buckets of analysis that they can then hand out as work streams to consulting staff on the project.
Similarly, MECE can be used in technical problem solving and communication. In some technical projects, like Six Sigma projects, the most effective method of communication is not the same as the problem solving process. In Six Sigma, the DMAIC process is used, but executive audiences looking for a summary or overview may not be interested in the details. By reorganizing the information using MECE and the related SCQA storytelling framework, the point of the topic can be addressed quickly and supported with appropriate detail. The aim is more effective communication.[3]
Criticisms
editThe MECE concept has been criticized for not being exhaustive, as it doesn't exclude superfluous/extraneous items.[4]
Also, MECE thinking can be too limiting as mutual exclusiveness is not necessarily desirable. For instance, while it may be desirable to classify the answers to a question in a MECE framework so as to consider all of them exactly once, forcing the answers themselves to be MECE can be unnecessarily limiting.[5]
Another attribute of MECE thinking is that, by definition, it precludes redundancies. However, there are cases where redundancies are desirable or even necessary.[6]
Acronym pronunciation
editThere is some debate regarding the pronunciation of the acronym MECE. Although it is pronounced by many as /ˈmiːsi/,[7] the author insisted that it should be pronounced as /miːs/.[2]
See also
edit- Proof by cases or case analysis
- Partition of a set for a mathematical treatment
- Work breakdown structure for application in project management
- Algebraic data type in programming, which makes it possible to define analogous structures
- Carroll diagram in logic, which divides a set into partitions of attributes
References
edit- ^ Spencer, Tom (30 January 2013). "MECE Framework". tomspencer.com. Consulting Frameworks.
- ^ a b c Minto, Barbara. "MECE: I invented it, so I get to say how to pronounce it". McKinsey Alumni Center. Retrieved 2019-08-29.
- ^ Pruitt, W. Frazier (May 2020). "Some Assembly Required". asq.org. ASQ. Retrieved 25 September 2020.
- ^ van Gelder, Tim (June 4, 2010). "What is MECE, and is it MECE?". timvangelder.com.
- ^ "MECE vs ICE". faculty.msb.edu. Homa Help Site. Archived from the original on 2019-03-07. Retrieved 2014-11-12.
- ^ Chevallier, Arnaud (2016). Strategic Thinking in Complex Problem Solving. Oxford, UK; New York: Oxford University Press. p. 78. doi:10.1093/acprof:oso/9780190463908.001.0001. ISBN 9780190463908. OCLC 940455195.
- ^ Cavano, Katharina (3 April 2016). "3 Steps to a Faster Moving Sales Pipeline". www.business2community.com.