When clinicians encounter patients, they need to quickly review their history, complete and approve forms in progress. This entailed scrolling and time, making it difficult to find the form they needed to complete their workflow. As a result, they spent less time caring for the patients during their visits.
I held a Kickoff Meeting and met with the product owner and stakeholders to gather requirements. I gained insights into the goals, user needs, and technical constraints.
I conducted interviews with stakeholders and SMEs to better understand their habits, desires, and needs. I wanted to know how their answers would vary depending on their skill level.
Key Findings & Insights
The interviews helped me understand the current flow and define the users: nurses, physicians, and students. Nurses were the primary users.
Users need a way to quickly filter forms based on statuses in desktop and mobile views. Their goal is to move through their workflow more efficiently to see as many patients as possible per day.
I found that users of varying roles have different needs. As a result, I created three user personas for nurses, physicians, and students. Nurses were the primary users, so that was my main focus. I revisited these personas often to remind myself of user’s needs and frustrations and maintain a user-centric focus for the duration of the project.
I created a user flow, which gave me a clear picture of the steps that the user would need to take to get to their final goal in the most effective manner possible.
I identified core features that answered my persona’s problem.
I explored different solutions with sketches until I found a combination of elements and features that would be as intuitive as much as possible. I presented these to the team and we decide to move forward with the Dropdown Menu option.
Next, I created wireframes in Miro and presented them to stakeholders for feedback. There were several rounds of iterations.
The HF Team made notes of the positive and negative feedback so that I knew what to rework.
It’s not clear in the UI that users need to press the button labeled with the Filter Icon to enter the feature.
Areas for Improvement: make the icon of the filter button more understandable. Consider adding the term “Filter” to the label or replacing the icon altogether.
Resolution: The team agreed to put the text “Filter” on the button.
I made changes based on the user feedback. I created a high-fidelity version of the feature and added the label “Filter” to the button.
My solution aligned with the objectives set in place. It includes core features necessary for users to filter forms efficiently and became the standard way to filter across our suite of applications.