Hi there,
1) It is always good to have the 2nd layer so interviewer know you actually have some ideas here. Otherwise anyone can say "the last I would look into risk & next steps". Give some examples of the potential risks. There are a few common ones you can apply based on the industry and the type of case you are solving.
2) If you have time you can go deeper, otherwise just mention in the recommendations
3) There is no fix way of doing this. If having an "action" bucket makes you feel more effective (e.g. don't miss any key points), you can do that. This is not a requirement

Best,

Emily

1. no
2. whenever you make a decision

Hi,

1) Better as a 2nd layer. Your structure should ideally replicate the work streams on the real project. There is no work stream as risks (until you do a complex valuation)

2) Usually, it's at the end of your structure and you never have time to get there yourself. However, it can be an additional question on creativity. You should not necessarily mention it in your recs part, if you have other things to mention (e.g. if you did not have time to cover some important things, I would rather mention these things than risks)

3) Don't overcomplicate. Just propose the interviewer to brainstorm the actions once you find a root cause

Best

(edited)

Hello!

Here are my toughts:

1. Why wouldn´t you have a 2nd layer? I don´t agree with it being hard to list down second layer at the beggining, actually, risks laying out is something quite simple even without knowing the whole case yet.
2. As said in 1, I would lay it out in the structure with some ideas and comment briefly.
3. Both can work, depends on the problem.

Hope it helps!

Cheers,

Clara