Porridge and the End User Experience

Porridge and the End User Experience

According to the Standish Group, what do IT projects that are defined as successful have in common with IT projects that fail? The common link to both successful and failed project is “end users.”

In successful projects the number one determinant factor of success was “user Involvement.” Similarly the number one reason listed for IT ‘fails” was – you guessed it – “lack of user input.”

Is this surprising? Yes and no.

When so many things can go wrong technically in any large IT deployment to have the number one cause of failure being people and not, by the way, the technical team or their skill sets but the actual users one could find that surprising.

But in another way it is not surprising at all.

Information Management systems fall in this category and perhaps the biggest thing IOS has learned in installing over 500 of them is this: the user experience means everything. In fact, when a company invests in a serious content management system what are they really hoping they bought? Great software? Cutting edge technology?

Savvy companies are really hoping they have purchased an end user experience so positive that adoption will happen quickly and without management mandate... that the business process re-invention will be not just accepted but applauded because their people are gleefully embracing a new and better way of working without kicking and screaming because they actually understand it…that change is actually managed….you know, change management?

Companies want to buy that end game and yet still engage in an outdated vetting process to determine which provider is most likely to furnish it.

Possibly the goofiest aspect of the buying process is that most companies ignore the finish line of the user experience – the end game - and focus solely on the false prophesies of RFP’s, different variations of software demo hell and requesting lengthy propaganda proposals where the authors will need to be  paid by the word or platitude.

So much of that is now baked into the techno buying culture that they ignore the one question they should be asking, one we actually love to hear. It would sound like this:

“Hey IOS: About 44% of projects like this are challenged - meaning over budget and over-promised. Roughly 24% are defined as abject failures. SO TELL ME SPECIFICALLY what you do to ensure a successful implementation ensuring a positive end user experience?”

That is a great and honest question.

Our answer?  IOS is small enough to be flexible and creative, to be responsive during design and implementation. IOS is large enough to have redundancies in our technical and software support roles. We are freaking Goldilocks.

This allows us to be able to focus on the end user experience and we work backwards from that. Everything that needs to occur to ensure that outcome is designed and factored including the sharing of what countless other companies have done in similar circumstances with our help.

Porridge anyone?

Share this post