Recently I had a conversation with a prospective client about the user experience of internal applications. The question was about the ROI of having a good user experience of an internal application. While I may write another article on the math side of the ROI question, the conversation revolved around how the ‘internal’ application and experience isn’t always internal.
In my last blog post, I wrote about the need for your software / personnel / any customer experience to provide a consistent user experience. I wrote about an airline attendant who was less than helpful to me. That said, this rep was saddled by a computer system that clearly made it difficult for her to do her job.
David Armano wrote a short piece about Randy Pausch’s $100,000 salt and pepper shakers, and quoted Randy:
"If I sent a child into one of your stores with a broken salt and pepper shaker today, would your policies allow your workers to be kind enough to replace it?"
To paraphrase that, "if a customer called your call center with a problem today, would your software allow your workers to take care of the problem." This is my single biggest reason why I believe the user experience of internal applications are so critical. Very few applications today, whether ERP systems, time sheets, or CRM systems, are so silo’d that they only impact the users themselves. A bad user experience, e.g. rigid rules, antiquated systems, disconnected systems, bad data, etc., for a user of the system, rarely impacts that user only. If that user has to interact with the customer, make decisions on behalf of the customer, or provide customer data to a manager, then a bad user experience will have downstream impacts on your customers.
The next time you are thinking about whether to improve your internal systems, ask yourself how internal those systems truly are.






Miranda, EatonGolden Intern






















