Project Information

Healthcare Web Application was the company's flagship product. It had an old version that had not been updated in quite some time. Myself and the rest of the team were working to rebuild the product from scratch on a completely new tech stack, using updated modern UX and UI principles. It was meant to serve both new and existing customers.


The main problem that my team was tasked with was to completely redesign the Application that was being rebuilt on a new modern stack with a new modern interface. We had to make sure this new version could do everything the old version could do, but be more user friendly and easily understandable by those who have been using the old tool for many years.


I was the UX lead on the Healthcare Web Application. I worked on the project from initial brainstorming sketches, up to launching the MVP of the Application. I worked closely with the other designers, the product team, and the development leads from the initial stages of the project to the MVP launch. As the UX lead it was up to me to figure out how to best implement the features that were requirements of the stakeholders. I made sure that each step of the way we were considering the correct user personas and getting user feedback about all the designs the UX team was creating. I aided in the initial brainstorming and requirement gathering, the designing of both the UX and UI, and iterating upon the designs based upon user feedback. At every step of the way I made sure to consider the users who were upgrading and those users who were going to be new to the application.


We started by interviewing users of the old Application. We wanted to learn how they use the tool on a daily basis. I conducted interviews, remote video sessions, and focus groups. I learned how the tool was used and what kind of users used it the most. I also recruited a group of users who would be comfortable testing the different iterations as we moved forward with creating the new version of the application.

After the initial research was gathered we started white boarding what this new version of the application had to include. We wanted to be sure that we included the features, functionality, and user flow for all the different types of users. I was the voice of the user in all of these white board sessions.

Once the initial concept was decided upon we reached out to users in the user group to validate the user flows and what features were going to be included in the MVP of the Application. We wanted to make sure that the MVP of the Application could be utilized by them. We also informed them that we were going to be changing a few of their flows and although would be different from how they were used to doing things, that they would save time once they were shown the new Application. Once we explained this new way of doing things within the Application almost all of them were onboard for us to move forward. After that was verified we moved forward with another white board session to refine the design, before we started designing it within UXPin.

Once the designs were in UXPin we began laying out where each function should exist within the application. One of the most important parts of the Application was the home screen. We had to make sure that it showed a good overview and made it clear what was going on with each project, since users would be completing multiple projects at once. We made sure to validate what should be on each screen at every step of the way by showing the wireframes to our user testing group.

The most important screen that I worked to design was the Project Summary screen. This was the screen that users saw the most and had to give them a great snapshot of what was going on with that project. This screen went through many different iterations, but over the course of all that user testing ended in a really good place. It was different from the users were use to with the old tool, but once they saw where everything was and how to use the new templating feature they really thought this was a great improvement over the old tool.

We made a lot of design choices between the first wireframes and the MVP wireframes. We landed on a tool that was different than the old tool, but much more streamlined and greatly increased the speed at which our users could work. By adding greatly improving template functionality our users were able to do things they could never have done in the old tool. At every step of the way we made sure that the changes to the tool were ones that would help them.

The project details screen contains a lot of data, but it is easy to drill down and see just what you care about. It allows the user to have control and be able to see just what they want to see at any point. I made sure to continually test this screen with our user group. They gave a lot of feedback which lead us to the final design for the MVP.

After the first version of the application shipped, I had already begun working on how to improve upon it. Using internal and user feedback I had come up with a way to simplify some user flows, which lead to the design of new navigation for the application. I left the project before the new navigation could be implemented.