Monday, 08 August 2011 13:16

Implementing Change

Written by 
Rate this item
(0 votes)

Evolution is key to the survival of any species. This isn’t a revolutionary concept; it has been around since man moved from eating raw meat to finding his first source of heat and energy. In business, the same is true. Those still using caveman techniques in a world evolving around them are likely to become extinct like the dodo.

There is clearly a need to constantly adapt, to realize that if one approach doesn’t work that it isn’t the end but rather the beginning. There is a need to recognize that you do not know all the answers, but collectively, those around you may.  This ability to adapt, to change tack at will and collaborate with others is what distinguishes the business analyst profession.

I have sat in many meetings listening to stakeholders who are convinced beyond a shadow of a doubt that their approach is right, that what they have been doing for the last 10, 20 or 50 years is right. That no outsider could, or should, tell them otherwise or even propose that another way is feasible or better. I have also sat in meetings where the stakeholders love the new approach, some even raving about it, while their ash-faced colleagues look on, knowing full well the work required of them and the difficulty involved in implementing such a change.  The change-experienced business analyst is willing to assist them through this process, and help both the stakeholders and the users adjust to (and even celebrate) the change.

Yes, business analysts are great at changing, at adapting. We can go into an industry, ranging from publishing to banking, airline industries to petroleum, adapting our approach to the content as necessary.

 What we business analysts often forget is that our clients and stakeholders are not always ready for such change, especially in the timelines expected of them. 

“Change management” is becoming more and more of a buzzword. The adoption of a word by industries somehow seems to devalue its meaning, perhaps as a result of its frequency of use, or use in the wrong contexts. Whatever the reason, phrases like “synergy,” “business model” and “thinking outside of the box” all end their days unappreciated, undervalued and disused in the cemetery of boardroom blabber. And if they haven’t yet, they should.

 A project is only as successful as the change embedded by it. A solution that meets 80% of requirements but is 100% embedded is by far a better outcome than a solution that meets 100% of requirements but is only 20% embedded. Implementing change in small to medium organizations or multinational conglomerates should be pursued with the same amount of vigour, conviction and creativity.

Asking people to change the way they function is no easy task, nor should it be viewed as such. The scale may change, but ultimately people are reluctant to change, particularly when they do not see anything wrong with their approach. Often, they will simply ask why? Unfortunately, this is a question that remains unanswered in most failed change management attempts.

Based on my interactions with change management, there are 6 key concepts that should be kept in mind:

  1. Answer the unspoken question first: “Why is this change being made?”
  2. Ensure that everyone is reassured, e.g., “This change is not being made as a result of you, but rather to improve our overall approach.”
  3. Remember that not everyone enjoys change. Make sure the approach taken is creative, innovative and engages all stakeholders. As a business analyst on the ground and interacting with a variety of different stakeholders from different sections of the business, your role may be more important than you realize.  
  4. Involve as many formal and informal influencers as possible. Observe team/group interactions:  there will be indicators of who to engage with.
  5. People will often only do what they are measured on, so to ensure a sustainable change is created, it is important to introduce reasonable measures reflecting target behaviours.
  6. Be patient and communicate. The change cannot be implemented or accepted overnight. Implement regular reminders of why the change is being made, and why each individual involvement is crucial.

Change and the management thereof is a key part of evolution, and without it we will stagnate. Without sufficient change management, people will covertly continue to do as they have always done, or will accept the change with barely contained contempt. Remember, unless shown otherwise, people will prefer to do things as they’ve always done.  After all, “why fix it if it’s not broken?”

Don't forget to leave your comments below.


Catherine Perks is a London-based business analyst working for BSG (UK). She looks at what make a solution work, including the technical and interpersonal effects of implementing the solution. 

Read 3089 times Last modified on Tuesday, 27 March 2012 13:46

Comments  

 
0 # Denise Kemp 2011-08-09 01:30
Very good read - written by someone who obviously understands the staff challenges experienced by business owners when trying to "fix something that is not broken"
Reply | Reply with quote | Quote
 
 
0 # Wendy Dold 2011-08-09 01:47
So true - good to be reminded that we are all essentially the same, and that its tough trying to shift a team!
Reply | Reply with quote | Quote
 
 
0 # David Wright 2011-08-09 15:57
I have found that the strongest driver of change is declining profits. If a company is still making money "the old fashioned way", it is tough to sell it on change of any kind. The problem is when returns go from good to bad very quickly; can the organization adapt fast enough to return to profitability? or will it go out of business? For an average project within a company, this view may seem too macro to drive change at a team or department level, but you have to trace what your project is doing back to the overall goal(s) of the company, because the "wrong" change can be worse than no change at all.
Reply | Reply with quote | Quote
 
 
0 # Ken Livingston 2011-08-09 19:22
I would argue that Change Management is becoming less and less of a buzzword, and more and more of a profession - as Project Management was 20 years ago, and Business Analysis 10 years ago. I think we, as BA's, are the change instigators and therefore we're much more open to change, but as (I think) you point out, we just need to be aware that some/many of our users aren't as amenable to different ways of doing things. In many cases, people simply don't see the warning signs - change only happens when crises hit. This means that the need for change has to be very clearly identified, and equally clearly explained to users so they understand that they can't carry on the way they are now. Then you're more likely to get their buy-in at subsequent project steps. (Oh, trivial stuff - dodo's weren't squeezed out by evolution, they were wiped out by humans - like many projects, I guess).
Reply | Reply with quote | Quote
 
 
0 # Tony 2011-08-09 23:16
Love it. I constantly have to remind people that 'change management' is not 'change control' or 'configuration management'. Organizational change management is by far my favorite aspect of BA work. I want a Masters in it! When you say 'embedded' you're talking about the acceptance rate of the products of the project right? My analogy is whether the business staff have been spoon-fed and inspired to embrace the new environment, versus having it crammed down their throat with a wooden spoon. And I wholly agree - I have worked on projects that implemented excellent technology and processes, and teetered on failure because of the organizational aspect. Those projects taught me to self-learn and love change management. @K en - I read that no amount of facts and clear communications will budge stalwart resistors. The author suggested creating an emotional imperative that cuts through the resistance of the hard cold facts, charts and truths. "If this org/department/ business doesn't change, and change soon, it will die." Sort of like telling a smoker it will kill him - doesn't always work. Get the wife or kid to beg him to quit, now you have a catalyst for change!
Reply | Reply with quote | Quote
 
 
0 # Catherine Perks 2011-08-10 00:38
Thanks for your comments above - much appreciated. @David - I tend to agree, it seems as though change management can be a last ditch effort to try and do things right, when in reality, you should be constantly looking for new ways to adapt and evolve before the problem materialises. I think bigger organisations are often more hesitant to change because it would be such a large endeavour, whereas smaller organisations can be more flexible and there is possibly less cost involved in implementing that change. Maybe I'm wrong though? @Ken - I agree, I think it is our role to try to be at the forefront of a change and to try and get buy-in from the people/stakehol ders that we interact with. As a consultant, its also often easier to see the change that is needed because I am effectively an outsider, but often consultants have to work a lot harder to get their buy-in as they resent our involvement - to avoid overstepping the mark. Although I have experienced where the client does trust you to manage that change as they recognise that you are trying to help and do have different insights to share. Perhaps as in-house BA it is easier? Have you had any experience with that? (Thanks for pointing out about the dodo - hopefully the analogy still works - perhaps we try too hard to force a change when we should recognise the damage we are really inflicting?) @ Tony - thanks for the positive feedback. I referred to embedded as more than just acceptance of the products of the project, more that they are willing to use it and do use it as regularly as they can. Often, a change will be made, and instead of going along with the change. People will simply accept it, nod and continue doing what they've always done. What I'm suggesting is more that people embrace the change and are willing to engage with it. Less that they have been spoon-fed and more that they have learnt why its important, and then when satisfied with the why, have understood and appreciated and chosen to make use of the change. I love the comparison with the smoker - your example pretty much sums up the message that I was trying to get across. It is very easy to tell people to change, but much harder to understand their motivation for making the change. An understanding and appeal to the emotional imperative will help ensure that the change is embraced.
Reply | Reply with quote | Quote
 
 
0 # Louise Molyneaux 2011-08-10 20:58
Hello Catherine, Love d your article. You summed up the challenge of change so well. As someone who has worked training people to change the way they think and behave, I understand the challenges facing the challengor and the challengee! People have to buy into the change required and if they can see and feel the benefit of the change, they will embrace the change required. They have to have a real sense of the benefit to them of the necessary change, not just to the company. Many people fail to see the benefit to the company as being of benefit to them e.g. cut costs, improved profits, improved benefits to company. They tend to see cut costs, improved profits, someone else takes home more money. One also has to make sure that the employees believe that they will be able i.e. they will be taught the skills if required to be able to do the job. A lack of confidence or self believe is often behind the resistance to change. The key for me and I have personal experience of this, is the the way the new idea is communicated to the staff. You need to think very carefully of examples of successful changes and explain them in a simple to understand way, listen to peoples concerns and respond to them in a manner that indicates you have truely heard their concerns. Dale Carnegie's book "How to Win Friends and Influence People" has 21 chapters - each describing a principle which cover two areas of concern when working with people. Firstly how to get willing co-operation from others and how to change a persons attitude without offending them and causing resentment. I can personally vouch for every one of these principles - they work. I am delighted to see an old Maris Stella Girl from Durban South Africa doing so well and living in London! Welldone girlfriend.
Reply | Reply with quote | Quote
 
 
0 # Catherine Perks 2011-08-11 03:00
@Louise Thank you so much for your positive feedback, its greatly appreciated. I agree that the crucial element of why the change is being made is often missed by those implementing the change, and often not asked enough by those receiving the change. So much of successful change management is understanding the human element, and ensuring that employees feel ready for that change - both in terms of skill preparation and in adjusting their attitudes. I will definitely look out for that book, thank you for recommending it! Lovely to hear from you, and thanks!
Reply | Reply with quote | Quote
 
 
0 # Craig Willis 2011-08-12 06:30
Great piece, I'd add that you need to make sure that people are sufficiently armed for the change too. By this I mean make the change as easy as possible but this is one area that might be the most difficult to influence. Oft en people will understand the change and the benefits it brings but if, for whatever reason, they are being prevented from making the change then it is likely to fail. Take software training as an example. I've seen large software implementations fail even though the project team thought they had covered all bases. Even after all the analysis it was hard to figure out why, training had been delivered, communications done, the users even agreed that the change was needed. So what happened? The software itself was just too damn complicated for people to use. It didn't need to be, it was just poorly designed. The principles of design can be carried into the general workplace too. Make sure that adequate instructions are provided at relevant points. Even instruction manuals have a habit of being too difficult to use. Simply saying we have provided instructions and training is no longer enough. Thanks !
Reply | Reply with quote | Quote
 

Add comment