Standards and Compliance Insights

A dashboard to help companies spot burnout before it happens.

The Challenge

Burnout and low morale are costly for organizations, but most tools only report on what already happened. At Headversity, we saw an opportunity to go beyond training modules and build something predictive: a dashboard that could show when a workforce was at risk of burnout and poor culture before it became a problem.

The Challenges:

  • Help admins understand stress drivers in their teams.
  • Turn complex, sensitive data into intuitive, actionable insights.
  • Deliver value for both users (HR admins) and the business (retention, sales, and marketing collateral).

The Role

I led UX/UI design from concept to final product while working cross-functionally with Product, Marketing, and Engineering teams.

  • UX/UI Design: Wireframes, prototypes, final UI
  • User Research & Testing: Focus groups, interviews, usability sessions
  • Cross-Functional Facilitation: Workshops with Product, Engineering, Marketing, and Data teams.
  • Iteration: Refining based on real-world client feedback



The Research & Discovery

We kicked off with internal and external discovery sessions to map the admin journey and validate where data collection could have the most impact. Using Miro, we identified key engagement points and hypothesized what “early signs” of burnout could mean to different users.

Insights gained with cross-functional impact:

  • Product: Early research helped prioritize features for the roadmap (Engagement trends, and actionable prompts).
  • Marketing Understanding admin pain points informed messaging and demo strategies for prospects.
  • Engineering: Insights shaped technical feasibility discussions around real-time data updates and interactive visualizations.



The Wireframing & Prototyping

I created low and high-fidelity wireframes in Miro and Figma to align stakeholders and Engineering on technical feasibility.

Challenges tackled cross-functionally:

  • Simplicity vs Depth: Admins wanted clarity, some stakeholders wanted granular data. I worked with Product to define MVP priorities and with Engineering to ensure deep-dive metrics were technically possible.
  • Data Visualization: Collaborated with Engineering to prototype interactive charts and trends, ensuring smooth performance and accessibility.



The Testing & Validation

Before the final UI design was to be created, we ran external testing with some power users:

  • Some users found some of the visualizations “too clinical.”
  • The term “burnout score” caused anxiety; Marketing helped reframe messaging to reduce negative perception.
  • Engagement trends over time were more valuable than raw single-point data.

Cross-functional impact:

  • Feedback informed Product on feature prioritization.
  • Marketing refined demo content to highlight actionable insights.
  • Engineering optimized UI interactions for smooth data updates.

The Final UI

We refined the dashboard into a clean, interactive experience that highlights:

  • Key stress drivers per team.
  • Engagement trends over time.
  • Actionable prompts for admins to proactively address morale issues.

All while being mobile-friendly for admins on-the-go - Which is a major upgrade from the previous desktop-only workflows.




The Outcome

The dashboard achieved user, business, and cross-functional goals:

  • Client retention: Enabled contract extensions by proving predictive capabilities.
  • Sales and Marketing impact: Became a central demo feature for prospects, contributing to an 86% increase in new deals.
  • Engagement: Boosted repeat usage as admins returned to track workforce trends.
  • Cross-functional alignment: Product, Marketing, and Engineering all leveraged the dashboard: Product refined the roadmap, Marketing used insights for messaging, and Engineering scaled the solution effectively.

What I Learned

  • Predictive tools need extra care in language and framing. It's not just about the data, but how it feels to the user.
  • Iterating with internal and external groups uncovers blind spots that teams might never see in isolation.
  • Cross-functional collaboration is critical: design alone isn't enough to launch a product that works technically, delights users, and drives business outcomes.
  • Balancing business priorities, user needs, and engineering feasibility requires constant communication, flexibility, and structured collaboration.