Equipment360 Mobile Mechanic Redesign

Redesigning an iPad application used by mechanics, managers, and foremen to carry out work orders on equipment that require repair, maintenance, replacement, etc.

This callout is for projects that are under strict NDA. That means I cannot share a lot of information or even screenshots publicly. Should also include my email at nabilahsan95@gmail.com so interested parties can reach out to talk about the project.

Overview

Equipment360 is one of the flagship products by HCSS. It allows mechanics and managers at construction sites to manage and maintain their heavy equipment fleet, and track hours for each mechanic working on the site.

I was responsible for the UX design for the iPad application, along with my partner Isabel. We conducted internal user interviews to gather data, presented our findings to stakeholders, and constructed the information architecture for the application, along with wireframing, visual design, and high fidelity prototyping.

Tasks
  • User Research
  • User Interviews
  • LoFi Designs and Wireframes
  • High Fidelity Design
  • Clickable Prototyping
Tools
  • Figma
  • Confluence
  • Jira
  • Google Docs
Company

Heavy Construction Systems Specialists (HCSS)

Timeline

May 2019 - July 2019

Project Goals

Conduct user research to understand how the users interact with the products and what their pain points are.

Modernize the user interface and implement new branding colors, making it look modern.

Identify and fix pain points faced by the users, take out unnecessary functionalities, and look for opportunities to add new features that help our users.

Outcome

Conducted user interviews and UI analysis,  which helped understand the core issues.

Collaborated with Subject Matter Expert and aligned business goals and user goals to identify what needed to be worked on first.

Worked collaboratively with my partner, Isabel, to deliver a large-scale redesign that met the stakeholder’s desired business goals.

Our Process

User Research and Interviews

We were given the project in May 2019. After playing around with the software we decided we should interview a few key stake holders.

We interviewed three Customer Service Representatives. They were always the ones who were closest to the customer and the users (construction workers and mechanics). They are aware of the troubles the customers faced.

We asked about the kind of users we have, what differentiates them, their technological skills, educational background, common day to day activities, and other questions like

  1. Needs the customer and/or users would like the software to address
  2. How long users spend using the software and when do they use it the most?
  3. What are the age demographics of the users
  4. Common frustrations the user talks about during calls with the representatives
  5. What do goals look like for different types of users who use the app

We learned about a bit about our users

The Mechanics:

  1. Identify and add work orders to their time cards and carry them out. Don’t want the app to be a bottleneck to their work.
  2. Younger mechanics were more tech-savvy and would use the Equipment360 application as they completed their work orders.
  3. Older mechanics have less technical experience would rely on pen and paper for their needs and would use the Equipment360 app at the end of the day.

The Manager

  1. Most delegate tasks to mechanics.
  2. Some would carry out the work orders themselves (Manager-Mechanics)
  3. Keep track of work orders and ensure smooth work flow at construction sites.

What did we need to work on?

My partner Isabel and I divided the app by user-specific workflows and conducted a heuristic analysis to identify workflow and UI issues.

It was presented during the project kickoff meeting.

Along with our user interview data, we pitched to the stakeholders on what we decided to be mission critical issues that need immediate attention.

It was well received and we were given the green light to start ideating solutions.

Design-a-thon

We were provided a brand style guide with all the new colors that were decided for the redesign. We also had access to the old version of the app so we could play around with and learn the structure, the intended workflows, and how our users used the app.

From there we started drafting wireframes, then creating high fidelity designs, all the while checking with our senior designers on proper design techniques and acceptable structuring.

We also put a lot of emphasis on the components system. We wanted to leave a guide for the developers that will be building from our designs, and also the future designers who will rely on this.

Project is ongoing

This project is currently under an NDA so I am unable to share anymore of the work that I have done. However, I do have slides that go into a bit more detail on what we did. Those are for interviews only.