Project Scope

 
 

The Client: Global Real Estate group manages workplace services, assets, and spaces for IBM employees and Clients.

Team Included: Myself (UX Mobility Lead), Jr Mobility Resource, Technical Lead, Project Manager, 3 Developers, Integration Lead, GRE Stakeholders

 

Maximo Mobile Technician

A role based app

My role involved a comprehensive analysis of GRE’s workflows to identify the features available in the out-of-the-box version of the Technician app. Additionally, I focused on determining the necessary developments required within the app to meet the specific needs and preferences of our clients.

Technician App Out-of-Box

  • Limits the amount of information shown to Techs.

  • Tasks include: Creating a new Work Order, Viewing assigned work. creating a Service request, creating a follow-up WO

Maximo Technician App leverages multiple levels of Data including:

  • Data migration

  • Admin Configurations

  • Health Monitor and Predict

  • Reporting

  • Integration

This data was utilized to create predictive maintenance and utilizes Watson AI to gather insights from IBM’s Cloud to help workers make informed designs on the spot. Interface is also responsive, allowing users to access this information from any device.

 
 

My Design Strategy

 
 
 

Stage 1: Gathering Requirements

Workshops sessions were used to gather requirements (primarily for Maximo Mobile).  There were no specific ask for tech spec., however, the client (GRE) requested a detailed design document highlighting how do we plan to achieve these requirements (customization / configuration or both). We then created a very high-level design document.

My Role in Research

The Workshops hosted by Myself and our Technical Lead,  included the GRE’s site manager and supervisors; to get clarification on the current process and demo what features were available on the Out Of Box Maximo Technician Application.

I refined these documents and produced a template for tech specification.

 

Data Points

 

Our Workshops uncovered the following user pain points:

  1. Difficulty communicating Updates to line managers. 

  2. Insight to employees immediate challenges

  3. Work order statuses

  4. knowledge Transferring to new employees

  5. Large amounts of time spent finding records

  6. No Wifi

 
 

Identifying Product Gaps

 

Stage 2

 
 

Having a good grasp of our products was essential. Knowing Maximo 8.8 features and upcoming upgrades helped us provide the best to our client.

 

Constant communication between client stakeholders and internal team.

Managing Jira, daily standups, Box notes, utilizing Slack, email, and scheduling daily calls were to ensure that the client remained informed and up-to-date. It was vital to provide detailed and regular updates to keep the client in the know. This practice fosters transparency and strengthens communication channels, ultimately enhancing the overall client experience.

Work in Progress

After evaluating what was available v.s what was needed, I developed this Gaps Work in Progress (WIP) Document to effectively handle and communicate the advancement of the project with The GRE team, alongside overseeing the related Jira Tickets.

 

Stage 3

 

The Dev Stage

Designs were configured based on Clients needs,then passed over to developers where we discussed blockers and solutions before referring platform lifts to the product team.

 
 

For each redesigned section or configuration, a mockup with design notes were passed along to Developers. Eventually the mockups were placed in a spec doc complete with technical specifications.

Mockups and Spec Docs

 

Mockup with notes for Dev Team

The new app design addressed major pain points by featuring quick tabs and touch points to access certain KPI’s including:

  • List View Tab

  • Work Order Tab

  • Assignments Tab

  • Related Records Tab

  • Actuals Tab

  • Safety Plan Tab

  • Log Tab

  • Data Sheet Tab

  • Failure Reporting Tab




Out-of-box-screen

Out of Box with no config.

dev-mockup-screens

Data informed redesigns with Annotations

Work Order Screen Documented

Spec Documentation

Workflow Simplified

This is a flowchart of Gre’s redesigned workflow I created in Figma

 

User Acceptance Testing

Stage 4

 

Our Mobile Technician App, which was originally developed in a controlled sandbox environment, had transitioned to the dev environment for user testing before being meticulously evaluated and tested in the production environment.

 
 

User testing played a crucial role in the continuous improvement of the application. Our testing provided data insights that helped refine and enhance the user experience. Below you can see the User testing document used by our team to undergo each step and report any errors and validate that the app performed as designed.

 
 

User Test Scripts

 
 

Final Screens

final-mobile-screens-1
Final-mobile-screens
 
 
 

Project Retrospective

 
 

What went well?

  • Setting expectations for the client,

  • Regular team meetings and progress reports,

  • Great product development.

 

What could we have improved on?

  • Managed deadlines better,

  • Worked harder to keep Jira updated for the client.