Moody’s Maxsight
(Company)
Moody’s
(Role)
Senior product designer
(What I did)
Product design
UX/UI audit
User research
(Key outcomes)
Reporting time reduced by
40%
Increase in reporting feature adoption
29%
01
Background
Maxsight is a compliance and risk management platform by Moody’s that helps companies assess and monitor the risk of their customers, suppliers, and partners.
Platform combines customer’s internal data with Moody’s data and external sources, then applies analytics, automation, and AI to give a comprehensive view of risk and help teams manage it more effectively.
Reporting plays a key role in helping teams understand this data at a portfolio level and support decision-making and audits.
02
Problem
As Reporting evolved with the introduction of Tableau dashboards, the experience became fragmented across native and third-party interfaces. Users struggled to navigate between different experiences, lacked a portfolio-level overview of risk, and found it difficult to quickly understand the overall picture.
03
Role
I joined as a Senior UX Designer when Tableau had just been introduced. My key scope included UX/UI audit of Tableau dashboards, redesigning filtering, native design for Risk Overview dashboard and redesigning export experience.
04
Goals
• Create a more cohesive Reporting experience across native and Tableau dashboards.
• Improve usability and consistency.
• Help users quickly understand portfolio-level risk.
Discovery
UX audit
I started with a UX/UI audit of the newly introduced Tableau dashboards. The goal was to identify inconsistencies, usability issues, and gaps between the Tableau UI and the native product.
I partnered closely with engineers to understand Tableau’s technical capabilities and constraints. This helped define realistic design boundaries and trade offs, allowing us to focus on the highest-impact changes.
User research
To complement the UX audit, I reviewed existing user feedback and conducted 8 additional interviews with compliance professionals to better understand how they used Reporting in their day-to-day work.
Key objective of my research was to define the content and information hierarchy for a new Risk Overview dashboard. While it was already clear that users needed a high-level view of portfolio risk, it wasn’t yet known what information should be surfaced immediately and what was only relevant in specific scenarios. I wanted to understand how users assessed risk, what they needed to see at a glance, and which details could remain accessible through drill-downs and filters.
Insights
The research indeed revealed an important distinction:
• Power users valued access to detailed data and advanced analysis.
• Most users primarily needed a clear overview and felt overwhelmed by information-dense dashboards.
Rather than designing separate experiences, the opportunity was to create a dashboard that was simple by default while preserving access to deeper analysis when needed.
These insights shaped the dashboard’s information hierarchy, with the most critical metrics surfaced upfront and secondary information available through filters and drill-downs.
Beyond the dashboard experience, the interviews uncovered another recurring pain point: users frequently needed to work with reporting data outside the platform. Existing limited export capabilities didn’t support their workflows, leading to significant manual effort. As a result, improving the export experience was added to the project scope.
Prioritization
Working with the PM and engineering team, I translated audit findings and research insights into a prioritized roadmap. We agreed on 3 key priorities for the project:
1. Improve consistency and usability across Tableau and native Reporting experiences.
2. Create a portfolio-level overview that surfaced the most important risk information at a glance.
3. Support end-to-end reporting workflows by improving how users could export reporting data.
06
Solutions
Aligning Tableau dashboards
Given the technical constraints of Tableau, the focus was on improving what we could control — aligning layouts with the design system, clarifying information hierarchy, and refining filtering to make dashboards more usable and actionable.
I also worked on defining what information should be shown on each dashboard, ensuring each view was aligned with specific user needs rather than exposing all available data.
Native Risk Overview dashboard
The Risk Overview dashboard was built natively as the core entry point for Reporting. Here focus was a clear, high-level view of portfolio risk, rather than deep analysis, with the ability to take mitigating actions directly from the dashboard.
Keeping it native allowed us to ensure better performance, consistency, and tighter integration with the product. It also enabled more actionable design, allowing users to take mitigating actions directly from the dashboard.
Designing export functionality
Exporting was a critical part of the workflow, as users often needed to share insights outside the platform. Research showed that users frequently reworked exported data manually, which highlighted a gap in the product.
I worked with the PM to define what should be included in exports, how data should be structured, and what formats were needed. A key focus was flexibility — allowing users to customise what data to include so the output was relevant to their needs.
07
Outcomes
~40%
faster reporting workflows
+29%
increase in reporting feature adoption
Improved data understanding, allowing users to explore and segment data more effectively for decision-making
Significantly reduced manual work, minimising the need to compile and rework data outside the platform
More confident and auditable decisions, with structured, ready-to-use outputs for stakeholders and regulators
08
Learnings
• Designing for data is about decision-making, not visualisation. Effective dashboards are not about showing more data, but about helping users quickly understand what matters and what action to take.
• Real workflows often extend beyond the product. Reporting doesn’t end in the UI, users need to share, present, and justify decisions. Supporting export and external use is just as important as the dashboards themselves.
• Constraints drive better design decisions. Working within Tableau limitations required prioritisation and focus, leading to more intentional, simplified solutions.
• Consistency doesn’t always mean uniformity. With a mix of native and third-party tools, the goal is to create a cohesive experience, not identical interfaces.
• Collaboration with engineering is critical in complex systems. Close alignment with engineers helped balance usability with feasibility and ensured solutions were practical to implement.