Enterprise Data Governance

DataVerse

DataVerse unified Lowe's fragmented reporting ecosystem into one governed experience where teams can find trusted metrics, understand definitions, and act faster with AI-assisted guidance.

Disclaimer: All data presented in these case studies has been generated for illustrative purposes only and does not represent actual company data.

Updated DataVerse homepage with application health, curated reports, and navigation to core modules
The Conflict

Fixing the Trust Gap in Enterprise Data

Associates had access to data, but not confidence in it. Metrics lived across disconnected tools, definitions varied by team, and reporting workflows were hard to navigate. Teams spent too much time validating numbers and too little time making decisions.

Role

Senior Product Designer

Timeline

2022 – 2025

Objective

Create a single source of truth for report discovery, metric definitions, and governed decision support

Tools

Figma, FigJam, Design Systems, Cross-functional workshops, UX validation

The Blueprint

Architecting End-to-End Decision Flows

I mapped the operational logic behind DataVerse, including this example for how notifications are triggered, routed, and surfaced across teams. This blueprint defined who gets alerted, when channels switch between in-app and email, and how actions propagate, so users can move from signal to resolution without breaking flow.

DataVerse notifications view showing update alerts and workspace activity
Structural Organization

From Fragmented Tools to Guided Navigation

We replaced one-size-fits-all dashboards with a clear progression from discovery to personal workflow management. The information architecture gave users predictable paths to reports, ownership context, and governance controls from a single entry point.

User Centric Views

DataVerse Home Screen view
The Turning Point

Operationalizing Trust with a Metric Glossary

The highest-impact shift was introducing a centralized Metric Glossary directly inside the workflow. Instead of leaving reports to verify terms, users could validate definitions in context and keep moving. This reduced interpretation drift and made cross-team reporting discussions materially faster.

01 / Live Source Health

Status indicators for glossary and reporting streams so users can immediately see whether definitions are current and available.

02 / Standardized Language

A searchable definition layer that aligns teams on shared terms, including core metrics like revenue, margin, and forecast variance.

DataVerse metric glossary reference for standardized language and definitions
The Craft

Designing an AI Chatbot That Feels Native

Built in-house on AI Foundry, the DataVerse chatbot behaves like a native product layer instead of an add-on assistant. It answers metric questions in context, cites glossary definitions, and routes users to the right report, owner, or next step so teams can go from question to action without context switching.

DataVerse AI-assisted reporting view with searchable cards and quick actions
Evolution

Evolving the Experience for Clarity and Scale

Original DataVerse homepage layout prior to redesign

Legacy Experience

Updated DataVerse homepage with modernized layout and clearer health/status modules

Optimized Experience

The Resolution

Outcomes and Business Impact

Lower Discovery Friction

Consolidated reporting entry points into a single hub, cutting manual report hunting and reducing tool fatigue across teams.

Higher Decision Confidence

Shared metric definitions and in-context AI support reduced interpretation gaps and improved confidence in cross-functional decisions.

Back to Work