Hello,

Yes, some other traps that come to mind:

1) Using different units when it comes to quantity, e.g. ounce, kg, lb

2) Using different currencies

3) Using 4,000,000 is one place and ‘5M’ in another

4) Hard to read graphs with a lot of data to filter through

A common skill to develop is to have an attention for details and to be very meticulous in your calculations. It often helps to write things down very clearly with the units so that you don't miss anything!

All the best!

Rushabh

Hi there,

Adding to what Rushabh has written, I can also add these two traps/tricks with math.

1- Sometimes the data available is not enough for you to reach to the final answer, yet you try to figure out what you can do with the available data. Or you may come up with assumptions, which may not necessarily be calculation friendly. Asking for a piece of data can make your life much easier.

2- You reach an answer but as long as you do not compare it to some other reference data, you might interpret this quantitative piece of information in the wrong way. A cost item that is a couple of tens of millions of dollars may be only a very small portion of the whole cost structure.

If you fall into any traps while doing a case, I'd suggest giving the same case to any other case partner and observing their behaviors. Do they get it right the first time or do they realize their mistake and correct it after a short while? Or do they just move on with the wrong answer?

Good luck!

Emre

Things to listen out for / look out for:

1. Differences in units (eg monthly / annually; per customer / per segment)
2. Profit vs revenue
3. Percent difference - what is it a percent of?

Good luck! 

(editiert)

A lot of candidates tend to forget to differentiate between total market and addressable market when dealing with market shares during cases

Hi there,

Typically it's mostly units, zeros (using 000 instead of symbols like K,M,B), and timeframes that cause the most mistakes.

Mario

Good answer above. Just wanted to highlight that these are not really traps. It's just real-life complexity.