My Role
I led this project end-to-end as the sole designer for a client, who came with the initial idea and very little brief: from research through to final UI and design system.
Discovery & competitive analysis
Problem statements & HMW questions
Information architecture & sitemap
User flows & journey maps
UI design & design system
The Problem
A maintenance round on an industrial site still runs on paper in most plants. On paper, a check that was done and a check that was skipped look exactly the same: no timestamp, no proof, just a signature at the bottom of a page. The supervisor only finds out hours later, through a phone call or an end-of-shift report.
RoundPro starts there: not "digitize the checklist," but give the technician a faster way to prove he did the work, and the supervisor a way to see it happen instead of hearing about it later.
Discovery & competitive analysis
Problem statements & HMW questions
Information architecture & sitemap
User flows & journey maps
UI design & design system
The Problem
A maintenance round on an industrial site still runs on paper in most plants. On paper, a check that was done and a check that was skipped look exactly the same: no timestamp, no proof, just a signature at the bottom of a page. The supervisor only finds out hours later, through a phone call or an end-of-shift report.
RoundPro starts there: not "digitize the checklist," but give the technician a faster way to prove he did the work, and the supervisor a way to see it happen instead of hearing about it later.
Discovery & competitive analysis
Problem statements & HMW questions
Information architecture & sitemap
User flows & journey maps
UI design & design system
The Problem
A maintenance round on an industrial site still runs on paper in most plants. On paper, a check that was done and a check that was skipped look exactly the same: no timestamp, no proof, just a signature at the bottom of a page. The supervisor only finds out hours later, through a phone call or an end-of-shift report.
RoundPro starts there: not "digitize the checklist," but give the technician a faster way to prove he did the work, and the supervisor a way to see it happen instead of hearing about it later.
What the research showed
Around ten field interviews (seven technicians, three supervisors), run with two prepared question guides alongside on-site observation, then cross-checked against sector research, revealed a two-sided problem. For technicians, trust is the real issue: paper that proves nothing, checklists that don’t match the equipment, apps that feel like surveillance. For supervisors, visibility dominates: status known hours too late, technicians double-dispatched on the same alert, no reliable equipment history. The common thread on both sides: nobody can prove what actually happened, until it’s too late to matter.
Personas
Karim Haddad, Technician, 34, 8 years on industrial maintenance sites. Rigorous on-site, but everything downstream still lives on a paper notebook: no reliable trace, easy to miss a point when the list doesn't match what's in front of him.
"Karim needs the round itself faster and more reliable."
Rana Khoury, Supervisor, 41, overseeing 14 technicians across 3 zones. Her day is reconstructing status from phone calls and paper hand-ins instead of reading it off a screen.
"Rana needs what Karim does to become visible without asking."
Architecture
Two sitemaps, one shared logic, meeting at exactly one point on purpose: the alert. Everything on the technician side funnels toward reporting one; everything on the supervisor side starts from acting on one. That seam is also the part of the sitemap that went through the most rework, once the technician-matching logic moved earlier in the flow.
The supervisor side spans desktop (planning, reports) and tablet (field checks), same architecture adapted per surface.
Emotional Journey
Karim's round starts with low-grade friction and settles into routine confidence once the scan and adapted checklist remove the guesswork: he finishes knowing it's actually recorded, not just written down.
Rana's day starts with uncertainty about three zones at once and moves toward reassurance as status updates live instead of waiting for a call, on her desktop or her tablet between zones. The anxious part of her day was never the maintenance itself, it was not knowing.
Karim's round starts with low-grade friction and settles into routine confidence once the scan and adapted checklist remove the guesswork: he finishes knowing it's actually recorded, not just written down.
Rana's day starts with uncertainty about three zones at once and moves toward reassurance as status updates live instead of waiting for a call, on her desktop or her tablet between zones. The anxious part of her day was never the maintenance itself, it was not knowing.
Key Flow
The clearest single flow through RondePro is anomaly reporting and resolution, because it's the one moment both roles touch the same event:
Karim reports an anomaly's severity → minor issues resolve on the spot, majeure/critique cases raise a full alert → Rana sees a technician-match indicator already in the assignment field and validates from a recap screen → the technician follows guided steps, trackable in real time until resolved → the equipment's history updates automatically for both sides.
No manual sign-off buried in a separate screen, no anomaly that only exists in one person's head.
The clearest single flow through RondePro is anomaly reporting and resolution, because it's the one moment both roles touch the same event:
Karim reports an anomaly's severity → minor issues resolve on the spot, majeure/critique cases raise a full alert → Rana sees a technician-match indicator already in the assignment field and validates from a recap screen → the technician follows guided steps, trackable in real time until resolved → the equipment's history updates automatically for both sides.
No manual sign-off buried in a separate screen, no anomaly that only exists in one person's head.
Design System
RoundPro’s design system runs on a deep forest green primary and semantic status colors, so an alert's severity reads instantly across surfaces. Typography runs on Poppins across a type scale built for legibility at a glance, even in bright daylight on site.
Shared components (buttons, status badges, tabs & filters, cards) keep Karim's checklist card and Rana's alert card visibly part of the same product, on mobile, desktop, or tablet.
What i shipped
Technician app: QR-based equipment scan, checklist adapted per equipment type, material & PPE confirmation before starting, guided intervention steps, on-the-spot resolution for minor anomalies, round and equipment history, PIN-based login.
Supervisor dashboard (desktop + tablet): calendar-based assignment, technician-match indicator on every alert, recap-and-validate before dispatch, live intervention tracking, technician roster, equipment history, weekly/monthly/quarterly reports with PDF/Excel export. Rolled out to around 15 technicians and supervisors at launch. Feedback from the field has been positive; no formal usability metrics were collected.
