PRODUCT CASE STUDY

Environmental Monitoring Solutions (Endpoint)

A modernized touchscreen interface for an IoT endpoint that captures environmental data in highly regulated industries.
preview of tablet
Screenshot of the touchscreen homepage, which displays a line graph of live data with a data table underneath.

Project Summary

Details

Aug 2022 - Oct 2022
Design Lead
Native Android device
Figma, Zeplin, Miro, Loom
Distributed team

Background

It is critical that regulated industries such as healthcare and manufacturing meet certain requirements for their facilities. For example with vaccine storage, if the temperature rises above the acceptable range, this could result in vaccines losing potency. Monitoring variables such as temperature, humidity, and pressure is a long established requirement of regulated industries. But lack of visibility, clarity, and speed of response are ongoing major pain points, especially as these industries grow in scale and pace.

Dickson is an environmental monitoring company that produces IoT-enabled devices that collect and feed data to their cloud monitoring platform, DicksonOne. In their modular system of hardware, sensors that collect environmental data can be connected interchangeably to data loggers, which are connected to DicksonOne through the internet or through RF networks. The various data loggers also have interfaces of varying levels of complexity, which help provide immediate feedback on the current readings and alerting status.

Product Summary

The data logger is an IoT endpoint that collects and displays data, both on its touchscreen interface and on DicksonOne. This device provides users with configuration capabilities and live updates on readings and alerts. The goal of our redesign was to modernize the interface and create a more user-friendly onboarding experience.

Note: Due to timeline changes, this project only included design and did not involve engineering. This actually isn’t my preference, as I believe that embedding design with integrated teams creates more successful results, but the project still resulted in interesting work worth showcasing. To view my experiences with integrated teams, visit my other case studies.

Before diving into the redesign process, I had to make sure I understood the existing product so that any existing functionality was not lost. Dickson shipped me some pieces of hardware to set up to get familiar with their current experience.

Audit of Existing Experience

About 3 weeks full-time

Screen Inventory

I created a screen inventory by setting up the hardware I received and taking stock of all the pages and user flows that I could identify (a few flows required additional guidance from the client, such as the super admin page). I made sure to document the different states and interactions I encountered, and made note of any questions and suggestions I had along the way.

screen inventory
Screenshot of the entire screen inventory in miro.
annotations on screen inventory
Screenshot of a closeup of the screen inventory in miro, with some sticky notes noting suggestions and questions.

User Flows and Experience

It was important to understand the major user flows and pain points of the current experience. I collaborated with the client to highlight the main use cases and took note of opportunities for improvement. Aside from modernizing the UI, our main goal was to provide more guidance during the onboarding process. Today, after powering on the device, the user is simply plopped on the homepage and needs to know where to navigate in the settings in order to configure the device. We highlighted the major configuration items required of a standard setup so that we could bring those to the surface.

notes on user flows
Screenshot of 2 user flows outlining the current experience, and section with ideas for improvement.

The original touchscreen interface was designed more than 10 years ago and was due for a refresh. In my redesign, I focused on improving the visuals, accessibility, and usability of the UI.

UI Refresh

About 2 months full-time

Design System

Though I was able to use the design system I had created for DicksonOne in the UI Refresh, I also identified the need to adjust the system for a tablet device. Not only do touch interfaces require larger inputs in general, but this device would require something bigger and bolder - since the device might be mounted on the wall or a hard-to-reach spot, users might view it from a farther distance (perhaps up to 5-10 feet) or view several devices at once as they’re setting them up.

The first step I took in the visual design phase was to create an inventory of all the components of the current experience. This informed the initial list of components and patterns needed. I then redesigned these components to match the new design system, with some intentional changes to size everything appropriately.

inventory of components needed
Screenshot of inventory of existing components, with sticky notes labeling the different components.
new components
Collection of new components, redesigned to match the new design system.

Design Iterations

The original UI had many opportunities for improvement. After reviewing the screen inventory, I identified the following as changes I would apply across the board:

  • Use more consistent and uniform spacing
  • Improve the color contrast for accessibility, especially for disabled inputs
  • Avoid combining icons into custom graphics, use a standard icon set
  • Improve the affordance for inputs and status indicators
before and after screens
A before and after comparison of the Information and General Settings pages. Before, the layout was inconsistent, colors were low contrast, icons were chaotic. Afterward, the designs are more uniform, consistent, and high contrast.

I went through a few iterations during the UI refresh to reach a design that the team was aligned on. In the first iteration, I was mostly concerned with feature parity. Therefore, on most pages, I retained the basic layout and only updated colors and typography. While this was a big improvement, on the second iteration, I took inspiration from modern tablet devices such as the iPad and Google Nest Hub and focused on simplifying the UI. And finally in the third iteration, I toned down some of the boldness to make certain features stand out more.

iterations of UI redesign
A showcase of 3 iterations of the admin page, which went from a 2-column grid with large icon buttons to a standardized page of inputs.
network settings pageadd network page
(left) The network settings page, which shows what networks the device is currently connected to and other network-related functionality. (right) The Add Network page, which shows inputs for the network name and password and the option to view more settings.
graph view of homepagetile view of homepage
(left) A graph version of the homepage in an alerting state, which displays a line graph of data and a data table below. (right) A tile version of the homepage in an alerting state, which displays a grid of channels and their current reading and alerting state.

The onboarding experience of the existing device was basically non-existent, and so we aspired to include a number of configuration capabilities directly in onboarding so that users would not need to search for them later. The main goal of the new onboarding experience was to make sure the device was successfully connected to the correct network.

Onboarding Experience

About 2 months full-time

Competitive Research

For inspiration on user-friendly onboarding experiences, I did some research in the adjacent market of smart home devices and documented how they handled setup and connectivity. The Google Nest Hub was particularly influential here, as it not only provided guidance on initial connections, but also conveniently surfaced additional settings to the user with the option to skip over them if desired.

Based on trends that I noticed, I made some recommendations for our experience that would mirror the experience of smart home networks.

smart home device researchproposal of onboarding experience
(left) Screenshot of user flow documentation of the onboarding experiences from Amazon, August, and Google smart home devices. (right) Screenshot of a summary of common trends in smart home device setup and the proposal for the touchscreen device.

User Flow Iterations

Designing the new onboarding experience definitely pushed me out of my technical comfort zone, which was both fun and challenging. We went through several situations of the user flow, going back and forth between low-fidelity wireframes, high-fidelity mockups, and flowcharts. As we went through the different iterations, we continued to discover additional requirements needed, making the user flow increasingly more complex until we were able to simplify it in the final steps. While this was not necessarily the most linear or straightforward design process, it was nevertheless useful to filter out the proposals that wouldn’t work and arrive at a more streamlined experience.

iterations of onboarding flow
2 screenshots of some early iterations of the onboarding experience.

The final user flow was divided into 2 main phases - initial setup and connection setup. The connection setup consisted of what I referred to as “modular bundles” of experiences that could be added or bypassed depending on what the users selected - these included ethernet connection setup, wifi connection setup, and bulk wifi connection via bluetooth (which was postponed to post-MVP), which included both a client-side and host experience.

final user flow of onboarding
A user flow diagram of the final onboarding experience, which is described above.
onboarding welcome screenonboarding wifi connection page
(left) The welcome page of the onboarding experience, which includes some support text for manual connections needed and the option to go through the setup experience of skip to the homepage. (right) A question asking, "How would you like to connect?" with the "Both Wi-Fi and Ethernet" option selected.

Page Templates

Part of the challenge of designing the onboarding experience was that every page contained different content, and it quickly became clear that custom designing each page was not efficient. I decided to create some constraints by creating a set of page templates for each onboarding page. These templates both simplified the design process and created a more consistent, unified feel for the user.

page templates for onboarding flow
Screenshot of the collection of page templates used for the onboarding experience.

Reflection

figma wireframe thumbnails
Two screenshots of large collections of wireframes in Figma - one of the page index and one of the onboarding experience.

I have always wanted to design an interface for. device that was neither a computer or phone, so this was a very exciting opportunity for me. Throughout this process I learned:

  • That I really missed working with engineers, so sticking with integrated teams is definitely in my future.
  • When things start to feel so complicated that I can’t keep track of my own designs, it’s time to simplify.
  • It pays off to do some technical research before designing.