Sites Page Redesign

Project Background

Verkada provides enterprise physical security solutions — video surveillance, door access control, air quality monitoring, alarms, intercoms, and visitor management — all managed from one platform.

The Sites page is where admins organize devices and manage permissions across every location their organization runs. It’s foundational to the platform experience: almost every other workflow eventually routes through it. But the existing interface was a dense, spreadsheet-style grid that hadn’t been rethought as the product line grew — and it was effectively unusable on mobile.

My goal was to redesign it into something scalable, mobile-capable, and aligned with the newer Verkada 3.0 design language — without breaking the complex permission and hierarchy logic power users depended on.

Why It Needed to Change

Research

I ran a UX audit, then structured the investigation around a few research questions before doing any exploration:

To answer these, I combined a UX audit, stakeholder and design-history interviews, sessions with Solutions Engineers (who see how large enterprise customers actually configure their sites), and direct customer interviews.

What I learned

Org Admins and Site Admins use this page primarily to structure and restructure sites: creating and naming sites and subsites, splitting a site into multiple subsites, moving a subsite elsewhere in the hierarchy, and managing permissions as that structure shifts.

The friction was concentrated in three places:

• Cumbersome restructuring — users had to strip out every device and subsite before they could delete or move a site.
• Disjointed workflow — restructuring meant bouncing between separate pages to move devices and separately manage permissions.
• No bulk actions — every change was one at a time, even for customers managing hundreds of sites.

A few data points that shaped prioritization:

• A Solutions Engineering Manager noted that one of Verkada’s largest customers restructures roughly 10 subsites into different parents every year.
• A customer publicly requested drag-and-drop restructuring at a Verkada customer conference.
• An engineer described customers needing to change site hierarchy without deleting and recreating sites — since that meant re-adding every device and resetting every configuration from scratch.
• One Solutions Engineer was writing a custom script for a 700+ site enterprise customer just to help them manage their structure — a strong signal the built-in tooling had failed them.
• Design leadership emphasized that naming conventions and device-count visibility mattered enormously to how customers reasoned about their site structure.

Beyond the core friction, a few opportunities stood out: the Sites page had potential as a homepage (Verkada currently defaults to the Camera page), floorplan integration was a natural extension since floorplans are site-based, and customers wanted the ability to pin key sites and export site data for compliance reporting.

Design Exploration & Rationale

I explored three layout approaches, each solving for “immediate visibility into site structure” differently, because different customer segments needed different things from the same view:

Final Design

Navigating Constraints

Senior-level design work is as much about what you push back on and what you let go of as what you ship. A few trade-offs from this project:

Outcome

• ✓ Fully responsive on mobile
• ✓Scalable to Verkada’s full, growing device catalog
• ✓ Aligned with the Verkada 3.0 design system
• ✓ Simplified permission viewing and editing
• ✓ Faster, lower-friction site restructuring

[Add one number or scale statement if you have it — usage, tickets, or “shipped to X customers.” If not, skip it; the checkmarks above are fine as-is.]