Enterprise UX · Information Architecture · Interaction Design · Design System
Transforming a legacy MDM platform into an efficient operational workspace
Redesigned core information architecture and workflows for a global utility platform, reducing record review time by 72.9%.

THE CHALLENGE
Siemens’ legacy Meter Data Management (MDM) had legacy UI that was reaching end of support. We needed to rebuild the entire front end from the ground up.
How do you fix existing usability problems while supporting future product needs?
How do you create a scalable foundation so that we’re not building the entire application screen by screen?
What I designed
Core information architecture and interaction patterns for a new operational workspace, combining search, results, and details into a continuous workflow.
What changed
72.9% faster record review (3:23 → 0:55 for 5 records)
36 enterprise clients migrated to the new UI
Established a reusable page pattern for the new SaaS platform
My Role
As the lead UX designer on a 16-person cross-functional team, I collaborated with Product, Engineering, QA and Documentation.
Led research and validated design concepts
Defined UX direction and aligned stakeholders on scope
Owned interaction design and UI specifications
Partnered with engineering to resolve implementation challenges
Problem
Siemens’ Meter Data Management (MDM) processes high volumes of meter data for electric, water, and gas utilities. Users need to review and correct data issues throughout the meter-to-cash workflow.
But the legacy interface made the work unnecessarily slow and cumbersome. Users had to navigate across multi-pages and nested tabs to inspect records, repeatedly switching context, waiting for the data to load, and inconsistent data labels were confusing.
Fragmented navigation – Information is scattered across different sub-pages and nested tabs
Loss of context – Users had to navigate back and forth to move between records and details
High cognitive load – Inconsistent labels made information harder to scan and interpret

Legacy Workflow (Before redesign)
1
Search for a record in the search tab.

2
Drill into record details. Details shown in the second tab with additional sub-pages and nested tabs.



3
Return back to search and select another record.

Solution
Before vs. After
Legacy UI
Database-like search tool
Search, results, and details spread across pages
Repeated navigation and context switching
Slow page transitions


NextGen UI
Operational workspace
Search, results, and details in one workspace
Continuous review and action
Progressive loading

The legacy system was optimized for searching one record at a time. But users typically needed to review a set of records, investigate issues, take action, and move on.
I redesigned the experience around this workflow by bringing search, results, and details into a single workspace, where users could move between records, inspect relevant information, and take action without repeatedly navigating between pages.
Search (Top) - Enter search criteria that needs attention
List (Left) - Scan the search results and move between records
Details (Right) - Inspect and take actions without losing context

Iteration
Usability testing revealed that users needed more control over how they searched for records and reviewed details. I refined the design to support their existing workflows and information needs.
Users reused frequent searches → Saved search
Users wanted to see relevant information first → Data fields clean up and information optimization
Users are accustomed to old UI → Flexible layout views
Users wanted more precise and focused search → Advanced search operators


Design Decisions
A. Redesigning the workflow around “triage”
Through user research, I found that most of our users operate in a “triage mode”––meaning they have a number of records to work through, rather than performing targeted search or conducting deep analysis on a single record.

I led multiple discussions with stakeholders to demonstrate how the underlying data intersected with the user’s workflow, and how they could possibly result in faster and better workflow, which would directly impact the product’s bottom line.
We agreed on a high-level architecture schema…

Became this wireframe…

Became this rough UI…

At this point, the architecture change and UI outlines got a green light from the engineering that they can accommodate the change.
B. Balancing information density and usability
Combining information from multiple pages created a new challenge: fitting context into a single page without overwhelming users.

I prioritized the information users needed most, made search and detail areas more compact, and established consistent labeling patterns to improve scanability.

I finalized the design by vetting all edge cases such as empty states, loading states and error messages.

Default landing

Loading

Search results - List empty

Related list empty
Design System
I documented the page structure, interaction patterns, and key states as a reusable component in the design system, creating a foundation for future work.
“
Without the NextGen UI, we wouldn’t even be in the conversation with City of *****. This is more than a UI—it’s a step-change in our product.
We’re now competing on a completely different level.

–– Head of Product, Siemens Grid Software
Outcomes
72.9% faster record review (3:23 → 0:55 for 5 records)
36 enterprise clients migrated to a new UI
Contributed to the company’s first SaaS customer deal
Established a reusable page pattern for our design system
Replaced the legacy UI with a scalable interface for the SaaS platform