Google Retail Custom Dashboards Design Challenge

Welcome to the Google Retail Custom Dashboards Design Challenge. In this challenge, we are looking to create six desktop dashboard screen designs. We would like you to define the initial design direction for these dashboards with a focus on usability, accessibility, and a user-centric approach.

Good luck!  We are looking forward to your designs!

Round 1

The following screens (See User Interface Guidelines)

1) Executive Summary Dashboard
2) Merchandising Dashboard

- Readme.jpg: Provide notes about your submission
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03)

 

Round 2

All screens (See User Interface Guidelines)

1) Executive Summary Dashboard
2) Merchandising Dashboard
3) Sales Dashboard
4) Training Dashboard
5) Cases Dashboard
6) Inventory Dashboard

- Readme.jpg: Provide notes about your submission
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03)

The purpose of this challenge is to design six custom dashboards that can be integrated with the Visualforce interface framework (Salesforce). The dashboards will help key Google personal understand how well their products are being represented in various stores.

User Interface Guidelines:
- All user interface elements should adhere to the Google Material Design guidelines.
- - - Focus on consistent design patterns, bold graphic and typography, and a clear visual hierarchy.
- - - When using motion or animation, pay close attention to choreography and authentic motion.
- - - Make liberal use of white space to create contrast and define interface and data elements.
- - - The color palette is primary and accent colors; bold hues juxtaposed with muted environments and bright highlights that take their cues from contemporary architecture, road signs, pavement marking tape, and athletic courts.
- Keep interface elements consistent. All interface elements should reflect predictable placement, style, and behavior across all environments. This is especially important when styling actionable items.
- Priority should be given to recognition rather than forcing users to recall paths to tasks. Using the Material Design Guidelines will help ensure recognition.
- For experienced users or common actions, include accelerators and shortcuts within the app to speed task completion. Ensure that these elements do not interfere with primary navigation/actions and are styled distinctly and differently.
- Automatically populate call forms when possible.

Required Design Sizes:
- In terms of viewport size, use a desktop view (MacBook Pro Layout) - 1280 x 800px

Required Screens:
We need the following screens to be created for this application..

1) Executive Summary Dashboard:
- Header

Navigation
- Executive Summary (Currently selected)
- Merchandising
- Sales
- Training
- Cases
- Inventory

Filter Settings    
- Country
- Country Region
- Product
- Retailer

Metrics Display
- Overall Compliance (EMEA)
- Overall compliance % score (entry)
- [Up/down arrow] compliance % vs last week (week-on-week)
- [Up/down arrow] compliance % vs 6 week average

* Overall Hardware Sales (EMEA)
*** Sell-out
- - - % of sales (sell-out) quarter-to-date vs target
- - - Number of sales (sell-out) quarter-to-date
- - - [Up/down arrow*] sell-out as % vs last week (week-on-week)
- - - [Up/down arrow*] sell-out as % vs 6 week average

*** Sell-in
- - - % of sales (sell-in) quarter-to-date vs target
- - - Number of sales (sell-in) quarter to date
- - - [Up/down arrow*] sell-in as % vs last week (week-on-week)
- - - [Up/down arrow*] sell-in as % vs 6 week average

* Overall Training (EMEA)
*** Staff
- - - Number of field staff trained (total quarter-to-date)
- - - % of field staff trained (vs target total quarter-to-date)
- - - Number of field staff trained (this week only)
- - - [Up/down arrow*] Number of field staff trained vs last week (week-on-week)

*** Modules
- - - Number of modules trained on (this week only)
- - - % of modules trained on vs target (quarter-to-date)
- - - [Up/down arrow*] Number of modules trained on vs 6 week average

*** Hours
- - - Number of hours spent on training (total quarter-to-date)
- - - % of hours spent on training vs target (quarter-to-date)        

2) Merchandising Dashboard:
- Header

Navigation
- Executive Summary
- Merchandising (Currently selected)
- Sales
- Training
- Cases
- Inventory

Filter Settings
- Country
- Country Region
- Product
- Retailer

Metrics Display

* Overall Compliance
- - - Overall compliance % score (entry) for this week
- - - [Up/down arrow*] compliance % vs last week (week-on-week)
- - - [Up/down arrow*] compliance % vs 6 week average

* Location
- - - % score on location for this week
- - - [Up/down arrow*] location % vs last week (week-on-week)
- - - [Up/down arrow*] location % vs 6 week average
Note: Ability to deep-dive into Location score to view the two components

* Fixture
- - - % score on fixtures for this week
- - - [Up/down arrow*] fixture % vs last week (week-on-week)
- - - [Up/down arrow*] fixture % vs 6 week average
Note: Ability to deep-dive into Fixture score to view the three components

* Demo
- - - % score on demo for this week
- - - [Up/down arrow*] demo % vs last week (week-on-week)
- - - [Up/down arrow*] demo % vs 6 week average
Note: Ability to deep-dive into Demo score to view the two components

* Messaging
- - - % score on messaging for this week
- - - [Up/down arrow*] demo % vs last week (week-on-week)
- - - [Up/down arrow*] demo % vs 6 week average
Note: Ability to deep-dive into Demo score to view the four components

* Product Availability
- - - % score on product availability for this week
- - - [Up/down arrow*] product availability % vs last week (week-on-week)
- - - [Up/down arrow*] product availability % vs 6 week average
Note: Ability to deep-dive into Product Availability score to view the two components

3) Sales Dashboard:
- Header

Navigation
- Executive Summary
- Merchandising
- Sales (Currently selected)
- Training
- Cases
- Inventory

Filter Settings
- Country
- Country Region
- Product
- Retailer

Metrics Display
* Overall Hardware Sales (EMEA)
- - -  % of sales (sell-out) quarter-to-date vs target
- - -  Number of sales (sell-out) quarter-to-date
- - -  [Up/down arrow*] sell-out as % vs last week (week-on-week)
- - -  [Up/down arrow*] sell-out as % vs 5 week average    

* Sell-In
- - - % of sales (sell-in) quarter-to-date vs target
- - - Number of sales (sell-in) quarter to date
- - - [Up/down arrow*] sell-in as % vs last week (week-on-week)
- - - [Up/down arrow*] sell-in as % vs 5 week average

* Forecast (Sell-Out)
- - - Number of units in the pipeline (quarter-to-date)
- - - [Up/down arrow*] % change in forecasted units in pipeline (quarter-to-date)
- - - Number of units forecasted to close by end-of-quarter
- - - [Up/down arrow] Change in number of units to close by end-of-quarter

* Forecast (Sell-In)
- - - Number of units in the pipeline (quarter-to-date)
- - - [Up/down arrow*] % change in forecasted units in pipeline (quarter-to-date)
- - - Number of units forecasted to be sold to retailers by end-of-quarter
- - - [Up/down arrow*] Change in number of units forecasted to be sold to retailers by end-of-quarter.

4) Training Dashboard:
- Header

Navigation
- Executive Summary
- Merchandising
- Sales
- Training (Currently selected)
- Cases
- Inventory

Filter Settings
- Country
- Country Region
- Product
- Retailer

Metrics Display
* Overall Training (EMEA)
- - - Number of field staff trained (total quarter-to-date)
- - - % of field staff trained (vs target total quarter-to-date)
- - - Number of field staff trained (this week only)
- - - [Up/down arrow*] Number of field staff trained vs last week (week-on-week)

* Modules
- - - Number of modules trained on (this week only)
- - - % of modules trained on vs target (quarter-to-date)
- - - [Up/down arrow*] Number of modules trained on vs 6 week average

* Hours
- - - Number of hours spent on training (total quarter-to-date)
- - - % of hours spent on training vs target (quarter-to-date)

5) Cases Dashboard:
- Header

Navigation
- Executive Summary
- Merchandising
- Sales
- Training
- Cases (Currently selected)
- Inventory

Filter Settings    
- Country
- Country Region
- Product
- Retailer

Metrics Display
* Open Cases
List of cases still open with following items in headline:
- - - Reports (who reported the case)
- - - Owner (who is repsonsible to remediate the case)
- - - Type (Fixture, Maintenance, ...)
- - - Priority (High, Medium, Low)
- - - Store (the store where the case originates)
- - - Title description
- - - Close button (to close the case)
Note: Each line can be expanded to show the full description and pictures

* Closed cases
List of cases closed with the following items in the headline
- - - Report (who reported the case)
- - - Owner (who was reponsible for remeidating the case)
- - - Type (Fixture, maintence, ...)
- - - Priority (High, Medium, Low)
- - - Store (the store where the case originated)
- - - Title description
- - - Re-open button (to re-open the case)
Note: Each line can be expanded to show the full desciption and pictures

* New case 
To create a case right from the dashboard with the following field to be filled in:
- - - Owner (who is repsonisble to remdiate the case)
- - - Type (Fexture, Maintenance, ...)
- - - Priority (High, Medium, Low)
- - - Store (the store where the case originates)
- - - Title description
- - - Full description
- - - Picture (able to upload/add pictures)
Note: The person creating the new case would become the reporter.

6) Inventory Dashboard:
- Header

Navigation
- Executive Summary
- Merchandising
- Sales
- Training
- Cases
- Inventory (Currently selected)

Filter Settings    
- Country
- Country Region
- Product
- Retailer

Metrics Display
* OSA
- - - On shelves availability in %
- - - The % of store with a level of stock above a certain minimum threshold (in units)

* Wos
- - - Weeks of stock at retailer and product levels (e.g. Best Buy has 6.7 WoS on Chromecast Audio).
- - - Weeks of stock are calculated against forecast and retailer stock level.
- - - Weeks of stock have no sense as aggregates of retailers (e.g. Target + Best Buy) or products (e.g. Nexus + Chromecast). It can only be displayed at retailer + product level.

Note: WoS should be written as a number (e.g. 6.7 WoS) with the total inventory figure in units written in brackets next to it (e.g. 9800 units)
- E.g. Best Buy / Chromecast / 4.7 WoS (43560 units)
- The WoS figure should be color coded to show whether is above a below the requested level (5 grade code would be better)

* Intake plan
- - - Week per week calendar displaying the units each retailer show take of each product to sustain a cetain leve of Wos.
- - - There should be 1 chart per retailer with 2 lines per product:
- - - Actual: volume (in units) the retailer plan on ordering week/week (manual imput)
- - - Ideal: weekly volume (in units) recommanded to maintain a cretin WoS level (automated: calulated against the last week sell-out figures and inventory figures)
- - - The Acutal shoul be color coded to show wheather it is aligned with ideal (if ideal > actual >> bad).  2 grade color code is OK.

Overall Note: 
- Up/down arrow is an arrow that indicates if the trending direction (3% up or 6% down)

Target Audience:
- The dashboard views will help key Google personal understand how well their products are being represented in various stores.

Judging Criteria:
We will be judging on:
- How well your design aligns with the objectives of the challenge.
- Adherence to the Material Design Guidelines.
- Usability and user-centric approach.
- Consistency of elements across dashboards.
- Clear, simple, visual hierarchy.
- Ability of your design to support user tasks in a straightforward, pleasant, efficient manner.
- Overall user interface design and layout.

Submissions and 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 original source files of the submitted design. Files should be created in Adobe Photoshop and saved as layered PSD file, or Adobe Illustrator as a layered AI file.

Final Fixes
As part of the final fixes phase you may be asked to modify your graphic elements (sizes or colors) or modify portions of the color palette. We may ask you to update your design or graphic elements based on checkpoint feedback. See more information about Final Fixes.