Showing posts with label Leadership. Show all posts
Showing posts with label Leadership. Show all posts

Tuesday, December 31, 2013

Leadership on Rotation

Leadership by Rotation is my attempt to develop leadership qualities and abilities at various levels in an organization…

About 8 years ago, I was faced with a situation when the Tech Lead of my team was facing a burnout and needed a break. At this time, as the Manager, I was responsible for product deliveries and for resolving the issue of leadership. 

I performed a preliminary assessment of the Team Members and found that there were more than 1 eligible candidates for the Tech Leadership Position. If I chose one over the other, there would be dis-satisfaction and going ahead, there would be a power struggle and politics. There was a risk of disintegration of the team which I was not prepared to take.

It was here that I came up with the idea of "Leadership on Rotation"

I had 2 ongoing projects, and 4 more in the pipeline. I assigned one of the "eligible" candidates - Jack, as the Tech Lead for Project X and the other "eligible" candidate - Jamie, as the Tech Lead for Project Y. 

The rule was that Jack was a Tech Lead for Project X and was also having a certain responsibility as a Team Member in Project Y. On the other hand, Jamie was a Tech Lead for Project Y and was also a Team Member for Project X.

This way, both Jack and Jamie were getting to be the Leader and the team member at the same time.

For a new Project Z, both Jack and Jamie were team members to a new Tech Lead John.

I had a reasonable amount of success with this concept - in deliveries and in creating a pipeline of future leadership in the company.

Here's a list of advantages of this approach:

  • Those who want to lead, get an opportunity to do so.
  • Those who get the opportunity to lead, understand & know that they have to be team members in their next project - this brings about a sense of empathy to fellow team members and solves the "power corrupts, absolute power corrupts absolutely", problem.
  • Some team members who always have awesome ideas on leadership and how to run projects got to implement their ideas.
  • We had a pool of leaders in the making.
By implementing this concept, I was able to identify "Adaptable" leaders, those who could Lead and Be Led. It was an eye opener for a few individuals who thought they could lead but unable to do so. 

The implementation needed close monitoring and a lot of effort investment, but that is a small price to pay for the long term goals of the organization...

Saturday, February 18, 2012

What I learnt from my Mother: Responsibility

When I was a kid, I used to feel important when my parents would assign some tasks to me, like watering the plants everyday or bringing the newspaper and milk bottles from our door-step every morning. I remember very clearly, that I would perform each of my tasks for a few days and then either lose interest or get lazy and then forgot all about it only to find out many weeks later, that my mother had "assumed the responsibilities" of my tasks....

There was not a single day, when my mother would forget to make breakfast on a Sunday or chose to skip doing the laundry because it was a National Holiday!

My mother would ask me, my brother and my dad, what we would like to eat the next day and carefully plan every night how she is going to fulfill our wishes for "tomorrow". There is not a single day that I remember of, when my mother did not fulfill a "reasonable" demand!

Another interesting fact that I remember about my mother is that, I don't recall my mother falling sick or being too sick to cook, there was always something to eat when I was hungry.

What I learnt from my mother was RESPONSIBILITY and that
  • Responsibility is ABSOLUTE! - there are no ifs and buts, no National Holidays, no breaks and no vacations. 
  • Responsibility is not a 9 to 6 job! - it is a 24x7 job. 
  • When one takes up a Responsibility, it better get done, because someone is depending on you to do it. 
  • Responsibility does not need "Comfortable Working Conditions" or "Encouraging and Supportive Customers", only an iron will to do a great job at all costs.
  • Responsibility is a Thankless Job! - don't expect a pat in the back for each successful attempt, get on to the next task as soon as possible.
  • There are no Shortcuts when one takes up a Responsibility! - the involvement and commitment required is 100% - no one likes a half cooked meal.
  • Anything that prevents one from executing the Responsibility is just an Excuse! and not a Reason.
  • Most important thing about Responsibility is that one feels for the task or the group of people. The "Brain" follows the "Heart" when a responsibility is involved.
An amazing lesson, valid at home and at work at all time. 

How I wish, we all implement these lessons at work, there will be no loss making companies and no dis-satisfied employees...

Sunday, March 27, 2011

Rising to the Top!

In my opinion, most "Promotions" (not all! ) in organizations have been reduced to actions to fill the vacuum in the Organization Structure created by Attrition!.

There was a time when people were promoted for their skill, their capability, the value that they bring to the table, their past contributions, reliability on deliveries, commitment to the job and last but not the least loyalty to the company.

High demand for skills has resulted in a floating population of opportunists who are always on the lookout for "better opportunity", "growth prospects" and "learning", while they are actually looking for "more pay for less work". Who said, "Customer is the king"? Who said, "Customer Satisfaction" is the most important thing? What is more important is my next Car, or that Limited Edition Watch or that Villa project and how I am going to fund it.

Here's a story about Tom.....

The Villa costs X, and Tom is eligible for a loan of only 0.4X, so, he looks for a job that pays him more and his Bank Loan eligibility goes up. Tom wants more money so he can spend more!, not because he needs more to live or for attaining financial security by saving more!

So, while Tom is looking for higher pay, he might as well bargain for that higher position and some joining bonus, which will help him make that down payment, amazing strategy isn't it?

What happens to Tom's current customer who is expecting him to deliver this project? --- Tom says, "this project is so simple, that a fresher can run it, you don't need me".

What happens to Tom's company who trusted him and offered him a job when he was without one just 2 years ago? --- Tom says, "Well, that's not my problem, I worked for the company for 2 years isn't it?".

Here's Tom's list of achievements in this company....
  1. Training in Software Development Life Cycle for 2 months
  2. Training in C++ for 3 months
  3. Coding for the Leave Management System for 4 months  (an internal project
  4. On bench for 1 month - this is the company's problem, and not Tom's! well, he was ready to work, but they did not have any projects!.
  5. Training on SAP for 6 months (Tom applied for a training in SAP because his friends said, an SAP consultant's job will pay 3 times his current salary!, the company obliged, but paid for later!).
  6. SAP Maintenance Project for 8 months (Tom has been assigned to this SAP Maintenance project for the past 8 months and has received a couple of customer appreciation emails for his performance)
Tom is now looking for a job because --- "I have learnt everything there is to learn. There are no challenges and learning on my current job."

Let's analyze this list of achievements:
  1. Training: 15 months: 62% of the time
  2. Idle time: 1 month: 4% of the time
  3. On Project: 8 months: 34% of the time
What is the impression this guy makes on the interview panel? --- he makes A VERY GOOD IMPRESSION!, the panel sees this person as a "ready made resource" who can be directly deployed on a project and a means to earn instantaneous revenues, no training period and no lead times. The panel says "There is a project on hand and we need people urgently. This guy fits the bill, let's hire him".

HR makes an offer, Tom is unhappy and refuses and says he wants more and wants the Position of a Project Leader.

HR comes back to the interview panel with this new problem. The panel has to come up with a new strategy, they say "let's give him what he wants, instead of hiring experienced people, let's hire some freshers. This guy wants more responsibility, so he has to train these new people and get them up to speed in 2 months". HR is happy, Tom is happy and resigns from his current position. He tells his colleagues and friends that this new company really knows the value of individuals, they know how to treat people.

What happened in this case is sad and easy to visualize..... here's the list of the highlights:
  • Tom got what he wanted even though he did not deserve it. 
  • The new company went ahead and obliged Tom what he wanted because they were under pressure to deliver this new project. 
  • Tom's colleagues and friends from his first company are thinking Tom is having a great time and they are disgruntled because they are not getting similar breaks, work suffers........
  • In reality Tom is under tremendous pressure to deliver and is on the verge of cracking. 
  • Tom has put a HOLD on the Villa, the Limited Edition Watch and the new car..... 
  • Tom's team is also under great pressure to deliver and are looking up to Tom to teach them but Tom is not able to find sufficient time to train his team.
  • Tom's team is showing signs of disgruntlement
  • Management is after Tom to perform
  • Tom fails!
  • Tom is now complaining to his colleagues and friends about how this company is treating him and how unfair the management is. 
After 1 year, Tom is looking out for a new job which offers him higher pay!. He does not want to insist on a higher position as he wants more exposure now, he is willing to join as a Project Leader but does not mind if a higher position is offered!.

..... and the "Promotion" cycle goes on.....

Friday, January 8, 2010

Leadership

Leadership is all about inspiring people to break their performance barriers and over achieve. It’s about directing people to get things done and meeting goals and objectives within time and cost constraints. Leadership is a set of qualities and is not necessarily associated with a title. A title is consequence of demonstration of the leadership quality. Leadership is not about banging the table and telling people that you are “the boss”. Leadership can be established but is not readily accepted. Leadership comes with respect and respect is to be commanded and not demanded. Being a leader takes a lot of hard work. Leadership is not for the individual to state, but it is to be acknowledged by others who surround you.

LEADERSHIP is an ART. It is the ART of creating FOLLOWERS…

Leadership is a mixture of some qualities in the right proportion and these qualities must be developed and practiced over time. In the following paragraphs, I put down some of my thoughts and practices, which, I hope, will help me to be a good leader someday, and I am working very hard to get there…

Be humble
I believe that I am a Manager and because I possess certain skills and qualities. I am a Manager because there is no other person in my current organization who suits this position better. So, I must be thankful to others who have not spent the kind of time or effort in honing the skills that I have become good at over time.

Another line of thought is that, “What is my identity without my team” the answer is “I am nothing, because, I will not be able to deliver any product without my team”. So, for me to perform I need my team and I am grateful to all my team members for choosing to stay and work in my team and in my organization.

These thoughts keep me grounded and humble.

Be approachable
My team members must feel free to come over anytime to, discuss the product requirements, escalate matters, discuss personal differences with me and other team members, get inputs on their personal finance management or discuss the pros and cons of buying an apartment in a certain location. Some of my old team members have even approached me to get my advice on a certain job assignments that they are considering. When I am approachable, the bad news travels faster resulting in quicker actions to minimize damage. First things first, I will be approachable only if people feel comfortable talking with me. For people to feel comfortable with me, they have to be assured that I am their well wisher and a neutral individual, meaning, I have demonstrated that I am fair and impartial. They have to believe that I am not there to harm them. It takes a lot of time and effort to win over people.

Be available
I must be available when my team needs me. If I am not physically present, I must make suitable arrangements for communication with my team and ensure that the team functions well, in my absence. I must demonstrate “let’s get to work” instead of “go and get to work” effectively. I must be able to foresee issues that my team might face and have suggestions and/or solutions in hand ahead of time.

Be fair
I must be fair to all my team members, I must not demonstrate special liking to one or a few individuals and my decisions must be neutral and acceptable to all. There must be a single set of rules applicable to all team members and no special accommodation to one or few people in the team. I must load all team members with equivalent amount of work.

"Being fair" is tricky as I am dealing with perceptions of people. I can control my actions but not people's perceptions. There have been occasions when I have been accused of partiality by my Managers when my intentions were good, this hurts. I could have run, but I chose to stand and continue to fight this perception and change it. I am learning to think thru' all my decisions and it's effects on people before implementing it. It takes a little more time than usual, but it is worth it.

Be a good follower
Many times, I have faced situattions where I was unable to take a decision, unable to take a stand. In these occasions, I bring together a few key players in the team and explain the problem to them. I also express my inability to take a decision. Then I invite suggestions from these team members and look for a consensus. Once all have agreed to a decision, I stand by the decision and take it forward. By doing this, I am demonstrating to my key team members that I can follow too. Being a good leader requires one to be a good follower too. By following others' decision, I don't degrade myself, I only better my chances of being accepted as a good leader.

Demonstrate patience and control the temper
I must accept and be patient with the shortcomings of the business, the system and it's people. If something does not happen as expected, it does not always mean that the effort was not there, I must understand and accept that "we win some and we lose some". An outburst and throwing a temper tantrum only complicates matters, it demotivates and humiliates others. The relationships that I have worked on for years are very delicate by nature and good associations go bad with one outburst or show of temper. The result of a temper tantrum is a team which fights battles half heartedly, evidently the battle will be lost.

When things go wrong, I must express dissatisfaction first and then work on the shortcomings of the system and it's people, demonstrate patience, and encourage people to go on and the job will be done.

Demonstrate a positive attitude
I must demonstrate a positive outlook and attitude towards life, my company, people in my team and the project in general. I believe that good things happen to people who do good. If I have any difference of opinion, I must be able to mask it suitably so that my difference of opinion does not come between the team and the goals of the project I am working on. When my team members have a negative feeling, I must be able to guide them and give them a positive outlook without compromising on the goals and objectives set for me or for the team member by my Company’s management. Last but not the least, I must shield my team members from the business pressures, I must be smiling and encouraging under all circumstances.

Demonstrate knowledge
I must have a good understanding of the project requirements my team is working on, or the project that the team will take up next. I must be able to give my team suggestions and solutions when required. If I don’t know an answer, I must obtain an answer thru’ escalation and revert to the team members without fail. Most of all, I must be in a position to take an informed decision on any situation in the project. I understand that people will approach me only if they know that I can provide a solution to their problems, so I must be prepared.

Demonstrate empathy
When my team members approach me with a problem, professional or personal, I must demonstrate empathy, I must acknowledge the problem and listen them out instead of jumping to conclusions without giving them a chance to talk. Other people’s problems may seem silly to me because I am not facing the problem myself, nevertheless, I must show sufficient interest and try and provide a neutral solution to the individual. Sometimes, I don't have to provide a solution, I just have to listen them out, they get rejuvenated and find a solution by themselves.

Empower
I must identify the next in command and groom them to take on more responsibilities. I must partner with them and empower them to enable them to take decisions on project activities and I must show trust and stand by their decisions. If the decision is wrong, I must correct them and show them the way, so that they don’t make the same mistake again. I must enable them to run the show in my absence.

There is a lot more to leadership qualities than what I have stated in the previous paragraphs and I am sure these are documented elsewhere...

Here are some key aspects of leadership
  • The success of a leader is measured by how well the team performs when the he/she is absent.
  • Leadership does not depend on your level of operation in the Organizational hierarchy, you can demonstrate leadership qualities at all levels.
  • Never wait for an opportunity to demonstrate leadership qualities, demonstrate it in your current assignment.
  • Win over others with your positive attitude, knowledge and personality.
  • The leader does not wait for things to happen, the leader makes things happen.

Friday, January 1, 2010

Empowerment

Empowerment is a very important and interesting aspect of Management. An action that plays a vital role in building teams, creating ownership and accountability within people, resulting in success of the team/project/organization.

From my experience, "Empowerment" is a very loosely used word, Managers think, they can empower people by...

  • making an individual or a team responsible for a certain task
  • giving an individual the power to take a decision
  • giving an individual the authority to take a financial decision

This is not enough and this is not all.


In my opinion, true Empowerment comes from creating
  • a good feeling for the team/organization: "I FEEL GOOD" Factor
  • a sense of belonging in the organization/team: "I BELONG HERE" Factor
  • an awareness of the vision and imparting knowledge: "I KNOW WHAT TO DO" factor

When people are empowered in the "True Sense", they demonstrate a sense of Responsibility, Ownership and Accountability for a task/project. They demonstrate initiative. They are proactive. The war is theirs and they celebrate each victory in a battle, however small the battle is. There is energy everywhere, people help each other, share knowledge and stay late just because their colleague is having a difficulty in his/her task. People come forward to ask for more work a week ahead.


This is not all, the organization starts seeing a difference, the defects are low, the customers are happy resulting in more business. There is prosperity.


I strongly recommend to Managers, to use the following steps to achieve "true" empowerment in their teams/organizations
  1. Treat people well
  2. Impart Knowledge
  3. Bestow responsibility


Treating People Well


This is the first and the most important step in empowerment. "Treating people well" is not always achieved by talking nicely to them or greeting them or accepting anything and everything that an employee has to say.


Managers have to encourage them, inspire them, trust them, listen to them and acknowledge their achievements.


Encouragement comes from saying kind words and being supportive when people are down. Kind words of encouragement fills team members with a strange confidence to do the "undoable". The team member does wonders with his/her task.


A word of caution:
  • the maturity of the individual plays a very important role in "Treating people well". An individual with high maturity will respond positively to encouragement and kind words, the ones with low maturity will go around boasting that the Manager is his/her friend and will not hurt him even if he/she makes a mistake. Managers have to study their people's maturity and then act. I have seen admonishment, a bit of embarrassment and then saying the kind words of encouragement works with people with lower maturity levels in most cases. 
  • High maturity usually results in high commitment in individuals and these kind of people work with good intentions,  managers need to be supportive and encouraging, these people feel bad, when they make a mistake, these people usually accept admonishment as a punishment for wrong doing, but they cannot and will not appreciate humiliation or embarrassment. These people will leave the company if they are subjected to humiliation.


Impart Knowledge


Step 2 deals with training people, providing them knowledge, tools and techniques that come handy in day to day activities.


There are two types of Managers who impart knowledge:
  • Type 1: Most managers have a unique way of dealing with tasks and situations. These are techniques that they have read in books, used and perfected over time. These managers usually have better success in step 2 of empowerment as they are closer to ground realities, they know more about the project, product and processes and have a better relationship with their teams.
  • Type 2: Some managers, however, go by the book. They are better "read" than the "Type 1" managers, they are loosely related to their teams, the project, the product and the processes. These Managers will have a tendency to implement a Six Sigma Technique that was successful in another company, without showing consideration to the current organization, it's maturity, it's people, it's people's maturity or the product requirement. These managers try to implement systems with "Mission Critical robustness" when it is not required, just because some "Guru" appreciated this technique. These Managers have a lower chance at success in imparting knowledge as most people in their team just don't understand what this person is saying or where he is coming from.
Imparting knowledge means, "showing them the way", by telling them:
  • What to do
  • How to do it
  • How to Measure
  • Take necessary Actions (based on the measurements to minimize deviations)
  • How to Share Knowledge with others in the team

This is a classic Plan-Do-Check-Act cycle first stated by Deming, PLUS knowledge sharing.


Managers need not define everything by themselves, they may get their key team members to participate and define the tasks, the process, measurements and the possible actions to take when deviations occur. This way, the key players themselves will own the process and train others on the process that they defined.



Bestow Responsibility


Once the team members are trained, the Managers must share responsibility of the project along with key players in the team. An announcement must be made to let everyone know, so that other team members know whom to approach, when required. A formal announcement, makes team members proud and gives them a sense of responsibility. Their pride helps them contribute to the project objectives and goals.


Once a person is made responsible, the Manager must stand by this individual under all circumstances. Great leaders acknowledge the success of the individual and make it known to all. A failure is also handled, thru' escalation, and thru' counseling to the individual, reassuring him/her, that this happens and that it can be overcome. The counseling should be kept private.


The act of bestowing responsibility fails when the Manager resorts to "Success is mine and failure is yours" philosophy. In these cases, the person will never accept responsibility from this manager again.


Where managers go wrong is when, they call a certain team member to their office, and tell him/her that he/she is responsible for a certain process and keep the act of bestowing responsibility private. This way, the person never really accepts the responsibility, even if he/she does, he/she does not get the support from other team members to execute the responsibility. This results in frustration and disgruntlement in the employee, he/she is unable to live up to the expectation of his/her manager and the manager holds him/her responsible for the failure, while, the failure is really the Manager's, who could have turned this situation around by merely making an announcement and showing his/her support to the cause.


To Summarize, empowerment, when done properly, works wonders and helps building great teams. Great teams produce great products, great products result in great revenues for the company. The manager must acknowledge success and attribute to individuals and also standby and accept responsibility if things go wrong.