They say about habits - When you take "H" out of a habit, "a bit" remains,
If then take "A" out, still "bit" remains,
If you then take "B" out, still "it" remains - habits are hardwired.
If you teach a person to do something a certain way, no matter what are the repercussions, he will continue to do things the old way. I have seen this happen at several of my claims system implementations where people were asked (say), not to follow a long winded process to input claims, rather use the structured application process for this which was quick and easy, but people were hesitant to do that for multiple reasons. This brings us to our topic for today - "Change" and "Change Management".
Insurance Transformation projects (or any large projects for that matter) as such are pretty complex, with lots of factors in play such as - multiple systems to integrate, legacy data dependencies and statutory requirements and restrictions, business and competitive pressures etc. For all the Policy and Claims transformation projects that i have been, there is always and will be a need for change management.
For a multi million dollar project, involving hundreds of people, impacting hundreds even thousands of people in the insurance organizations, you cannot afford to ignore change, you have to make sure this change happens effectively and smoothly throughout the organization.
What is Change Management?
Change management is simply transitioning from current state to future state and addressing the problems that come along the way. The most important aspect in change management in 'Awareness'. This one factor changes the game altogether, An aware and trained organization accepts and adapts to change more easily than one that is not. Change Management is not just user training, but it also requires changing and shaping user attitudes and perceptions towards the change overall. Change Management begins from the time you start your project planning. First you have to identify the correct stakeholders, their roles in the organizations, how they can help shape and translate the change throughout the organization, followed by training needs, pilot roll out, issue resolution etc all goes hand in hand.
There are some factors that should definitely be considered for Change Management.
Perform a Organizational readiness study
Study the overall organizational perception towards the change, are they people open to change?, are they defensive?, subdued? not concerned?, worried? etc. Have a plan to address each of these areas by either one on one sessions or having regular meetings and get togethers to sort doubts. Remember it is very important that you have the buy in from your people on the change and they are not just 'sold' on the change..
Stakeholder study
As i mentioned earlier, after identifying individual stakeholders, perform an individual stakeholder study so as to understand their viewpoints and then produce a focused training material. There should be a detailed issue resolution process spelled out for the pre deployment and post deployment stage.
Develop your own change leaders
Executive and higher Managment cannot reach each and every person in the organization to explain the need to change. The organization has to identify, develop and nurture the right change torch bearers. I say, the 'right ones' because the change champion has to be very clear on what is changing and why. How is it going to benefit the organization in the long run.
These ideas have to be translated to all levels in organization, so that all involved are engaged and are a part of the whole change movement.
If they see any concerns, they should try to address those and if they cannot, bring it out to the top management.
Highlight the organizational directive
It is not enough for you as a project manager to provide your version of the change, but you have to focus on the overall organization objective and group direction. For instance in the Insurance world, organization direction is not to use the old excel sheets method to calcuate the reserve estimates or calculating policy rates, but use the application reserve setup, rating worksheets etc. Do not use notes to capture the claims history, but use the data fields and elements to create and develop the claim file story.
Visual Training, Support and Learning
Sometimes as i mentioned above, it becomes very important to visually depict a particular paradigm shift (like showing the 200 MPH bullet train to travel from point 'A' to point 'B' rather than using the 70 MPH subway or in my world, using the highly structured and organized new policy and claims administration systems vs the old rigid legacy system with only notepad functionality).
Plan, plan and plan
Each organization has different dynamics at play in terms of different organizational structures, different executive priorities and politics. So this means you need a unique plan for your organization. A plan that is well though of, has bench marking and change tracking templates, regular communication meetings and bulletin board updates scheduled, undergoing a few levels of pilot testings and dry run implementations definitely helps.
Organizations that down play or underestimate the importance of change management, do so just because there is not enough awareness of the Change Management factors or the impending implications if it is not implemented or implemented incorrectly. It is the job of the C Level executives, Project Managers, Business executives to make sure that any implementation has minimal disruptions during the change imlementations and the change leaders are there to support the end user needs. The business is happy with the change and ultimately realise the application really does help them do their jobs better.
Showing posts with label change management. Show all posts
Showing posts with label change management. Show all posts
Saturday, June 18, 2011
Thursday, May 19, 2011
Soft Skills
You might ask - how and why is article related to Project Management.
Back in the days when dinosaurs ruled the earth and not so far off till late 90s, it was thought that the Technical knowhow or the 'hard skills' was the only factor attributed a project's success. People who were pure Techo managers, sitting in one corner desk could solve the problems troubling planet earth.
But not any longer, the outlook has changed, C-level executives, mid managers etc have begun to realize that soft skills are also as important, infact soft skills are identified in today's world as also one the most important success criteria to execute a project.
What do you mean by soft skills -
Soft skills is an art - an art to communicate effectively. Effective meaning so that people will understand, listen and relate to what you are saying. For some people this trait is inborn. But for most, this has to be acquired by constant practice and learning.
This article is for those who, when surrounded by people, never fail to secretly salute a black spider that manages to find dark nooks and corners even in broad daylight.
For those - not so brave hearts, fear not - the art of soft skills can definitely be learned, cultivated and honed to the extent of becoming an expert.
One of the major issues wrt soft skills is, you do not know the importance of this trait till it hits you - like a deer hit by blazing lights of a running car,
The educational courses that teach management as a part of any curriculum talk about the technical aspects of Management, and prepare you with a Project Management framework but nothing prepares you for the soft skillset required.
Some may ask why do we need Soft skills to run a project? The reasons are many,
First and foremost is 'Objectives and expectations alignment'
- Projects deal with multiple stakeholders with varying skills, diverse personality types.
- Each stakeholder may have different understanding of the project.
- For influencing the work outcome either with stakeholders or even Team members, you will need strong leadership, communication and convincing skillset.
Everyone has to be aligned to a common goal, just like a army of ants carrying grains of food in a straight line to its storage area.
- At an individual level, i have personally seen many a talented people fail. Not because they did not have the Technical prowess, but because they only had Technical mastery.
No one wants to work with people, who may be so called masters of their Technology domain, but do not have the basic people skills. This is an attribute of a person's Emotional Quotient (EQ).
There is no magic formula to gain soft skills. The steps needed to achieve Soft skills could range from showing empathy and optimism towards your colleagues to extreme self-awareness in knowing what's going on around you and this is a constant learning process. You need to keep on practicing this day in and Day out.
As a person grows in his career, in order to reach higher echelons of success, it is much more important to be have soft skills competence than low level Technical knowhow.
In short, gaining Soft skills is like a fear factor game challenge where the contestant has to be on a running speedboat and has to climb the copter above using a low hanging rung of ladders in a limited timespan.
Standing on the speedboat and watching the copter above (The Project) is not enough, having excellent upper, lower body strength will not get the job done (Hard skills). But what will get you to the winners circle, is to reach out for the ladder and climbing it one rung at a time (Soft skills).
Baby steps:
You cannot climb Mt. Everest in one day (or maybe you can, but not in this case). There are certain steps that one can follow to achieve excellence in this personality skills
Join Public speaking groups:
1> e.g. Toastmasters Group: Toastmasters club is an excellent forum for personal development in terms of fear of public speaking, teaches you various traits required to be better listener and speaker. How to formulate your thoughts clearly and precisely.
One day at a time:
2> Start with meeting 1 person at a time. When you are meeting a person - even for project reasons, try to get to know the person, understand his background, his likes/dislikes, perspective on the project, what may be the pain points for him and how you can help resolve them? What does it mean by project success to him? Learn to be a good listener.
The person could be anyone from project sponsor to an end user-stakeholder to one of your internal development and testing Team members.
Professional Courses and Training:
3> Seek professional help. There are numerous training institutes and courses which delve on this particular subject. These courses will help you change the perspective and suggest ways and mean that will help you achieve your goals.
In Summary, be people centric and more extroverted than you are, start to get out of your comfort zone. We have to remember that a project is teamwork and a project is deemed successful or a failure only by the efforts of the individuals that make the Team. So encourage your Team members, have regular get together sessions, appreciate and acknowledge achievements, provide guidance and seek help, when and wherever required.
It is definitely time to come out of that dark cave and bask in the glorious sunlight.
Back in the days when dinosaurs ruled the earth and not so far off till late 90s, it was thought that the Technical knowhow or the 'hard skills' was the only factor attributed a project's success. People who were pure Techo managers, sitting in one corner desk could solve the problems troubling planet earth.
But not any longer, the outlook has changed, C-level executives, mid managers etc have begun to realize that soft skills are also as important, infact soft skills are identified in today's world as also one the most important success criteria to execute a project.
What do you mean by soft skills -
Soft skills is an art - an art to communicate effectively. Effective meaning so that people will understand, listen and relate to what you are saying. For some people this trait is inborn. But for most, this has to be acquired by constant practice and learning.
This article is for those who, when surrounded by people, never fail to secretly salute a black spider that manages to find dark nooks and corners even in broad daylight.
For those - not so brave hearts, fear not - the art of soft skills can definitely be learned, cultivated and honed to the extent of becoming an expert.
One of the major issues wrt soft skills is, you do not know the importance of this trait till it hits you - like a deer hit by blazing lights of a running car,
The educational courses that teach management as a part of any curriculum talk about the technical aspects of Management, and prepare you with a Project Management framework but nothing prepares you for the soft skillset required.
Some may ask why do we need Soft skills to run a project? The reasons are many,
First and foremost is 'Objectives and expectations alignment'
- Projects deal with multiple stakeholders with varying skills, diverse personality types.
- Each stakeholder may have different understanding of the project.
- For influencing the work outcome either with stakeholders or even Team members, you will need strong leadership, communication and convincing skillset.
Everyone has to be aligned to a common goal, just like a army of ants carrying grains of food in a straight line to its storage area.
- At an individual level, i have personally seen many a talented people fail. Not because they did not have the Technical prowess, but because they only had Technical mastery.
No one wants to work with people, who may be so called masters of their Technology domain, but do not have the basic people skills. This is an attribute of a person's Emotional Quotient (EQ).
There is no magic formula to gain soft skills. The steps needed to achieve Soft skills could range from showing empathy and optimism towards your colleagues to extreme self-awareness in knowing what's going on around you and this is a constant learning process. You need to keep on practicing this day in and Day out.
As a person grows in his career, in order to reach higher echelons of success, it is much more important to be have soft skills competence than low level Technical knowhow.
In short, gaining Soft skills is like a fear factor game challenge where the contestant has to be on a running speedboat and has to climb the copter above using a low hanging rung of ladders in a limited timespan.
Standing on the speedboat and watching the copter above (The Project) is not enough, having excellent upper, lower body strength will not get the job done (Hard skills). But what will get you to the winners circle, is to reach out for the ladder and climbing it one rung at a time (Soft skills).
Baby steps:
You cannot climb Mt. Everest in one day (or maybe you can, but not in this case). There are certain steps that one can follow to achieve excellence in this personality skills
Join Public speaking groups:
1> e.g. Toastmasters Group: Toastmasters club is an excellent forum for personal development in terms of fear of public speaking, teaches you various traits required to be better listener and speaker. How to formulate your thoughts clearly and precisely.
One day at a time:
2> Start with meeting 1 person at a time. When you are meeting a person - even for project reasons, try to get to know the person, understand his background, his likes/dislikes, perspective on the project, what may be the pain points for him and how you can help resolve them? What does it mean by project success to him? Learn to be a good listener.
The person could be anyone from project sponsor to an end user-stakeholder to one of your internal development and testing Team members.
Professional Courses and Training:
3> Seek professional help. There are numerous training institutes and courses which delve on this particular subject. These courses will help you change the perspective and suggest ways and mean that will help you achieve your goals.
In Summary, be people centric and more extroverted than you are, start to get out of your comfort zone. We have to remember that a project is teamwork and a project is deemed successful or a failure only by the efforts of the individuals that make the Team. So encourage your Team members, have regular get together sessions, appreciate and acknowledge achievements, provide guidance and seek help, when and wherever required.
It is definitely time to come out of that dark cave and bask in the glorious sunlight.
Wednesday, May 18, 2011
Manage Stakeholder Expectations
Many things have been written and said about Managing Stakeholder Expectations. This is one of the most difficult tasks a project manager has to perform throughout the life cycle of the project depending upon the type and number of stakeholders involved. Essentially what may mean as a 'perfect and successful' project to the project manager, may turn out to be a complete disaster in the eyes of the stakeholders.
During Concept Phase:
A Project is conceptualized when the stakeholders or project sponsors meet and layout the project idea. Objectives and goals are set at this stage and a project is born. Once it has taken a definite shape and the ball has started rolling and the project progresses from the concept or initiation phase to design, construction, testing and finally delivery and closure. At every stage, we, as Project Managers have to manage stakeholder expectations.
Every stakeholder comes from a different arena or a different functional area and therefore has different definition of success. Hence it is very important at the onset, to make sure all stakeholders are on the same page and are driving towards a common goal. This is achieved in the Project Kick off meeting. The project sponsors or the ones who had laid the project high level objectives may not be the only ones who are the actual stakeholders that are involved with the project, as the project progresses you will find the number of stakeholders and actual representatives may also vary.
So, from the initial requirement sessions you may find that the stakeholders that get involved are deviating from the ground rule and are asking for something that is not in project scope or not inline with the general project agenda.
This may happen due to various reasons,
1> Stakeholders not clear on the Project Objectives
2> Need some understanding wrt different project areas or how projects are executed.
It is the job of the Project Manager to make sure these risks are addressed at proper time by proper planning.
Example:
Coming to an insurance industry example of this scenario,
say the project deals with integrating your Policy-Claims administration system with a Contacts management software and during the stakeholder meetings, the discussions lean towards tweaking and tuning of another dependant 3rd party interface - CMS upload for medicare.
Agreed, the 2 items may be related, but that does not definitely mean that the other interface is to be handled in this project scope (Unless that is the way the project has been scoped out).
To handle this situation make sure the project objectives are strongly and succintly communicated to the stakeholders that we are integrating to a new contact management software and this may mean some changes associated to some middleware bridge to make the other contact dependent interfaces work as expected, with minimal to no impacts. This lays a ground rule and restricts the deviations that may otherwise happen.
How to:
Major steps to stakeholder management in any project large or small are,
Step 1:
Conduct Stakeholder interviews:
- Study your stakeholders - their roles, who they are - organizational positions, their project roles - e.g. sponsors, end users, business SMEs, what they do? How would they influence the project outcome - completely understand their 'needs' and 'beliefs'? All this can be managed by having a 'Stakeholder map'.
- Know them wrt likes, dislikes, project expectation etc
Step 2:
Stakeholder Communication:
This is the most important thing in any project. I cannot stress on how important is this factor to guarantee a project success.
- Involve your stakeholders in all stages of the project right from initiation.
- Try to understand the project objectives from the stakeholders perspective. What does it mean to them by project success/failures/key painpoints etc? Let them define this in their own terms.
- Familiarize them with project financials, give them an overall project picture by having regular project status report meetings. In these meetings, make sure you concentrate on areas that are important to the stakeholders rather than delving into your project management methodologies and bravado stories.
- By effective communication and holding them accountable to project realities in times of project changes we can definitely and successfully manage stakeholder expectations. Remember Stakeholders and Project Sponsors have as much vested interest in project success as everyone.
During Concept Phase:
A Project is conceptualized when the stakeholders or project sponsors meet and layout the project idea. Objectives and goals are set at this stage and a project is born. Once it has taken a definite shape and the ball has started rolling and the project progresses from the concept or initiation phase to design, construction, testing and finally delivery and closure. At every stage, we, as Project Managers have to manage stakeholder expectations.
Every stakeholder comes from a different arena or a different functional area and therefore has different definition of success. Hence it is very important at the onset, to make sure all stakeholders are on the same page and are driving towards a common goal. This is achieved in the Project Kick off meeting. The project sponsors or the ones who had laid the project high level objectives may not be the only ones who are the actual stakeholders that are involved with the project, as the project progresses you will find the number of stakeholders and actual representatives may also vary.
So, from the initial requirement sessions you may find that the stakeholders that get involved are deviating from the ground rule and are asking for something that is not in project scope or not inline with the general project agenda.
This may happen due to various reasons,
1> Stakeholders not clear on the Project Objectives
2> Need some understanding wrt different project areas or how projects are executed.
It is the job of the Project Manager to make sure these risks are addressed at proper time by proper planning.
Example:
Coming to an insurance industry example of this scenario,
say the project deals with integrating your Policy-Claims administration system with a Contacts management software and during the stakeholder meetings, the discussions lean towards tweaking and tuning of another dependant 3rd party interface - CMS upload for medicare.
Agreed, the 2 items may be related, but that does not definitely mean that the other interface is to be handled in this project scope (Unless that is the way the project has been scoped out).
To handle this situation make sure the project objectives are strongly and succintly communicated to the stakeholders that we are integrating to a new contact management software and this may mean some changes associated to some middleware bridge to make the other contact dependent interfaces work as expected, with minimal to no impacts. This lays a ground rule and restricts the deviations that may otherwise happen.
How to:
Major steps to stakeholder management in any project large or small are,
Step 1:
Conduct Stakeholder interviews:
- Study your stakeholders - their roles, who they are - organizational positions, their project roles - e.g. sponsors, end users, business SMEs, what they do? How would they influence the project outcome - completely understand their 'needs' and 'beliefs'? All this can be managed by having a 'Stakeholder map'.
- Know them wrt likes, dislikes, project expectation etc
Step 2:
Stakeholder Communication:
This is the most important thing in any project. I cannot stress on how important is this factor to guarantee a project success.
- Involve your stakeholders in all stages of the project right from initiation.
- Try to understand the project objectives from the stakeholders perspective. What does it mean to them by project success/failures/key painpoints etc? Let them define this in their own terms.
- Familiarize them with project financials, give them an overall project picture by having regular project status report meetings. In these meetings, make sure you concentrate on areas that are important to the stakeholders rather than delving into your project management methodologies and bravado stories.
- By effective communication and holding them accountable to project realities in times of project changes we can definitely and successfully manage stakeholder expectations. Remember Stakeholders and Project Sponsors have as much vested interest in project success as everyone.
Subscribe to:
Posts (Atom)