When one is an engineer, there is usually only one correct answer. The best answer. And it can be proven that that answer is correct, and the best. An engineer usually emphatically and vigorously puts forward his answer, his solution. Not so when you do MBA.
MBA teaches, rather forces, you to use vague, uncertain words and phrases such as "might be", "could be", "it is possible", "perhaps better", "likely to be", "uncertain business environment", "perhaps more important", "it depends", and other useless bullshit. Not only that, MBA forces you to use fancy concepts [the sandwich approach, for example] to put forward your thoughts or criticism or feedback. It also forces doublespeak and euphemisms deep down your throats ["your stupid mistakes" turns into "areas of improvement for you"] ["reduced profits" becomes "compressed profits"]. Finally, it makes you use crappy jargon such as "kickoff meeting", "leverage", "basis points", "opportunities", "synergies", "deep dive", and so on.
Frankly, MBA destroys the engineer in you. Or at least it tries. It's up to you to make sure that you only let in good stuff, and keep the bad stuff away from you.
That being said, and to be fair, it's important to remember that all of these fake words, fake tones, doublespeak, etc., that I've mentioned above are not only useful in the real world, but also necessary. It's important in real life, for example, to "manage all your stakeholders" and "to set expectations", so to say.
I have always been clear in my mind that I will not let my MBA make my language vague. I have always believed in and exercised straight talk and clear thoughts, and I will continue to do so [unless, of course, MBA-like language is absolutely necessary to get a particular work done]. I have used direct, un-MBA-like language in this post too :)
I am Rishabh Singla and I approve this message.
MBA: National University of Singapore
MBA: Korea University Business School
B.E.: Delhi College of Engineering [University of Delhi]