Prisma Cloud Homepage

Homepage for Prisma Cloud - a B2B CNAPP SaaS product

As the lead UX researcher and designer on this project, I introduced Prisma Cloud’s first homepage to streamline navigation, reduce time-to-value, and drive product adoption. This strategic redesign addressed discoverability challenges across a complex cloud security platform serving multiple security personas.

Role

UX Research UX Design Visual Design

Duration

2 months

Context

Problem

Prisma Cloud, a comprehensive CNAPP SaaS platform, faced poor onboarding and low feature discoverability due to complex navigation, buried functionality, and a generic landing experience. These friction points slowed adoption, hindered product-led growth, and left users dependent on support and sales to find their way around.


Goal

Design a personalized and centralized homepage for Prisma Cloud that:

  • Provides a clear, contextual starting point for essential workflows, accelerating user onboarding and adoption

  • Surfaces relevant product updates to enhance product discoverability and time to value

  • Support guides to enhance self-serve discovery, reducing reliance on external documentation and sales calls


Challenges

Designing a homepage for Prisma Cloud wasn’t just about creating a UI—it meant solving for multiple layers of complexity:


Diverse user personas

Cross-functional alignment

Changing priorities

Serving 15+ roles across 3 core personas meant designing a flexible yet unified experience

Worked with 5+ PMs representing different product areas, aligning diverse goals through workshops and async reviews

Midway scope changes emphasized product-led growth; I adapted the MVP in collaboration with PMs to maintain user value


These challenges demanded a collaborative, systems-thinking approach, and reinforced the importance of grounding decisions in user data while maintaining stakeholder trust.


Process

Outcomes

Designed Prisma Cloud's first ever homepage


Impact within first 3-6 months

  • ~60% users kicked off their workflows from the homepage

  • 76% customer satisfied as measured through CSAT

  • 4 → 1 click reduction for key workflows

  • 15+ feature announcements surfaced through new homepage

  • 12% reduction in time-to-value, as measured by onboarding completion data


The homepage became more than just a landing page—it became a strategic entry point that advanced product-led growth and empowered users from day one.

Discover & Research

"Understanding users, stakeholders, and the current state"

Research Methods
  • Stakeholder interviews with PMs and solution architects

  • Review of prior user feedback (support tickets, sales notes, and field team insights).

  • Product usage data analysis (via Pendo)

  • Competitive analysis


Key Insights
  • Navigation complexity: Users struggled to locate key workflows, like adding cloud accounts, buried deep within Settings or secondary menus

  • Heavy reliance on external help: Most users turned to TechDocs, support, or sales engineers just to get started

  • Poor first impression: Users were dropped into the Alerts page (6th in the nav), leading to confusion and alert fatigue—especially for first-time users during POCs

  • Limited product-led onboarding: With no contextual entry point, users missed value during early experiences—particularly when not guided by a sales rep.

  • Lack of personalization: The platform treated all users the same, despite serving 15+ roles across 3 core personas.


These insights emphasized the need for a centralized homepage that could serve as a functional and strategic starting point for different personas.

Define

"Framing the problem and aligning on a north star"

From Insights to Feature Direction

Following research, we synthesized patterns into key opportunity areas:


  1. Users needed clearer guidance

  1. Faster access to critical workflows

  1. Content tailored to their role and responsibilities


I collaborated with PMs and product leadership to shape a focused PRD centered on delivering immediate value for new users. As PLG goals gained traction, we aligned cross-functionally to integrate them into the MVP—prioritizing impact without increasing complexity, narrowing down to the following homepage focus areas:


  • Guide users to onboarding-critical actions like adding cloud accounts and repos, without navigating through complex menus

  • Offer clear, contextual entry points to high-value areas like Compliance Overview, Adoption Advisor, and Alerts

  • Keep users informed with embedded product updates (Release Notes) and curated blog content to surface relevant features, guidance, and latest threat vectors

  • Support long-term adoption and operationalization through personalized guidance from Adoption Advisor and quick links to essential features


This narrowed scope kept dependencies low while giving us the data and user feedback needed to inform future iterations.

Designing for Personas

The 15+ roles, could be distilled to three core personas that represented the most common and high-impact workflows.


Vanessa | Security Practitioner/Admin

Manage and monitor cloud security posture, detect and respond to threats

Ricardo | DevOps Engineer

Secure containers, hosts and serverless across application lifecycle

Aaron | Application Security

Secure app artifacts, analyze code and fix issues


These personas helped us define role-relevant homepage modules and personalize entry points into their daily workflows.



Design

“Iterating toward clarity and usability.”

From Concepts to Clarity

With the MVP direction locked, I began exploring layout options and content strategy for the homepage. The design needed to serve first-time users looking for guidance, while remaining useful for returning users seeking operational visibility.

I started with multiple layout explorations that tested:

  • Above-the-fold prioritization of onboarding actions

  • Entry points to high-value modules like Alerts and Compliance

  • Visibility of new features and announcements

My goal was to create a homepage that felt intuitive, purposeful, and aligned with the mental models of our primary personas.



Designing for Multiple User Journeys

Each homepage section was mapped to a core persona need. Illustrating a few examples:


Section

Persona

Need

Onboarding Actions

Vanessa

Fast access to add cloud accounts/repos

Alerts Snapshot

Vanessa, Ricardo

Awareness of current risks

Adoption Advisor Links

Vanessa

Guidance towards unused features and increase operationalization

Quick Links

All

Fast-track to core workflows

Release Notes

All

Keep users informed, support self-serve discovery


These modules were designed using existing components to reduce development lift while ensuring visual consistency across the product.


User Testing & Iteration

To validate early concepts, I conducted moderated usability tests with internal and external users representing our three personas focusing on

  • First-click behavior

  • Information hierarchy clarity

  • Perceived value of content modules


Key Learnings:

  • Users appreciated immediate and clear guidance

  • The Adoption Advisor section was often overlooked in early versions; we addressed this by reworking its visual priority

  • Security-focused users valued release notes and blog content and showed interest in ability to view API and policy update notes as well

These insights led to updates in layout, copy, and content grouping.


Stakeholder Alignment

Throughout design, I ran async reviews with PMs, content, and engineering to ensure feasibility and alignment. This collaboration helped us:

  • Prioritize modules for MVP vs future iterations

  • Reuse components to reduce front-end complexity

  • Refine content role relevance

  • Finalize copy for clarity

Thank you for visiting my portfolio 🎨

Get in touch!

Thank you for visiting my portfolio 🎨

Get in touch!

.

divya.agarwal@utexas.edu

Thank you for visiting my portfolio 🎨

Get in touch!