Skip to content
Reducing friction in factory work-order management
Enterprise SaaSIoT

Reducing friction in factory work-order management

Operators and managers were dealing with a fragmented workflow for creating, assigning and tracking work. I redesigned the experience around how work actually moves through the factory.

Role

UX Designer

Company

Manufacturing / Industrial IoT

40%

Faster task handling

70%

Fewer manual errors

30%

Operational efficiency

Live previews

User 1 - Plant Head Click to expand
User 2 - Operation leadClick to expand

Overview and design context

I designed an AI-assisted operations platform that turns scattered, reactive maintenance into one connected flow — surfacing what's critical first, automating handoffs, and putting the right technician on the job with full context.

The Problem and scenario

Maintenance teams in high-stakes manufacturing operate without shared visibility work orders, data, and coordination scattered across disconnected tools, forcing every stakeholder to work in isolation under pressure.

The result: engineers spend more time documenting than fixing, ops heads can't track live progress or dispatch the right technicians, and service workers arrive under-informed — turning every failure into avoidable downtime and reactive firefighting.

Understanding the problem

Why solving this matters

Less downtime, more output straight to the bottom line

  • Every minute of downtime costs money — when a machine stops, production stops. Faster fixes mean less lost output and lower costs.
  • Clarity replaces chaos — one shared, real-time view helps teams act faster, make fewer mistakes, and reach the machine sooner.
  • Reacting becomes preventing — a connected workflow spots patterns early, stopping repeat breakdowns before they happen.

Who are the users

Three teams, one broken handoff

What they ownWhere it brokeUser set
Validate failures, create work ordersBuried in documentation instead of fixingPlant Engineers
Assign technicians, track progressNo real-time view to act or allocateOperations Heads
Resolve issues on-siteArrived with incomplete repair contextService Teams


The business impact

Higher uptime, leaner operations, and smarter maintenance over time — every fix keeps machines running, cuts wasted spend, and builds data that moves the plant from reactive firefighting to predictive control.

StakeholderWhat they ownWhere it broke
Plant EngineersValidate failures, create work ordersBuried in documentation instead of fixing
Operations HeadsAssign technicians, track progressNo real-time view to act or allocate
Service TeamsResolve issues on-siteArrived with incomplete repair context
01

The person

AArjun, 34 / Maintenance Engineer · Factory Floor 2

At 7:40 a.m., a conveyor motor on Floor 2 stops dead. Arjun opens the ticket app to log it — and the form asks him twenty-six questions before it will let him save a single thing.

He's already being called back to the line. He saves a draft he'll never return to, and the motor goes unlogged — invisible to the ops head, invisible to the service team, invisible to the next shift.

Ticket #4471Draft · abandoned
10 of 26 fieldsstuck at 40%
61%
Tickets completed
74%
Field accuracy
26
Fields to save one ticket
02

So I went to the floor

Before redrawing a single field, I watched how the work really happened.

01
On-site observation
Watched 12 live ticket events across 2 floors — no interrupting, just recording how the work actually moved.
02
Interviews
8 engineers and 4 ops heads, semi-structured, focused on the decision moments — where they paused, guessed, or gave up.
03
Timed ticket sessions
40 timed sessions, step by step, to see exactly where the minutes went and which fields stalled people.
04
Ticket data audit
3 months of completed tickets read end to end for error patterns and the fields that were always left blank.
“The AI was correcting people too late. They didn't need a fix after typing — they needed a head start before it.”
03

The decisions that mattered

The obvious first move wasn't the right one.

First attempt
Redesign all 26 fields on one cleaner page.
What I pushed for
A 4-step progressive form where the AI pre-loads context before each step — so the page is never a wall of fields.
Completion61%→89%
First attempt
Show AI suggestions below each field, after the person types.
What I pushed for
Put the AI context before the field — scaffolding the answer, not correcting it after the fact.
Field accuracy74%→91%
First attempt
Keep the familiar table view for the Ops Head.
What I pushed for
Make Kanban the default — it matches how work actually flows. Tested with 4 Ops Heads; Kanban won on task accuracy.
Validated with4 Ops Heads · Kanban won

Solution & polished UI

01 / 03

~35–40% faster resolution

Task handling

🔴Before

Manual coordination delayed every work order

🚀After

Prioritized, streamlined flow

02 / 03

Up to 70% fewer errors

Manual errors

Before

Scattered data caused frequent mistakes and rework

After

Single source of truth

03 / 03

~25–30% more efficient

Operational efficiency

🔴Before

Reactive firefighting drained time and resources

🚀After

Connected, real-time workflow

Conclusion and takeaways

From Chaos to Clarity

  • I led the entire design from research to final UI
  • Created lifecycle tracking, skill-based assignment, and real-time status updates.
  • Improved response time by 40% & managers gained full visibility.
  • Learned how to align multiple stakeholders and standardize workflows.