Get Active in Our Amazing Community of Over 451,000 Peers!

Schedule mock interviews on the Meeting Board, join the latest community discussions in our Consulting Q&A and find like-minded Case Partners to connect and practice with!

Issue Tree or Conceptual Framework

Framework Structure
New answer on Apr 11, 2022
4 Answers
752 Views
Anonymous A asked on Apr 09, 2022

For those of you, who have interviewed people especially in candidate led interviews … what is preferred: Issue tree or conceptual framework for the beginning of the case? 

There is a lot of conflicting advice out there! 

Overview of answers

Upvotes
  • Upvotes
  • Date ascending
  • Date descending
Best answer
Moritz
Expert
Content Creator
updated an answer on Apr 09, 2022
ex-McKinsey EM & Interviewer | 7/8 offer rate for 4+ sessions | 90min sessions with FREE exercises & videos

Hi there,

First of all, any well structured conceptual framework can look like an issue tree. There’s just one major difference with regards to the “issues”:

  • Areas of analysis: If you’re going to use your structure as a blueprint for exploring and discovery, you will have to produce a well organized and prioritized list of items that you will analyze throughout the case to get to the bottom of a problem and find a solution. These items can be a bit more high level. This is what you would typically refer to as a framework.
  • Concrete ideas: Sometimes you’re being asked a direct question e.g. “What do you think could be the reasons for x happening?”. In this case, your structure is not a blueprint for later analysis but rather a well organized list of concrete ideas or rather hypotheses (because you can’t know yet). You’re essentially answering a question. It’s therefore important to not be generic or too high level here. This is what you would typically refer to as a MECE issue tree.

The above distinction is hugely important because I often ask candidates for concrete ideas and get a generic structure, which is inadequate.

Anyways, what’s the difference between conceptual frameworks and issue trees in your view? Let me know and maybe I can provide a better answer!

(edited)

Was this answer helpful?
Matteo
Expert
updated an answer on Apr 09, 2022
McKinsey & Company | Currently offering 1 free coaching session| Happy to PARTNER with you to get an offer from MBB

Hello, 

thanks a lot for the question. :) 

I would say the issue tree is the preferred way to structure the case. There are 3 main reasons for that: 

1) Higher flexibility → Since it is a way of structure your reasoning, it can easily be adapted to every kind case

2) Higher effectiveness in testing a specific preliminary hypothesis → It allows to build a structure more tailored to the specific business case and to the hypothesis you are testing

3) Better impression with the interviewer → It gives the positive impression that the candidate has a good business sense and he/she is not using the same framework for every case

Having saying that, I think it is important to clarify the things in common and the main differences between the issue tree and the conceptual framework (e.g., profitability framework): 

Things in common

  • Origin: the “specific conceptual framework” concept is born from the more specific “issue tree” concept. They are not MECE and there is no conflict between the 2 terms. For instance, the profitability framework is just an example of the many possible issue trees. Generally speaking, we use the term “framework” to refer to a very specific and standardised issue tree (e.g., profitability framework)
  • Main objective: test the initial preliminary hypothesis
  • Top down structure: from general to details

Differences 

  • Degree of standardisation: the issue tree, being a more general concept than the conceptual framework, allows for an higher level of flexility. In particular, the element of the overall structure (e.g., preliminary hypothesis; bucket testing the hypothesis etc…) are not already set

To conclude, I would strongly suggest to practice in the creation of very effective and specific issue trees. It is a good way to convey a strong positive impression to the interviewer at the beginning of the case. And as we all say… there is not a second chance to make a first good impression :) 

Do not hesitate to reach out me in case of further questions! I am currently offering a free coaching session.  

Good luck!

Matteo

(edited)

Was this answer helpful?
Cristian
Expert
Content Creator
replied on Apr 11, 2022
#1 rated MBB & McKinsey Coach

Hi there,

From my point of view, neither. 

Ideally you should apply first principles thinking here and develop a muscle to actually think through the cases individually rather than relying on set frameworks. It's obviously harder, but it's a not only a sure bet for the interview, it's also good training for the actual job when you'll get to do it. 

Was this answer helpful?
Ian
Expert
Content Creator
replied on Apr 10, 2022
#1 BCG coach | MBB | Tier 2 | Digital, Tech, Platinion | 100% personal success rate (8/8) | 95% candidate success rate

Hi there,

Quite frankly you should do the one that you are most comfortable with!

That said, I prefer a framework because you don't really have time to do a proper full issue tree. Additionally, if you do your framework right, it should “sound” like an issue true (each sub-bucket has a purpose/flow). If you're just listing out words/ideas you're doing frameworking wrong!

Was this answer helpful?
How likely are you to recommend us to a friend or fellow student?
0
1
2
3
4
5
6
7
8
9
10
0 = Not likely
10 = Very likely