Monitoring, calculation and reporting, in one place.

A platform for monitoring, calculation, reporting and statistical analysis, used by specialists both internally and by customers. I redesigned the expert experience in many ways, from dashboards to data views.

Role: UX Designer (sole designer on the project)

Focus: Expert tools, data visualization, and Design System modernization

~4 min read

UX & Interface Design
Design System Migration
Data Visualization
Stakeholder Research
Reliability Improvements
Solo Ownership

The problem: A monitoring and reporting platform for industrial specialists had become hard to use: long text lists, calculations done by hand, work lost to missed saves, and a design library stuck in an old tool.
My role: Sole UX designer on the platform, 2020–2023. I took over from the previous designer and owned the whole experience.
Solutions and hands-on work: Readable information: I condensed complex data and long lists into clear visual blocks, so the essentials can be found at a glance.
Simpler processes: I split heavy, multi-step tasks into guided, step-by-step flows (wizards).
Confidence in the tool: I improved continuity of work and reduced users' load by adding auto-save to the views.
Design system overhaul: I migrated the design system from Sketch to Figma and rebuilt the components to scale.
Outcome and impact: Specialists grasped the data they needed quickly, and running complex calculations became reliable and easy for the whole team. Thanks to auto-save, work was no longer lost. Moving designers and developers into one shared tool made collaboration clearer, and both the development team and the project manager told me their day-to-day work became noticeably smoother.

The brief

Starting Point

An industrial platform for monitoring and reporting had grown complex over time, with expert users struggling through long text lists and manual calculations. I joined as the sole designer, taking over from a previous one, to make the tool work the way specialists actually needed it to.

Selected screens

Desktop and mobile, one platform

Results

The Impact

After launching new features, we systematically ran feedback and testing sessions with actual users. This continuous loop helped us validate what worked in daily operations, identify areas for refinement, and keep the product evolving based on real user needs.

Faster, clearer data at a glance
Turning the dashboard's data panels into visual cards meant specialists no longer had to read through long text lists to find what they needed. Information that used to take scanning and interpreting now became something they could understand in seconds, directly speeding up their daily monitoring and reporting work.
Complex calculations, without the guesswork
Before this, running a complex calculation required deep expertise and careful manual work. The new calculation window guided specialists through the process step by step, reducing the risk of errors and making it possible for more people on the team to run these calculations confidently, not just the most experienced ones.
Less lost work, more trust in the tool
Adding auto-save to data and reporting views removed a real, everyday frustration: losing work due to a missed save or a dropped connection, something that mattered a lot to users working with time-sensitive data from remote factory locations.
A foundation the whole team could build on
Migrating the Design System from Sketch to Figma didn't just modernize the tool, it meant developers and designers were finally working in the same environment. That made handing designs over faster and reduced the back-and-forth that came from working across two disconnected design tools, freeing up time developers had previously spent interpreting or translating designs between formats. I received direct, positive feedback from both the developers and the project manager, who noted how much smoother their day-to-day work became as a result.

Background

I stepped into an ongoing project, picking up work from a previous designer. Some of the first things I focused on were visual improvements to the interface, for example turning the small panels on the dashboard into visual cards instead of plain text lists, which made them much easier to read at a glance. From there, we also designed an auto-save feature for data and reporting views, and improved the structure and content of reports.

The hard parts

Designing for complex expert workflows

One of the ongoing challenges was clarifying complex work processes for expert users. I designed a calculation window that splits a complex calculation into steps, so specialists could run it through a much simpler interface. What consistently helped was never trying to solve this alone. I worked closely with the specialists and factory workers who used the tool daily, co-designing solutions with them instead of guessing what they needed.

Research across time zones

A big part of the challenge was simply logistics. Stakeholder interviews often involved people based in the US or Asia, which meant working around significant time differences and staying flexible with my own schedule. Having the product owner, who already had strong relationships with these stakeholders, involved in the conversations made it much easier to build trust and get people engaged.

Modernizing the Design System

The existing Design System lived in Sketch, an older tool that made collaboration with the rest of the team harder. Alongside the day-to-day design work, I took on migrating the library over to Figma, cleaning up and rebuilding components along the way rather than just copying them over as-is, so the team ended up with a more usable and maintainable design foundation to build on going forward.

In hindsight

Looking back, I would approach the technical side of this project differently today. Instead of relying on static mockups handed off to developers, I'd use AI tools like Claude Design to build working prototypes directly, closing the gap between design and implementation much faster. I'd also structure the Design System from the start with code-level implementation in mind, working closely with developers and building with Claude Code, so it would be not just a well-organized component library in Figma, but something developers could pull from directly.

The team itself worked well together throughout the project, and I don't think our size or setup was ever the real issue. The growth I see now is more about how I'd use today's tools and ways of working to close that design-to-development gap earlier and more effectively.

Keep reading

Other case studies

Public education

National Education Administration Platform

Brought structure to a massive public sector platform by uniting complex municipal school workflows into a clear, accessible tool for teachers and administrators.

View case study →