Why mapping as-is can be quite a good idea…

If this doesn’t frighten you and/or make you extremely skeptical about so-called ‘experts’ then I don’t know what will, however I promised to tell the story in an earlier post …

Names and places have been removed to protect the innocent.

We were introduced to a large hospital group that was about to implement SAP. The CIO was an ex SAP person, IBM Global Services was the SI and numerous people from SAP were involved in the project;  it was apparently one of the largest implementations to date into a healthcare business and accordingly had a very high profile.

The short answer from our meeting with the CIO was the following:

    • can absolutely see that approaching the implementation this way makes complete sense…
    • ….can completely see how this would help our company…
    • …can’t possibly do it as we’ve already signed the contract with IBM GS and we can’t modify it now

We graciously retreated and waited for them to call back.

18 months later….

IBM GS have gone home with a ‘successful’ implementation to the contracted ‘on-budget, on-time’. The client has been left with a disaster…..

IGM GS have, in their wisdom, decided not too confront the as-is/to-be issue and therefore haven’t actually realized that a hospital is a hospital and the core processes is the same everywhere, PIPOHA (patient in, patient out, hopefully alive). They decided that since there were 9 different regions (same country, same laws, no sound reason for much process variance) they should therefore implement the system in 9 different ways…

Would it be cynical of me to suggest that it was in fact in their interest to do this as it would clearly result in many more chargeable days? (bear in mind that this would have been decided before contract signature and therefore the budget would have reflected this).

Unsurprisingly the call back arrived.

The client invited us back in to try to help sort out the mess as they had a system that nobody was using and had cost multiple millions to implement, (one of the IT group joked: “It’s the most expensive holiday booking system I’ve ever seen”). SAP had given them an estimate of the training rollout which was incredibly time consuming as they had to train differently in each region (it was measured in years!).

In short – Nimbus Control was deployed as a process layer on top of the SAP system displaying end-to-end processes with both the manual and automated steps shown and the training was delivered dramatically faster.

But that’s not really the point of the story.

Had IBM GS actually had the client’s best interests at heart they would have mapped as-is first and would have realized  that each region was in essence the same and that they only needed one instance of SAP to support the whole company.

Of course this would have meant that their consulting days would have reduced dramatically as well…


5 thoughts on “Why mapping as-is can be quite a good idea…

  1. Deja Vu here Mark! Except no one is correcting it out here 🙂
    They now think the problem is in technology alone! A process improvement is a journey. You must know where you are and then travel to where you want to be!

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