Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Search instead for
Did you mean:
Dashboard example: Workforce Planning
Problem to Solve:
As an HR manager, I need to enter the Salary raise numbers for multiple regions that I'm responsible for.
As a domain best practice, my driver-based model helps me to enter raise guidelines, which will then change at the employee level.
Usability issue addressed: I have 10 regions, 8 departments in each, with a total of 10,000+ employees. I need to align my bottom up plan, to the down target I received earlier.
So, I need to quickly identify what region is above/behind target and address the variance. My driver-based raise modeling is fairly advanced and I need to see what the business rules are. I need to quickly see how it impacts the Employee level.
Call to Action:
Step 1: First, spot what region I need to address.
Step 2: Drill into the variances by department.
Steps 1 & 2 are analytics steps - "As an end-user, I focus first on where the biggest issues are." This is a good usability practice that helps users.
Step 3: Adjusting the guidelines (drivers)
There are not excessive instructions on how to build and use guidelines, which would've cluttered the dashboard. Instead, the "view guideline instruction" button was created. This button should open a dashboard dedicated to detailed instructions, or could be a link to a video that explains how guideline works, instead.
The chart above the grid will adjust as guidelines are edited. That is a good practice for impact analysis: no scrolling or clicking needed to view how the changes will impact the plan.
Step 4: Review a summary of the variance after changes are made. Putting steps 1-4 close to each other is a usable way of indicting to a user that he/she needs to iterate through these 4 steps to achieve their objective, which is to have every region and every department be within the top down target.
Step 5: Is a detailed impact analysis, which is placed directly below steps 3 and 4. This allows end-users to drill into the employee-level details and view the granular impact of the raise guidelines.
Notice the best practices in step 5:
The customer will likely ask to see 20 to 25 employee KPIs across all employees, and will be tempted to display these as one large grid. This can quickly lead to an unusable grid made of 1000's of rows (employees) across 25 columns.
Instead, we have narrowed the KPI list to only 10 that display without left-right scrolling.
Criteria to elect these 10: be able to have a chart that compares employees by these KPIs.
The remaining KPIs are displayed as an info grid, which only displays values for the selected employee. Things like region, zip codes, and dates are removed form the grid as they do not need to be compared side-by-side with other KPIs or between employees.