So why should UX be included in the implementation lifecycle? The needs of users constantly change, therefore, products need to change. Institutions such as Google and Apple realize the need for product design within systems. Why shouldn’t the rest of Enterprise? The matter of the fact is that one shoe size does not fit them all. Every product or interface whether administrative or normal, needs to cater for the works of users with different needs and varying business processes.

Enterprise is constantly challenged by the fact that users need training to maintain systems. UX challenges this notion of training asking the question: “Is this overhead even necessary?” I’m not saying training can be eradicated, I’m simply asking are we compromising quick delivery for simply researching the very users that use your system?

By investing in User Experience you are investing in a company with smoother run processes. Normal information driven websites might attract the information foraging user . Enterprise is however constantly bombarded by the needs of users logging into systems, not to forage, rather to maintain the very works of business. User flow and research thus become the oil that makes the economy of information systems run smoothly.

The next question that comes to mind is how do we measure ROI when it comes to User experience and information flow? ROI can only be seen in what I call the Blind Side. The Blind Side is the symptom of well implemented UX. Well Implemented UX goes unnoticed. The opposite thereof is frustrated users and management complaining about not being able to find what they are looking for. Legacy symptoms or should I say systems are infused with these frustrations. By adding UX to your budget you are therefore investing in less frustration ,not prolonging the 1990’s symptoms, but rather creating a future blueprint of excellence.