We find many candidates drown in feedback. They want as much good feedback as possible and speak to as many people as possible thereby receiving lots of detailed and sometimes average feedback on their performance. There are two problems here. First, much of this feedback will likely be contradictory and possibly misleading. Second, the candidate will literally drown in this feedback usually consisting of a 2-page list of improvement areas. We expect our candidates to always prioritize the top 3 issues and tackle them, as explained in this podcast. It is vital to follow this 80/20 principle and ignore the majority which will be of little value overall.

Candidates sometimes divulge too much confidential details, or too little in interviews, resumes, cover letters and LinkedIn profiles. These are the rules for disclosure. It is important to remember that disclosing confidential information merely indicates to McKinsey that you cannot be trusted with their own client information. Moreover, disclosing information on your resume and hiding it from your LinkedIn merely means you are aware of the ethical breach you are making. It is important to avoid these problems at all costs. From the beginning, be the person that is worthy of a consulting firm.

Building hypotheses is very difficult. Most candidates in a McKinsey, BCG et al interview would not know when to build the hypothesis, what comprises the hypothesis, how to test if it is MECE etc. This simple technique is one way to build hypotheses and used on real consulting engagements. It was developed to help candidates prioritize their analyzes and ensure the hypotheses are MECE. When practicing this technique note that the development of the decision tree must be done quickly and cleanly.

Far too many candidates focus on being faster. That is another myth. Speed is an outcome of having good technique. So if you are slow, deconstruct your technique, analyze weaknesses and develop a new way to solve arithmetic. That is key. Unless your technique improves aka "your process to solve math," you will never improve. We explain how in this podcast. Moreover, if an interviewer or practice partner indicates you are slow, think carefully if your technique can be improved, versus merely trying to speak faster. Note, there are many different techniques to solve arithmetic problems so do not search for the "best" technique. Find one that works for you..

The myth of demand side estimation cases is the greatest mistake taught in case books worldwide and is probably the worst technique a candidate should be using. Candidates around the world are taught that all estimation cases are market sizing cases and all market sizing cases must be done from the demand side. The problem is that not all estimation cases are market sizing cases and not all market sizing cases should be done from the demand side. Fortunately, it is easy to fix

Solving a case while talking an interviewer through your thinking (written or otherwise) is, for the interviewer, a little like trying to understand a presentation without seeing the slides. Or at the very least seeing untidy slides – that is, assuming your working sheets are messy. Here we talk through the anatomy of a case dialogue pointing out key mistakes candidates make and a very simple technique they can use when communicating in case interviews.