The Essentials dashboard serves as the home screen of the Essentials platform and the initial communication center for users. Through feedback and analytics, we saw that the dashboard's engagement was extremely low, and the communication channels were not effective.
The dashboard's UX needed to be optimized to allow for customization for different types of users. The communications needed to be streamlined, and support channels needed to be reimagined.
3 months
Senior UX Designer
Design Thinking
How might we make the Essentials dashboard more relevant and useful to meet the needs of all our different users, and add value by modenizing our tech stack to enable more features.
Improve Communications
Enable Customization
Establish Task Lists to Increase Efficiency
Users should be able to select how they want to work. Provide:
Create Effective Help and Support Channels
Stakeholder interview notes where they outline their goals. (Miro)
The complex part about designing this dashboard is that it had to be effective for multiple types of organization and personas. We decided to focus on two opposing types of organizations to start.
From there, we identified two personas that were responsible for some of the same billing tasks: Paula, the practice administrator for the large health clinic and Marly, the owner of the catering/ meal delivery organization.
We launced a GainSight survey to gather over all user sentiment about the current dashboard.
We spoke to power users who handled claims and payments for large clinics, like Paula. We found that their needs were dynamic. We recorded these needs in Miro.
We focused our ideation sessions to dig deeper into the task lists and progressive support.
The Checklist should help both Paula and Marly with:
Feedback from users really impacted the design. The users did not like a lot of change, because they are measured by their productivity. When things are moved around or changed, they have to take time away from tasks to learn a new system. Knowing this, I tried to work within the information flow of the old dashboard.
We created a beta version and piloted it with a very small group of users. We set pilot goals and they were successfully met. In fact, we received only 6% negative feedback from users.
In the end, Availity decided to postpone the launch of the new dashboard and go a different direction. However, I learned a lot of great things from this project.
Say hello.