Challenge Summary
Welcome to "FAST! Price Detector Dashboard Design Concept Challenge". In this challenge, we want to explore and create the best possible UI/UX Dashboard Interface to clearly illustrate outliers/offenders for our Executive User that will help them to make decisions in order to get maximum profit for the company.
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!
THIS IS A FAST CHALLENGE AND ONLY 4 DAYS AVAILABLE FOR SUBMISSION PHASE. THIS CHALLENGE USING ONE ROUND FORMAT CHALLENGE (WITH ROLLING CHECKPOINT). PLEASE BE AWARE OF THE CHALLENGE TIMELINE AND MAKE SURE TO REGISTER ASAP!
Background Overview
Our company has a lot of products and those products sell in different packs. We are selling our products in different regions, from Europe, US, etc. In this challenge, we need a way of monitoring our product sales and have an ability to fix any issues immediately once the app detects any outliers/offenders.
The dashboard also needs to provide some interaction like providing a suggestion about what steps our Executive User should take in order to get the maximum profit.
This dashboard will be developed later using TableAU, but we are going to focus on the look and feel (design) for now!
Challenge Goal
Create a simple, modern, functional, and interesting Dashboard design for our Executive User that will be able to help them to decide the best price for our products in the future in order to get the maximum profit from sales
FAST Challenge Timeline and Rolling Checkpoint
- Submission Start: Friday, 03rd August 2018 21.00 PM EDT
- Rolling Checkpoint Start: Sunday, 05th August 2018 21.00 PM EDT
- Submission End: Tuesday, 07th August 2018 21.00 PM EDT
We are offering 3 Main Prizes + 5 Rolling Checkpoint
1) 1st Placement: $1300
2) 2nd Placement: $400
3) 3rd Placement: $150
Plus 5 placements for Rolling Checkpoint prizes @ $50 each!
Note: Important Rolling Checkpoint Details
- Client will provide feedback directly to all Rolling Checkpoint Submissions!
- We will answer questions and provide Rolling Feedback as fast as possible.
- You must watch the Forum for your feedback!
- All initial qualifying checkpoint submissions will win $50 (5 Placements)
Design Consideration
- We will develop this Dashboard later using tableau tool (Your design needs to consider this!)
- What should the priority features be?
- UI/UX Best Practice for the Dashboard!
- How quickly could you find information?
- The interface will be easy and intuitive to navigate
- Give importance to the overall layout and think on how a user would interact with the content on the page.
- Show all the screens and provide a user flow/click-path and navigation, so we can see how the interactions fit together in the application
Reference
Example dashboards designs that were published in tableau
- https://public.tableau.com/en-us/s/gallery
- https://www.tableau.com/learn/webinars/design-tricks-great-dashboards
Target Device
- Desktop view: 1366px and height as required.
- Make sure you create your graphics in 'shape' format, so when we resize graphics will still look sharp!
Branding Guidelines
- Font, Colors, Design Style is up to Designers
Dashboard Requirements
- Please check our sample data provided in "topCoderExample (with notes 1).csv"
- Here is the description of each field in the CSV document:
-- Column A - product: name of the product
-- Column B - subcategory: type of sub-product category
-- Column C - packSize: type of packaging size
-- Column D - geography: the retailer or region under consideration
-- Column E - P3M Sales: total unit sales in the past 3 months
-- Column F - P3M Price: average price in the past 3 months
-- Column G - optPrice: retailer's sales price that optimizes the profits
-- Column H - compare: how does the optimal price compare to P3M Price
-- Column I - potentialTotal: total potential profit to the company and the retailer
-- Column J - potentialforCompany: total potential profit for the company
-- Column K - suggestedCostToRetailer: suggested price to retailer
-- Column L - elasRange: points showing the beginning and end of regions where elasticities were estimated
-- Column M - elasticity: elasticity between the points in elasRange (number of points is always one more than the elasticity estimates)
- Note that the current data in that CSV doc are only a sample, in the real world the data can be many (it can be hundreds to thousands, please feel free to add more sample data in your design to simulate real case scenario)
- We need to create a Dashboard to visualize these data for the Executive User so they can evaluate, monitor, simulate the data in order to make a good decision that resulting maximum profit for the sales in the future.
- We need to clearly illustrate outliers/offenders (sales data that provide less profit for the company), where the Executive User is looking for prices that need to be fixed. Find by Geo, pack size, etc - who are the biggest "offenders". Instead of report, create exception base or impact analysis. What are the prices that need the most fixing to give biggest bang for the buck?
- By default, when Executive User is opening the Dashboard screen by default, the worst offenders/outliers should be visible, clear and pop right out. The Executive User then can evaluate/drilled down to see more data and then in addition to that, be able to get some recommendation from the app, something like "if you fix this, the impact could be growth by X%" and to do that graphically using chart/graph.
- Column A shows you the product, and Column B shows you what category it is (so if Column A was 'Toys', Column B would be 'car, doll, etc')
- Logically, Columns A, B, and C are linked together - together they define the product that was sold. Visually grouping them makes sense and users should be able to filter by them, by that group too maybe.
- Executive User should be able to filter the data based on Geographical sales area too (Column D)
- Any possibility to filter the data based on other data variables?
- Columns E and F are for the PAST 3 months and Column I and J are for the NEXT 3 months: these will be the base variables used by Executive User to make a decision so they can get more profit/money in the future
- Column G (Opt Price) is Optimum price - this is where they think they get the best price value. that's what they want to be paid for it
- Column H in informative only, have two values (Above or Below).
-- Above = the "optimum price" was over the actual per unit price that the Thing sold at in the last 3 months, so that is a negative thing
-- Below = the "optimum price" was under the actual per unit price that the Thing sold at in the last 3 months, so that is a positive thing
- Column I is the total amount of MORE money the company and retailers could make IF they use the optimum pricing.
- While Column J is the total amount of MORE money the company alone would make, using the sale.
- Column I is what the grocery stores would sell, and J is how much would come back to the company.
- Column J is most important, imagine they have more than 200 records data, the dashboard should show where J is most impactful of them all.
- Column K is not that important, it just a suggestion for the retailer on how much they should sell the product
- To visualize the Elasticities in Column L and M, please understand about "Price Elasticity" and why it matters for the Executive User from this article link: https://marketbusinessnews.com/financial-glossary/price-elasticity-definition-meaning/
- Columns K and L - can be improved, as stated above for "Price Elasticity", would be very good to be able to show better the elasticity by range then they are showing here
- There are 5 values in column L and 4 values in column M. The first value in M corresponds to the elasticity between the 1st and 2nd values in L, The second value in M to the elasticity between the 2nd and 3rd values in L. For Example: '1 M = 1,2 L', '2 M = 2,3 L', '3 M = 3,4 L'', '4 M = 4,5 L'
Important:
- Keep things consistent. This means all graphics styles should work together.
- All of the graphics should have a similar feel and general aesthetic appearance
- Focus on User Experience / how the user interacts within the dashboard
Marvel Prototype
- We need you to upload your screens to Marvel App.
- Please send your marvel app request to copilot in the forum (fajar.mln@gmail.com)
- 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 this link while you upload).
Target Audience
- Top Level Management - Executive User
Documentation
- Sample Data (topCoderExample (with notes 1).csv)
Judging Criteria
Your submission will be judged on the following criteria:
- Overall idea and execution of concepts
- How well does your design align with the objectives of the challenge
- Execution and thoughtfulness put into the solving the problem
- The overall design and user experience
- Cleanliness of screen design and user flow
- Ease of use
Submission & Source Files
Preview Image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
Submit JPG/PNG for your submission files.
Source Files
All source files of all graphics created in either Adobe Photoshop, Illustrator (might need to convert it to photoshop later), XD, or Sketch and saved as an editable layer
Final Fixes
As part of the final fixes phase, you will be asked to update the style tile to reflect any new elements that you have added to the design. You may also be asked to modify your graphics (sizes or colors) or modify overall colors. We may ask you to update your design or graphics based on checkpoint feedback.
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!
THIS IS A FAST CHALLENGE AND ONLY 4 DAYS AVAILABLE FOR SUBMISSION PHASE. THIS CHALLENGE USING ONE ROUND FORMAT CHALLENGE (WITH ROLLING CHECKPOINT). PLEASE BE AWARE OF THE CHALLENGE TIMELINE AND MAKE SURE TO REGISTER ASAP!
Background Overview
Our company has a lot of products and those products sell in different packs. We are selling our products in different regions, from Europe, US, etc. In this challenge, we need a way of monitoring our product sales and have an ability to fix any issues immediately once the app detects any outliers/offenders.
The dashboard also needs to provide some interaction like providing a suggestion about what steps our Executive User should take in order to get the maximum profit.
This dashboard will be developed later using TableAU, but we are going to focus on the look and feel (design) for now!
Challenge Goal
Create a simple, modern, functional, and interesting Dashboard design for our Executive User that will be able to help them to decide the best price for our products in the future in order to get the maximum profit from sales
FAST Challenge Timeline and Rolling Checkpoint
- Submission Start: Friday, 03rd August 2018 21.00 PM EDT
- Rolling Checkpoint Start: Sunday, 05th August 2018 21.00 PM EDT
- Submission End: Tuesday, 07th August 2018 21.00 PM EDT
We are offering 3 Main Prizes + 5 Rolling Checkpoint
1) 1st Placement: $1300
2) 2nd Placement: $400
3) 3rd Placement: $150
Plus 5 placements for Rolling Checkpoint prizes @ $50 each!
Note: Important Rolling Checkpoint Details
- Client will provide feedback directly to all Rolling Checkpoint Submissions!
- We will answer questions and provide Rolling Feedback as fast as possible.
- You must watch the Forum for your feedback!
- All initial qualifying checkpoint submissions will win $50 (5 Placements)
Design Consideration
- We will develop this Dashboard later using tableau tool (Your design needs to consider this!)
- What should the priority features be?
- UI/UX Best Practice for the Dashboard!
- How quickly could you find information?
- The interface will be easy and intuitive to navigate
- Give importance to the overall layout and think on how a user would interact with the content on the page.
- Show all the screens and provide a user flow/click-path and navigation, so we can see how the interactions fit together in the application
Reference
Example dashboards designs that were published in tableau
- https://public.tableau.com/en-us/s/gallery
- https://www.tableau.com/learn/webinars/design-tricks-great-dashboards
Target Device
- Desktop view: 1366px and height as required.
- Make sure you create your graphics in 'shape' format, so when we resize graphics will still look sharp!
Branding Guidelines
- Font, Colors, Design Style is up to Designers
Dashboard Requirements
- Please check our sample data provided in "topCoderExample (with notes 1).csv"
- Here is the description of each field in the CSV document:
-- Column A - product: name of the product
-- Column B - subcategory: type of sub-product category
-- Column C - packSize: type of packaging size
-- Column D - geography: the retailer or region under consideration
-- Column E - P3M Sales: total unit sales in the past 3 months
-- Column F - P3M Price: average price in the past 3 months
-- Column G - optPrice: retailer's sales price that optimizes the profits
-- Column H - compare: how does the optimal price compare to P3M Price
-- Column I - potentialTotal: total potential profit to the company and the retailer
-- Column J - potentialforCompany: total potential profit for the company
-- Column K - suggestedCostToRetailer: suggested price to retailer
-- Column L - elasRange: points showing the beginning and end of regions where elasticities were estimated
-- Column M - elasticity: elasticity between the points in elasRange (number of points is always one more than the elasticity estimates)
- Note that the current data in that CSV doc are only a sample, in the real world the data can be many (it can be hundreds to thousands, please feel free to add more sample data in your design to simulate real case scenario)
- We need to create a Dashboard to visualize these data for the Executive User so they can evaluate, monitor, simulate the data in order to make a good decision that resulting maximum profit for the sales in the future.
- We need to clearly illustrate outliers/offenders (sales data that provide less profit for the company), where the Executive User is looking for prices that need to be fixed. Find by Geo, pack size, etc - who are the biggest "offenders". Instead of report, create exception base or impact analysis. What are the prices that need the most fixing to give biggest bang for the buck?
- By default, when Executive User is opening the Dashboard screen by default, the worst offenders/outliers should be visible, clear and pop right out. The Executive User then can evaluate/drilled down to see more data and then in addition to that, be able to get some recommendation from the app, something like "if you fix this, the impact could be growth by X%" and to do that graphically using chart/graph.
- Column A shows you the product, and Column B shows you what category it is (so if Column A was 'Toys', Column B would be 'car, doll, etc')
- Logically, Columns A, B, and C are linked together - together they define the product that was sold. Visually grouping them makes sense and users should be able to filter by them, by that group too maybe.
- Executive User should be able to filter the data based on Geographical sales area too (Column D)
- Any possibility to filter the data based on other data variables?
- Columns E and F are for the PAST 3 months and Column I and J are for the NEXT 3 months: these will be the base variables used by Executive User to make a decision so they can get more profit/money in the future
- Column G (Opt Price) is Optimum price - this is where they think they get the best price value. that's what they want to be paid for it
- Column H in informative only, have two values (Above or Below).
-- Above = the "optimum price" was over the actual per unit price that the Thing sold at in the last 3 months, so that is a negative thing
-- Below = the "optimum price" was under the actual per unit price that the Thing sold at in the last 3 months, so that is a positive thing
- Column I is the total amount of MORE money the company and retailers could make IF they use the optimum pricing.
- While Column J is the total amount of MORE money the company alone would make, using the sale.
- Column I is what the grocery stores would sell, and J is how much would come back to the company.
- Column J is most important, imagine they have more than 200 records data, the dashboard should show where J is most impactful of them all.
- Column K is not that important, it just a suggestion for the retailer on how much they should sell the product
- To visualize the Elasticities in Column L and M, please understand about "Price Elasticity" and why it matters for the Executive User from this article link: https://marketbusinessnews.com/financial-glossary/price-elasticity-definition-meaning/
- Columns K and L - can be improved, as stated above for "Price Elasticity", would be very good to be able to show better the elasticity by range then they are showing here
- There are 5 values in column L and 4 values in column M. The first value in M corresponds to the elasticity between the 1st and 2nd values in L, The second value in M to the elasticity between the 2nd and 3rd values in L. For Example: '1 M = 1,2 L', '2 M = 2,3 L', '3 M = 3,4 L'', '4 M = 4,5 L'
Important:
- Keep things consistent. This means all graphics styles should work together.
- All of the graphics should have a similar feel and general aesthetic appearance
- Focus on User Experience / how the user interacts within the dashboard
Marvel Prototype
- We need you to upload your screens to Marvel App.
- Please send your marvel app request to copilot in the forum (fajar.mln@gmail.com)
- 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 this link while you upload).
Target Audience
- Top Level Management - Executive User
Documentation
- Sample Data (topCoderExample (with notes 1).csv)
Judging Criteria
Your submission will be judged on the following criteria:
- Overall idea and execution of concepts
- How well does your design align with the objectives of the challenge
- Execution and thoughtfulness put into the solving the problem
- The overall design and user experience
- Cleanliness of screen design and user flow
- Ease of use
Submission & Source Files
Preview Image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
Submit JPG/PNG for your submission files.
Source Files
All source files of all graphics created in either Adobe Photoshop, Illustrator (might need to convert it to photoshop later), XD, or Sketch and saved as an editable layer
Final Fixes
As part of the final fixes phase, you will be asked to update the style tile to reflect any new elements that you have added to the design. You may also be asked to modify your graphics (sizes or colors) or modify overall colors. We may ask you to update your design or graphics based on checkpoint feedback.
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.