Redesigning the platform behind 90M daily transactions

Redesigning the platform behind 90M daily transactions

Redesigning the platform behind 90M daily transactions

Every tap. Every swipe. Every secret - the engineers protecting it all couldn't trust their own tools.

Every time you tap your card at checkout, every time a nurse logs into a hospital system, every time a government official accesses classified files - there's a good chance CryptoHub is protecting that transaction. 7 of the world's top 10 banks. 15,000+ organizations. 90 million transactions per day.


But the security engineers using CryptoHub? They couldn't trust the interface. Two buttons looked identical - one was safe, one could break production. Finding a setting took 4 minutes of guessing. Every feature worked differently.


I redesigned CryptoHub's platform UX to transform uncertainty into confidence - reducing task time by 50%, cutting support tickets by 70%, and earning "Encryption Solution of the Year."

RSA Conference was the deadline. The team moved fast. Here's how we did it.

Role

Product Designer

Worked with: Solutions Architects, PMs, IT security and UX teams

Project Timeline

July 2024 – February 2025

Tasks

Platform UX
Navigation Workflows
Design Systems
User Research
Usability Testing

Tools

Figma
Maze

Context

The invisible vault

The invisible vault

The invisible vault

Think of CryptoHub as the control room for a vault protecting 90 million transactions per day.

Futurex built it. 40+ years of encryption expertise. The company governments trust with classified data.


The vault was bulletproof. The control room was not.

Problem

90% sure isn't enough

90% sure isn't enough

90% sure isn't enough

Fortune 100 security teams trust CryptoHub to protect their most sensitive data. These security admins aren't beginners - they build encryption for governments and global banks. But the interface made them second-guess every click. Finding a setting took 4 minutes. Dangerous actions looked identical to safe ones. Every service worked differently.


The interface relied on memory, not predictability. And 70% of support tickets were the same question: "How do I configure this?". When experts start hesitating, something is wrong.

Research

8 users. 340 tickets. 1 insight.

8 users. 340 tickets. 1 insight.

8 users. 340 tickets. 1 insight.

With any project, I start with questions:


  • Why are experienced security admins struggling?

  • Where does confusion happen most?

  • What can support tickets tell us?

The platform had years of legacy features. No one had mapped the user journey end-to-end. I started from scratch - shadowed 8 security admins (the users), reviewed 340 tickets, ran workshops with solutions architects.

The data was clear: 6 out of 8 admins failed basic navigation tests.

But data shows what. I needed to know why.


So I turned to our solutions architects - the internal team who trains Fortune 100 clients every day. If anyone understood how security admins think, it was them.

That reframed everything.

The interface was organized by system architecture. Security admins think in problems to solve.

Goal

Protect the protectors

Protect the protectors

Protect the protectors

Security admins safeguard millions of transactions, client data, and critical infrastructure every day. But they were spending time fighting the interface instead of fighting threats.


My goal is to give them confidence in their tools - so they can focus on protecting everyone else.

Design Process

Only if it made sense

Only if it made sense

Only if it made sense

One challenge was working with a 40-year-old company. Legacy features had piled up over decades. Changing one thing could break another. I couldn't redesign everything. I had to be strategic - fix what mattered most without disrupting what worked.

Q: How to balance info with UX?

Q: How to balance info with UX?

Q: How to balance info with UX?

Let's decide with data

Let's decide with data

Let's decide with data

Data partners hoped for more information on each product page. Design partners advocated for less clutter and better user experience. I tested multiple layouts with 12 security admins. The answer: progressive disclosure. Show key stats upfront, reveal details on demand.


Working with PMs and engineers, we found the balance that served both business needs and user clarity.

Q: 50+ features. Where do they go?

Q: 50+ features. Where do they go?

Q: 50+ features. Where do they go?

The old navigation mirrored the codebase. Made sense to developers. Not to users.

I ran card sorting with Solutions Architects - the team who trains clients daily. They didn't group by system. They grouped by task: "What do I manage? What do I protect? What do I enable?"

Navigation success jumped from 54% to 82%.

Design Solution

Danger looks dangerous

Danger looks dangerous

Danger looks dangerous

Key info upfront

Key info upfront

Key info upfront

One pattern, all services

One pattern, all services

One pattern, all services

Results

From hesitation to confidence

From hesitation to confidence

From hesitation to confidence

Security admins stopped second-guessing. They started clicking with confidence.

54

navigation success - down from 54%, fewer costly errors

0

faster workflows - across 15,000+ organizations

0

fewer support tickets - freeing teams resources

0

faster onboarding - new hires productive in days, not weeks

Recognition

RSA Conference 2025

RSA Conference 2025

RSA Conference 2025

41,000+ professionals, San Francisco

CyberSecurity Breakthrough Award

CyberSecurity Breakthrough Award

CyberSecurity Breakthrough Award

"Data Protection Solution of the Year"

ABI Research

ABI Research

ABI Research

#1 in Payment HSM Innovation

Global

Global

Global

  • India (Global Fintech Fest, Oct 2025)

  • Dubai (GITEX, Oct 2025)

  • Mexico (Foro Copayment)

Team

The team behind it

The team behind it

The team behind it

US. Europe. South Asia. Weekly calls in English, Spanish, Portuguese. Different time zones, same mission.

Beyond the platform, I designed booth and marketing collateral that launched CryptoHub to the world.


This work happened because of them.

Learnings

On wearing multiple hats

On wearing multiple hats

On wearing multiple hats

CryptoHub wasn't my only project. I was also designing Futurex's marketing website, contributing to the cloud platform, and supporting hardware launches.

And Futurex itself is a 40-year-old company - legacy systems, decades of features, every change could break something downstream. That taught me ruthless prioritization. Focus on high-impact areas first. The navigation overhaul unlocked everything else.

On earning trust with experts

On earning trust with experts

On earning trust with experts

Security admins didn't expect a designer to understand encryption, HSMs, or key lifecycle management. I spent my first weeks learning the language - not to become an expert, but to ask better questions.

By the end, Solutions Architects brought me into client calls. Engineers trusted my recommendations. My research helped PMs prioritize what to build next.

On the simplicity trap

On the simplicity trap

On the simplicity trap

My instinct was to simplify. But security admins don't need simpler - they need predictable.

I stopped designing for "ease" and started designing for "confidence." That shift changed everything.

The Bigger Picture

CryptoHub launched at RSA Conference 2025 and is now deployed globally. The design system I built continues to scale as new services are added.

Every tap at checkout. Every hospital login. Every classified file.The security admins protecting all of it now trust their tools.