Evolving an unused app into an efficient mobile solution, turning paper-based field work into a practical digital workflow_
Adding new features and redesign the navigation and interfaces of the mobile applications for technicians, streamlining their fieldwork
Lead UX/UI Designer for all the company’s design needs across mobile, desktop, and other tools. Worked directly with the company director and developer to define design direction and make key decisions, ensuring alignment with user needs and business goals.
What I had to work with
Live Product
The product was already live, meaning any change had to be carefully considered to avoid disrupting existing users and workflows.
Multi-Tool Ecosystem
The mobile app was part of a larger suite of tools, connected to a desktop application used by different user profiles but sharing the same ecosystem.
Limited User Access
Direct access to end users was limited, restricting the amount of primary research that could be conducted.
My process
Every project follows the same three phases. Open a step to see what it produced.
How I worked
Prioritizing improvements in a live product
To work safely within a live product and limited development capacity, I defined a phased redesign strategy based on urgency and impact, focusing first on the areas that would most improve the user experience.
This approach delivered incremental value without risking the stability of the product, while remaining realistic given technical and resource constraints.
Ensuring consistency across a multi-tool ecosystem
I reused existing patterns, technical constraints, and user habits from the current mobile and desktop tools, and leveraged the desktop design system I was building by adapting it into mobile-friendly components.
This ensured visual and functional consistency across the suite, reduced friction for existing users, and minimized development effort.
Adapting research methods to limited user access
With limited direct access to users, I combined interviews with close collaboration with the support team, analysis of user reports and workflows, review of desktop app usage, and usability testing with construction professionals in my personal network.
This allowed me to make informed design decisions grounded in real-world usage, despite research constraints.
What I did
Navigation
Users struggled to orient themselves on mobile. They needed to move between different ways of accessing their files and, once inside a file, navigate multiple layers of content. This created cognitive overload and made it harder to understand where they were and what they could do next.
I structured navigation around two successive contexts, following the technicians’ real workflow.
First, users need to find and access the file linked to their next intervention. The app therefore opens directly on the calendar — the natural starting point for field work and the entry point chosen by 99% of users. They can also access other files through Files, Map and Internal exchanges, depending on their context.
Once a file is opened, navigation switches to a dedicated structure for exploring and working within that file, so users only see the options relevant to their current task.
Multiple ways to access a file
Calendar, Files, Map and Internal exchanges provide different entry points depending on how users approach their work.
File-specific navigation
Once inside a file, the main navigation is replaced by contextual navigation dedicated to its different sections, such as information, media and exchanges.
Schedule
The existing schedule was visually dense on mobile, making information difficult to scan. It also didn’t support key actions such as creating, starting or ending meetings, forcing technicians to leave the agenda to complete simple tasks.
I redesigned the schedule as an action-oriented workspace rather than a passive calendar. The priority was to make upcoming interventions easy to scan, distinguish between personal and team schedules, and bring the actions technicians need directly into their workflow.
A simplified mobile agenda
The interface focuses on the essential information technicians need to prepare for their next interventions, with a layout designed for quick scanning on smaller screens.
Personal and team schedules
Filters allow users to switch easily between their own appointments and the wider team schedule.
Meeting actions in context
Technicians can create a meeting and start or end an intervention directly from the agenda, without navigating through additional screens.
Quote & report creation
Technicians needed to create quotes directly on-site from their phones. The process had to be fast enough for field work, while still capturing detailed information required for pricing, materials and subsequent reports.
A traditional linear form would have made the workflow repetitive and cumbersome, particularly when documenting several rooms.
I structured the quote around the way technicians collect information on-site. General information is captured once, while detailed information is organized by room, allowing users to progressively add the level of detail they need without repeating the same steps.
The goal was to prioritize speed and flexibility without sacrificing precision.
Global and room-based structure
General quote information is separated from room-specific blocks, making complex quotes easier to navigate and complete progressively.
Detailed room capture
For each room, technicians can enter measurements and deductions such as windows or doors, then attach relevant articles, photos and comments.
Quick contextual actions
Large, accessible actions make it easy to add information while moving around a site, with content attached directly to the relevant room or to the quote globally.
Faster article entry
Optimized forms allow technicians to add multiple articles consecutively without having to restart the workflow each time.
This turns the quote into a modular structure that adapts to the intervention, rather than forcing every technician through the same rigid form.
Water leak investigation report
Water leak specialists need to produce highly specific technical reports using different terminology, measurements and investigation methods from standard damage reports.
These reports also have important insurance and legal implications, while still needing to be completed efficiently on-site from a mobile device.
I based the experience on real professional practices rather than adapting the existing generic report.
I analyzed paper reports already used by leak specialists and studied the step-by-step investigation process, then translated both into a structured mobile workflow. The objective was to preserve a process technicians already understood while making data entry faster, clearer and more consistent.
A workflow based on the investigation process
The report is divided into clear stages: Case information, Damage, Investigation and Conclusion, following the order in which technicians work in the field.
Damage documentation
Technicians can locate and describe the damage, then add photos with comments attached directly to each image.
Adaptive investigation methods
Users can add one or several technical investigation methods. The form adapts dynamically to the selected technique, displaying only the relevant measurements and fields.
Contextual technical evidence
Photos and observations can be attached directly to each investigation method, keeping supporting evidence connected to the action that produced it.
Structured conclusion
A dedicated final step gives technicians a clear space to synthesize their findings and produce the final technical conclusion.
The impact I made
increase in mobile license purchases
new major clients acquired
gain in field reporting productivity
