Keyzen - Mobile & web application
Reimagining Multi-Factor Authentication for Keyzen
Created a cohesive MFA experience that connects device enrollment, authentication decisions, and recovery across Keyzen’s product ecosystem.
3 mins read
Product
Enterprise MFA Product
Role
Responsible for UX flows · IA · Wireframes · UI · Design System
Method
A Secure authentication experience across desktop and mobile
Keyzen Auth is a centralized multi-factor authentication (MFA) Application for employees accessing Keyzen’s cybersecurity products. The project explores how desktop sign-in and mobile verification can work together across three connected journeys: device enrollment, authentication, and device recovery.
The Challenge
When Authentication Interrupts Access
Employees rely on multi-factor authentication to access Keyzen’s cybersecurity products. However, unexpected approval requests can make it difficult to judge whether a sign-in is legitimate, while losing a trusted device can interrupt access altogether.
The design challenge was to connect device enrollment, sign-in verification, and recovery into one clear, secure journey—helping employees make informed decisions and regain access when their trusted device is unavailable.
THE SOLUTION
One Connected Experience, From Enrollment to Recovery
I brought Enrollment, Authentication, and Device Recovery together into one centralized MFA experience, connecting desktop sign-in with mobile verification to help employees make informed approval decisions and regain access securely when a trusted device is unavailable.
RESEARCH
Turning Research Into Design Opportunities
The competitive analysis, persona insights, and business objectives pointed to three priorities: clearer approval decisions, secure device recovery, and consistent MFA across Keyzen’s products. These priorities shaped the design strategy, connecting enrollment, authentication, and recovery into one continuous experience.
Business Objectives
Strengthen Security — Verify employee identities before granting access.
Centralize MFA — Deliver consistent authentication across Keyzen products.
Minimize Disruption — Help employees regain secure access when problems occur.
Simplify Support — Reduce avoidable Helpdesk intervention through secure recovery.
Key insights
1. Centralization creates consistency: Unify MFA across cybersecurity products to strengthen access security and reduce avoidable IT support.
2. Recovery is part of the user experience: Help employees securely regain access after losing a device, while enabling Helpdesk teams to verify identity reliably.
3. Authentication needs more context: Provide clear sign-in details so users can distinguish legitimate approval requests from suspicious ones.
Blueprinting the End-to-End Authentication System
Using Systems Thinking and Interaction Design, I mapped how employees sign in to Keyzen’s products on desktop and verify their identity through the Keyzen Auth mobile app. Inspired by Microsoft Authenticator, I considered both the primary approval flow and exceptions such as denied requests, timeouts, and lost devices.
I established a clear Information Hierarchy across two connected touchpoints: desktop communicates sign-in progress and verification status, while mobile supports device enrollment, approval decisions, and device management. Each platform plays a distinct role in one continuous authentication journey.
I translated this structure into desktop and mobile wireframes, connecting each action to its corresponding response and next step. This helped define the interaction flow across successful sign-ins, failed attempts, and recovery scenarios.
UX DEcisions
Key Design Decisions
Make Device Enrollment the Starting Point of Trust
The Challenge
Employees need a trusted device to verify future sign-in requests.
My approach
I structured enrollment as a guided journey with clear steps and progress feedback.
Design intent
Make device setup easier to follow and establish a reliable starting point for authentication.
Give Employees Context Before They Approve
The Challenge
Unexpected approval requests can leave employees unsure whether a sign-in is legitimate.
My approach
I designed the mobile approval flow around reviewing the request before choosing to approve or deny it.
Design intent
Help employees make informed decisions before granting access.
The Challenge
Losing a trusted device can interrupt access and leave employees unsure how to proceed.
My approach
I incorporated device management and recovery into the authentication lifecycle, beyond the successful sign-in flow.
Design intent
Make recovery steps clear while preserving the need to verify identity.
VISUAL SYSTEM
A Consistent Foundation for Authentication
I translated Keyzen’s brand into a reusable Design System, combining teal and coral with consistent typography, spacing Design Tokens, and a shared Component Architecture. Defined interaction states helped create a consistent visual language across desktop and mobile.
I considered Accessibility (WCAG 2.2) when defining color contrast, focus states, typography, and feedback patterns, keeping clarity and usability central to the experience.
Design system outcomes:
Consistent UI patterns across desktop and mobile.
Reusable components and defined interaction states.
A scalable foundation for future authentication flows.
Accessibility considerations built into design decisions.
Testing & iteration
Refining the Authentication Experience
Screen 1 — Initial Design: The initial design prioritised quick access by keeping authentication codes visible and account actions prominent. However, visible codes raised privacy concerns, while the delete action competed for attention.
Screen 2 — Iterated Design: I refined the interface by masking codes by default, using a neutral delete icon, and introducing a dedicated QR scanning action. These changes prioritised privacy, improved visual hierarchy, and made key account actions easier to distinguish.
FINAL EXPERIENCE
One Connected Journey. Three Moments of Trust.
The final experience connects device enrollment, sign-in verification, and device recovery into one cohesive MFA journey. Each step addresses a key challenge—from establishing trust to making informed approval decisions and restoring access securely—bringing greater clarity and consistency to authentication across Keyzen’s products.
1. Device Enrollment
Building the Foundation of Trust: Before employees can approve sign-in requests, they need a trusted device. This journey guides them through setting up Keyzen Auth and registering a device to establish a starting point for secure authentication.
2. Authentication
Making Every Approval Count: With a device enrolled, employees can review and respond to sign-in requests across Keyzen’s product ecosystem. Clear request details and distinct actions support informed approval decisions
Device Recovery
Restoring Access Without Losing Trust: When a trusted device is lost or unavailable, employees need a clear path forward. This journey explains the recovery steps and available support so they can understand how to regain access securely.
Impact & Outcomes
I connected 3 authentication journeys across 2 platforms into one experience. By mapping key scenarios and creating reusable components, I made enrollment, sign-in verification, and device recovery more consistent. The design provides a foundation for future growth, with usability and operational impact yet to be measured.
What i learned
This project helped me see how enrollment, authentication, and recovery work together. I learned to consider security risks early, plan for failure scenarios, and make interactions easier to understand. It reinforced the importance of making design decisions that support the entire user journey.
Explore my other case studies
website design
Making Custom Handcrafted Shoes Accessible Through E-commerce
I created custom footwear e-commerce experience for Firstcraft, combining UX strategy, product customization, and interaction design to simplify shoe personalization and make handcrafted footwear more accessible through an intuitive buying journey.
Read Case Study
web application
Building a Centralized Control Platfrom for Identity Verification
Structuring complex identity verification operations into a scalable control platform that balances administrative efficiency, governance, and system-wide visibility while enabling enterprises to manage tenants, users, licenses, and platform health.
Read Case Study