I came across the concept MECE (Mutually Exclusive and Collectively Exhastive), first put forward by McKinsey's, and it stuck out as an excellent principle to apply repeatedly as I look at proposed solutions. I realise that it is largely a common sense principle and, certainly analytical thinkers, will apply this rule by nature. However, thankfully, not everyone works in the same way and this MECE concept will help me to explain to people how I'm approaching their solution.
If things are not mutually exclusive, then there is overlap. Overlap means muddled thinking and will result in confusion. Collectively exhaustive is more problematic to me as a simple phrase; it needs context - a scope.
Clearly the term does not mean to exhaustively cover everything. Therefore, it must also be intentionally non-exhaustive; in other words, the areas that are not covered are intentionally excluded. It's the same as saying define what's in and what's out and then ensure the solution is exhaustive within the domain.
When we developed our Framework (loosely based on TOGAF) for EA, we took a logical view of the technology areas and were not constrained by the organisational structure or skill sets of people. As a result we achieved the mutually exclusive goal. The starting point in TOGAF pretty much set us up to be exhaustive, although the Framework is not defined to the same depth in all areas. The evolution of the Framework means this will improve over time.
No comments:
Post a Comment