When CHEC was first developed, the application’s workflows and functionality were relatively simple. Extra information for users could be provided in context with a single line of text or in a tooltip. However, as the app grew in functionality, the workflows became more complex, requiring more detailed explanations than could be accommodated by a brief tooltip.

In an effort to address this, later iterations used modals to house additional content. However, modals in CHEC interrupt the user’s workflow by preventing interaction with the page until the modal is closed. This forced users to leave their task, read the content, and then return to where they left off. Since humans typically retain only 3-4 pieces of information at a time, users often had to repeatedly open and close the modal to access the information they needed. This back-and-forth led to frustration, friction, and eventual abandonment of the content meant to help them. A more seamless and contextual solution was needed.

Contextual Help

Users often needed information specific to the element they were working with, whether it was a part of their custom logic or a particular vehicle they were servicing. In its raw form, this information would be displayed in a spreadsheet format, requiring significant expertise to interpret. This approach was not feasible for the vast majority of users—about 95%—who would struggle to make sense of it.

To address this, several sprints were dedicated to finding a more user-friendly way to present this complex content. The solution we implemented involved a design system that broke the information into small, digestible blocks of text, paired with interactive selections. This allowed the application to display only the relevant details based on the user’s specific context, making the content far more accessible.

In-depth Help

As custom logic in CHEC evolved, advanced functionality controls became more common. These controls affect behavior without explaining to developers why they work the way they do. While external documentation is available, users lack a direct way to access this information within the application.

To address this, a new in-application help system was introduced within the custom logic interface. The help system provides high-level information for each section, featuring concise text and illustrated examples. Users can review the content while interacting with their custom logic, seeing firsthand how their changes affect the system. If this approach proves popular, there are plans to expand it to other areas of the application.

Custom Logic Updates

CHEC’s custom logic uses a gating system that lets users edit logic before applying it to a vehicle. If edits are needed, users can return the logic to an earlier lifecycle stage, make changes, and then promote it again for use. However, changes to the custom logic do not automatically update on the vehicle, a step that users frequently overlooked, causing frustration.

To address this, CHEC now prompts users to update the vehicle after editing custom logic. Users enter the serial numbers of the vehicles that need updating and are guided to the first step of the update process. By proactively alerting users, we help slow them down and prevent them from skipping critical steps in the workflow.

Analog Input Pin Selection

When creating custom logic, users can trigger physical (analog) pins on a vehicle’s Electronic Control Units (ECUs). For the triggers to work correctly, they require physical connections to two separate pins on the ECU.

In this case, the help system dynamically responds to the user’s input, presenting only the relevant information based on their selection. This ensures users receive precisely the details they need, without extraneous information.

Digital Pin Locations

When creating custom logic, users can trigger pins on a vehicle’s Electronic Control Unit (ECU). These triggers can be linked to one of several dozen pin locations on the ECU, each of which requires technicians to manually connect wiring. However, most users lack the in-depth knowledge to navigate these complex wiring diagrams and often had to search for the correct pin with trial by error.

What users do know are the vehicle type, the QuickFit Sales Code, and the digital pin name they plan to use with their custom logic. By leveraging these three pieces of information, CHEC can contextually display the exact physical pin location on the ECU, saving technicians hours of work with every vehicle they interact with.

Physical Switch Activation Indicators

The cab of a truck is filled with switches that drivers use daily as part of their job. Many of these switches rely on custom logic to perform their functions, and one of the simplest tasks for both the switch and the custom logic is providing feedback to the driver when the switch is activated. This feedback often takes the form of a colored indicator light within the switch itself.

Initially, developers using CHEC had to remember whether the switch they were working with supported an indicator light. If it did, the developer needed to manually add the functionality and the correct signal. This led to the frequent omission of the indicator light command, as users didn’t always realize they had to add it manually.
To address this, CHEC now suggests adding the indicator light function contextually, including the correct signal based on the switch being used. This proactive suggestion eliminates a common error and prevents issues that could impact truck drivers every day.