Modernising a Legacy Reporting System

The Emissions Data Monitoring and Analysis (EDMA) System was originally developed more than a decade ago. EDMA 2.0 was a system-wide revamp aimed at making the platform more user-friendly and introducing a modern, consistent interface across its internet and intranet experiences.

Working alongside a senior designer in a two-person design team, I contributed to 13 modules spread across 9 sprints, with our two-person design team producing 80+ screens per three-week sprint. I translated user stories, old interfaces and spreadsheet wireframes into screens using the established design language system, defined supporting interactions and took my assigned designs through client review, sign-off and developer handover.

The revamp needed to modernise a decade-old system while accommodating detailed reporting requirements and business rules across multiple modules.

Joining during delivery, I needed to become familiar with the established design patterns quickly and apply them consistently across my assigned work. Each module required translating its requirements into screens, working through relevant interactions and resolving questions with client stakeholders and developers within sprint timelines.

I used Azure DevOps user stories and spreadsheet wireframes to understand each module’s requirements, then developed its screens using reusable Figma components.

My work included defining screen sequences and supporting states for relevant actions, such as submission and deletion. I independently facilitated reviews for my assigned modules, incorporated stakeholder feedback and clarified design behaviour during developer knowledge-transfer sessions.

Initial approach. Users uploaded up to 70 supporting files at the start of a form, then tagged the relevant sections against each file.

Issue I identified. Managing section associations across a long file list could become cumbersome.

My proposal. I kept the central upload area and reversed the interaction: users select supporting files within each form section. Side tabs let them move between sections; the file list scrolls beyond ten items to keep the modal height consistent.

Signed-off outcome. My proposal was accepted and included in the signed-off design.

I chose to keep dependent fields visible but disabled until the preceding selection made them available. The form’s logic was complex, and showing those fields upfront made the relationship between inputs clear: users could see what information the form would require and what they needed to do next.

Progressive disclosure would have hidden that structure until each condition was met. Keeping the fields in place gave users a consistent view of the form while preventing entries that were not yet applicable.