Wednesday, September 30, 2015

Problems with written communication

In life and career, I have faced many problems due to written communication i.e email. Those issues really disturbed me a lot and my career. Did you face issues like that? Have you ever thought of restricting excessive usage of written communication?

If not then it is time to pause and think about it in your life!

I think below are the order of effective communication:
1. Direct communication i.e dialogue
2. Voice communication  i.e Phone, voice mail
3. Written communication i.e email, internet, via media
4. non-verbal communication i.e gesture, dress, body language

Instance 1: 
When I was working with my previous employer, my manager called for quick meeting one day. He conveyed me that our process partner was not happy about my email. I was surprised and asked what email and what was the context? Manager explained me that I used phrase 'that's it' in my mail when explaining something to my process partner due to which they were offended and my manager bashed me for that. 

Frankly speaking, still today I don't know why that was made us such a big issue. Again, if I would have avoided that communication I had been happy that time. Probably, customer might have thought that I'm frustrated to help them that's why they escalated that. What ever, lesson learnt is: Use +ve words in mail comm. instead of showing frustration or -ve words. 

Instance 2: 
When some one is communicating with us, we expect they should respect us, talk politely and request for something in direct communication. But this won't happen in written comm.. For effective written comm. both side should have same kind of communication skills. Otherwise, it would be mess-up. 

So, Lessons are: 
1. Where ever possible prefer direct comm.
2. Don't have mail comm. when you think other end is not good in that
3. Don't use abusive or vulgar or angry words in mail comm. for any reason which could spoil your image and eat up your peace of mind.
4. Never expect respect from others in mail comm.
5. If they comment on you then face it and solve it by calling them

Tuesday, February 10, 2015

Aligning with Org?!

Background

As a developer, I spent very less time in organization level meetings. I never realized that would impact my career until recent time. Yes, I have seen many developers like me in IT used to spend less time attending org level meetings. This is due any or all below reasons:
  1.  Fully occupied in work & no buffer was given to spend time on these events
  2.  Even when I get time, I used that to improve my skill set
  3.  Most of the time these meetings present boring finance and statistics report
  4.  Due to time alignment issues when you work in MNCs
  5.  Used these time for personal task like going bank, calling friends...etc

Why it is dangerous?

Org level meetings are not only conducted to display company performance reports but also companies strategy/goal for the year. A shrewd software developer should keep eye on these meetings as well to align his performance goals with org. If not then he would left out in competition and there would be great chance of loosing job/opportunity.

In my case, I underestimated about these meetings and avoided most of them due to all reasons above. When I stopped following companies/org/section's goal/strategy, I left out without improving skills required for the goal. So, I'm not given any projects (WPF) though I'm the 'Exceeding Expectation' rated guy last year. 

What lesson learnt?

You might be super developer. Exceeds all expectations set for you every year. But, unless you align with companies strategy by attending appropriate meetings, you are left with no opportunity. You may envy and hurt yourself looking your peer who used to be poor performer than you but indulge in many new projects. 

So, friends "start aligning with org goals and stop worrying about loosing jobs!"


Friday, January 30, 2015

Survival of the fittest in IT industry is "Continuous Improvement"?!

I think, it is not easy to survive in Indian IT industry too without continuously improving ourselves.

Until I had been a software developer, I never worried about road maps of my project. Because, my program manager used to bring new projects for us. After I changed my company from pure IT into manufacturing company, I see lots of roles missing in manufacturing company which has smaller software development group. In order to survive in these kind of companies, I think one must:
1. Come up with new ideas which generate new projects
2. Know teams in the company in order to work with them
3. Improve technical/domain knowledge by putting extra effort.

But, why continuous improvement is difficult?

Though many people emphasis the importance of being up to date in software industry, in reality organizations have little interest to train you in latest technologies. They usually create 2 plans for employees:
1) Performance Development Plan
2) Personal Development Plan
The first one is crucial for the employer as it has their development strategies in terms of goals. Also, yearly hikes/promotions are based on the 1st one. Due to which though many employees have plans to develop their skills or aspirations with plan 2, they are left with little time/progress/interest every year. This is definitely leading to less improved employees in technologies and trends. Due to which they are lagging in skill set compared to their peers who by chance working in the latest technologies. If these continues then the person who became lead has left out with plethora of difficulties to generate idea or propose new project.

So, it's time for IT pros to start focusing on "Personal Development Plans" along with their "Performance Development Plans". If those kind of plans are not existing in your company then you really got to have one. Otherwise, you may left out in the fast phasing world!