LISA.EXE v2.0 // MISSION LOG
--:--:-- NL / EN
◂ BACK TO MISSIONS
FieldAssist: End-of-Life Rescue — two phone screens showing the daily schedule and a delivery flow, next to floating elements for calling, navigating, and notifications, with the keywords speed, IA redesign, and cross-user design
MISSION_004 ✓ DONE ★★★ +2000 XP
FieldAssist — from outdated app to field service tool

An app that could no longer be updated, reborn as the digital companion for drivers and technicians — and the first step in LogicTrade's broader app redesign.

[ROLE]
Product Designer
[DURATION]
Jan – May '25
[TEAM]
1 designer · dev team
[TOOLS]
Figma
// LOG_ENTRY — BACKGROUND

An app that outlived its own hardware

LogicTrade already had two standalone apps for the field team: DeliveryAssist and StoreAssist. DeliveryAssist was so outdated that the hardware it ran on — tablets, phones, PDAs — could no longer be updated. No room for a slow, careful redesign: something new had to arrive fast.

// LOG_ENTRY — THE BRIEF

Rebranding to FieldAssist

Rebuild and rebrand DeliveryAssist as FieldAssist: one app for the entire field team, from deliveries to service and measuring visits. No longer a delivery app, but the digital companion for everyone who leaves the building.

// LOG_ENTRY — THE TURNING POINT

A redesign turned out not to be enough

PLOT TWIST

Conversations revealed that the existing app's low adoption wasn't just a design problem — the structure itself had to change too. Halfway through the redesign phase, I started over, with an approach that began much more explicitly from the user.

// LOG_ENTRY — APPROACH

The whiteboard as an accelerator

With a deadline in sight, brainstorm and whiteboard sessions helped me get to the core fast. Not as upfront decoration, but as the place where the question was asked that steered everything after: "What do I need to do today?" That led to the conclusion you see below — whether you have a schedule or not, you need a good home screen.

A whiteboard with handwritten notes: on the left what's missing from the schedule and colleagues' feedback, in the middle sketches of phone screens with tabs and a for-you view, and on the right the question What do I need to do today? with the conclusion that it should be leading A fragment from the session where the core question surfaced — with colleagues' feedback alongside it

From there I worked it out in low-fidelity screens, so the structure could be discussed before it was made to look good. You can see the three-step layout take shape — and in the last sketch, room is already made for what would be added later.

Click an image to view it at full size.

// LOG_ENTRY — CONCEPT

Two ways to see your work

ACHIEVEMENT UNLOCKED — CORE CONCEPT

"A driver doesn't need to see everything — he needs to see his day."

01
"FOR YOU" PAGE

By default, a driver or technician only sees their own scheduled items — no noise, no overview that isn't theirs.

02
CLASSIC FULL OVERVIEW

Still exists alongside it, for the moment someone needs to search more broadly — for example when a customer asks something.

// LOG_ENTRY — INTEGRATION WITH LOGICTRADE

A different user group, the same engine

FieldAssist has to work seamlessly with LogicTrade itself, especially the Planning module — but its user group is completely different from the office staff the rest of the system is built for. That called for design choices suited to people on the road, not behind a desk.

// SIDE_QUESTS — OBSTACLES ALONG THE WAY

The obstacles along the way

Time

The app had to be replaced ASAP, so customers could keep using it — no room for a slow, careful process.

Cross-device

FieldAssist had to work seamlessly with the desktop software, not be designed as an isolated standalone product.

A wide, interconnected user group

From permanent field staff to hired contractors, to office staff who process orders and communicate with the field — and the field team who, in turn, reports back through comments, signatures, photos, and payment.

// LOG_ENTRY — BEFORE & AFTER

The same step, redesigned

Two moments that exist in both apps: checking off an order's line items, and capturing proof at the customer. The steps haven't disappeared — they're just no longer a form to click through.

Click a screen to open it at full size.

// LOG_ENTRY — TIMELINE

From kickoff to launch

JAN '25
Project started
MAR '25
Pilot launched with first users
MAR–MAY '25
Iterations based on pilot feedback
MAY '25
Final version live
// LOG_ENTRY — RESULT

The first step in the app redesign

From kickoff in January to a pilot in March, followed by two months of focused iteration based on user feedback, until the final version went live in May.

FIRST OF
TWO
FieldAssist → StoreAssist
END-OF-LIFE
HARDWARE REPLACED
the original problem solved
LIVE SINCE
MAY '25
after a pilot and two months of iteration
// LOG_ENTRY — REFLECTION

What I take from this

Arguing for the right solution even under time pressure

The pressure was real: the app had to be replaced ASAP. Still, based on what came out of conversations, I chose to push for more than a quick visual redesign — and to start over halfway through toward a structural solution. That felt risky with a deadline in sight, but a quick fix that didn't solve the real problem (low adoption) would have cost more in the long run.

The pilot solved two problems at once

The customers under the most time pressure could get going early thanks to the pilot — exactly the people who couldn't wait. Those same customers immediately became heavy users, which also gave the pilot the most valuable feedback. Urgency and quality of feedback turned out not to be a trade-off here, but the same group of people.

◂ PREVIOUS MISSION 4 / 4 NEXT MISSION ▸