Challenge Summary
Welcome to "Dragonet Power BI DViz UI Design Challenge." In this challenge, we are looking to completely redesign 7 different Power BI report templates used by various departments within the North American zone of a global insurance company. These data visualization reports will be implemented using Microsoft Power BI.
Read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. Let us know if you have any questions in the challenge forum!
Challenge Objectives
The purpose of this project is to redesign online desktop resolution data visualization reports generated with Microsoft Power BI.
The objective of the project is to design modern and intuitive Power BI reports that allow easy understanding of a huge amount of data.
GLOSSARY
BSA: Business Systems Analyst
1) HR (Onboarding, Offboarding, Ad Hoc)
2) Customer Satisfaction
3) Financial
4) Incident Ticket Reporting
As part of your checkpoint submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt
Make sure all pages have the correct flow. Use the proper file numbers, (1, 2, 3, etc.)
1) HR (Onboarding, Offboarding, Ad Hoc)
2) Customer Satisfaction
3) Financial
4) Incident Ticket Reporting
5) Productivity
6) System Stability
7) Workload
As part of your Final submission, you must replace your checkpoint submission with the final submission into MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt
Make sure all pages have the correct flow. Use the proper file numbers, (1, 2, 3, etc.)
If you're not submitting in the Checkpoint/Round 1, you are not eligible to submit in the Final/Round 2.
BACKGROUND INFORMATION
Our client is a large global insurance company focused on these core business segments: Global Life and General Insurance. The BSAs team from North America generates different reports for areas such as Customer Satisfaction, Financial, Productivity, and Workload. These reports are generated and visualized through Microsoft Power BI.
AUDIENCE
- Company Stakeholders & Managers
USER STORY
John is a manager at Dragonet company. One of his main duties is to monitor the status of the Business System Analysts (BSAs). He needs to assess whether the BSAs are matching expected workloads and efficiency goals. To do this he frequently reviews online reports generated through Power BI and sees various charts and data reports for important areas: Customer Satisfaction, Financial, Productivity and more.
John is expected to use the reports to make sure that the workload is being split evenly among the BSA's. The reports should also allow him to identify problem groups or BSAs that need to be addressed. The reports provide real time data to keep John as up to date as possible on these systems.
Currently, the online reports lack a good user experience. They are visually busy, difficult to read, and do not convey the company brand aesthetic. Because of these limitations, John cannot fully understand the data that is available in the BSAs’ reports.
John would benefit from a visual update to more effectively deliver this valuable information. A new user-friendly design should make the data easier to understand. An updated look should fit with his company’s brand.
DESIGN CONSIDERATIONS
POWER BI REQUIREMENTS
REFERENCE
Example dashboards & reports design reference for your considerations:
- https://powerbi.microsoft.com/en-us/
- https://community.powerbi.com/t5/Data-Stories-Gallery/bd-p/DataStoriesGallery
- https://docs.microsoft.com/en-us/power-bi/service-dashboard-create
- https://id.pinterest.com/steffuhnee/power-bi-dashboards/?lp=true
EXPLORATION SCORE
In terms of expectations, we would like to measure the concept against the following in the one to ten scales (ask the client to rate each of the parameters):
Creativity: 8
1: barely new ideas
10: a utopic product with features not proven to be able to be fully implemented
Aesthetics: 10
1: low-fidelity design, wireframe or plain sketch
10: top-notch finished looking visual design
Exploration: 8
1: strictly follow an existing reference or production guideline
10: open to alternative workflows/features not listed here that would help the overall application
Branding: 5
1: don’t care at all about the branding just functionality
10: without a properly branded product there is no success
REQUIRED FEATURES:
SCREEN REQUIREMENTS
GLOBAL - For ALL Reports:
This screen consists of 3 main sections. We are looking for the best way for our user to access and navigate between them. It could be all on a single screen view or separated. The solution is up to your own design ideas.
Onboarding – This section displays anything related to employees being onboarded. This includes: request status, request count for the current month, days open, and if they met success requirements. The request count is split between contingent workers and employees.
Offboarding – This section is the equivalent of Onboarding, but instead tracks employees being terminated. It should display: request status, days open, request count for the current month, and if we are meeting success requirements.
Ad Hoc – This section tracks the requests being submitted by users for software/hardware requests. It should display: status of request, the count for the current month, days open split between Hardware/Software and Other, and success stats for the current month. It also shows the breakdown of the requests from the previous month.
Link to current screen for reference.
2) Customer Satisfaction
This view displays tracking of how long tickets stay in the queue for the different resolver groups. A color cue should indicate if it is within acceptable levels. The user should see a breakdown of ticket status into assigned, on hold, and in progress. Show a percentage breakdown of total tickets by group that can be filtered to show days in queue (upper right of sample screen), as well as time queue by hour by group (bottom of sample screen).
Link to current screen for reference.
3) Financial
This view displays reports of Financial Success metrics in various formats. Our user should see dollar amounts of profit, Capex, ROI, etc. This screen should also display services offered per month and sales split by segment.
Link to current screen for reference.
4) Incident Ticket Reporting
This view should track data about Incident Tickets. Show the number of days for tickets to be escalated, how many are closed or open, and the longest tickets recorded. Also allow a more detailed breakdown on these incidents (bottom of sample screen).
Link to current screen for reference.
5) Productivity
This view displays information showing how often tickets are being bounced around to different resolver groups. Show the total amounts of closed, resolved, assigned, on hold, and in progress tickets. Also display a split between ticket status and ticket age.
Link to current screen for reference.
6) System Stability
This view should display the number of Severity Level Incidents, grouped by year and support group. Severity incidents levels range from 1 to 5, with 1 being most severe.
Link to current screen for reference.
7) Workload
This view should display information about Workload for various groups. Show the split of high priority incidents for individual users, and by assignment groups. The user should be able to filter to: number of ticket bounces, date range, or ticket age. Show the average number of bounces per ticket and average days open (upper left of sample screen). Also display the Ticket Age (individual tickets with their age) and number of times they were bounced.
Link to current screen for reference.
BRANDING GUIDELINES
MARVEL PROTOTYPE
TARGET DEVICE
Desktop: 1366 x 768px.
SUBMISSION AND SOURCE FILES
Submission File
Submit all JPG/PNG image files based on Challenge submission requirements stated above
Source File
All source files of all graphics created in either Power Bi (.pbix), Adobe Photoshop, XD, Sketch, or Figma and saved as an editable layer
Declaration File
FINAL FIXES
As part of the final fixes phase, you may be asked to modify content or user click paths
Read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. Let us know if you have any questions in the challenge forum!
Challenge Objectives
The purpose of this project is to redesign online desktop resolution data visualization reports generated with Microsoft Power BI.
The objective of the project is to design modern and intuitive Power BI reports that allow easy understanding of a huge amount of data.
GLOSSARY
BSA: Business Systems Analyst
Round 1
Submit your initial designs for the checkpoint review. Feel free to add any screens which are necessary to explain your concept1) HR (Onboarding, Offboarding, Ad Hoc)
2) Customer Satisfaction
3) Financial
4) Incident Ticket Reporting
As part of your checkpoint submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt
Make sure all pages have the correct flow. Use the proper file numbers, (1, 2, 3, etc.)
Round 2
Submit your final designs plus checkpoint feedback implemented for the final round. Feel free to add any screens which are necessary to explain your concept:1) HR (Onboarding, Offboarding, Ad Hoc)
2) Customer Satisfaction
3) Financial
4) Incident Ticket Reporting
5) Productivity
6) System Stability
7) Workload
As part of your Final submission, you must replace your checkpoint submission with the final submission into MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt
Make sure all pages have the correct flow. Use the proper file numbers, (1, 2, 3, etc.)
If you're not submitting in the Checkpoint/Round 1, you are not eligible to submit in the Final/Round 2.
BACKGROUND INFORMATION
Our client is a large global insurance company focused on these core business segments: Global Life and General Insurance. The BSAs team from North America generates different reports for areas such as Customer Satisfaction, Financial, Productivity, and Workload. These reports are generated and visualized through Microsoft Power BI.
AUDIENCE
- Company Stakeholders & Managers
USER STORY
John is a manager at Dragonet company. One of his main duties is to monitor the status of the Business System Analysts (BSAs). He needs to assess whether the BSAs are matching expected workloads and efficiency goals. To do this he frequently reviews online reports generated through Power BI and sees various charts and data reports for important areas: Customer Satisfaction, Financial, Productivity and more.
John is expected to use the reports to make sure that the workload is being split evenly among the BSA's. The reports should also allow him to identify problem groups or BSAs that need to be addressed. The reports provide real time data to keep John as up to date as possible on these systems.
Currently, the online reports lack a good user experience. They are visually busy, difficult to read, and do not convey the company brand aesthetic. Because of these limitations, John cannot fully understand the data that is available in the BSAs’ reports.
John would benefit from a visual update to more effectively deliver this valuable information. A new user-friendly design should make the data easier to understand. An updated look should fit with his company’s brand.
DESIGN CONSIDERATIONS
- We are looking for a layout that is: simple, easy-to-use, informative, modern and clean.
- Simplify the information on your dashboard reports. Make it compelling by using interactive visualizations, and allow users to walk through or drill into the different insights.
- Highlight comparison with color, visual elements, and drill-down charts.
- IMPORTANT: You must use the colors provided in the branding section of this challenge.
- Desktop layouts at: 1366 x 768px (Desktop only. Power BI is responsive by nature so just need to design / build once)
- We have provided reference images for the graphics and the data the screens should contain. DO NOT COPY SAMPLE SCREENS. Please use them as a reference only. We are looking for improved chart/graphics types wherever possible to make the experience cleaner and more meaningful.
- Principles of good UX design are critical success factors for this challenge.
- For example: minimize user clicks, make the experience more intuitive, ease access to desired selection criteria, store user selections for multiple reports and performance, user friendly color and font combinations, etc.
POWER BI REQUIREMENTS
- Follow Power BI Design Best Practices. Also take a look at the Design Tips.
- Please do some research on the Power BI software and get familiar with its purpose, limitations, and what's possible. Have in mind that if your design solution is not Power BI compatible, it will not be selected. So consider this while designing your solution.
- You can reference this video about Power BI.
REFERENCE
Example dashboards & reports design reference for your considerations:
- https://powerbi.microsoft.com/en-us/
- https://community.powerbi.com/t5/Data-Stories-Gallery/bd-p/DataStoriesGallery
- https://docs.microsoft.com/en-us/power-bi/service-dashboard-create
- https://id.pinterest.com/steffuhnee/power-bi-dashboards/?lp=true
EXPLORATION SCORE
In terms of expectations, we would like to measure the concept against the following in the one to ten scales (ask the client to rate each of the parameters):
Creativity: 8
1: barely new ideas
10: a utopic product with features not proven to be able to be fully implemented
Aesthetics: 10
1: low-fidelity design, wireframe or plain sketch
10: top-notch finished looking visual design
Exploration: 8
1: strictly follow an existing reference or production guideline
10: open to alternative workflows/features not listed here that would help the overall application
Branding: 5
1: don’t care at all about the branding just functionality
10: without a properly branded product there is no success
REQUIRED FEATURES:
- Global items plus specific requirements for each screen view (Reports), listed below.
- Provide an intuitive experience for end customers
- Create developer friendly and easy to build designs
- Must translate to Microsoft Power BI reports.
- Allow a variety of charts and data visualization. Think on filtering, sorting and exporting the data.
SCREEN REQUIREMENTS
GLOBAL - For ALL Reports:
- Include a dropdown that allows the user to select an active BSA (Business Systems Analyst). This will filter the view to requests being fulfilled by that BSA. Should be “All BSAs” by default.
- Show the rolling average of requests for the past 12 months.
This screen consists of 3 main sections. We are looking for the best way for our user to access and navigate between them. It could be all on a single screen view or separated. The solution is up to your own design ideas.
Onboarding – This section displays anything related to employees being onboarded. This includes: request status, request count for the current month, days open, and if they met success requirements. The request count is split between contingent workers and employees.
Offboarding – This section is the equivalent of Onboarding, but instead tracks employees being terminated. It should display: request status, days open, request count for the current month, and if we are meeting success requirements.
Ad Hoc – This section tracks the requests being submitted by users for software/hardware requests. It should display: status of request, the count for the current month, days open split between Hardware/Software and Other, and success stats for the current month. It also shows the breakdown of the requests from the previous month.
Link to current screen for reference.
2) Customer Satisfaction
This view displays tracking of how long tickets stay in the queue for the different resolver groups. A color cue should indicate if it is within acceptable levels. The user should see a breakdown of ticket status into assigned, on hold, and in progress. Show a percentage breakdown of total tickets by group that can be filtered to show days in queue (upper right of sample screen), as well as time queue by hour by group (bottom of sample screen).
Link to current screen for reference.
3) Financial
This view displays reports of Financial Success metrics in various formats. Our user should see dollar amounts of profit, Capex, ROI, etc. This screen should also display services offered per month and sales split by segment.
Link to current screen for reference.
4) Incident Ticket Reporting
This view should track data about Incident Tickets. Show the number of days for tickets to be escalated, how many are closed or open, and the longest tickets recorded. Also allow a more detailed breakdown on these incidents (bottom of sample screen).
Link to current screen for reference.
5) Productivity
This view displays information showing how often tickets are being bounced around to different resolver groups. Show the total amounts of closed, resolved, assigned, on hold, and in progress tickets. Also display a split between ticket status and ticket age.
Link to current screen for reference.
6) System Stability
This view should display the number of Severity Level Incidents, grouped by year and support group. Severity incidents levels range from 1 to 5, with 1 being most severe.
Link to current screen for reference.
7) Workload
This view should display information about Workload for various groups. Show the split of high priority incidents for individual users, and by assignment groups. The user should be able to filter to: number of ticket bounces, date range, or ticket age. Show the average number of bounces per ticket and average days open (upper left of sample screen). Also display the Ticket Age (individual tickets with their age) and number of times they were bounced.
Link to current screen for reference.
BRANDING GUIDELINES
- Please use the branding guidelines provided in the forum.
- Use the brand palette only. DO NOT ADD colors beyond the ones shown in the branding material.
- Also, we are providing some reference sketches so you can have a better understanding of the requested pages.
MARVEL PROTOTYPE
- We need you to upload your screens to Marvel App
- Please request for marvel app in the challenge forum
- You MUST include your Marvel app URL (in your marvel app prototype, click on share and then copy the link & share it with your notes/comment on this link while you upload)
TARGET DEVICE
Desktop: 1366 x 768px.
SUBMISSION AND SOURCE FILES
Submission File
Submit all JPG/PNG image files based on Challenge submission requirements stated above
Source File
All source files of all graphics created in either Power Bi (.pbix), Adobe Photoshop, XD, Sketch, or Figma and saved as an editable layer
Declaration File
- Declaration files document contains the following information:
- Stock Photos Name and Links from allowed sources
- Stock Art/Icons Name and Links from allowed sources
- Fonts Name and Links source from allowed sources
- MarvelApp share link for review
FINAL FIXES
As part of the final fixes phase, you may be asked to modify content or user click paths
Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.