Esper: Blueprints



Objective. Enable streamlined batch device configuration

Background. Prior to my employment, a team of three designers worked for a year without producing a working concept for a new feature request that would enable automated device configuration at scale. This new feature would save users potentially dozens of maintenance hours each month, and position Esper far ahead of competitors.

Timeline. 1 month user research & ideation, 2 months implementation

Approach: The first iteration involved consolidating settings that had been spread across multiple areas of the product, and reorganizing them into intuitive categories. The goal was to establish one-to-one parity with the existing functionality while introducing automated updates based on how devices were nested in groups. I worked with a PM and VP of Product to establish concepts to create, edit, establish version control, and finally deploy the configurations.


Device settings were distributed across Provisioning Templates and Compliance Policies, which failed to provide a cohesive preview of their impact on associated devices. Provisioning Templates only applied to devices the first time they were applied—they could not be reapplied. This meant that when devices fell out of compliance with their Provisioning Templates, the user was required to create a Compliance Policy—or multiple Compliance Policies—to reapply mismatched settings. This created a heavy cognitive load on the user, and required rigorous device monitoring.

Blueprints Before Sidebar wArrows

A collection of content and configurations applied to devices when adding to Esper

The same options for content and configurations, but applied to devices that fall out of compliance with the original Provisioning Template

Esper Diagram Compliance Policy Provisioning Template

Creating a Provisioning Template involved a lengthy 6-step process for configuring as many as 70 settings. The space for editing templates was completely isolated from the devices they impacted, which reiterated the unfortunate disconnect that occurred between templates and devices over time.

Before. Devices & Groups: Grid View

Provisioning Template Before

The Grid view provides a more visual layout that companies with smaller fleets may prefer. Users can upload featured images as at-a-glance identifiers for the groups' contents, like logos or device types.

Esper Provisioning Template Preview Before

A separate area to manage the templates added to the users’ workload.

Before. Provisioning Template Management

Esper Provisioning Template Landing Page

Before. Create Compliance Policy


< Issues

Next Feature >