When does a sports dashboard need the court to be more than a background?

In this case, we were designing Deuce a tennis analytics platform that needed to make complex match data feel immediate and spatial, not just numerical.

The brief was clear: analysts and coaches don't just want stats. They want to feel like they're watching the match while reading the data.

So we made the Wimbledon court the literal center of the interface. Every panel orbits it match overview and surface performance on the left, live scoreboard and tournament state on the right, performance trend running the full width below. The court isn't decoration. It's the anchor that makes every number feel like it belongs to a real moment on a real surface.

72.34% win rate. 48 aces. 210 km/h best serve. Djokovic leading Alcaraz 6-4 on Center Court. Alcaraz vs Sinner tonight at 11 PM. Tactic heatmaps showing where points are won and lost.

What we noticed was that spatial context changed how the data felt. The same numbers in a standard table read as analysis. Wrapped around a court, they read as intelligence.

Do you think sports UI design is still underestimating how much context and spatial layout affect how data is understood?

Nice aesthetics, but composition feels bottom-heavy.

HR Analytics Dashboard | Power BI

Project Overview

I built an interactive HR Analytics Dashboard in Power BI to transform employee data into meaningful workforce insights and support HR-focused decision-making.

The project covered the complete dashboard development process — from understanding and preparing the dataset to creating KPIs, developing interactive visuals, designing a custom wireframe, and building the final dashboard.

Rather than directly copying the layout from the learning tutorial I followed, I first created my own wireframe and used it as the blueprint for the final dashboard.

Tools & Skills Used

Tools: Power BI | Power Query | DAX | Excel/CSV

Skills: Data Cleaning | Data Transformation | Data Analysis | Data Visualization | KPI Development | Dashboard Design | DAX Measures | Data Storytelling | Business Intelligence

What I Built

The dashboard provides an overview of employee demographics, workforce composition, employee attrition, salary levels, job roles, experience, and job satisfaction.

Key KPIs include:

Total Employees

Active Employees

Attrition Count

Attrition Rate

Average Age

Average Experience

The dashboard also analyzes:

Attrition by Department

Attrition by Gender

Attrition by Age Group

Attrition by Salary Slab

Attrition by Years of Experience

Job Role and Job Satisfaction

Employee distribution across departments

The final dashboard contains 1.42K employees, 1.19K active employees, 231 attritions, and a 16.3% attrition rate based on the cleaned dataset used for the project.

Data Preparation & Power Query

One of the first things I learned from this project was that importing a dataset into Power BI does not mean the data is automatically ready for analysis.

I used Power Query to inspect and prepare the dataset before building the dashboard.

I checked the data for empty values and removed unnecessary rows. I also used Group By and Count Rows on Employee ID to investigate whether employee records appeared more than once.

This was particularly useful because I initially did not understand why the tutorial was grouping Employee IDs.

I learned that grouping an ID and counting rows can be used as a duplicate-checking technique. Filtering the count so that it does not equal 1 helps identify IDs that appear more than once and therefore require further investigation.

This helped me understand the difference between simply following a Power Query step and understanding why that step is being performed.

DAX & KPI Development

I created measures to calculate the key HR metrics used throughout the dashboard.

One of the concepts that stood out to me was Active Employees.

The dataset contains an Attrition field indicating whether an employee left the organization.

Therefore:

Attrition = Yes → employee has left

Attrition = No → employee is considered active

To calculate Active Employees, I used the employee count together with an Attrition = No filter.

This helped me understand how a column that does not directly contain the metric I need can still be used to create a meaningful KPI.

I also worked with measures for Attrition Count, Attrition Rate, Average Age, and Average Experience.

Dashboard Design

Before developing the visuals, I created a custom wireframe in my preferred design tool.

I wanted the final dashboard to have its own visual identity rather than replicate the layout of the tutorial.

I chose a purple, white, and ash/gray color palette and structured the dashboard around six KPI cards followed by analytical sections for departments, attrition, salary, age, experience, and job satisfaction.

The wireframe helped me plan the visual hierarchy, spacing, and placement of each component before recreating the design in Power BI.

This was an important part of the project because it reinforced the value of planning the user experience before building the actual dashboard.

Challenges & What I Learned

One of the biggest learning moments was understanding Attrition and how it can be used to derive other HR metrics.

Initially, I questioned why the Employee Count needed to be filtered using the Attrition column when creating the Active Employee KPI.

Understanding that Attrition = No represents employees who have not left the organization made the calculation much clearer.

I also learned more about Power BI's sorting behavior.

For example, the salary slab visual was sorted by Attrition Count in descending order, rather than by the salary categories themselves. This meant the salary slab with the highest attrition appeared first.

Understanding this helped me realize that sorting is not simply a formatting decision — it can change what information a chart emphasizes.

Another important lesson was understanding the difference between data cleaning and data validation. Finding duplicate or empty records does not automatically mean they should be deleted. The analyst needs to understand why the records exist and whether removing them is appropriate.

Outcome

This project strengthened my practical skills in:

Power BI | Power Query | DAX | Data Cleaning | Data Analysis | Data Visualization | Dashboard Design | Business Intelligence

More importantly, it helped me move beyond simply building charts and start thinking about the reason behind each transformation, calculation, and visualization.

The project reinforced my approach of:

Understand → Clean → Validate → Analyze → Visualize → Communicate

I’m continuing to build projects that demonstrate not only my technical skills, but also my ability to turn raw data into clear and useful business insights.

Learning Credit

This project was inspired by a Power BI HR Analytics tutorial that I followed as a hands-on learning exercise, while designing my own wireframe and dashboard layout.