Bogorad on the basics of Change Management – TechRepublic

TechRepublic linkedin

As always any LinkedIn.com links require you to be a member of the site and the group links require you to be a member of the group.

In recent weeks, I have posted two pieces relating how a discussion thread on the LinkedIn.com Chief Information Officer (CIO) Network group had led to an article on TechRepublic. The first of these was, The scope of IT’s responsibility when businesses go bad and the second, “Why taking a few punches on the financial crisis just might save IT” by Patrick Gray on TechRepublic.

This week, by way of variation, I present an article on TechRepublic that has led to heated debate on the LinkedIn.com Organizational Change Practitioners group. Today’s featured article is by one of my favourite bloggers, Ilya Bogorad and is entitled, Lessons in Leadership: How to instigate and manage change.

Metamorphosis II - Maurits Cornelis Escher (1898 - 1972)

The importance of change management in business intelligence projects and both IT and non-IT projects in general is of course a particular hobby-horse of mine and a subject I have written on extensively (a list of some of my more substantial change-related articles can be viewed here). I have been enormously encouraged by the number of influential IT bloggers who have made this very same connection in the last few months. Two examples are Maureen Clarry writing about BI and change on BeyeNetwork recently (my article about her piece can be read here) and Neil Raden (again on BeyeNetwork) who states:

[…] technology is never a solution to social problems, and interactions between human beings are inherently social. This is why performance management is a very complex discipline, not just the implementation of dashboard or scorecard technology. Luckily, the business community seems to be plugged into this concept in a way they never were in the old context of business intelligence. In this new context, organizations understand that measurement tools only imply remediation and that business intelligence is most often applied merely to inform people, not to catalyze change. In practice, such undertakings almost always lack a change management methodology or portfolio.

You can both read my reflections on Neil’s article and link to it here.

Ilya’s piece is about change in general, but clearly he brings both an IT and business sensibility to his writing. He identifies five main areas to consider:

  1. Do change for a good reason
  2. Set clear goals
  3. Establish responsibilities
  4. Use the right leverage
  5. Measure and adjust

There are enormous volumes of literature about change management available, some academic, some based on practical experience, the best combining elements of both. However it is sometimes useful to distil things down to some easily digestible and memorable elements. In his article, Ilya is effectively playing the role of a University professor teaching a first year class. Of course he pitches his messages at a level appropriate for the audience, but (as may be gauged from his other writings) Ilya’s insights are clearly based on a more substantial foundation of personal knowledge.

When I posted a link to Ilya’s article on the LinkedIn.com Organizational Change Practitioners group, it certainly elicited a large number of interesting responses (74 at the time of publishing this article). These came from a wide range of change professionals who are members. It would not be an overstatement to say that debate became somewhat heated at times. Ilya himself also made an appearance later on in the discussions.

Some of the opinions expressed on this discussion thread are well-aligned with my own experiences in successfully driving change; others were very much at variance to this. What is beyond doubt are two things: more and more people are paying very close attention to change management and realising the pivotal role it has to play in business projects; there is also a rapidly growing body of theory about the subject (some of it informed by practical experience) which will hopefully eventually mature to the degree that parts of it can be useful to a broader audience change practitioners grappling with real business problems.
 


 
Other TechRepublic-related articles on this site inlcude: “Why taking a few punches on the financial crisis just might save IT” by Patrick Gray on TechRepublic and Ilya Bogorad on Talking Business.
 
Ilya Bogorad is the Principal of Bizvortex Consulting Group Inc, a management consulting company located in Toronto, Canada. Ilya specializes in building better IT organizations and can be reached at ibogorad@bizvortex.com or (905) 278 4753. Follow him on Twitter at twitter.com/bizvortex.
 

Maureen Clarry stresses the need for change skills in business intelligence on BeyeNetwork

The article

beyenetwork2

Maureen Clarry begins her latest BeyeNETWORK article, Leading Change in Business Intelligence, by stating:

If there was a standard list of core competencies for leaders of business intelligence (BI) initiatives, the ability to manage complex change should be near the top of the list.

I strongly concur with Maureen’s observation and indeed the confluence of BI and change management is a major theme of this blog; as well as the title of one of my articles on the subject. Maureen clearly makes the case that “business intelligence is central to supporting […] organizational changes” and then spends some time on Prosci’s ADKAR model for leading change; bringing this deftly back into the BI sphere. Her closing thoughts are that such a framework can help a lot in driving the success of a BI project.
 
 
My reflections

I find it immensely encouraging that an increasing number of BI professionals and consultants are acknowledging the major role that change plays in our industry and in the success of our projects. In fact it is hard to find some one who has run a truly successful BI project without paying a lot of attention to how better information will drive different behaviour – if it fails to do this, then “why bother?” as Maureen succinctly puts it.

Without describing it as anything so grand as a framework, I have put together a trilogy of articles on the subject of driving cultural transformation via BI. These are as follows:

Marketing Change
Education and cultural transformation
Sustaining Cultural Change

However the good news about many BI professionals and consultants embracing change management as a necessary discipline does not seem to have filtered through to all quarters of the IT world. Many people in senior roles still seem to see BI as just another technology area. This observation is born out of the multitude of BI management roles that request an intimate knowledge of specific technology stacks. These tend to make only a passing reference to experience of the industry in question and only very infrequently mention the change management aspects of BI at all.

Of course there are counterexamples, but the main exceptions to this trend seem to be where BI is part of a more business focused area, maybe Strategic Change, or the Change Management Office. Here it would be surprising if change management skills were not stressed. When BI is part of IT it seems that the list of requirements tends to be very technology focussed.

In an earlier article, BI implementations are like icebergs I argued that, in BI projects, the technology – at least in the shape of front-end slice-and-dice tools – is not nearly as important as understanding the key business questions that need to be answered and the data available to answer them with. In “All that glisters is not gold” – some thoughts on dashboards, I made similar points about this aspect of BI technology.

I am not alone in holding these opinions, many of the BI consultants and experienced BI managers that I speak to feel the same way. Given this, why is there the disconnect that I refer to above? It is a reasonable assumption that when a company is looking to set up a new BI department within IT, it is the CIO who sets the tone. Does this lead us inescapably to the the conclusion that many CIOs just don’t get BI?

I hope that this is not the case, but I see increasing evidence that there may be a problem. I suppose the sliver lining to this cloud is that, while such attitudes exist, they will lead to opportunities for more enlightened outfits, such as the one fronted by Maureen Clarry. However it would be even better to see the ideas that Maureen espouses moving into the mainstream thinking of corporate IT.
 


 
Maureen Clarry is the Founder and President/CEO of CONNECT: The Knowledge Network, a consulting firm that specializes in helping IT people and organizations to achieve their strategic potential in business. CONNECT was recognized as the 2000 South Metro Denver Small Business of the Year and has been listed in the Top 25 Women-Owned Businesses and the Top 150 Privately Owned Businesses in Colorado. Maureen also participates on the Data Warehousing Advisory Board for The Daniels College of Business at the University of Denver and was recognized by the Denver Business Journal as one of Denver’s Top Women Business Leaders in 2004. She has been on the faculty of The Data Warehousing Institute since 1997, has spoken at numerous other seminars, and has published several articles and white papers. Maureen regularly consults and teaches on organizational and leadership issues related to information technology, business intelligence and business.
 

The Top Business Issues facing CIOs / IT Directors – Results

Back in January, in collaboration with Chase Zander, I started a process of consulting with senior IT managers to develop a list of the top business issues that they faced. This exercise was intended to shape the content of a IT Director Forum that we were planning. This will now be happening on 26th March in Birmingham (for further information see this post).

Questionaire Responses
The Top Business Issues faced by CIOs / IT Directors

Back then, I promised to share some of the findings from this study. These are summarised in the above diagram. The input was based on public comments made by a selection of senior people on the CIO group of LinkedIn.com, plus e-mails sent to me on the topic and feedback received by Chase Zander.

A textual version of the data appeas below (sample size ~60):
 

  Issue % of Votes  

  IT / Business Alignment 27%  
  Cost-saving 13%  
  Managing change 8%  
  Status of the IT Director 8%  
  Legacy Systems 5%  
  Customer focus 5%  
  Enterprise Architecture 5%  
  Business Intelligence 5%  
  Avoiding the latest and greatest 3%  
  Cloud Computing 3%  
  Only one response 17%  

  Total 100%  

 
I would like to thank all of the IT professionals who contributed to this survey.
 

“Gartner sees a big discrepancy between BI expectations and realities” – Intelligent Enterprise

Doug Henschen
 
Doug Henschen at Intelligent Enterprise reports from the Gartner Business Intelligence Summit in Washington D.C., explaining that Gartner analysts John Van Decker and Kurt Schlegel cited five reasons why BI projects do not live up to expectations (article link here):
 

  1. No IT-Business Partnership – “We have to get away from thinking of it as a vendor-customer relationship,” said Schlegel.
  2. No Link to Corporate Strategy – BI team have to listen to the executives and develop metrics and measures that are aligned with their goals.
  3. No connection to the Process – “BI has been overtly disconnected for too long,” Schlegel proclaimed. It’s not enough to deliver the right information to the right users. You have to insert those insights into the processes and interfaces that business users live in every day.”
  4. No Governance or Too Much – It has to be just the right amount of governance. BI grew up departmentally, so it’s all too common to have many silos of BI. At the other extreme, some companies are so uptight about data standards that companies can’t get their data into the warehouse.
  5. No Skills – Business users often lack skills, chimed in Van Decker, citing the one area where the business side was said to be falling short. “Most companies have very sophisticated capabilities available that folks just aren’t taking advantage of,” he said, pointing to corporate performance management (CPM) software as a leading example.

 
I come close to the situation of words failing me when I read a list like this (though not close enough to prevent me penning an article of course). I appreciate that maybe a public seminar is not the easiest place to provide deep insights (I present a lot myself), but the commentary against each of the problem areas seems odd to me. I’m not sure that these are really the five reasons for BI continuing to disappoint in some organisations, while it continues to delight in others, but here are my thoughts on each headline.
 

  1. No IT-Business Partnership – We have to stop talking about IT and Business as if they were two parties trying to negotiate a cease-fire. IT is a business department, it carries out business projects. It would be ridiculous to say that there needs to be a Sales-Business Partnership, it should be equally so with IT. I expand on this theme in the very first article on this blog.
  2. No Link to Corporate Strategy – There should not be a link to Corporate Strategy, BI does not exist as a separate entity that requires linkage. Instead BI work should be an expression of Corporate Strategy (as should any IT project), what else is it an expression of? This is not about listening to executives (though that is important) it is about IT being part of the senior management team of an organisation and not some semi-detached entity, focussed only on the beauty of its own navel. I give some indication of how to go about ensuring that this is the case in two articles, one focussed on a European environment and one spanning four continents.
  3. No connection to the Process – I agree that embedding good BI in a coporoate culture requires effort (indeed I have written a series of articles on the subject, starting with this one), however I struggle to see how any BI team could fail to realise this and pay the area due attention. If this is truly a reason for failure, then it is because of a lack of basic project and change management skills in BI teams.
  4. No Governance or Too Much – I’m not sure that achieving the Goldilocks approach to Governance is the issue here. BI’s impact on an organisation is directly proportional to how pervasive it is. This means that silos of BI reduce value and the walls need to be knocked in. Does this have to be all in one go? of course not, there are always benefits in a balance between incremental progress and paradigm shifts. Any organisation who has gatekeepers who refuse access to the warehouse because of and overly rigid approach to data standards is going to have problems. Equally where systems are developed with little thought to the information that they provide and data is simply thrown over the wall to the BI team, this is going to destroy value. As ever, there needs to be a sensible balance struck, one that yields the greatest business benefit for the lowest cost.
  5. No Skills – “Business users often lack skills”, this seems both incredibly patronising (are only IT people smart enough to get it?) and also a poor excuse for BI teams not paying enough attention to education (see point 3. above). If business people truly lack the skills to use good BI, then they are probably unfit to be in business as the tools are pretty intuitive (if not over-engineered by an approach that is too technology-focussed). More likely, training has been poor, or the BI deliveries have failed to be tailored to answering questions that the business wants to ask.

 
In summary, I don’t have five reasons for BI failing to live up to expectations, I have one. I firmly believe that BI done well is both the easiest of IT systems to sell to people and has one of the highest paybacks of any IT initiative. BI done badly (at the design, development, implementation or follow-up stages) will fail.

The issue is basically a simple one: just how good is your BI team? If a BI implementation fails to deliver significant business value, then instead of looking for scape-goats, the BI team should purchase a mirror and start using it.
 


 
Continue reading about this area in: Some reasons why IT projects fail
 
 
Doug Henschen joined Intelligent Enterprise as Editor in 2004 and was named Editor-in-Chief in January 2007. He has specialized in covering the intersection of business intelligence, performance management, business process management and rules management technologies within enterprise applications and architectures. He previously served as Editor-in-Chief of Transform Magazine, which covered content management and business process management challenges.

I comment on another Intelligent Enterprise article, this one by Cindi Howson, here.
 

The confluence of BI and change management

y =x^3 + 2x^2 - x + 1

The tag-line of this blog brings together business intelligence and cultural transformation. While one driver for this is that I have led BI projects that had explicit goals of cultural transformation, I think that there is a deeper connection to be explored here.

In other articles (notably “Can You Really Manage What You Measure?” by Neil Raden and Actionable Information), I discuss my experience that BI only adds value if:

  1. The information it provides answers pertinent business questions, and
  2. The answers to these questions lead to people taking action.

This means that any successful BI implementation has to consider such messy and difficult things as changing how people behave. This is where the link with change management arises.

Now of course you can argue that change management is an indispensible discipline for any business project (my strong opinion is that any IT project is a type of business project) and this is clearly true. However the parameters within which a new transaction processing system has to operate are different. Here if a person does not use the system, then work does not get done. Either it is impossible to carry out your job without the system (maybe only the system generates the necessary documentation), or not using the system to record transactions is a breech in compliance (keeping paper copies in your drawer).

BI systems are not like this. People chose to use them because they judge that they either make their business life easier, or they help to improve their decision-making (hopefully both). If someone doesn’t want to use a BI system, then they won’t and can probably get on with other parts of their job. The reason that change management is even more important in BI projects is that the element of compliance (or even coercion) is absent. If you want people to use the system and behave differently as a result, then you need to think about how best to influence them in these directions.

I have written elsewhere about the importance of marketing, education and follow-up in these areas. It also is important to explicitly recognise that a BI practitioner needs to be fully engaged in change management if they are to be successful.

A final thought also worth considering is that, as the BI industry matures and focus turns more to making it work in a business context than the latest flashy dashboard technology, it is likely that one of the things that will differentiate the best users of BI is how well they manage the necessary and desirable change that it drives.

πυρὸς θάνατος ἀέρι γένεσις, καὶ ἀέρος θάνατος ὕδατι γένεσις

 

Sustaining Cultural Change

This article is the final one in a trilogy focussed on enacting change. The previous instalments were as follows:

  1. Marketing Change
  2. Education and cultural transformation.

The first two pieces covered generating enthusiasm for change in advance of enacting it and then the role that professional training has in repositioning behaviours. I left off with the first training event having been a success. I will pick up the story from this point and seek to answer the question: how do you sustain initial success over the medium term?

Before starting to discuss some approaches that worked for me in this area, I should remind readers of the context. This was delivering a new BI system in a European insurance organisation with the explicit aim of enacting a cultural transformation; in this case making top-quality management information part of the corporate DNA.
 
 
Introduction

flying-buttress-h200

It is part of human nature to sometimes rest on your laurels. Having worked hard to make sure than something goes well, it is tempting to sit back and admire what you have done. Unfortunately gains are not always permanent and indeed may be quickly eroded. It is a useful to recall the adage that you are only as good as your last performance. As in a sporting contest, when you have made a good start, it is then the time to press home your advantage.

After our first successful training session, we had several other waves of training for our first report family – in fact we trained over 300 people in this first activity, 150 more than we had anticipated, such was the demand that we had generated and the positive feedback from people who had attended. But at this stage we had only won the first battle, the outcome of the war remained in the balance. We had made a good start, but it was important that the team realised that there was still a lot of work to be done. In this final article I want to talk about some of the ways in which we sustained our focus on the system and managed to embed its use in day-to-day activities.
 
 
Using new functionality to reinforce training

By the time the training team had come to the end of its first phase, the development team had produced its second report family. This was aimed at a slightly narrower group of people, so training was a less extensive task. Also we were showing new BI functionality to people who were already users, or at least had attended the training. The training for the second release was just a half day, but we asked people to book out a whole day. The extra time was spent in attending either a refresher course (for people who had not been confident enough to use the system much after initial training) or a master-class (for those who had taken to it like a duck to water). We also offered these two options to people who were not recipients of the second report family.

Inevitably there were initially some people who were not 100% converts to the new system at first; crucially less than half of users fell into this category. Over time both the enthusiasm of their peers and the fact that early adopters could present information that was not generally available at internal and external meetings began to exert pressure on even the most sceptical of people.
 
 
Travelling to the users

With later report families, which were again aimed at the mass market, we change our approach and travelled to give training in different countries. This helped to tailor our training to local needs and prevented anyone becoming isolated by language issues. Again when we travelled we would go for two days and have two half-day formal classes. The other half days were taken up with refresher courses, master classes or – something that started to become more and more requested – one-on-one sessions. These are in many ways ideal as the user can go at their own pace and focus can be on compiling and saving reports that are directly pertinent to them – classroom work has of its very nature to be more general.

Sadly we did not have unlimited funds to travel round Europe, so these one-on-one sessions morphed into using the telephone and network facilities with the trainer “taking over” the PC of the delegate to work together. This approach has also been very successful on our Help Desk.
 
 
The importance of the Help Desk

Speaking of the Help Desk – because the BU systems was very business-focussed people tended to raise business-focussed questions (as opposed to “when I click on this button, the system locks up”). This meant that the Help Desk needed to understand both the technology and the business and we used our business analysts and trainers to staff it – this is high-end resource to apply, but they were just as proud of the system as the extended team and wanted to help people to get the best of it.
 
 
Summary

So, we were relentless. We didn’t really ever lower the intensity we had established when launching the system; business adoption and retention both reflected this. Even once our cultural change had been mostly achieved and BI had become as much part of everyday life as the ‘phone or e-mail, the team continued to put just as much effort into new releases. The contributions of professional training and a business-focussed Help Desk functions were both indispensable in sustaining our success.
 

BI and a different type of outsourcing

outsourcing

The current economic climate seems to be providing ammunition for both those who favour outsourcing elements of IT and those who abjure it. I’m not going to jump into the middle of these discussions today (though I am working on an article about the pros and cons of outsourcing BI which will appear here at some future point). Instead I want to talk about another type of outsourcing, one that ended up being a major success in a BI project that I recently led. The area I want to focus on is outsourcing analysis to the business.

The project was at an Insurance company and in these types of organisations one hub for business analysis is the actuarial department. These are the highly qualified and numerate people who often spend a lot of their time in simple number crunching with the aim of ensuring that underwriters have the data they need to review books of business and to take decisions about particular accounts. As with many such people, they have both the ability and desire to operate at a more strategic level. They are sometimes prevented from doing do by the burden of work.

As I have explained elsewhere, an explicit aim of this project was cultural transformation. We wanted to place reliance on credible, easy-to-use, pertinent information at the heart of all business decisions; to make it part of the corporate DNA. One approach to achieving this was making training programmes very business focussed. One exercise that the trainers (both actuarial and indeed me) took delegates through was estimating the future profitability of a book of business based on performance in previous years (using loss triangulation if you are interested). This is a standard piece of actuarial work, but the new BI system was so intuitive that underwriters could do this for themselves. Indeed they embraced doing so, realising that they could get a better and more frequently updated insight into their books of business in this way.

This meant two things. First the number-crunching workload of actuarial was reduced. Second when underwriters and actuarial engaged in discussions, for example around insurance estimates to be included in year-end results, the process was more of an informed dialogue than the previous, sometimes adversarial, approach. Actuarial time is freed-up to focus on more complex analysis, underwriters become more empowered to manage their own portfolios and the whole organisation moves up the value chain.

This is what I mean by the idea of outsourcing analysis to the business. In some ways it is the same phenomenon as companies outsourcing internal administrative tasks to customers via web applications. However, it is more powerful than this. Instead of simply transferring costs, knowledge and expertise is spread more widely and the whole organisation begins to talk about the business in a different and more consistent manner.

It’s nice to be able to report a success story for at least one type of outsourcing.
 

“Can You Really Manage What You Measure?” by Neil Raden

beyenetwork2

I have to say that BeyeNETWORK is becoming the go to place for intelligent BI insights.

In this recent article, Neil Raden challenges the received wisdom that, if you can measure something, managing it follows as a natural corollary. This is a problem that I have seen in a number of BI implementations. It can be characterised as the Field of Dreams problem, if we build it, they will come!

One way to better align BI provision with the management of an organisation is to make sure that any BI element that you deploy is targeted at answering a specific business question. It is important that answering the question leads to action.

If the reaction to learning that sales in the Philadelphia office are down by 2% is a shrug, then not a lot has been achieved. If instead it is easy to further analyse the drivers behind this (e.g. which part of the sales funnel is suffering from a blockage?, is this a temporary blip, or a trend?, is the phenomenon centred on a specific product, or across the board?, etc.) then we begin to embed the use of information to drive decision-making in the organisation. If this leads to an informed telephone conversation with the Philly branch manager and the creation of an action plan to address the fall-off in sales, then BI is starting to add value. This gets us into the area of Actionable Information that Sarah Burnett writes about.

This is one reason why it is important that business intelligence is considered within a framework of cultural transformation; one of the main themes of this blog.
 


 

BeyeNETWORK provides viewers with access to the thought leaders in business intelligence, performance management, business integration, information quality, data warehousing and more.

Neil Raden is an “industry influencer” – followed by technology providers, consultants and even industry analysts. His skill at devising information assets and decision services from mountains of data is the result of thirty years of intensive work. He is the founder of Hired Brains, a provider of consulting and implementation services in business intelligence and analytics to many Global 2000 companies. He began his career as a casualty actuary with AIG in New York before moving into predictive modeling services, software engineering and consulting, with experience in delivering environments for decision making in fields as diverse as health care to nuclear waste management to cosmetics marketing and many others in between. He is the co-author of the book Smart (Enough) Systems and is widely published in magazines and online media. He can be reached at nraden@hiredbrains.com.
 

Gartner says “BI must transform and improve businesses”

The title is paraphrased. The actual quote, as reported on BeyeNETWORK, is as follows: –

“Organizations will expect IT leaders in charge of BI and performance management initiatives to help transform and significantly improve their business,” said Nigel Rayner, research vice president of Gartner. “This year’s predictions focus on the need for BI and performance management to deliver greater business value.”

To me this immediately suggests one, potentially awkward, question – what on Earth have some BI initiatives been focussed on before 2009 if it was not transforming and improving business?
 

Education and cultural transformation

Back in September of this year, Obis Omni were kind enough to invite me to speak at their Forum 2008, which took place on the outskirts of London and had the theme of “Realising Business Intelligence & Corporate Performance Management Success”.

The strap-line of my presentation was “EMIR – A case study in cultural change”. I have written about some of the themes that I discussed at this seminar elsewhere on this blog (e.g. about the importance of promoting your project in Marketing Change and the strong role to be played by extended business teams in Scaling-up Performance Management). In this article I am going to talk about some aspects of the pivotal area of education.
 
Obis Omni
 
Background on The EMIR Project can be found elsewhere on this site. Briefly it was a business intelligence / data-warehousing project aimed at improving the profitability of the European operations of a multinational insurance organisation.

More importantly, EMIR was always seen as primarily a cultural transformation initiative. The explicit aim of the system was to transform the culture of the organisation into one in which the use of credible, timely and easy-to-use information became as much second nature as picking up the telephone. Of course one initial learning here is that if you are in the business of cultural transformation, it helps an awful lot to tell people that this is the case. Having this element as a public goal was of great assistance.
 
 
Making a good first impression

Having already established a strong extended business team (see the links in the first paragraph above) the project team also realised that there was another important group to win over; our first set of 20 or so training delegates. We felt that if they went back to their offices singing the praises of EMIR then this, supported by the voices of the extended team would give us the necessary momentum to carry us through the first training phase and make a great start to our cultural change work.

It is often said (perhaps sometimes glibly) that as much attention should be paid to the deployment of IT systems as to their development. Many IT managers may not truly believe this in their heart-of-hearts, perhaps an “if I build it, they will come” attitude is sometimes more prevalent. However, with the EMIR project we took the educational aspect extremely seriously.

To start with this we made EMIR training a 3-day event, something that was unprecedented in IT training in the organisation. Second, we insisted that all delegates (the senior managers of the European organisation) travel to London to attend the course*. One reason for the duration was that we wanted to cover a lot of ground, but also we wanted to send a message that this was an important event and merited the devotion of an appropriate amount of time.

A lot of effort and thought went into the presentations that would be made, the different styles of training (some lecture style, more hands-on), the quality of the supporting training materials, the arrangement of the rooms and so on. I assigned one of my senior managers to oversee the training and we also employed an external training consultant to help us design the courses and user guides and achieve the professional look that we were going for.
 
 
The importance of real-life examples

Sometimes training simply explains how to use the technical features of a system, but, again, we were in the business of cultural transformation and so this shifted opur emphasis. Because of this, and also because the system was pretty intuitive and easy to use, in training we focussed on using the system to address real-life business problems. One example of this would be estimating the future profitability of a book of business based on historical trends.

This approach meant that the business value inherent in the system was clearly demonstrated. This was not an IT system, it was a business system. A key first step in changing the behaviour of managers was establishing that there was something in it for them; namely that they could get at information that was previously unavailable, that access to information was quick and easy and that their decision-making would be enhanced. Ticking these boxes through our real-life exercises helped to engage the enthusiasm of delegates and made them more receptive to our other proposals for how to build use of the system into their day-to-day lives.

This business-focussed training was initially carried out by our actuaries, however as demand for training soared in later weeks, I also ran many of these workshops. It was potentially a major challenge for an IT person to be telling insurance underwriters how to run their business, but something that I actually enjoyed very much. While discussing training personnel, we always had at least two people present in the classes as well as the lead trainer. The role of these other people was to check that delegates were keeping up and help anyone who was struggling with an exercise. We did not want anyone to fall so far behind that they became disengaged from the programme.
 
 
Breaking the back of cultural change

Our approach worked and our first twenty delegates became converts to the EMIR cause. Before the first training session, delegates has (understandably) been somewhat reluctant to commit so significant a period of time to the training process. After it an example of the type of message that attendees took back with them to their offices was: –

“This is the best management information I have seen, it represents a big leap forward”

It was not all down-hill from this point and a further article will deal with how we sustained cultural change over the latter stages of this project. However, after this initial success, some things became easier and we had safely negotiated what was probably the largest hurdle in the project.

Given this, I was quite happy to release some project funds for champagne at the end of our first three days, but should stress that the project was brought in under budget nevertheless.
 


 
Continue reading about this area in: Sustaining Cultural Change.
 
 
Note: –

* In latter training phases – having succeeded in making our point – training was often carried out in each European country, something I will cover in the future.