Lessons to be learnt from Mr.Narendra Modi for IT Management

I have been always a keen follower of Mr.Narendra Modi's (Renowned Indian Politician) thoughts on his governance, growth and development methods. 

He has recently become a more impacting and youth driving + motivating sensation in India, with millions of motivated youth from urban and rural parts of India following him and wishing him to be next PM of India. 

The few lessons that he conveys to public in his rallies are of such unique but brilliantly vibrant that they can be applied everywhere to give astounding results. I wish to derive the learning aspect of his speeches to devise methods that can make IT Management a very focused route in order to benefit all i.e. client, team, ourselves and employer respectively.

So here are the points:

1. Never Think of Becoming Someone rather Think of Doing Something: This mantra tells us the root of success in life. When a person thinks of becoming somebody important with power or prominence, it can hurt sometimes if the dream is not accomplished because not always you get what you want, not always the results of your hard work pays in the same amount you toiled for it. When this failure is encountered a person might get demotivated in life and can lose the sight on goal. Rather if you think of doing something which has importance, it motivates the person to deliver in short term goals which progressively leads the person to the larger goal and ultimately success. At times if a person loses the sight of short term goals or feels demotivated he can easily come back by realizing his stagnation or turmoils or mistakes. So now how can I apply this in managing an IT workforce. If we set target for our teammates on short term goals like automating parts of functionality each week, developing this part of code each week rather than giving them a bulk task of automation of complete payment procedure or developing code for complete checkout process. If we break the task it is easier to manage. In the same way if we think of earning a post of Delivery Manager we need to see that how well we are able to understand the basics of development while we are a novice developer, how will we advance on my skill set this year and how will I learn to mentor our juniors next year. Slowly like this when we pass the successive year we can later focus on leading team, innovating ang try to give value to client and then save company cost and increasing earning revenue. Working in the direction of doing something with excellence leads us to position of excellence and once this work habit is developed nobody can stop us from personal, social or organizational growth.
2. Never look upon someone, never look down on someone rather look collectively towards achieving a goal: This suggests that we should neither look over somebody with self-proclaimed superiority, nor we should look over somebody thinking that he or she is weak, without self-decisive point of view. Rather we should look in ways that how we can contribute with him or her in order to achieve a common goal together. If we waste our time in petty hatred building views in a group or team we can never succeed both personally and collectively. In a team we should try to allocate jobs as per person's dire interest and fore-see how this allocation can be done in order to collectively drive the team towards its set goals. For example if there is a young programmer who does not code well but is good in criticizing other people's code and on the other hand there is a software tester who can find discrepancies in code. This young programmer and tester would normally in real world be asked to continuously do the same job on  daily basis even though there vested interests are in opposite roles. But if we don't look upon or down on there performance and adopt a collective approach of problem solving keeping the interests of our code base quality as the benchmark of success we can easily switch the roles and see if this really works. If it works it is good for the team and them if not we can see how there roles can be slightly modified so that they can become code reviewer and software developer engineer for testing respectively. Thus solving both the problems and creating a win-win for all.
3. Life is choosing between intense hard work, hard work and smart way of working:  People can do the jobs in 3 ways, people  achieve their goals in 3 ways, people life is also governed by these 3 ways i.e. by doing intense hard work, or by doing hard work in general, or by doing work smartly. Suppose there is functionality to be tested this can be done by covering all the test scenarios manually on all the required platforms by working day and night i.e. intense hard work. This can also be done by combining automation and manual testing by covering all scenarios on all platforms i.e. hard work.Third is using cloud based automated test environments for test scenario execution in parallel yet covering all the scenarios. So the essence is that no matter hard work is always rewarded but smarter way of doing work is appreciated, it saves valuable time, earns benefits and above all develops a way of thinking to do things unconventionally. This out-of-the-box thinking makes us smarter and helps us in making our work more efficient and productive. 
4. Come together to Grow together: If we come together in a team and participate in each and every decision taken by the team management whole-heartedly we have better chances of succeeding together. Rather if people within the teams are divided in sub-groups who does not keep their points or discuss their issues going forward in a particular direction it becomes difficult for all to come together and work towards a team goal. Slowly all members lose interest and neither the team goals are achieved nor the individual goals are achieved. But if all members discuss things and resolve issues beforehand and then work towards a goal whole-heartedly it increases the probability of succeeding. Effort should not be made in the direction of avoiding or alienating team members if they are not willing to co-operate but towards finding ways so that all come together for the same.
5. Freedom to Work as per own's interest for some part of the day:  I personally have experienced the same in my team once. There was Software tester in my team who liked to think about new product designs and innovative products he always was full of wonderful ideas to discuss. But he was going nowhere with them as his job was just the mobile apps for the client. Once a manager thought of giving him some time to analyse the mobile apps and provide some feedback. After 2 days the draft version of app features suggestions he proposed were so marvelous that client's marketing head wished to meet him in order to work on the same ideas he proposed. This is the power of doing what we like doing the most. In IT companies if for identified individuals who have shown some interest based caliber in doing something different that in turn can benefit the project/product should be encouraged.
6. Growth for all is the solution for all problems: In a team if there are 50 IT specialists, then a lead or manager should have a plan from beginning to ensure growth for all these 50 members from day one. If a lead or manager fails to do so, the team will lose talent, team members will lose interest, team will lose targets, and like a domino effect everything will fail one day. And one day the lead or manager will have to escape and witness the downfall over the shoulder's of new lead or manager.
7. More the power lead/manager has distributed to subordinates the more powerful the team will be: If a person or 2 person have all the power and tries to manage everything then the team or system will fail. If the person-in-charge distributes the power to capable subordinates and in return looks into solving problems that these subordinates cannot solve, will make a team more productive. Rather than wasting time in managing subordinates. 
8. A Creative Man is motivated by Desire to Achieve but not by Desire to Defeat others: Suppose if I try to compete with a fellow architect and try to defeat him by doing few things better than him. What really I would be doing is that I will be limiting myself to the capabilities of the other guy and concentrate my energy in working on skills that will make me only competitively superior to the other guy. But if I work to compete with myself if I challenge myself that OK if I can design an effective architecture for developing High Performance Cloud Services for Healthcare then how can I better myself in reducing the throughput to a much lower level. If I work in this direction then I will be taking my knowledge and skill set level to a much higher standards rather than wasting my time on petty individual targeted advancement of skill set.
9. Life is 10% what happens to you and 90% of how you react to it: Suppose I get a low performance appraisal this year so shall I stop performing and stop enhancing my skillset, shall I stop going to office, shall I stop enjoying my work? No if I get something that I don't deserve then I should have the self-esteem and confidence to show the management that what I am capable of. If a person works undeterred towards his/her goal no matter how long he/she has to work he/she achieves what he has always deserved. No hard work goes waste no learning is useless. If we wish to go ahead and succeed we should learn to tackle 10% of hurdles with 90% of positive and powerful determination.