Why do the case examples not use Issue Trees often?

Question

Hey this is a super basic structure question, but just went through all the material on this site instructing that the first step you should create an Issue Tree structure. Then I went through the case examples and see that this is not done often in the suggested answers? Am I missing something? Any help would be much appreciated.

Thanks!

Answer 1

Hi,

There are many ways to structure a case, not just an issue tree:

Mathematical (issue tree)
Workstreams (Buckets with bullet points)
Value chain / process / customer journey, etc
Segmentations
Frameworks
Project steps
Mix of them

You should be flexible in your approaches. Every time you build a certain structure you should take into account:

The objective of the case
Context
Type of the case

Best!

Answer 2

Hello,

In the case examples here on Preplounge the issue tree is always replaced by "Diagram 1 - Case structure". Anyway I agree with you that a proper framework is missing and I always suggest my candidates to write down a real Issue Tree structure. During real interviews a structure like the one proposed in the examples is not enough.

If you are struggling with frameworks and you want to discuss them, feel free to write me.

Best,
Luca

Answer 3

Agree!

This is a key part of 95% of the interviews. I encourage you to practice it always.

Here is sometimes substituted by "Diagram 1 - Case structure", but it´s not the same.

Hope it helps!

Cheers,

Clara

Answer 4

Hi,
unfortunately, most of the cases do not show an issue tree, probably because difficult to draw in a document. I recommend to approach every case with an issue tree and to show it to the interviewer. It is a powerful tool largely used by consultants in brainstorming sessions and much appreciated if correctly used during your interview.

Best,
Antonello