Final Round Feedback - Actionable Tips

Hi there - 
 

Great sign that they liked you as a candidate — that means this is a narrow, more fixable gap (and it's one of the more coachable ones), not a personality or fit issue.

The core structuring problem for you here sounds like it's prioritization and communication. At final round, interviewers assume you can build a framework. What separates candidates is whether your buckets are the things that actually move this specific business, not a generic tree. Three things to practice:

• Lead with the objective and the metric. prioritization doesn't come from just the structuring exercise itself, it comes from what you do before that as well. Before drafting anything, use clarifying questions to pin down what success looks like in numbers for this client — a target margin, a payback period, a share figure. Every branch of your structure should visibly serve that number and/or goal. Anything that doesn't is the "irrelevant" stuff that feedback flagged.
• Pressure-test with "so what?" After each bucket, ask whether analyzing it would directly impact the recommendation. If not, drop it. This is the single fastest filter against irrelevance.
• Talk like the client's advisor, not an interview candidate. Imagine the CEO is across the table and will act on what you say tomorrow. That instinct naturally filters out generic, academic points and pulls you toward what's decision-relevant, phrasing each bucket in more conceptual terms than in generic labels - e.g., phrase buckets as a question tied to the actual decision (e.g., "Is the new plant's cost per unit low enough to beat imports?").
   

On unfamiliar industries: you don't need industry expertise, as you can (and should, when necessary) ask clarifying questions on the client's business model - i.e. how they generate revenue. What you need to be able to do, regardless of industry, is to anchor your structure to the client's specific objective and reason from first principles — e.g., is this market attractive, can we capture enough share, etc. — rather than reaching for sector jargon. Interviewers reward sound logic over insider knowledge every time.

I'd suggest doing targeted structure drills on your own, and then do a handful of structure-only exercises with a coach or partner where you ask them to grade only relevance and prioritization. 

Best of luck, and please don't hesistate to reach out if I can be of further help.

Hi there,

That feedback usually means you were close: it’s what strong candidates hear when the gap is small and fixable. To answer your two questions:

1. Fixing “not the most relevant points”: the gap here is business judgment, not structuring technique. Your tree was clean but generic, so it didn’t isolate the two or three drivers that actually move this business. What I’d recommend:

• Study real businesses. Read how specific companies actually make money (annual reports, earnings calls…) so you build a feel for how different business models work and where they’re vulnerable.

• Force yourself to name what moves the needle. On any prompt, before building the full tree, decide which few drivers would genuinely change the outcome for this business and lead with those. Most candidates lose relevance by being exhaustive; the skill is backing the handful that matter and cutting the rest.

2. Structuring an industry you don’t know: you don’t need sector expertise, and interviewers don’t expect it. Reason from the business model, not from memorised industry knowledge:

• Open with a clarifying question on how they make money. One good question (“who are the customers and how do they pay?”) gives you enough to anchor a structure, and it’s expected, not a weakness.

• Tie every branch to the client’s objective. A branch earns its place only if it helps answer the specific decision. If the goal is “should we enter this market,” your branches serve that call (is it attractive, can we win, is it worth it), regardless of sector.

Hope it helps, and feel free to DM me if you have any doubts or think a quick chat would be useful.

Federico

Your issue in the final round wasn’t structure in general, it was relevance. Final‑round interviewers don’t want a big framework; they want the two or three points that actually matter for this business problem. The way to train that is simple: practise forcing yourself to choose only the most important drivers.

The best exercise is to take any prompt and ask yourself: if I could only analyse three things, which three would move the outcome the most. This builds business judgement fast. Another exercise is to rewrite your frameworks as short problem statements instead of categories. It keeps you closer to the core of the case and stops you from drifting into far‑fetched points. You can also practise with industry summaries and turn each into a tiny structure, which helps when you don’t know the sector.

Best, Alessa

Hi,

Rejection is never easy - I was also rejected from R1 from one of my target MBB firms before I got the offer from another. 

I think one important thing is to understand that at a generalist level, they are not testing your industry knowledge but rather core problem solving skills. 

Your question on how to get better at frameworking and thinking about problems is the struggle that every candidate faces and that only 1-3% of candidates manage to demonstrate successfully. 

The answer is that you have to firstly understand what is the right problem solving process, and then be able to train up the ability to think in that way. 

The reality is that the theory is not complex or complicated, but the execution of it is tough. In my opinion the only way to improve it is through having a quality feedback loop. Because the specific errors you made can only be identified and discussed based on what you responded, not by generic advise online.

All the best!

Hi there,

First of all, I am sorry to hear about the rejection from BCG!

I would be happy to share my thoughts on your questions:

• First of all, contrary to what other coaches have said, I would strongly advise you to first verify for yourself whether the feedback is appropriate. Considering that you passed the first interview round, unless you think yourself that your case study performance was weak, it likely was at least fine enough.
• Moreover, if the feedback is appropriate, contrary to what other coaches have said, I would strongly advise you to consider working with an experienced coach like me on your structuring skills. When you get the feedback that certain aspects weren't relevant, it is not about industry knowledge, but about your approach. I developed the "Case Structuring Program" to help exactly such candidates like you who struggle with case study structures.
• Lastly, for industries you do not know: contrary to studying individual businesses and how they make money, I would stronlgy advise you to either have a look in a business school case book for an industry overview, or generate your very own with the help of GenAI.

You can find more on this topic here: How to deal with a rejection from a consulting firm.

If you would like a more detailed discussion on your specific situation, please don't hesitate to contact me directly.

Best,

Hagen

Hi there. Wow I was exactly in your shoes during my MBA summer internship rounds. BCG final round, didnt get it, needed to be better at casing and structures. The reality is that you need to practice, and you need someone to really give you pointers and feedback on the parts you're weakest at. Rather than try and write it out, I suggest using a coach (I did, and it helped me tremendously and got an offer during the full time rounds after significant practice). Let me know if I can help!

You do not need deep industry knowledge to build a relevant framework. You need first-principles thinking.

The real challenge is asking yourself what actually drives money and operations in that specific business model. Before drafting branches, pause for thirty seconds and ask: "How does this business make a profit, and what can break?" Focus on three tailored drivers instead of six generic buckets.