Reporting Clarity

Powerful data isn't enough if people can't find their way to it

Nielsen provides organizations with data and market-measurement tools that help them understand consumer behavior and make business decisions. But having powerful data isn't enough. Users have to be able to find the right way to access it.

Product metrics were showing low adoption of Nielsen's reporting experience. The reporting capabilities existed, but the experience made them difficult to discover, understand, and use. Users lacked a clear entry point for launching reports, accessing data, and sharing results. At the same time, report types relied heavily on color to distinguish one from another, providing little context about what each report actually did. The challenge became:

Low adoption was the signal, not the problem

Rather than assuming users simply weren't interested in the reporting capabilities, I examined the experience itself to understand what might be preventing adoption. Several usability issues emerged.

Access & navigation

Users needed a centralized location from which they could launch applications and reporting experiences.

Application consistency

Applications had evolved independently. Some experiences were dated, and patterns were inconsistent across products.

Report discovery

Users couldn't easily determine which report was appropriate for the question they were trying to answer.

Report creation

Even after finding a reporting tool, users had difficulty creating the reports they needed.

Customization & collaboration

Users wanted their own reporting area, access to custom data, and ways to share reports with colleagues.

Together, these findings reframed the challenge.

The existing experience exposed applications and reports, but it didn't sufficiently help users understand where to go, what to choose, or what to do next.

One reporting ecosystem, many kinds of user

Improving usability also supported a larger business objective. Nielsen wanted to increase customer adoption, support revenue growth, strengthen awareness of its capabilities, and increase market share. Users wanted something more immediate: easy access to data, custom reporting, and tools that helped them answer business questions.

The audience was also diverse, including brand managers, data analysts, Nielsen client service teams, research analysts, category managers, and space managers. That meant the solution couldn't be designed around one highly technical user. It needed to help people with different responsibilities and levels of familiarity navigate the same reporting ecosystem.

Starting from what users were trying to accomplish

Instead of organizing the experience primarily around Nielsen's applications, I began looking at it from the perspective of what users were trying to accomplish. For example:

• Brand manager compares sales across several new brands within a demographic.
• Space manager looks for opportunities to improve product placement on shelves.
• Business analyst compares promotional performance across seasons.
• Category manager shares reports and insights with colleagues.

These scenarios helped shift the conversation away from individual features and toward the questions users were trying to answer with the data.

Improving the ecosystem without rebuilding it

The redesign also had to work within the realities of a large enterprise platform. The project included:

• Short timelines
• High expectations for the MVP
• Changing component libraries
• Limited access to users
• A new codebase initiative
• New micro-frontend initiatives

Rather than proposing an entirely new ecosystem, I focused on improvements that could make the existing reporting environment significantly easier to understand while remaining feasible within Nielsen's evolving technical architecture.

Organizing reports around tasks, not internal systems

The redesigned experience introduced a stronger information hierarchy for discovering and launching reports. Instead of presenting applications as disconnected destinations, reports were organized around clearer launch points and categories. Users could navigate categories such as:

Within a category, related reports from different Nielsen systems could be surfaced together. This was an important shift.

The interface began translating the underlying system architecture into a structure based on the user's task.

More context at the point of decision

Navigation alone wasn't enough. Users also needed enough information to determine which report to choose. I redesigned the report tiles to provide more context at the point of decision. Rather than relying primarily on color, the updated cards incorporated stronger visual identification, report names, descriptions, preview imagery, and clear actions. The overall experience introduced:

• New navigation and organization
• Clearer category identification
• Disclosure patterns for progressive navigation
• Product and brand identification
• Redesigned report tiles
• Action menus for sharing and downloading
• Filtering, sorting, and favorites
• List and tile viewing options

The goal wasn't simply to modernize the UI.

Making the data easier to understand, not just showing more of it

The work extended beyond finding reports. The reporting interfaces themselves needed to turn dense consumer data into information people could scan and interpret. For example, the Brand Planning experience organized demographic information into focused visual modules highlighting consumption drivers, ethnicity, age, household income, and lifestyle groups. Instead of treating the dashboard as a collection of charts, the hierarchy emphasized the most meaningful information first.

We didn't have to assume the new experience was better

One of the most valuable parts of this project came after the design shipped. We could measure behavior. Google Analytics showed that usage of the new UI increased significantly after launch. At one point, the number of users in the new UI had increased 3× compared with the previous week.

Across the measured launch period, 266 users used the new UI, compared with 255 users in the old UI. Users also spent an average of 11.5 minutes per session in the new experience, 5.4 minutes longer than the old UI. These metrics provided evidence that users were finding and engaging with the redesigned reporting experience.

From a concerning metric to measurable behavior change

The project began with a concerning product metric: low adoption. But analytics alone couldn't explain why. By combining product data with UX evaluation and user needs, I identified a deeper issue around discoverability, navigation, and comprehension.

The redesign created a clearer entry point into Nielsen's reporting ecosystem, improved the organization of reports, provided more context at the point of selection, and introduced tools for finding, filtering, saving, and sharing information. Most importantly, we measured what happened after launch. Usage of the new experience increased, giving us evidence that the design changes were influencing real behavior.

Connecting UX decisions to measurable product behavior

Metrics tell you where to look, not necessarily what to fix

Low adoption told us something was wrong. UX investigation helped uncover why.

Enterprise complexity shouldn't become user complexity

Nielsen had multiple applications, reporting systems, and technical initiatives underneath the experience. Users shouldn't need to understand that architecture to accomplish their work.

Information architecture can be a product-strategy decision

Organizing reports around user intent rather than internal systems changed how users entered and understood the ecosystem.

Design outcomes should be measurable

This project reinforced the importance of defining success beyond usability testing, and continuing to evaluate the experience after release.