__STYLES__
For the Maven Sales Challenge, I played the role of a BI Developer for MavenTech, a company that specializes in selling computer hardware to large businesses. They've been using a new CRM system to track their sales opportunities but have no visibility of the data outside of the platform.
I created an interactive Power BI dashboard to enable sales managers to track their team's quarterly performance.
The dataset contained records exported from MavenTech's CRM from October 2016 to December 2017. It held details of opportunities with associated information such as product, account, and whether the sale was won or lost.
When creating an interactive dashboard, I always like to chat with the users to make sure I truly understand the intended purpose and the questions they seek to answer with the dashboard. In the absence of being able to chat with the sales managers, I made the following key assumptions which I used to guide my dashboard design.
As the dashboard is interactive, I also focused on making it user friendly for audiences who may not use Power BI every day. If the sales managers don't feel comfortable using the dashboard, there's no value to be gained. For this reason, I added a help page covering basic dashboard functionality and defining how the key metrics were calculated. This ensures sales managers canconfidently navigate the dashboard, and clearly interpret the information they are seeing and answer their key questions.
The dashboard sections are explained further below.
This is the main page of the report, containing the most critical information for sales managers. Users select their name from the sales manager filter, and this populates all pages of the dashboard with their team's information.
The key KPIs are shown clearly at the top of the page, with figures for the previous quarter and the average figure across all sales team for each metric provided below for additional context. This allows the sales manager to see their own figures and understand generally how they are tracking against the remaining teams and towards their own goals.
Users can click the question mark to view more information about the dashboard, and see a definition of how each metric has been calculated, to assist with interpreting the dashboard.
From the total sales card, users can click the arrow to dive deeper into the sales breakdown for the current quarter. This helps them to understand where they've had success and even see itemised sales data if required.
From the potential to close card, managers can also dive deeper into all opportunities labelled as engaging for their team. They can use this detail to prioritise actions such as following up offers to close before end of quarter, and CRM cleanups e.g., opportunities that have been open for too long and need to be marked as lost.
The current quarter performance page then steps deeper into the data, with the key KPIs listed against each individual sales agent, and conditional formatting highlighting in red which team members may be struggling in a particular area. This allows the sales manager to identify both areas they can focus on to improve the performance, and individuals who may require additional support. The product level breakdown also helps identify specific areas of improvement for the team as a whole and individuals.
While it's not the most important goal for the sales managers, they would also like to be able to see how their team is performing in comparison to the remaining sales team. The current quarter performance by team page allows them to do this, by ranking all sales teams across the key metrics, and highlighting the selected team so managers can easily see where they stand.
The final page of the dashboard allows sales managers to view their team's performance over the previous quarters to identify trends.