Environmental incident management system

Context

YPF had an environmental incident management platform designed for desktop, built around long forms.

In practice, field operators used it from their phones, reporting incidents directly on-site, often with limited connectivity.

Challenge

Align the experience with real conditions of use. The existing tool was a long form with no clear structure and no offline support. For someone reporting an environmental incident in the field, under pressure and on a phone, this created concrete problems:

• It was easy to lose progress or make mistakes.
• Operators didn't understand where they were in the process.
• There was no reliable way to handle poor or no connectivity.

Design approach

The project covered structure, flows, UI, and copy. I worked closely with the YPF team, under an agile approach that allowed us to iterate and progressively roll out improvements to the system:

• I proposed turning the long form into a step-by-step flow, making the process clearer and easier to follow.
• I designed two separate flows: one for connected scenarios and one for offline use.
• I defined how the sync system worked together with the development team.
• I worked with the YPF team on defining and refining the copy, especially for sync states and system messages.
• I integrated into the team's agile workflow, adapting the design process to sprints: starting from a general layout and progressively refining each section while the team implemented in parallel.
• I coordinated design work with the YPF team throughout the process, acting as the main point of contact from the consultancy.

The solution

The redesigned platform replaced a single, overwhelming form with a guided, step-by-step flow, built for mobile use in remote environments.

Navigation became clearer, progress was made visible, and the experience aligned with how incident reporting actually happens in the field.

Results

• A general layout was delivered as a starting point, which the YPF team began implementing right away.
• Work proceeded in sprints, progressively refining individual sections while development ran in parallel.
• The modular structure let the team adopt changes incrementally without blocking implementation.
• The client was satisfied with the process and the instructions provided for implementation.