Hi Anonymous,

Instead of recap I am rather inclinded to say introduction to what follows (your recommendation) - which must be kept as short and to the point as possible and often takes less than 10 seconds.

Why? Because the CEO to whom you are pitching this recommendation might have 10 strategic projects he is concerned about, and it's alsways good to set the stage and give appropriate framing/context to what follows next (your recommendation), so that everyone at the table knows exactly what you are talking about.

Hope that helps - if so, please be so kind to give it a thumbs-up with the green upvote button below!

Robert

In your summary, focus on the results, not the process. Your structure could look like:

• State the problem statement - in one sentence only
• Then give your overall recommendation, also only in one sentence
• After that, support your recommendation with your key findings
• Close with an outlook on next steps, i.e. what you would analyze if you had one more week for this to further detail out the recommendation and assess potential risks

Make sure to not add any new content in the recommendation that you haven't discussed/analyzed during the case.

Hello!

In my personal opinion, less is more in the final recommendation.

Try to keep it as short as possible, so it´s punchy.

If the words you are adding don´t add much to the message -those in the example don´t-, then spare them.

Hope it helps!

Cheers,

Clara

Hi there,

Yes and no. Your example is far too long! Cut all the words that don't matter (in everything you say). "The task is...based on our analysis, we discover that"....not a single word there adds value!

Rather say "When evaluating x decision, we recommend y"

Hi there,

no need to go very deep and recap all that's been said.

• justify your recommendation
• be on point
• answer the question
• summarize

Hope it was helpful!

GB