Technology Rollouts & Performance

Good technology rollouts really count. Many people I have worked with over the past few years often face the tough experience of having to make decisions around new technology that will fundamentally affect business results. In the past 18 months, I have noticed many clients have been pushed into situations where things must be upgraded urgently (due often to a merger).

Often this technology is something like a new platform, a best-of-class project management system or a set of core capabilities the business has never had. At times, these needs arise from a system that was put into the business 20 years ago and since then the IT team have been building bolt-on solutions. Eventually it reaches the point where there are so many workarounds for the users that everyone just considers the system a massive handbrake. Organisational change has to occur, as the focus for increased performance is greater than ever.

A good example of this kind of new technology is Oracle’s Seibel CRM product. AFG Group, one of Australia’s largest brokers, used this product with great success. They use it to source products, lodge applications, generate leads & manage clients, all from a single point of entry. Check out the video below – at 3 mins 9 secs, it shows how they are now using this technology to manage their teams and other overseas business development activities. This project has enabled AFG to stay ahead of the game in an extremely tough market.

The general solution is to spend up to hundreds of millions of dollars on new technology to consolidate workflows, reduce time taken to get information, or find the right information etc.

What often actually happens though is this:

  • The project goes way over time and budget and the change management process fails
  • Only specific users get the new technology right and they were the high performers anyway
  • The strategic planning done prior to implementation was nowhere near robust enough & so major gaps appear with the implementation & rollout to users
  • The final product offers only 60% of the capability promised and the system workarounds continue

If these were the only blocks faced after implementation, funnily enough the situation would actually not be too much worse. The problem is that this is only the start. What then seems to happen is that while the implementation occurs, sales and/or service levels drop significantly and sales managers start to get punished for their lack of results.

Many users get disillusioned and they start to either leave or look seriously for jobs in competing businesses in the same vertical. This causes increases in staff turnover and a need to then recruit more people at a time when training and reducing the time to competency for new team members is not the highest priority. Finishing the implementation and knowing the systems core capabilities actually collect “all” of the data accurately and can be used to get results is the priority.

So what’€™s the answer? Consider the following:

  • Who is on the rollout project team and why are they there?
  • Who is missing that should be there? E.g. possible managers of users who know what functions have to keep on going not matter what
  • Have you looked at who your absolute best talent is and how they can add value to the project?
  • What kind of mini pilots have you or are you intending to run prior to getting serious about the rollout?
  • If you have gathered groups of high performers to do the testing, have you then ensured these people are trained in knowledge-transfer and work-place training techniques to get your population back to its core results capability ASAP? How is this behaviour change actually going to occur on the ground?
  • What kind of knowledge-capture processes do you have around the more “€œtacit”€ or informal smarts the high performers have? How do these apply in the “€œNew”€ technology platform or world? How are these to be transferred? How is your talent management process taking this into account?

Making sure you have covered off the above at the very least will enable you to keep leveraging your best people to transfer their results across populations. Sometimes you may need to bring in technology providers you have never thought of prior to the project. In fact, this might not become apparent in any of the project design phases and might only be discovered during implementation.

The general solution is to spend up to hundreds of millions of dollars on new technology to consolidate workflows, reduce time taken to get information, or find the right information etc.

What often actually happens though is this:

  • The project goes way over time and budget and the change management process fails
  • Only specific users get the new technology right and they were the high performers anyway
  • The strategic planning done prior to implementation was nowhere near robust enough & so major gaps appear with the implementation & rollout to users
  • The final product offers only 60% of the capability promised and the system workarounds continue

If these were the only blocks faced after implementation, funnily enough the situation would actually not be too much worse. The problem is that this is only the start. What then seems to happen is that while the implementation occurs, team performance levels drop significantly and project managers start to get punished for their lack of results.

Many users get disillusioned and they start to either leave or look seriously for jobs in competing businesses in the same vertical. This causes increases in staff turnover and a need to then recruit more people at a time when training and reducing the time to competency for new team members is not the highest priority. Finishing the implementation and knowing the systems core capabilities in order to actually collect “all” of the data accurately often is the priority.

So what’€™s the answer? Consider the following:

  • Who is on the rollout project team and why are they there?
  • Who is missing that should be there? E.g. possible managers of users who know what functions have to keep on going not matter what
  • Have you looked at who your absolute best talent is and how they can add value to the project?
  • What kind of mini pilots have you or are you intending to run prior to getting serious about the rollout?
  • If you have gathered groups of high performers to do the testing, have you then ensured these people are trained in knowledge-transfer and work-place training techniques to get your population back to its core results capability ASAP? How is this behaviour change actually going to occur on the ground?
  • What kind of knowledge-capture processes do you have around the more “€œtacit”€ or informal smarts the high performers have? How do these apply in the “New”€ technology platform or world? How are these to be transferred? How is your talent management process taking this into account?

Making sure you have covered off the above at the very least will enable you to keep leveraging your best people to transfer their results across populations. Sometimes you may need to bring in technology providers you have never thought of prior to the project. In fact, this might not become apparent in any of the project design phases and might only be discovered during implementation.

The general solution is to spend up to hundreds of millions of dollars on new technology to consolidate workflows, reduce time taken to get information, or find the right information etc.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s