Customer Search & Job Scheduling Experience
UI/UX Design
Summer 2018 - Fall 2019
Improving the “Answer a Call and Schedule Work” experience for HVAC dispatchers and customer service reps. inside the Pointman Web App.
- Role
- Front End Engineering, User Research, UX Design, UI Design
- Team
- Steve Raines, Kurt Stangl, Mike Spencer, Michael Drewitt, Denise Nadal, David Cloyd.
- Org
- Pointman
Overview
Background
Every app or product or service has a workflow that is critical to its success. For Field Management Software there are two; one each for its 2 primary user groups. For CSR’s the most important task is to be able to efficiently answer a phone call and schedule work. For the technicians in the field, it’s efficiently working through the tasks necessary to complete a job.
Our mobile app did a good job of leading technicians through all the steps needed to work a job. Our desktop app, for the CSR’s and dispatchers, didn’t work so well.
It was a big problem to solve and it was at the heart of our application, and fixing it could possibly require rebuilding the app from the ground up. We made several attempts at addressing this issue, some successful, and other not; in the “Process” section I provide an overview of what we tried.
Atypical Navigation & UI conventions.
The “Answer a Call and Schedule Work” task had major usability issues when we started examining it. For new users, it was difficult to understand how to navigate the screens to find the information you needed and complete the steps in the task. Oftentimes, the visual cues were confusing, and you weren’t sure you completed the action you thought you did. Even for experienced users, buttons often didn’t do what you expected.
Usability Testing
We also conducted a usability test, tracking how long it took users to complete the task of looking up a customer and scheduling work at their home. We were shocked to find that it took an average 17 clicks, and up to 30 clicks in some cases - the fastest it could be done was in 11 clicks.
It was clear that we needed to make this process simpler and faster; if we’re expecting users to complete this task dozens of times a day, it needs to be a great experience.
Solution 1
Call Taking Feature
(June 2018 - April 2019)
Our first attempt at solving this problem was building a “Call Taking” feature. The idea was to create a search tool that would look up homeowners by either the owner, or the home. After finding the person or house, you would pull up information about them, and then be able to schedule a job at their house.
It was a struggle for many reasons. The project began with a list of user requests we were to treat as requirements. We didn’t do enough research to understand what problem we were trying to solve and how users would actually use our solution. We struggled to figure out how to collaborate effectively. When trying to leverage existing components to speed up development, it created more problems than it solved. We were all unhappy with what we built.
*We managed to build the feature that was requested - but we didn’t meet what the users really needed.*
Solution 2 (Part 1)
Summary View
(Feb 2019 -?)
Our previous release made it easier to look up a person or their home, and schedule work, but it didn’t make it much easier to look at information about them. I began exploring options whenever I had a spare moment, beginning to do user research by interviewing our target audience, writing stories and scenarios to test designs, and organizing the information architecture on the page.
Through this process, I managed to condense ten screens of information into one. I tested it internal users and received positive feedback. However, it was several months before it was prioritized for implementation.
Solution 2 (Part 2)
callTaking + summaries,
(Summer 2019)
Several months after I had created the “summary view” feature, our organization was ready to focus on improving the user experience in our app. We began to explore ways to integrate the new “summary view” into the “call taking” feature.
Again, we encountered serious technical difficulties during implementation, and this time, we couldn’t finish the project within the given timeframe.
Solution 4
Full Redesign
(Nov, Dec 2019)
After several failed attempts to inject user-focused experiences into the existing codebase, we as a team came to the conclusion that it would take just as long, or perhaps less time, to just try again from scratch. We decided to “do it right” this time, and start by challenging our assumptions and researching our users, their tasks, needs and wants.
We never implemented this redesign as we ran out of runway.
You can read the [full case study](“/works/pm-redesign”).
