ThreatDown
Re-imagining Global Feature Enablements for Security Analysts

ThreatDown
Re-imagining Global Feature Enablements for Security Analysts

ThreatDown
Re-imagining Global Feature Enablements for Security Analysts

YEAR

YEAR

YEAR

2025

2025

2025

ROLE

ROLE

ROLE

UX Lead

UX Lead

UX Lead

PRODUCT

PRODUCT

PRODUCT

Web Platform

Web Platform

Web Platform

THE OPPORTUNITY

THE OPPORTUNITY

THE OPPORTUNITY

I led the redesign of Threatdown’s feature enablement flow to help users more easily discover, understand, and activate new product capabilities as they’re released. Working closely with product managers and engineers, I reimagined the experience around a centralized Enablement Center, designed to simplify activation, surface feature requirements and compatibility insights, and provide transparent feedback.


The result was a faster, clearer, and more confidence-building way for users to implement new features across their environments.

THE PROBLEM

THE PROBLEM

THE PROBLEM

When a new feature was added to Threatdown, we noticed that it took users a long time to fully enable it and ensure all their endpoints were covered. The enablement process required going into each policy to activate the feature manually, which became tedious for users managing large environments.

In many cases, some endpoints still didn’t receive the feature due to version or configuration issues.

When a new feature was added to Threatdown, we noticed that it took users a long time to fully enable it and ensure all their endpoints were covered. The enablement process required going into each policy to activate the feature manually, which became tedious for users managing large environments.

In many cases, some endpoints still didn’t receive the feature due to version or configuration issues.

When a new feature was added to Threatdown, we noticed that it took users a long time to fully enable it and ensure all their endpoints were covered. The enablement process required going into each policy to activate the feature manually, which became tedious for users managing large environments.

In many cases, some endpoints still didn’t receive the feature due to version or configuration issues.

With Browser Phishing Protection for example, in the first 30 days after launch, adoption lagged significantly, leaving many endpoints without coverage and limiting the feature’s security impact.

With Browser Phishing Protection for example, in the first 30 days after launch, adoption lagged significantly, leaving many endpoints without coverage and limiting the feature’s security impact.

With Browser Phishing Protection for example, in the first 30 days after launch, adoption lagged significantly, leaving many endpoints without coverage and limiting the feature’s security impact.

User interviews sessions and customer support feedback revealed serious discoverability issues on the policy page — the main place where users enabled new features. Key actions were buried under multiple tabs and settings, making it hard to know when new features were available or how to activate them. This poor organization slowed adoption and led to repeated support tickets from users unsure if a feature was available or already enabled.

DESIGN CHALLENGE

DESIGN CHALLENGE

DESIGN CHALLENGE

How might we create an enablement experience that makes new features easier to find, understand, and activate, while giving users confidence that every eligible endpoint is covered?

How might we create an enablement experience that makes new features easier to find, understand, and activate, while giving users confidence that every eligible endpoint is covered?

How might we create an enablement experience that makes new features easier to find, understand, and activate, while giving users confidence that every eligible endpoint is covered?

EXPLORATION

EXPLORATION

EXPLORATION

Our initial approach focused on improving visibility by adding a “New Features” tab within the policy section. This made feature releases easier to discover but still required users to enable them one policy at a time, limiting scalability.

Our initial approach focused on improving visibility by adding a “New Features” tab within the policy section. This made feature releases easier to discover but still required users to enable them one policy at a time, limiting scalability.

Our initial approach focused on improving visibility by adding a “New Features” tab within the policy section. This made feature releases easier to discover but still required users to enable them one policy at a time, limiting scalability.

To streamline activation, we next introduced an “Enable on all policies” modal, which led to noticeably faster adoption and reduced setup time. However, the experience still lacked transparency—users couldn’t see which endpoints were unsupported or where enablement had failed.

These findings informed the next iteration: a dedicated Enablement Center designed to unify discovery, compatibility checks, and bulk enablement into a single, seamless workflow.

phase 2 - feature enablement center

phase 2 - feature enablement center

phase 2 - feature enablement center

The final design introduced the Enablement Center as a centralized hub for managing new feature rollouts.

Each feature included clear descriptions, compatibility insights, and one-click bulk enablement across policies. Users could now see which endpoints supported a feature before activation, reducing uncertainty and rework.

The final design introduced the Enablement Center as a centralized hub for managing new feature rollouts.

Each feature included clear descriptions, compatibility insights, and one-click bulk enablement across policies. Users could now see which endpoints supported a feature before activation, reducing uncertainty and rework.

The final design introduced the Enablement Center as a centralized hub for managing new feature rollouts.

Each feature included clear descriptions, compatibility insights, and one-click bulk enablement across policies. Users could now see which endpoints supported a feature before activation, reducing uncertainty and rework.

Early results showed a significant improvement in enablement efficiency—users enabled new features 3× faster on average—and a noticeable drop in support tickets related to missing or partially applied features.

Beyond speed, the new flow established a more transparent and scalable framework for future product releases, making feature adoption a predictable and confidence-building experience for administrators.

Early results showed a significant improvement in enablement efficiency—users enabled new features 3× faster on average—and a noticeable drop in support tickets related to missing or partially applied features.

Beyond speed, the new flow established a more transparent and scalable framework for future product releases, making feature adoption a predictable and confidence-building experience for administrators.

Early results showed a significant improvement in enablement efficiency—users enabled new features 3× faster on average—and a noticeable drop in support tickets related to missing or partially applied features.

Beyond speed, the new flow established a more transparent and scalable framework for future product releases, making feature adoption a predictable and confidence-building experience for administrators.