Business to the Buddha

Tag: Prof Boman Moradian

  • Journey itself is the destination, so learn non-stop…







    As a ritual which every B-school aspirant has to perform, I also wrote B-school essays before joining my MBA program. I remember one of the phrases of one essay the most – “…making mistakes that will cost nothing in a classroom environment…”. I knew I will learn from the mistakes as well. I feel, a failure teaches long lasting lesson then a success. I have learnt a lot from the mistakes during last couple of months. I am sure, I am going to live with and implement these learning in coming time.

    With a lot of disappointment I started writing this blog after my exam of Pricing Strategy. Then I realized thank god I did not commit the mistake in business; one incorrect pricing and revenues and profits take a beating. I started writing my mistakes and learning, so that I can revisit what I should not do and what I learnt. This would remind me that the Journey itself is the destination, so learn non-stop. Here are few of the lessons –

    1. Never believe in the forecasts, forecasts are correct hardly 15-20% of the times. I bet Murtaza and Avanii would agree with me 100% on this.

    2. Start early (in B-School simulation too), starting early and keeping the momentum going; it helps

    3. Always have a “to do list” and prioritize work – for this I wrote funny statement which only a few could understand “Tomorrow is your exam (sense of urgency), day after tomorrow you will die (prioritize your work, before dying what would you do?)”. I used to do this but here in my MBA this has been reinforced to an even greater extent

    4. Failing to score well in exams is alright, but failing to learn a concept and missing to use concept is a punishable offence – “a crime”. I learnt pricing strategies concept, explained the same to my friends and yet in the exam forgot to apply that. There is no ifs and buts for this crime

    5. I always write my blog on one concept ‘collaboration’, I observed this in outside world, I used it a lot in my MBA and that is the way for the future of businesses

    6. Ask questions, better to be stupid for some time. I have been stupid in some classes (recently, in class of Prof Lopez and Prof Ram Kumar) but that is better than assuming something incorrect

    To be continued in next blog…

  • Six Sigma failed…







    “Not invented here syndrome” is like making a statement to Prof Moradian or Prof Natarajan that your forecasting methods is flawed it does not work in my industry, company or department. Is not it prudent to ask if it worked somewhere, how did it happen? Let us take an analogy –
    Organization = Laptop
    Department = Microsoft Excel (MS Excel)
    When I make a statement–
    “You know what,
    1. Mathematically, 2+2 is not equal to 4 in MY MS Excel therefore Mathematics is flawed
    2. My MS Excel is different from the rest of the world because 2+2 in not equal to 4 in MY MS Excel
    3. My laptop is different from the rest of the world because 2+2 in not equal to 4 in MY laptop”
    If 2+2 is not 4 in your Excel it is not that the math is incorrect, perhaps your algorithm or your laptop processor is at fault. In this analogy Mathematics could be Six Sigma. I have heard that IBM failed in implementing Six Sigma (late 80’s to early 90’s), GE is extremely successful, why?

    Lately, in one of our simulation class Akshat’s team questioned “why Six Sigma failed in our company in the simulation?” one of my teammate wrote on facebook – “After 3 round of simulation today Pravin Krd accepted the disadvantage of using six sigma as corporate project :-)”. I went back to basics to answer this question. What is six sigma? Six Sigma is about vision, philosophy, management system and achieving aggressive goals. Six sigma is also a toolbox and a means to satisfy customers. If Six Sigma fails in an organization it could fail due to – improper vision or management, issues with the goals or incorrect use of tools. The basic philosophy of Six Sigma is reducing defects, how can reducing defect be a failure in a company? If I ask you what you would prefer “good enough” with 99% accuracy or 99.99966 what would you prefer from the following?

    Three sigma (99% accuracy) processes –
    5,000 incorrect surgical operations per week.
    2 short or long landings at most major airports each day
    Six Sigma (99.99966% accuracy) processes –
    1.7 incorrect surgical operations per week
    1 short or long landing every five years

    Naturally, your answer to this would be better accuracy. Six Sigma is all about facts and working logically to reduce defects, and what follows is reduced cost, customer satisfaction etc. I am not a Six Sigma guru or I am not professing it, I am only trying to put some facts – “the six sigma way”. Experts can jump in and suggest or inform why six sigma could fail and share success stories.

    Source –
    Breakthrough Management Group India training on Six Sigma certification. This Data was a sample from USA.
    Class Blue ocean strategy simulation (BOSS)

  • Every problem is a nail… if you only have hammer in your tool box!







    In a class of Prof Moradian we were learning about a model, a model which had two dimensions. Each axis has ‘Low’ and ‘High’ as the extremes. I have learnt that for few thing quantification is not necessary, ok! When I saw this combination of ‘Low’ and ‘High’, I understood it is a qualitative measure. I waited for two minutes (a long duration for struggle in mind), at last a typical attribute of a classic personality came out.
    “Sir, how do I define a number is ‘Low’ or ‘High’ on this model and on the scale?”
    I took two minutes because I struggled to put this in my mind – ‘do not try to quantify everything’. I was thinking quantify or not to quantify? It was equally a struggle for Prof Lopez to teach me – don’t try quantification of everything. Old habits die hard! Six Sigma taught me to be data centric and this struggle has always been in mind – clarity with data or instinct with less or no data (I worked as TRIZ/Innovation consultant). Seemingly two different approach six sigma data centric and innovation instinct based.
    I knew it is qualitative, and Prof Mordian said – ‘Pravin, it is not necessary to quantify this measure, come out of the engineering mind’. To save my face I can say I was just questioning my assumptions, you may check possibility thinking and questioning assumptions blog.
    Let me come to the “classic personality” type. Personally, this incident was making the same mistake (of course learning from that too). The trait I want to highlight here is ‘engineerish’ e.g. engineer and mathematician type thinking. What else can you expect from an engineer – numbers, data, technical details and much more concrete information?
    Here, I came up with few future blog ideas of Blue ocean strategy, frameworks and problem solving. I will try to cover them in future. As I wrote in my introductory blog, not necessarily every blog entry will be on relation between Business and the Buddha. I will not offer correlation here, though I can do that. For a change I would quote a real life example which many of us are suffering from –
    Dr Mankad taught us in class of Macroeconomics that – few bright engineers turned MBAs have created many models e.g. financial models that ‘quantified rationality/irrationality’ which became one of the worst problems and resulted in the melt down.
    So, I write here a cliché of many management consultants – Every problem is a nail… if you only have hammer in your tool box! I also encountered it many a times. It is occasionally a struggle to pull people out of their thought process and make them realize that – some problems are not nails. Our myopic thinking can be summarized in (again a cliché) joke to explain the issue –
    Once mechanical, Electrical, Chemical and Computer science engineers were traveling in a car. Suddenly the car stopped and everyone was puzzled. Mechanical Engineer suggested that that there is some problem with the engine. Electrical Engineer suggested that it is due to the fault in ignition system. Chemical engineer said “no-no car was making some strange knocking and the problem was with the fuel.” Suddenly the computer science Engineer intervened and said “I think we need to go out and then come in the car (log out and log in).”
    The message is …
    “Every problem is a nail… if you only have hammer in your tool box!”
    And the lesson – “Because you have a hammer, don’t go searching for a nail”!!