Skip to content
Case study · Product design

Elevate ONE View

Simplifying the app field mechanics rely on to bring Elevate elevators online, anywhere in the world.

Designing the mobile interface field mechanics use to commission and maintain Elevate elevators worldwide, turning a heavy workflow into something fast in the field.

My role
UX and UI designer, owning the design system and the 2.0 version
Scope
Enterprise mobile app, industry project
Platform
Mobile
Timeline
6 months
Stylised field service app screen showing a unit list with status indicators
Stylised field service app screen showing a commissioning detail with a progress ring
Sheet 01THE SETUP

The app a mechanic carries
into the field.

Elevate is one of the world's leading elevator and escalator companies, and this was an industry project delivered with LTIMindtree. Elevate ONE View is the app field mechanics carry, the critical enabler for the IoT platform out in the field.

Its job is to digitise and manage the full lifecycle of an elevator's connectivity, commissioning, troubleshooting, maintenance, and access to real time health data. Because it is an industry project, the designs stay limited here for confidentiality, so this study leans on the story more than the screens.

ProductElevate ONE View, the primary mobile interface for Elevate field mechanics, and the field side of an IoT platform.
ProblemA heavy, inconsistent app made commissioning and maintaining elevators slow and error prone in the field.
DetailsUX and UI designer on a cross functional team of 35, owning the design system and the 2.0 redesign over six months.
SolutionA single, simplified workflow for the full lifecycle of an elevator's connectivity, from commissioning to troubleshooting.
ResultA decluttered first version that streamlined the core flow and helped win the business.
Sheet 02Impact

In four regions, on real jobs.

10%

Reduction in the core flow after decluttering

core flow

1,899

Field uploads across regions

uploads

4

Global regions served, APAC, EMEA, NAA, and China

regions
Sheet 03The problem

Friction in exactly the moments
a mechanic needed speed.

Mechanic Issue

When technicians arrived on-site, they weren't thinking about the app. They were thinking about diagnosing equipment, keeping customers informed, and completing work efficiently.Instead of supporting those moments, the product often introduced unnecessary friction through inconsistent interactions, fragmented navigation, and unclear information hierarchy. The problem wasn't missing features. It was interrupting the work.

The best field app is the one mechanics barely have to think about.

Sheet 04Goals

One simplified app a field mechanic can move through quickly, anywhere in the world.

01

Replace multiple tangled workflows with a single simplified one

02

Make components behave consistently across the whole app

03

Give navigation a clear, predictable structure

04

Align the visuals with Elevate's industrial tone

Sheet 05The process

Built inside a team of 35.

Product planning and requirement gathering

Planning sessions with product managers, business teams, and scrum masters to align on requirements, priorities, and goals.

Cross functional requirement discussion

Worked with development, design, and product teams to understand scope, then shared technical detail with developers for feasibility.

Design implementation and approval

Created flows, presented them to the product team for approval, and handed off to development.

Development and testing

Supported the build, with an iterative loop between stakeholders, developers, and design to hold quality.

Sheet 06Key insights

Why the app fought its users.

01

The basics come first

The app did not adapt to different screens, so layouts broke and the basics had to come first.

02

Consistency is familiarity

Components behaved inconsistently across the app, which made every screen feel unfamiliar.

03

Navigation over features

Navigation felt heavy and disconnected, so a clear, consistent structure mattered more than any single feature.

Sheet 07The solution

The one view.

Elevate ONE View, rebuilt as one simplified workflow a mechanic can trust in the field.

Stylised field service app screen showing a unit list with status indicators
Stylised field service app screen showing a commissioning detail with a progress ring
Sheet 08The design tour

What the design fixed.

Stylised field service app screen showing a unit list with status indicators
Field app

Learn it once, know it everywhere.

Components behaved differently from screen to screen, so every view felt unfamiliar. One consistent set now behaves the same in every flow, so a mechanic learns the app once.

Stylised field service app screen showing a commissioning detail with a progress ring
Field app

Speed where it was slowest.

Commissioning and maintenance ran through tangled paths, costing time in exactly the moments a mechanic needed it most. The flow is streamlined end to end, so the app is something you barely have to think about.

Stylised field service app screen showing a health status view with a trend chart
Field app

It looks like the work it does.

A generic app look sat oddly against equipment and site conditions. The visual language follows Elevate's industrial identity instead, so the tool reads as part of the job rather than borrowed from somewhere else.

Screens

What can be shown.

Selected screens, kept limited for confidentiality.

Stylised field service app screen showing a unit list with status indicators
Stylised field service app screen showing a commissioning detail with a progress ring
Stylised field service app screen showing a health status view with a trend chart

The same job, fewer steps.

The heavy old flow beside the simplified redesign.

Before
Stylised field service app screen showing a unit list with status indicators
After
Stylised field service app screen showing a commissioning detail with a progress ring

The core flow

Commissioning

  • The heavy flow made simple and fast
My design principle for the redesign

For a mechanic on site, every extra tap is time lost, so the whole job was to take taps away.

Reflection

Influence, as much as screens.

This project taught me to advocate for the right design inside a complex corporate culture, and to translate stakeholder demands into practical solutions. Often that meant choosing the least worst path under real technical and capacity constraints, while still landing a simplified, high value outcome for the mechanic.

As a founding member of the centre of excellence team, I learned as much about influence as about screens.

A simpler app, and a faster job, for mechanics in the field.