The following covers a case study recapping a year long project that aimed to design and build an employee time management experience for individuals working in the healthcare sector (healthcare professionals, HR, support staff at clinics and hospitals, etc.) based on current functional requirements.
The project called for a redesign of the experience and interface of an existing back-end system from the prior go-live to provide a clearer and more intuitive experience. This was a multi-month long project that was an opportunity to re-create the UI of an existing back end solution emphasizing human centred design, incorporating user feedback to ensure functionality meets practical needs.
Lessons from a discovery phase after the initial roll out feedback reinforced the value of engaging end-users for insights, fostering confidence, and ensuring positive outcomes throughout the redesign and build process.
UX/ UI designer
Patterns and guidelines
I joined the team as the base of the design system was created, over the months I added multiple new components and styles to the design system alongside other designers. And worked with developers to refine existing and new elements and their documentation.
Advanced prototyping
I created a multitude of prototypes in short timeframes that allowed us to test our stories as we designed them to ensure we were creating the best possible user experience.
Cross functional workflows
I directly worked with developers and PMO work streams to ensure the work we were doing on the design stream fulfilled all business requirements and was within scope. Where possible new enhancement were created with the aid of these work streams if required for the best user experience.
The goal is to dramatically improve how the healthcare workers, managers, schedulers of our client organization manage their workloads - having an indirect impact on quality of care for patients by removing friction from a critical tool. Efficiency and productivity enabled by UI/UX decisions, saving users time and allowing staff to focus on patient care. Modern interfaces that are scalable and flexible, that can adapt to changing needs, ensuring technology remains relevant and meets operational demands. As this is a redesign of a prior launch that was met with a lukewarm reception, an improved user adoption and satisfaction for this release.
Our employees scheduling and timekeeping tool aids employees in managing their schedules, validating their work time, and providing a more consistent experience by reducing time-consuming manual processes. It introduces technology solutions that are mobile-friendly and provide access to accurate information, ensuring that employees are paid correctly.
The entire project was split up into 21 different features of various complexities. For each story we followed a process of:
- Initial discussion and research
- Flow and wireframe sketching
- Wire framing and medium fidelity screen designs
- Prototyping in med fidelity
- User testing of prototypes
- Final design in high fidelity.
The end to end process could take anywhere from 2 - 4 weeks based on complexities, and for some stories the user testing took place multiple times to arrive at the best solution.
Involving developers / Cross-stream workflows
As the designs were done as a wrapper on an existing back end, the initial discussion and research heavily involved back end devs to fully understand what we already had in terms of API functionality and data that could be displayed. Discussions with the devs took place throughout the process of each feature, it allowed us to understand the limitations of the front and back end, while also allowing us to introduce new capabilities where possible with their support.
Testing
With the aid of a pair of dedicated user researchers, 90% of our features went through at least one testing cycle with a minimum of 3-4 users. Once we had a base design for the pages, we could create medium fidelity variations for each page pretty fast that allowed us to create prototypes where we could test the flow of users going through a handful of different scenarios. Each testing cycle would provide us with feedback that we would continue on with into the next phase. It also allowed us to uncover more insights on day to day workflows that might not have been found during requirement gathering from client stakeholders.