Ashley Lynn
Admin Tool Re-design
Re-designing an in-house program
THE PROBLEM
Provider profiles weren't being updated regularly, which created discrepancies in data.
Providers are onboarded differently depending on the department they are in. This creates discrepancies in information. Some providers have filled out profiles, and others have bare profiles, if any at all.
With a push to improve care for our patients, we wanted to empower providers to take control of their profiles. We needed to make this be as simple as possible--that if they didn't receive adequate training they could still poke around and figure it out on their own.
HIGH LEVEL TIMELINE
4-6 months for the first phase.
MAKE OF THE TEAM
Research, design, front end developers, back end developers, associates,3rd party vendor, project managers, directors.
KEY GOAL
Create a backend program that will make it easier for data input.
MY ROLE
Research, site map, content inventory, application mapping, high fidelity wire framing, prototyping, facilitating testing, recruiting, moderating testing.
Co-lead the research portion of the project, teaming with a 3rd party vendor.
Before the launch of the project I had no experience with the platform. I needed to learn and become familiar with each screen and what fields were on them and what needed to be removed, added, expanded on. This was an undertaking. After completing the site map, and content inventory the process of creating the application map was started.
UNDERSTANDING THE USER
Professionals were the main user for this project. Trying to design something that would be intuitive to use without any training was more difficult than anticipated.
We had to design with the anticipation of someone who is very distracted, working through lunches, and used to having multiple programs. We wanted to design something that could utilize single sign on (SSO) so it would be one less password to remember.
View at the profile level.
LinkedIn is something many professionals are used to using. We decided to go with that type of a feel for inspiration for this project. For a provider or someone that is not in here frequently wanted to make sure that any edit was intentional. Super users have a different view.
BREAKING DOWN THE PROCESS
Daily touch points and design syncs kept the project moving.
The project was broken into phases. We used an Agile/Scrum approach. Once the design was started it was broke down into user types, and screens for those associated types. Starting with the lowest user type and expanding on that as the screens were wire framed out. Every two weeks we met and showed the Director and other stakeholders prototypes for functionality of what was done so far. This helped everyone to be on the same page, and spot any concerns early before it was expanded on in the more complex user types.
Testing was completed with internal colleagues, mixed with those that had used the current tool and those that had not. I moderated those sessions and analyzed them to provide feedback for improvements for the next phase.
SOME FINDINGS:
The LinkedIn approach was easy to use.
Users were easily able to complete majority of tasks, even those that had never used the current tool.
The left-side nav was easy for users to navigate the page
When they were given a task to do and they had to find specific sections it was natural for them to look at the left-side to see the navigation options..
Drag and drop functionality was enjoyed.
Drag and drop was a functionality that some concern had been raised about. When in testing majority of users were able to easily drag and drop.
TITLE OF THE CALLOUT BLOCK
LESSONS LEARNED
The importance of design syncs and weekly walk-thrus helped keep team members aligned.
This project was fun and challenging for me. I had never used the original tool before the launch of the project. I had to create a site map and content inventory, which was time consuming. Then I had to create an application map to make sure all members were aware of each phase that we would be working on. This also helped stakeholders decide which functions they did or did not want in the re-designed version.
I learned a lot about prototyping and and chunking up a large project into smaller sections to be more efficient. Working closely with design and a 3rd party vendor was a great experience. Communication was key for this project to be a success and remain on the two week sprints.