Security MFA Bypass Request

A secure, low-visibility path for handling legitimate MFA bypass requests — balancing strict enterprise security protocols with a frictionless path for developers and support teams.

Overview

The MFA Bypass request workflow needed to serve two audiences at once: security engineering, who required strict governance over every exception, and the requesters themselves, who needed a fast, low-friction way to submit a valid request without getting lost in the wrong process. This project redesigned that request and approval journey end to end.

Role

Product Designer

Timeline

Cisco, 2026

Framing the Problem

Defining a request life-cycle that didn't exist yet

  • Define the general account & MFA bypass request life-cycle
  • Define the request submission process flow
  • Define requirements
Framing the MFA Bypass problem

Goal

A better journey, not just a better form

Enhance the overall user journey for the MFA Bypass request process, and improve the MFA Bypass Approval form itself — so the right requests move quickly and the wrong ones get redirected before they become tickets.

Role

Owning it from discovery to delivery

  • Owned the end-to-end UX design process from discovery to high-fidelity prototyping
  • Facilitated internal design feedback sessions and cross-functional alignment with the Security Engineering team
  • Synthesized stakeholder feedback into iterative product updates

Key Impact

Security and speed, not security or speed

Optimized governance

Balanced strict security protocols with developer velocity by implementing a secure, low-visibility entry point.

Frictionless workflow

Eliminated manual data entry via smart automation (AD/ESP integration), substantially reducing form drop-off for valid use cases.

Proactive support

Guided unqualified users to alternative authentication options instantly, preventing redundant operational support tickets.

Deliverables

A prototype refined through feedback

Finalized the high-fidelity prototype through multiple rounds of internal and external feedback sessions.

Final MFA Bypass deliverables

Clarity is what makes a form fast

Clear data hierarchy matters most when people are filling out a form under stress. Designing for the MFA Bypass workflow meant treating that hierarchy — not the number of fields — as the real usability problem.

Learning

Security engineering as a design partner

Balancing enterprise security with frictionless UX: designing the MFA Bypass workflow taught me how to strictly adhere to enterprise security compliance while minimizing user friction. Clear data hierarchy in forms is critical when users are under high-stress, time-sensitive situations.

Cross-functional alignment in technical domains: collaborating closely with the Security Engineering team highlighted the importance of translating complex technical requirements into intuitive user flows. Using Jira Align and Confluence helped synchronize stakeholder feedback, ensuring the final prototype met both engineering constraints and user needs.

↑ Back to Top