PIT Inspection

Platform: Mobile (Android) - Deloitte Studios

The PIT Inspection tool is part of the Kroger's Compliance suite of applications that allowed store associates to inspect Personal Industrial Trucks (PIT) by scanning each vehicle and recording their responses on the app to meet the store and OSHA safety guidelines.

My Role

My role was a product designer responsible for discovery, user research, design, prototyping, and testing.

The Challenge

The challenge was how to get users to adopt a digital process on Android platform by incorporating multiple features; product scan, inspecting the vehicle by many inspection criteria, sending reports to store leadership for failed inspections and accessing 7 days of inspection repots , and all the while getting store associates to engage and adopt this application over previous versions.

Research: Personas and Associate Interviews

In order to better understand key insights from the business owners, I conducted multiple discovery sessions. I developed personas for associate and store manager who would be typical users of this application and use cases.

Persona #1: Alvin - Store Associate

Persona #2: Tara - Store Manager

Michael is certified to operate the PIT vehicles.
As per company guidelines, there must be at least 2 inspections every day.
He scans the barcode on the PIT vehicle to get the inspection started
There are multiple types of PIT vehicles separated by type and gas/battery-powered
Each type has a different set of different inspection criteria to inspect against
He will need to report a failed inspection to store leadership and lock/tagout the vehicle manually after the failed inspection.

Debbie gets an email from Michael when there's a failed inspection on a PIT vehicle.
She uses the Maximo system to submit a service ticket to have a technician come and fix the vehicle.
She also accesses the reports on the app for the last 7 days and on the desktop for reports prior to 7 days.
She's also certified to inspect the vehicle if a store associate isn't available.

Here are some insights in discovery sessions:

What is current method for performing PIT inspections?
How can we tell what was specifically the issue of the component when it failed inspection?
What is the notification process for failed inspections?
How can we tell if a vehicle failed inspection if no one has locked/tagout the vehicle?

Key Insights from user interviews:

Associates like the ability to input details about a failed inspection so it's more clear as to what was the issue
Associates expected that they can easily inspect a PIT vehicle across many components in a single hub
The ability to view tutorials to an inspection component was especially liked by associates
Associates expected a seamless notification process to store leadership about failed inspections and to other associates to prevent them from using a vehicle that failed inspection

Final Designs

The user interviews and the two personas helped to inform the final designs of the PIT Inspection application. Here are some key design decisions I made based on the research.

Context-driven approach to performing tasks
Provide seamless navigation to tutorials and updating associate responses and provide avenues for all profiles (novice, advanced)
Easy to use navigation utilizing modal layer template

next project