Eugenio Tamburini - Portfolio

EUGENIO TAMBURINI

PRODUCT DESIGNER

EUGENIO TAMBURINI

PRODUCT DESIGNER

CONTACT

Universe Dashboards and Reports. A unified solution with deeper flexibility.

I collaborated closely with my design, PM and engineering teams to redesign a unified suite that slowed client churn, rebuilt trust with users, and won new business by empowering users to decide what data mattered most to them.

60% Adoption

Over legacy reporting within a 3 month period, allowing us to sunset legacy reports, reducing maintenance costs.

40% of Reports Shared

Users were spending less time on workaround or external solutions when using new report customizations.

2 Seconds

Load time reduction. Maintaining trust with users and reducing bugs.

70% Overall Satisfaction

Clients were less likely to cite report shortcomings as deal breakers in contract renewals with Universe.

Role

Lead Product Designer

Responsibility

Identifying the problem, outlining design strategy, leading usability testing, hands-on building, release, and helping to roadmap future iterations.

Team

Product Manager | 3 Frontend Developers | 2 Data Engineers

Skills

End-to-end product design.
Design debt mitigation.
Hands-on shipping.

Problem

Ownership

Research

Before

After

Release

Takeaway

Problem

High-value enterprise clients were leaving Universe because reporting did not meet their business needs.

They didn’t trust the numbers, couldn’t find the answers they needed, and the business attempted band-aid solutions that compounded pain points.

How could we design an accurate, performant, scalable, and flexible reporting solution that made sticking with Universe the best choice for their business?

what i owned

I aligned the design strategy under the theme of certainty, optimizing for a focused set of tools over a breadth of features.

Every stakeholder prioritized something different. I was responsible for finding the connective thread between them. By auditing user flows, shadowing users, facilitating interviews and more, I learned that what everyone craved was certainty. They wanted to be able to trust the numbers.

How can design help users trust the numbers? By giving them the flexibility to pull and compare the data they needed.

Research

Clients were threatening to leave Universe because they couldn't trust the numbers due to fragmented reporting.

They relied on complex workarounds to get basic insights, often having to navigate to multiple screens to find the answers they needed, or cross-reference the numbers to make sure they were the same everywhere.

5 different pages, all doing their own thing. Did we need all of these pages?

What if we could sunset the redundant flows, and add depth to dashboards and account reports?

By adding depth and flexibility to account dashboards and reports, we could create a focused, scalable solution for our clients and business.

beFORE

Dashboards were limited, reports were rigid, and custom options were siloed.

This forced users to jump between different pages to find the answers they were looking for, and often met a system that was inconsistent not just in the data provided but also in design and user experience.

Account dashboards suffered from shallow and ambiguous metrics, limited filtering options, poor accessibility, and extremely low usage.
Event dashboards inherited the same issues as account dashboards, compounded by the fact that they weren’t fully aligned with our design system.
Account and event reports offered many of the same templates, but they often led to different outcomes. Filtering was extremely limited, forcing workarounds.
Custom reports had much of the flexibility our users needed, but they were locked behind admin permissions and built on outdated frameworks.
Account dashboards suffered from shallow and ambiguous metrics, limited filtering options, poor accessibility, and extremely low usage.
Event dashboards inherited the same issues as account dashboards, compounded by the fact that they weren’t fully aligned with our design system.
Account and event reports offered many of the same templates, but they often led to different outcomes. Filtering was extremely limited, forcing workarounds.
Custom reports had much of the flexibility our users needed, but they were locked behind admin permissions and built on outdated frameworks.
Account dashboards suffered from shallow and ambiguous metrics, limited filtering options, poor accessibility, and extremely low usage.
Event dashboards inherited the same issues as account dashboards, compounded by the fact that they weren’t fully aligned with our design system.
Account and event reports offered many of the same templates, but they often led to different outcomes. Filtering was extremely limited, forcing workarounds.
Custom reports had much of the flexibility our users needed, but they were locked behind admin permissions and built on outdated frameworks.
Account dashboards suffered from shallow and ambiguous metrics, limited filtering options, poor accessibility, and extremely low usage.
Event dashboards inherited the same issues as account dashboards, compounded by the fact that they weren’t fully aligned with our design system.
Account and event reports offered many of the same templates, but they often led to different outcomes. Filtering was extremely limited, forcing workarounds.
Custom reports had much of the flexibility our users needed, but they were locked behind admin permissions and built on outdated frameworks.

Account dashboards suffered from shallow and ambiguous metrics, limited filtering options, poor accessibility, and extremely low usage.
Event dashboards inherited the same issues as account dashboards, compounded by the fact that they weren’t fully aligned with our design system.
Account and event reports offered many of the same templates, but they often led to different outcomes. Filtering was extremely limited, forcing workarounds.
Custom reports had much of the flexibility our users needed, but they were locked behind admin permissions and built on outdated frameworks.
Account dashboards suffered from shallow and ambiguous metrics, limited filtering options, poor accessibility, and extremely low usage.
Event dashboards inherited the same issues as account dashboards, compounded by the fact that they weren’t fully aligned with our design system.
Account and event reports offered many of the same templates, but they often led to different outcomes. Filtering was extremely limited, forcing workarounds.
Custom reports had much of the flexibility our users needed, but they were locked behind admin permissions and built on outdated frameworks.
Account dashboards suffered from shallow and ambiguous metrics, limited filtering options, poor accessibility, and extremely low usage.
Event dashboards inherited the same issues as account dashboards, compounded by the fact that they weren’t fully aligned with our design system.
Account and event reports offered many of the same templates, but they often led to different outcomes. Filtering was extremely limited, forcing workarounds.
Custom reports had much of the flexibility our users needed, but they were locked behind admin permissions and built on outdated frameworks.
Account dashboards suffered from shallow and ambiguous metrics, limited filtering options, poor accessibility, and extremely low usage.
Event dashboards inherited the same issues as account dashboards, compounded by the fact that they weren’t fully aligned with our design system.
Account and event reports offered many of the same templates, but they often led to different outcomes. Filtering was extremely limited, forcing workarounds.
Custom reports had much of the flexibility our users needed, but they were locked behind admin permissions and built on outdated frameworks.

Account dashboards suffered from shallow and ambiguous metrics, limited filtering options, poor accessibility, and extremely low usage.
Event dashboards inherited the same issues as account dashboards, compounded by the fact that they weren’t fully aligned with our design system.
Account and event reports offered many of the same templates, but they often led to different outcomes. Filtering was extremely limited, forcing workarounds.
Custom reports had much of the flexibility our users needed, but they were locked behind admin permissions and built on outdated frameworks.
Account dashboards suffered from shallow and ambiguous metrics, limited filtering options, poor accessibility, and extremely low usage.
Event dashboards inherited the same issues as account dashboards, compounded by the fact that they weren’t fully aligned with our design system.
Account and event reports offered many of the same templates, but they often led to different outcomes. Filtering was extremely limited, forcing workarounds.
Custom reports had much of the flexibility our users needed, but they were locked behind admin permissions and built on outdated frameworks.
Account dashboards suffered from shallow and ambiguous metrics, limited filtering options, poor accessibility, and extremely low usage.
Event dashboards inherited the same issues as account dashboards, compounded by the fact that they weren’t fully aligned with our design system.
Account and event reports offered many of the same templates, but they often led to different outcomes. Filtering was extremely limited, forcing workarounds.
Custom reports had much of the flexibility our users needed, but they were locked behind admin permissions and built on outdated frameworks.
Account dashboards suffered from shallow and ambiguous metrics, limited filtering options, poor accessibility, and extremely low usage.
Event dashboards inherited the same issues as account dashboards, compounded by the fact that they weren’t fully aligned with our design system.
Account and event reports offered many of the same templates, but they often led to different outcomes. Filtering was extremely limited, forcing workarounds.
Custom reports had much of the flexibility our users needed, but they were locked behind admin permissions and built on outdated frameworks.

After

Users get at-a-glance information from dashboards, then dig deeper, export and schedule with reports.

Most users already began their journey in dashboards. We made it easier to get actionable insights from that first step. When they needed to dig deeper and compare different metrics, they would go to account reports. No more confusing workflows.

Overview showed sales data. Trends focused on patterns. Sources displayed affiliate and payment data. BoxOffice was all about attendance.

Account reports were given the same flexibility to edit and export as custom reports, removing the overreliance on one-off templates.

Like dashboards, account reports already provided event-level data. The primary user goal here was always to export reports with the data they needed, something custom reports were great at. Providing that flexibility improved usability and maintenance.

We kept the same level of templates but expanded key ones with our new approach. We would monitor usage data to leverage only a handful of templates over time.

A few key design decisions.
We used Apache Superset to bring dashboards to life. I designed inside the integration and matched it as close as possible to our design system.

Release

Dashboards were released first, with account report updates tested and roadmapped for future release.

The release reflected weeks of user testing and iteration, resulting in a unified, intuitive experience for clients. Early adoption and feedback confirmed we were moving in the right direction, setting the foundation for future reporting updates.

Initial release did not completely match proposed designs, as our chosen integration - Apache Superset - proved to be more difficult to style than anticipated. As such, we prioritized structure and performance while we iterated on designs.

TAKEAWAYS

Design should be proactive, integrations can be fickle, and testing is often more impactful than endless discovery.

By the time we tackled the problem, it was already in a critical state, leaving us with a relatively short runway to solve it. What if we had looked at the numbers and spoken to our teams and clients earlier?

We chose to leverage Apache Superset as our dashboard integration. It was open source and came with white label components that should have made design and development seamless. But it was a decision that required deeper exploration, as Superset proved to be fairly rigid. Given a second chance, I would consider alternatives more closely.

Lastly, though we had time for extensive discovery, it was user testing that made the biggest difference. Most of what we thought we knew about our user flows changed significantly when we put a prototype in front of users.

Next up

Bulk Edits

LEARN MORE