Is the problem-solving approach MECE?

Respectfully, and even while I'm not a coach officially, I would urge you to:

A] Get a coach! You need to re-align your Prep strategy and your learning goals asap! 

B] Stop practising with whomever is/are reinforcing certain bad habits which suggest themselves just by the manner you have posed your question.

It is not possible for me to answer your actual question, but I will address the unasked questions which, in my estimation, take precedence. The two unasked questions are centred around Communication and Case Prep strategies.

1) Your communication needs critical work!
At a minimum, a consultant's communication needs to be:

• top-down
• issue-driven
• directionally-linear

This is absent in your posting and will serve you poorly in interviews. The communication layout of your post would inspire distraction in most and impatience in many because it bears the following flaws:

a) The posting doesn't clearly establish all the questions you're trying to ask upfront. In other words, it is not top-down.

One is forced to dig, re-read, re-frame, fill in the gaps and then, guess (at best) that you have two questions you're asking: 

I - What is the best way to map Case prompts to effective frameworks/issue trees? and

II - Can you guide me on the effectiveness  of the framework I provided for the following Case of XX doing YY with ZZ? Metrics of effectiveness could include its ‘MEness,’ ‘CEness,’ hypothesis-driven approach, et cetera.

This roughly top-down manner is essential to set the tone for your query and signal to your audience that they know the critical questions and are about to be provided with critical context.

I can't see any happy outcome if you were to communicate in this manner in an interview. And while I know this is not an interview, the near-total absence of a top-down approach concerns me.

b) The posting omits or misplaces some of the most critical information to be considered in order to render an effective response. Consequently, the main issues are not clearly identified and cannot drive the narrative.

Unless I am much mistaken, there is no text of the actual Case Prompt for which you sought validation of the provided framework. This is a tell-tale sign that your Prep approach is focused on framework-memorisation and not on organic problem disambiguation.

(By the way, problem disambiguation is just a way of saying I want to break the problem into distinct components that can be analysed efficiently: for example, most Cases on examining Profitability of an entity would ‘disambiguate’ Profitability into Revenues and Costs as a starting element)

But back to why this matters. 

I find little context here to tell me how to disambiguate the initial problem and start driving towards the solution. Let me offer a rather indulgent analogy to illustrate why no two problems are alike and should therefore attract targeted solutions as opposed to plucking things off the shelf. If I came to you randomly and asked you the best way to cook a Steak dinner. You might look at me quizzically and say, "Well, I'm missing a  bit of context here: what's the actual cut of the Steak you're planning on cooking? Depending on the cut, my advice could differ dramatically. What cooking utensils are available: good oven? Cast-iron pan to do a reverse sear? I normally tell people to stick with a traditional sequence, but depending on what you have in your kitchen, you might have to do a reverse-sear and keep a closer eye on internal temperature which in the oven. What vegetables are in season to build the right pairing sauce? If you can get those wild Chilies with a bit of heat and the weather is right, a grill would be the way to go. But it it's going to be a conventional creamy mushroom sauce, you want to be more subtle with your cook. What are the preferences of your dinner guests: rare? medium-rare? And so on and so on.

Context matters. Depending on the combination of answers in my little analogy, we could be looking at several different options. All for the same Steak question.

For discerning consultants, no two Merger studies are the same…neither are any two Acquisition studies. Don't fall into that trap of saying to yourself, “Oh, this is an M&A Case; it needs 4 buckets, here they are.” 

c) The posting lacks linearity in a most distracting manner.

Cases, business conversations, and client presentations should proceed as time does: linearly and unidirectionally. Discourse that deviates from this will lose your audience's attention span.

While reading your posting, some of my emotions were as follows: 

i) You said "I find the bucket feasibility a little confusing, since market attractiveness…"

…which made me wonder: are we critiquing Casebook Case frameworks? I thought we were talking about a structure that is MECE that you wanted us to look at?

ii) Where is this framework we should be looking at? Oh, you already stated it above when you said, “The framework consists of feasibility, target company and financials (synergies).” Except, I find out later that it's actually not the framework you wanted us to consider. You saved the best for last (which you should never do in Consulting! Best is first and second-best is next).

iii) You said “I assume then this problem solving structure is either not complete, or it is not a framework for the case?” which again made me go back to see if you had provided the reference Case prompt. You hadn't.

At this point I gave up. But then I realised I could do better than giving up,  so, I tried to re-frame the conversation around questions you hadn't asked to create a related teachable moment.  

2) Your Case Prep strategy needs critical work!
For reasons that have, in part, been outlined above, your Prep strategy is reinforcing some bad habits which you need to stop. In addition to the Communication and other Communication-related lapses, I see that you are:

a) Boling the Ocean and hoping that some of that ‘ocean vapour' will resonate with your interviewer and score you points. Problem disambiguation and issue prioritisation (among other things) is why clients pay consultants millions of dollars. They don't pay them to choose from one of Mike Consentino's Case frameworks and apply them to the Case. If that's all it took, client engagements would be shorter, easier, and less prestigious. 

So, what can you do?

Switch to customising standard frameworks to the Case prompt at hand and supplementing the customised frameworks with additional elements that tie to the problem. Less of the cookie-cutter models is usually more.

b) Not driving the Case structuring with a hypothesis. This does not mean you need to state something explicit up front; rather, you should lean towards designing frameworks that drive in clear directions. Directions which make the case For or Against clearer and clearer as you progress.

So, what can you do? 

Get some coaching to explain the best way to open Cases, identify the main problems, establish a working ‘hypothesis,’ and build a structure that supports all those elements.

c) Believing, as many do, that Recommendations are an element of problem disambiguation. How can they be? Going back to my cheesy Steak analogy, the final result which my dinner guests see on their plates will be a reflection of all those questions I asked earlier. But the plate contents are an outcome. They are not ingredients that were added during the cooking process.

Having a ‘bucket’ of recommendations illustrates that the candidate may not have fully grasped why he or she is performing the analysis and how each new insight unlocked throughout the analysis is what ultimately builds the recommendation.

So, what can you do? 

Get some coaching or find better Case partners who have a more grounded perspective on what Case excellence looks like and who can guide you towards that.

If the tone if my response is overly-critical, please understand that it is not directed at you personally. It is merely to call attention to critical blind spots and re-align you for success.

EDIT: I may have missed that the actual Case prompt was included as a link. Great!  :-)

(edited)