Is it even a good idea? Combining personal and work accounts into one
Due to confidentiality agreements for research participants and the product, I am unable to show the deliverables in detail within this portfolio. However, I would be delighted to walk you through the process and share insights during an in-person or virtual meeting.
A Unique Login Solution: Simplifying Access for Healthcare Providers
My Health Account (MHA) is designed for public use, while My Health Account Workforce (MHAW) is tailored for health practitioners. These two applications operate separately, requiring users to go through the verification process twice if they use both.
A high-value client, a health service provider with 30,000 users, requested that their users be able to sign up and log in to MHAW using their personal email addresses. This is common among locum healthcare providers who often use personal emails to access clinic applications, especially in smaller clinics without dedicated onboarding or HR teams.
To address this, we proposed a hybrid account allowing a single login for both MHA and MHAW. However, this raised security concerns and user comfort issues, as users needed to be assured that their personal information would not be shared across platforms. Additionally, the user flow had to be clear to prevent confusion about whether they were accessing personal or work details.
We want to address this client's needs but we also need to consider other health practitioner users, and make sure that implementing this won't affect their experience negatively.
Image: My Health Account
Image: My Health Account Workforce
Goals and Objectives: Crafting a Seamless and Secure Experience
Create a technically viable design solution: before presenting it to users for concept testing.
Develop high-fidelity designs: to accurately reflect the proposed solution.
Conduct user testing: to understand users' thoughts and feelings about this concept, while also identifying which UI works best through A/B testing.
Overcoming Obstacles
Short Time Frame: We had only two weeks to learn about the requirements, work with business analysts and developers to find a viable solution, and present the design to potential users.
Knowledge Transfer: Many subject matter experts and technical team members were finishing their contracts in two weeks, necessitating quick answers to our questions.
Revenue-Driven Decision and High Expectations: Implementing this feature would help us generate revenue for the app, and we needed answers quickly to present to our potential clients.
Image: Quick user flow mapping to identify potential UX issues
Mapping User Journeys And Testing Concepts with Real Users
We mapped out potential user flows and discussed them with some healthcare service providers. Feedback from three different users varied significantly:
One was against using the same account for work and personal purposes.
Another found the idea convenient.
The third was neutral with no strong opinion.
Hypotheses and Insights: Addressing User Concerns
Base on some feedback, we set up the hypotheses and problems that need to be solved for users:
Users might feel uneasy about signing up for a work system using their personal email.
Users might fear their personal health information would be shared with their work account.
Users don’t need to fully grasp the purpose and functionality of MHA, but they should clearly perceive its value as a single login solution.
Users might be confused after adding their workforce account to their personal account.
Designing for Security and Simplicity: Our Proposed Solutions
Our primary goal was to ensure users felt secure, knowing their personal and work information was kept separate. Personal health information is highly sensitive, akin to banking information.
I drafted design solutions and reviewed them with business analysts and developers to understand technical feasibility and constraints. We decided that allowing users to sign in with their personal account and then add their work details was the best approach.
Bringing Ideas to Life: Prototyping and A/B Testing
MHA is primarily a login portal rather than a frequently used application. I created an interactive prototype simulating a user being onboarded by HR, logging into their personal MHA account, and adding work details to access their work system.
We want to test the onboarding scenario with potential users, seeking feedback on the process and evaluating different UI designs. Our goals were to:
Gauge users' comfort and understanding of the system.
Identify pain points and security concerns.
Determine which UI provided a better sense of security and clarity.
Outcomes and Deliverables
Interactive Prototype: Developed with scenarios for A/B testing.
User Feedback: Collected insights from user testing to refine designs.
Design Solutions: Proposed clear and secure hybrid account solutions.
Stakeholder Buy-In: Ensured stakeholders were aligned with the new approach, setting the stage for future implementation.