Reimagining Security at AWS: Designing the Future of Unified Cloud Security

Overview

Role: Principal UX Designer & Research Strategist

Timeline: November 2024 – Initial Launch (5 months)

Scope: AWS Security Organization

Partners: C-suite leadership, VPs, Principal Engineers, Applied Scientists, Product Management, Security Organizations, UX Research

The Challenge

By late 2024, AWS leadership was hearing a consistent message from enterprise customers.

Customers understood the value of AWS Security services individually, but collectively they experienced the portfolio as fragmented and difficult to navigate.

Common questions surfaced repeatedly:

  • Why am I paying for so many different security services?

  • What does each service actually do?

  • Which products overlap?

  • How do I know whether I'm adequately protected?

  • How can I quickly determine if I'm currently under attack?

These weren't usability issues—they represented a strategic product problem spanning multiple organizations, architectures, and customer experiences.

Leadership recognized that solving the problem would require more than redesigning interfaces. It required rethinking how AWS Security presented itself as a unified ecosystem.

I was brought into the initiative as a UX strategy and research lead because of my experience designing across AWS Security products and my understanding of customer workflows both inside and outside the AWS Console.

My responsibility extended well beyond interface design. I was tasked with helping define the long-term customer experience vision while identifying a realistic path to deliver meaningful improvements within five months.

Defining the Vision

I relocated to the Bay Area to work directly with senior leadership through a series of strategy and whiteboarding sessions.

Together we established what success would look like—not simply for the next release, but for the future of AWS Security.

Rather than discussing individual features, we focused on larger questions:

  • What should a unified security experience feel like?

  • How should customers understand their overall security posture?

  • Where were the biggest friction points across existing products?

  • Which organizational dependencies would determine success?

These sessions became the foundation for the initiative.

Together we mapped:

  • Future-state customer journeys

  • Cross-product architecture

  • Organizational ownership

  • Missing platform capabilities

  • Technical constraints

  • Executive milestones

Just as importantly, we identified which organizations needed to be involved early to reduce downstream dependency risks and avoid delays during execution.

Designing Within Constraints

One of the project's defining constraints was that the initial launch could not require changes to existing APIs.

This dramatically limited traditional redesign approaches.

Instead of viewing the constraint as a blocker, I reframed it as a systems design challenge.

Working closely with Principal Engineers, I developed a deep understanding of the existing console infrastructure and identified opportunities to create a flexible presentation layer above the existing services.

I partnered with our Applied Science organization to explore a component-driven interface capable of dynamically assembling customer experiences using existing backend data.

Rather than rebuilding infrastructure, we designed an adaptive UI framework that could intelligently generate customer experiences while leveraging current service contracts.

This allowed us to dramatically improve the customer experience without introducing significant engineering risk or delaying delivery.

Aligning AI with Customer Mental Models

Because the initiative relied heavily on intelligent recommendations and dynamic interfaces, I partnered closely with Applied Scientists to ensure our AI capabilities reflected how customers actually think about security.

Rather than organizing information according to internal AWS service boundaries, we shifted the experience toward customer goals:

  • Understanding overall security posture

  • Prioritizing risk

  • Identifying active threats

  • Knowing what actions to take next

This represented an important shift—from exposing AWS architecture to exposing customer intent.

The result was an experience that translated complex infrastructure into actionable guidance rather than requiring customers to understand dozens of individual security services.

Strategic Leadership

Beyond product design, I served as a connector across multiple organizations that historically operated independently.

My work included:

  • Facilitating executive vision workshops

  • Translating customer research into strategic priorities

  • Aligning Product, Engineering, Applied Science, and Design

  • Identifying organizational dependencies before development

  • Reducing delivery risk through early systems planning

  • Helping define the roadmap for future security unification initiatives

By creating shared artifacts and visual frameworks, I enabled teams with different priorities and technical vocabularies to align around a common customer vision.

Outcome

Within five months, the initiative established the strategic foundation for the first phase of AWS Security unification.

The work delivered:

  • A unified vision for the future AWS Security experience

  • Executive alignment across multiple Security organizations

  • A scalable interaction model capable of supporting future services

  • A component-driven architecture that minimized engineering disruption

  • An AI-assisted experience centered on customer outcomes rather than individual products

  • A roadmap for continued portfolio consolidation

Perhaps most importantly, the initiative reframed AWS Security from a collection of independent services into the beginning of a cohesive customer experience.

Impact

This project fundamentally shifted my role from product designer to strategic design leader.

Rather than designing individual interfaces, I was helping shape organizational strategy, influence executive decision-making, and define the long-term customer experience for one of AWS's largest product ecosystems.

The engagement demonstrated how UX leadership can drive business transformation—not simply by improving usability, but by creating clarity across organizations, aligning technical strategy with customer needs, and establishing a shared vision that enables execution at enterprise scale.