Sharlene Parra
Project Details
My Role:
Timeline:
Tools:
Company
Platform:
Related To:
UX/UI Designer (End-to-End)
3 Weeks
Figma, Optimal Workshop, Miro
Xplor Technologies
FieldEdge Web & Mobile (B2B SaaS)
Mobile 2.0 Redesign
Team
Teresa Ingalls
Product Manager
Charles Cubbage
Software Architect
Engineering Team
Development collaboration
BACKGROUND
A gap that came directly out of the Mobile 2.0 research
One of the recurring findings from the Mobile 2.0 research was that secondary techs and crew members had no way to add their own notes on a job; a limitation users brought up repeatedly, since important on-the-job details had nowhere to go if you weren't the tech assigned to the work order.
Mobile 2.0 addressed this by letting secondary techs add their own work summaries directly within a work order. But solving it on mobile surfaced a second, less visible problem: how should those summaries show up on web?
PROBLEM
Two problems, one after the other
On Mobile
Secondary techs had no way to record important information on a job themselves, a gap cited repeatedly in user research.
On Web
Once mobile supported multiple work summaries per job, there was no existing data structure on web that could display more than one, and FieldEdge's architecture made adding one a much bigger lift than the mobile fix.
SOLUTION
What shipped on mobile, and the workaround that made it work on web
Part 01 - Mobile
Secondary techs can now add their own summary
Directly within the work order, no workaround needed
Within Mobile 2.0, any secondary tech or crew member assigned to a job can add their own work summary directly on the work order, closing the gap that had been flagged repeatedly in research.
Other techs' work summaries will appear within the timeline.
Part 02 - Web
Surfaced through the Timeline, with edit, delete, and filtering
Not the ideal structure, the one the architecture allowed
Web had no existing field built to hold more than one work summary per job. Rebuilding that structure wasn't feasible given how deeply it's tied into FieldEdge's architecture, so instead, each work summary appears within the existing Timeline as a Note, with a "Work Summary" category tag applied so it's still clearly identifiable as one, reusing infrastructure that already existed rather than building something new from scratch.
On web, users can also edit or delete a work summary after it's added, and filter the Timeline by who created it and by "tag", making it easy to find a specific tech's notes on a job without scrolling through everyone else's.
Tradeoff: This wasn't the first-choice solution. A dedicated summaries section on web would be cleaner but it shipped the feature without waiting on a larger architecture change, while keeping the data identifiable and accessible in the meantime.