Esper | Pipelines

Designing how a company manages and updates it’s device fleet


Project Overview

Role: Lead Product Designer

Tasks: UX Research, UX Design, UI Design, Data Analyst

Team: 6 Engineers, 1 Project Manager, 1 Designer

Duration: 2 months

TL;DR

Software delivery to dedicated devices like point of sale systems, kiosks, and digital signage is one of the most complex issues IT professionals face today. In most situations, it’s all or nothing — you either deploy to your entire device fleet or you don’t. That’s not how it should be.

Project Summary

As users of Esper can have thousands of devices in their fleet that they need to manage, the company needed a way to easily let them run actions on each of the devices remotely and simply. Our primary process was to gather data on user needs, design a user friendly way to stagger actions across devices, and align the designs with Esper’s brand guidelines. By making sure that we followed set patterns for in the Esper service already provided for the Pipelines functions, we aimed to create this new service with minimal onboarding needed for users.

Project Functions

Esper Pipelines enable you to stagger actions such as application installations or Esper Software Updates.

Start a new run to initiate a pipeline - you can choose to update the application version to be installed before starting a new run. A Run can be started, paused, resumed, or terminated. Learn more about Pipeline terms. 

Any pipeline can have multiple jobs created, and each job can have multiple runs (only one run active at a time) associated with it.

  • Filled State

  • Pending State

  • Failed State

  • Empty State

  • Empty State

  • Prefilled State

Next
Next

UBB Ticketing CRM