Explaining a Complex, Transactional Enterprise UX Engagement
If is not easy to explain the UX on a complicated application even if you have plenty of time and lots of visuals. But on Behance, with busy people who just want an idea of the work and the limitations set forth by non-disclosure agreements, the story of UX becomes even more abstract and difficult to explain.
With that, here's a series of images reflecting a large-scale application that is the first-of-its-kind for healthcare: an application that checks patient's benefits and then prescribes and orders treatments online. These treatments require a great deal of documentation for payers (insurance companies). The application engaged as many as 5 vendors at any one time, with a multitude of APIs and CRM systems activated throughout.
Critically, my role with the small agency that was responsible for front-end design and overall client engagement, had to straddle the standard UX of wireframes, user journeys and sitemaps but everything from technical guidance, insight into user behavior, detailed functional specifications, business requirements documentation all the way through testing and implementation.