Project Type
Enterprise Platform UI/UX Redesign
Project Timeline
July 2024 – February 2025
My Role
Product Designer - Platform UX (Navigation, Workflows, Design Systems)
Team
2 Product Designers
Content / Copy
Context & Challenge
At Futurex, CryptoHub supports security engineers managing encryption systems for Fortune 100 clients. While technically powerful, decades of organic growth made everyday actions hard to predict and easy to second-guess.
The research findings:
Navigation Debt:
Engineers spent 3–5 minutes finding routine settings across 10+ tabs (shadowing 8 users)
Safety Anxiety:
6 of 8 engineers hesitated on destructive actions because high-risk and low-risk tasks looked identical
The Goal:
Make a high-power cryptography platform predictable, so security engineers can complete routine and high-risk tasks quickly and with confidence, without relying on memory or second-guessing.
Navigation Structure
The legacy navigation was a "junk drawer" of features. I led a card-sorting workshop with 6 Solutions Architects to move toward a task-based mental model.
The Validated Schema:
Devices & Clusters: Hardware and HSM infrastructure
Keys & Policies: Encryption assets and rules
Services & Integrations: Cryptographic capabilities
System Operations: Monitoring and recovery
The Validation: I verified this new structure through tree testing with 8 security engineers, achieving an 82% task success rate compared to 54% with the legacy UI.
Workflow Design
I focused on Cluster Management, a high-stakes workflow where engineers previously struggled to verify if configurations were consistent across global devices.
The Solution: Real-Time Feedback
Explicit Status:
I designed clear status badges ("Connected," "Out of Sync") directly into the device lists.
Success Confirmation:
Added high-visibility success banners (e.g., "24 items synced successfully") to eliminate "did it work?" uncertainty.
Validation:
In moderated testing with 6 users, task completion time for manual backups dropped from 4 minutes to 2 minutes.
Creating encryption keys is governed by complex compliance rules. Previously, these rules were "invisible" until a user hit an error at the final step.
The Design Decision: Upfront Validation
Surfacing Constrains:
I redesigned the flow to show algorithm requirements and approval counts while the user is selecting parameters.
Result:
In testing, 5 out of 6 engineers successfully configured compliant keys on their first try (vs. 2 out of 6 previously). This eliminated the tedious rework cycle.
Interaction Patterns
To ensure Futurex could add new services without re-introducing friction, I defined consistent interaction patterns so new services behaved the same way across the platform.
Standardized States:
Documented behavior for every component across Default, Active, Loading, and Error states.
The Service Catalog:
Designed a modular "marketplace" UI where every service - from Google EKM to IoT Key Injection - follows the same pattern: preview capabilities → configure settings → deploy. This consistency meant engineers could deploy unfamiliar services without documentation.
Result:
The support team reported a 70% reduction in deployment-related questions.
Impact & Outcomes
This redesign moved the platform from a "manual-heavy" tool to an intuitive operational system.
average improvement in task completion time for core workflows
reduction in navigation-related support tickets (6-month post-launch data)
faster onboarding for new engineers.
task success rate in navigation tree testing
The redesigned CryptoHub interface launched at RSA Conference 2025 in San Francisco and was subsequently presented at major industry events including Foro Copayment, Global Fintech Fest in India, and GITEX Dubai. The platform earned industry recognition including the CyberSecurity Breakthrough Award for "Encryption: Data Protection Solution of the Year" and was ranked #1 by ABI Research as Top Innovator and Leader in their Payment HSM Competitive Assessment, validating its position as the industry's first unified cryptographic platform.
Reflection
What I learned:
Experts don’t want fewer options - they want confidence. Predictability mattered more than simplification, especially in high-risk workflows.
What I’d Validate Next:
Involve security engineers earlier
Instrument analytics earlier for clearer attribution