IOT Control Center
Cisco Jasper's Flagship product, Control Center, allows for the management, provisioning, and control of IOT devices. My role as a Senior UX Designer puts me in contact with many aspects of the product.
Version History Audit Tool
When auditing automation rules, our support administrators expressed frustrations with our existing audit trail, which made it a challenge to determine quickly which fields had changed
Working closely with PM, I designed a version comparison tool that would, given any two versions, highlight the deltas between them. This made it easy to not only see the changes between successive versions, but compare the state of two versions that were several steps removed from each other.
Additional flows to restore a version, and to edit the current version were also designed in order to allow superadmins quick access to trouble shoot or create a new version from within the comparison tool.
Email Notification Frequency
This was a remedial fix after a misconfigured email notification crashed several of our Clients' email servers. The original notification sent an email notification each time a device triggered a rule, and a cascading condition caused several thousand devices to hit the threshold within a short period of each other.
The short-term fix is to change the default automation rule notification frequency from once every time a device rule is triggered, to once per day.
Additional work went to design aggregate email notifications, rule summaries and other supplemental flows, not shown here due to NDA
Over the 10 year lifespan of the product, the toobar in the workhorse grid pages had slowly acquired new features and actions.
This resulted in heavy cognitive load and difficulty scanning. An audit of all the different places where the grid displayed, showed between twelve and eighteen average decision points by the time our users reached the first line of data.
Attempts in the past to address the toobar included adding icons to each of the actions to help differentiate between discrete actions, and to provide some visual separators. This resulted in an even more crowded toolbar
Our first step was to define a problem statement that would guide us through the rest of the project. In the case of this update, our guiding principle was "Our User needs to efficiently perform actions when it's relevant"
By just reducing the toolbar icons from a horizontal list to a vertical list, we substantially reduce the cognitive load while minimizing horizontal scanning.
Changing the actions from a horizontal list to a vertical list also removes the need for iconography as separators.
Continuing to iterate, grouping Export with Refresh removes another decision point and helps visually group those actions. This reduces the number of decisions to a manageable level
The final result is a more streamlined toolbar that gives our users access to a more scannable set of actions when it's relevant, allowing them to perform their day-to-day tasks more quickly.