Design Product · JLL

Corrigo Mobile

Technicians run their day from the Corrigo mobile app: pick up a work order, check in, work through the steps, attach photos, and complete. Every action is a push through nested screens, nothing shows how much is left, and the app mixes redesigned screens with legacy ones that feel like a different product. Technicians told us it takes too many clicks to finish one work order. I am redesigning the work order experience for executing, creating, and finding work.

Company
JLL
Product
Corrigo
Role
Design Lead
Period
2026

Decisions

01

The next action is one tap from the Dashboard.

A card at the top shows the active work order and the only valid next step: pick up, check in, check out, or complete. When the next step is not clear, the card shows the status only and opens the work order, so a fast tap never does the wrong thing.

02

Progress follows the technician.

A checklist of what is done and what is still required stays with them across every screen of the work. Complete stays disabled until the required items pass, so nobody has to go back to find what is missing.

03

Structure before education.

The problem is not that people cannot find things. It is how deep the screens go and how often they break. So I set aside in-app guides and changed the structure.

04

Measure first, then change.

The app could not yet be measured well on iOS, so turning that on comes before the redesign, and no target is set until there is a baseline to judge it against.

05

A native prototype on the real backend.

I built a SwiftUI prototype that mirrors the production app's structure and runs on live data or sample data. The team sees what a platform-native app looks like, a teammate can bring a PRD and have the agent map it to screens, and Corrigo's agents get a place in the technician's day, like a reschedule request to the dispatcher and a receipt the agent reads.

Outcome

In progress. I am leading the redesign as Design Lead with the product owner and an engineer. The problem briefs and PRDs for executing, creating, and finding a work order are written, each claim tied to its source, through a discovery process I run with an agent. The native prototype runs end to end on the real backend. Validation is next, so nothing is measured yet.

Screens

The native prototype: the Dashboard in light and dark, My Work Orders, Work Order Details and its actions, the calendar with a reschedule request sent to the dispatcher, receipt scanning with the agent reading the receipt, and asset details. Then how the Dashboard changed across four builds, from the first native concept to the production colors.

The screens are behind a password

The screens for this and the other case studies are shared with the people I am talking to. The password is in the resume I sent with my application. If you do not have it, ask me for it.