|
|
I googled change management this morning to see the latest hawked wares and approaches. Since I am a spatial learner and love pictures I chose “images of change” as my first stop.http://tinyurl.com/245t9s5.
Wow.
Could the approaches be more overwhelming? Change itself has a tendency to be the same. As a practitioner wouldn’t you want to make the process easier? Although if I am selling snake oil…
Here are some observations from my image journey-
- Change practitioners adjust their approach to their own perspective (strategic, OD focused, PMO based, Leadership oriented etc)
- Change apparently either revolves around a hub (yes I am guilty with my spider web article-http://issuu.com/garrettgitchell/docs/prosci2010paper), moves along a torturous curve or follows clearly from step to step on a timeline (oh and it could look like an iceberg which is really helpful for the whole fear of change thing)
- You need phases, must have phases
- They are all heavily influenced by historical gurus
- Change is funny (I admit I did like the pictures and cartoons)
After a couple hundred blog posts of my own (maybe I need “the book” to get there) I still can’t quite explain this, but they all feel like they are forcing change into a funnel that magically comes out the other end with a solution. I can picture what an engagement would look like about 3 months in having followed one of these pretty pictures (you can bet the practitioners are inextricably entwined with their own drawings). If I were to ask at that point, “what will this look or feel like when it is all over?”, odds are the answer would not be there (for the practitioner, the leader and especially for the stakeholder).
For that to happen, assumptions, perspective and history usually have to be unraveled, looked at and then rebundled into a change approach that works back from the goal rather than forward to …. can’t resist…. infinity and beyond.
Communicating for Change Management serves three purposes- to motivate, to guide and to provide place.
Place
We are going backwards from my list to illustrate a point. Most change management methods, and the consultants who practice them, move forward in time with my list. Not so effective. Not so effective because place gets lost in the mix. “Place” is the work of an individual in relation to the whole. When communicated well each stakeholder can explain how their work fits in to the bigger picture, how it connects to the next person and how it leverages the work of the previous stakeholder. At any given time place could mean a lot of things with a lot of connections. It is up to the change team and its leaders to make those connections make sense.
Guide
Having done the job of placing work at a spot in time, communication must address how the whole process moves forward. Actually processes, because there is the list of things to do, the project management, and there is the transition from the now to the end state. That may mean behavior changes, new or different technology, additional or changed interactions, perspective that is not status quo etc. Change communication must help explain these two processes and connect people, individual stakeholders, to the events along the way both to get the work done and to ground a human connection to what may be overwhelming change.
Motivate
I am guessing the cheerleaders on the sideline have little to do with the effort put forth by the players in the last minutes of the game. Change works the same. Cheering, amping up a sense of urgency, creating tension may start the play (and our change) fast and furious. The shelf life for that effect is short. Motivation, the kind that moves people forward by choice and deep down commitment is the third purpose in line. With place and clear guidance (read reason and a measure of safety/assurance) motivation appears on its own. Communication within the change process then becomes an exercise in illustrating the good, the positive, the examples of overcoming, effectiveness, commitment and extra effort by individuals
As a stakeholder if I cannot explain my exact spot at any given time, if I am not aware of what is to come and what has passed and if I am not given a reason to connect to the change in my own way, change management has failed.
A Change Practitioner will need to steer, guide, lead and prod for a variety of situations. While human nature can be consistent cultures and processes within organizations are distinct. Which of course is the result of human nature. Intuition, experience and empathy may carry the day for knowing people in general, but to get to the specifics and the “distinct” of one organizations takes an initial list of questions and to-do’s.
-
How do they communicate
-
What are the horizontal connections (if any)
-
Where is leverage the strongest
-
How weak or strong is the PMO
-
What is the history of change
-
What is the understanding of change management
-
At the individual level what are the disconnects in the organization
Turning these bullets into actual questions to individual stakeholders will create a list of helpful and not so helpful in terms of the way the organization exchanges, moves and learns. In fact the last bullet usually reveals the first (but feels too much like a resistance/negative approach to be a start for new conversations). What you hope for as a leader/change agent are clean lines of communication horizontally, vertically and circular; enough breakage of a silo structure that the change work can cross functions; leverage in the right spots as catalysts rather than roadblocks; an effective, aware and capable PMO; as little bad baggage as possible and understanding/willingness on the part of the stakeholders.
You can see how the short list gets long fast and now have some more data on why most organizations need Change Management.
Taken completely out of context (barely) from a post within a LinkedIn group.
Nor did he have the internet, global communications, virtual teams, contracted work groups or the need to constantly keep up with the business environment. What he did have is structure, hierarchy and unwritten rules about participating and unemployment (for not doing so).
As a leader why do I need change management?
You don’t.
If… you have the capacity in your organization to come up with ideas, that lead to vision, that illustrate end states, that tie to the energy, motivation and skill set of those you hired. Oh, and collaboration across function, culture, geography and virtual space, lack of internal politics that slow the fulfillment of goals. Of course you will also need to fully understand the mood and trust within your organization along with what you have for competencies, leadership and capacity.
You could delegate some of this out to the PM, you could pass the responsibility down to your junior leaders, you could partner with HR, you could force feed work in order to get it done. If you did all this passing and pushing where would you be…back in his day.
Think that works?
Change can be the overall time line of moving from one thing to another, or old to new. It can be the moment the switch happened- you actually move into that new home. It can be the process itself of transforming and changing behavior. It can mean movement, perspective, action, technology and/or behavior.
Transition might well be the same if semantics are not your game.
As an English undergrad words and languaging are an environment all their own for me.
So I like to think of transition as that sweet period- sometimes short sometimes a longer transformation- from the end of the old to the beginning of the new. Perhaps walking through the door of that new home…
With change management and the process of guiding change that sweet spot is something to capture as difficult, discomforting, then interesting, then satisfying and if more of those transitions may be in the future, contemplative and measured.
I came across a post the other day that said getting stakeholders to use new technology meant addressing their own self interest http://blogs.techrepublic.com.com/tech-manager/?p=3976. The post is on the right track. IT implementations are, admittedly, a specific type of change. Every form of change has a “punch a different key” aspect and IT change rarely stays confined in a nice manageable timeline. So lets look at self interest as a general perspective.
Well, of course
Everything we do is in our own self interest. The more we need to change the more our self interest comes into play. We balance need for action against willingness to act. We place ourselves inside the change to see if there is a fit. We watch those around us to see how self interest guides them. We measure action against inaction on a self interest scale.
Just another resistance approach?
Something is just not right with this view of change…it feels negative. “No way are they going to do this… because it is not in their own best interests.” I sense the next statement would be, “we need to show them what not changing will look like”. And then you have another approach based on the assumption that people automatically resist.
Self interest is OK
Better we look at self interest as an automatic thing. Better we use it advantageously. What happens as a result of self interest is usually a symptom of something else- especially if it is inaction. Is the structure of the organization getting in the way? Has history of botched change put up walls? Is the reward system so based on paying off self interest that participating on a larger scale does not make sense? Is self interest dialed in and out based on functional connection (this I have seen in IT do to the specificity of their roles, but they certainly do not own functional connection)? Is corporate strategy weak and/or short term? Do changes make sense (all the way to the individual level)?
Having asked these questions self interest begins to be a barometer of the effectiveness of the organization and its people. It turns out to be a way to, yes, find out reasons to resist. Addressing those valid reasons is a first step for an effective change approach. Self interest just became OK.
As an external consultant there is always a fine line between honoring “the way we do things here” and pushing for and guiding change. Many, if not most, organizations have a tie to processes, structure and communication that is hard to break. Here are some areas to keep in mind in terms of the status quo of cultural loyalty:
Group Think
Group think helps people with consistency, clarity and sameness (which is comforting if you keep your viewpoint narrow). It homogenizes to the point where almost everything is predictable. The longer the tenure for an employee the greater the need to stick to the norms-cultural loyalty.
It is surprising how many times at an individual level cultural loyalty (CL) is questioned. The questioning typically (especially if drawn out by a CM practitioner) produces smart, viable alternatives. If that person does not have authority or leverage those alternatives die quickly.
Internal Politics
Patterns appear over time in organizations that are a direct result of the jostling and wrestling for position by individuals. That positioning tends to work the best when the jostler follows the path of least resistance. That path is the road to the way we do things here. So you end up with a structure that rewards and reinforces the status quo.
Functional Loyalty
The same patterns but much harder to break occur at a functional level. Certain functions tend to have more leverage than others (usually because they bring in revenue which, on the surface at least, makes sense). Those functions then match their group think against others. What you end up with is a secondary level of loyalty to culture-functional loyalty. Which is a synonym for a silo.
Founder(s) Influence
The majority of the time the patterns that replicate within the silos and cultural pods in an organization are the result of the founder(s) initial vision, values and business direction. Emulating that package tends to move individuals up the ladder. The more that spreads the more group think builds and the harder to break the way we do things becomes. Another secondary level exists here when the organization gets big enough for the functional leaders to steer their own vision and approach.
Guiding change at the transformational/horizontal level requires the ability to frame the “make sense” communication in order to replace the CL that is holding back change and growth. In my own practice I have found that I must take the difficult step of working with leaders to tweak structure and process before trying to touch cultural and functional loyalty. The same pattern happens with the change process itself. Often there are underlying structural and process weaknesses that will make complete fulfillment of the end state close to impossible.
The fine line approach is to draw out the CL that makes collaboration, negotiating and compromise possible.
When it exists is like a sponge. It pulls in until it fills to capacity.
This is something to consider, leverage and acknowledge for change management. It is not necessarily something to be fed and nurtured.
What is Loyalty in the context of change management?
Loyalty to the cause
This is a connection to the core purpose of the change that creates interest, motivation and action. A technologist may quickly be on board for an IT implementation (or not of course). Someone sitting in HR may jump right on board for a human capital initiative. A senior executive may pencil in more and more free space on their calendar for dialogue and exchange for a program that touches their function.
Loyalty to the company
This is the version we think of when we see the word loyalty tied to work or workplace. It might infer staying power in terms of retention, it might mean atmosphere and culture, it might mean the tenacity with which people stick to goals/strategy/plans. It might even be the level of evangelism from participants extending outside internal operations-social marketing.
Ongoing connection
Loyalty that is truly strong is ongoing. Loyalty has a distinct time connection and a measure of strength over that time frame. Ideally it is increasing strength-measured differently for each individual and/or stakeholder.
Which brings me to the sponge.
Loyalty has both a pull and a maximum limit. The expectation of loyalty in change management often creates that maximum limit quickly. This is the common pattern of project/change management- shove something in, assume loyalty and get-…wait for it…Resistance.
Thankfully loyalty has a rosy side too. The pull. The more things (our things being change) make sense and connect in some way the smoother and more powerful the pull. Loyalty tends to spread easily once the pull begins. Charismatic leaders can help with the pull- someone has to communicate the “make sense”. The pull tends to produce evangelists who can increase the speed and, at times, the capacity of the pull.
When it is strong loyalty should be acknowledged within the change process. The acknowledgement can be kudos in communications, illustrations of commitment, examples of time saved through dedication and collaboration, etc. This is the right approach for feeding/nurturing/leveraging loyalty.
What does not always makes sense is rewarding loyalty.
Think of the expectations airline miles have created. Think of the backlash about blackout periods. Rewarded loyalty has a scale of expectations that increases quickly which decreases loyalty if not continuously fed.
Loyalty’s dark side is group think, retention of the lowest common denominator and potentially reduced innovation. In terms of change management the dark side is models and approaches that make incorrect assumptions or are based on internal best practices. The way we do it, a form of cultural loyalty, may not always be the most efficient or effective (effective adding a human capital component).
Keeping all this in mind, change management can build loyalty by rewarding skill and showing how that skill connects to end states and the health of the change entity. If compensation structures do the same bonuses can be added that tie to change participation.
Kudos always work. They work because they are after the fact and specific. Incentives are the opposite, before and general. They do not work so well because of the expectations they create.
When it comes to loyalty, specifically reward rather than generally encourage.
Because it creates a chance for congregation, for display of achievement, for shining a light on talent, for the noise of a communal group, for laughter, for conversation and for acknowledgement. A parade is a good analogy for understanding Change Management.
We have a Fourth of July parade here in Danville that attracts 40,000 people (almost the same as our population). It is a typical local parade. Lawn chairs are lined up the night before 2 and 3 deep for over a mile. Proof positive that everyone loves a parade.
Change benefits (and moves along smoother and faster) when tradition and people are recognized in the process of changing. A parade happens at the same time each year. Some participants are there for years at a stretch. Some go in and out. Some show up just once. In long standing parades there is an order to the procession. But who’s to say there is not a better sequence?
There will be whispered comments about this year versus last year, the parade not being the same as it used to etc. This is the continual conversation that goes on with the tradition/change interaction.
Within the parade are displays of achievement, participation and accomplishments. An annual meeting can do the same with the last years change. When called out as change and included in a change entities process the displays can become more of a cultural acknowledgment and less of a display of feathers.
Celebration is important in the change process. Tying that celebration into the fabric of an organizations culture can help with transitions from yesterdays tradition to tomorrows change.
What is the role of the C level leader for change management initiatives?
It depends on the specific C role and the size, scope and breadth of the initiative. This “it depends” list is a good way to look at our question because it follows the pattern that change tends to go through-and the order.
Size
This is a measure of how big this thing is going to be. The scale can be in terms of time (as in months to multi-year), number of people that will need to be involved or the budget needed.
Scope
Hopefully an area that is looked at and analyzed early on -strategically. After that it is the amount of resources, times and money that will be needed in each track or stream of the roll out. This area just gets bigger and bigger in its creep if the “hopefully” sentence is left out or skimmed over. It is this area that CM can bring cost controls (I know not a typical role for CM- but one that makes sense).
Breadth
When this initiative, especially if it is transformative, begins to pour like water over the organization how far will the edge of the water go? Uncomfortable as it may be for linear, straight line, 2 D, time based thinkers (and doers) the water goes in every direction. The change process is a little like a funnel turned upside down. Early on the flow is controlled. As time goes on and the initiative gets closer to the end state more and more stakeholders get touched. The funnel opens up and the spread gets bigger. How big that spread will be is breadth. “Will be” is a signal that this must be looked at from the very beginning planning stages. In keeping with my change management philosophy you might want to read these paragraphs backwards.
CEO
If the change is a transformation (culture, process, structure or all) the CEO is the owner. If you have not read my previous posts (or Alan Weiss, my tweak of definition comes from his writings) the owner pays for it and is the figurehead. Although admittedly the budgets usually come from the first and second horizontal (fortune 100) so the CEO might be a half owner.
Her/his role is to absolutely insure that this change makes sense. It can make sense based on data, based on emotion or based on reason/intuition. As a communicator the breadth category is the most important. Breadth can be a lead in for the other three. Please ,not the other way around- size and scope leading to breadth, that is just ugly (but common) creep.
As the organizational leader I think the CEO also had a previous role- or has one before this big change- to create an entity in the organization to orchestrate change. With that there is the ability to apply so the CEO can lead and communicate.
For all of the smaller less transformative initiatives the CEO can serve as the introducer of the change with an early communication, can be inserted into the process to boost something along or provide clarification and can serve as a motivator (I mean that in a helpful rather than coercive way- if you are using coercion you either have the wrong model or you missed the “make sense” step).
CFO
For the big changes scope will be the hands on role. That is where the money is spent (or saved). There is a version of the “makes sense” assumption here. Every expense is in competition with another. It benefits all change for the CFO to understand and be proficient in communicating that constantly balancing scale. The CFO must understand and learn to be comfortable with the 15% CM line item. A random number maybe- I have seen 10% constantly run into problems and 20% fairly quickly taken away, so 15 is our compromise. With a CMG (change management group) those costs can be spread operationally.
The CFO may also have leadership, figurehead responsibilities if the engagement is within their function (or reporting structure- here is an interesting article for CFO’s and CIO’s on the ownership of IT http://tinyurl.com/2ajrl3q take the CM part with a grain of salt though).
CIO
Hands on for the technology layer of the change. A leader if the change is strictly an implementation. There is a fine line here though. All changes in technology involve behavioral or skill change, so the CIO quickly becomes a figurehead for the “people side”. Did I say figurehead? I might have meant scapegoat. In order to avoid the passing of the buck for blame it helps for the CIO to hone their empathy skills and their knowledge of the changes individuals must go through if you “move the key on the keyboard”. Following that key to its new spot is Adoption and in that area the CIO is usually the owner.
As with all C level roles there is a responsibility for the make-sense-communications. Thanks to the CFO’s interpretation of budgeting and the CEO’s explanations of strategy to work connections the new tool should slot right in-correct?
COO
Is the right hand person to the CEO (and possibly in succession) so read section one first.
For the big initiatives size is their category. What kinds of resources will be needed? Because the COO is responsible for corralling all resources in an efficient way. All is both the change and day to day operations. This is typically a mud wrestling match with the dirtiest (and I don’t mean finishing covered with mud) winning. The COO is combination referee and parent at the mall. Their role has a lot of explaining and a lot of measurement of value and results.
The CMG is one way to keep that balanced and to support the responsibilities of this C role. CM can be paid for with the many operational savings it uncovers. It can be leveraged by the COO to create collaboration and surface new ideas and approaches. While it does not always seem apparent that surfaced innovation can either save or make money for the future the COO has their hands on possibility every day. It is their role in the change process to pull that out.
CLO
First deserves more credit (and more leverage).
They are responsible for making all of the other C level responsibilities work and get better.
For a transformation their immediate role is to provide the training and development needed to pave the way for the change. As the leader of that area they have a responsibility to illustrate the spot stakeholders are in. The “spot” is time, place, capability and gaps in knowledge and ability. Their challenge is to fill in the gaps for the change readiness (here is a good use of this term- it is one of the change words I do not like).
The CLO may also be the owner if the transformation falls within their function or influence. But most learning initiatives quickly or soon will become something the rest of the organization can use. Ownership may scale up in those instances.
All C level
Your executive summary is that the C level is heavily responsible for front loading change. The next person in line, the next landing of the buck, is an implementer. Implementation must have structure, approach, reasonable method and a lot of make sense. They do not have the power, influence or dollars to make that happen. Expecting them to is not fair and is, I think, the main reason for change “failure”.
And as a comical note Wikipedia lists 46, I am not kidding, different C level roles http://en.wikipedia.org/wiki/Corporate_title.
|
|
