Emotions and business:
I am back to blogging after a hiatus. I relocated from Singapore to Noida, left Barclays to join Cadence... to complete it, I am back to eternal happiness :-).
OK, let's focus on today's topic. Whether you love it or hate it, emotions are an integral part of business these days. Obviously, depending on how one uses/misuses/abuses them, they may act to the advantage of disadvantage of onself, and of course, the business, at large.
Let me tell you my inspiration behind this write-up. I (re)joined Cadence about a month back, and in the last few days, I created about 20-odd CRs on my product (the product for which I have been(re)hired.) The CRs were on the user-guide, tutorial, workshop, software, and use-model. This did not go well with a few people who thought that I am proving a point to the management, or playing around with the product without taking them into confidence.
I agree that the politically-correct way would have been to discuss my observations with people who have more experience w the product, and then bash the product. However, when it comes to business, I am an emotionally malnutritioned bloke. I have only one objective at work -- business. I am critical of the emotions of my colleagues, and give due reverence to them only when the emotions translate into passion.
A problem that I see is that people start associating themselves with their products. That is suicidal. A product and a person who owns that product are different entities. I am hired to take this product to the zenith, and in the process, if I happen to strangulate the existing version of the product, great! However, if people take it personally, I am sad... for them... but definitely not regretful.
Labels: Emotions and Business.

2 Comments:
Agree and disagree.
Agreed on being true to your work and others being emotional/too_attached with their work.
Something which dont affect too much to the end-user (cosmetic in nature) might be a low-hanging fruit for somebody trying to find faults, but might not affect the long-term goal of product improvement. It may create a perception of improvement, but is too far off from it.
Most of the product developers want to work on something which actually makes a difference to the long term improvement to the product (read enhancement or critical bug). Thats why it may create a conflict of interest between two parties involved.
Better things should be to file these CCRs, but with a correct perspective that they are improtant but not critical. (in other words SHOULD but not MUST)
I would agree. But then no one said that the ride to taking a product to its zenith is going to be easy. It is my experience that people blocking progress are present in every company, in every group, everywhere. And this problem is not just in IT. It is the human being in general, irrespective of nations. We should agree to disagree and try to find a way amongst the plethora of disagreements blocking us :-)
Post a Comment
<< Home