Challenge Summary
Welcome to the "Novus Organizational Resource Document Intake System Concepts Design Challenge". In this challenge, we need your creative thoughts to create a brand new, usable and more convenient UI for an existing and highly manual process to enter new products into the Novus online catalog. 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
Project Background
The following roles should be available in the system. At the moment NOVUS has 1 person for accessories, 2 for device planning and at least 2 for catalog management. All together the system will have around 30 users. Each user level should have the rights of all levels below it.
User Story
The Data Structure
Family level and SKU level. For instance, Novus has a breakdown between family and SKU level at the color distinction. So “iPhone 12 – 64gb” would be a family and “iPhone 12 – 64gb – Black” would be an SKU level product. The SKU level records are identified by the WPC ID.
Device and accessory connections
Suggested record statuses: New, Started, Missing Image, Image Processing, Launching (the record will remain in this state until the launch date), Launched, Relaunch (rare, but possible), Update
Screen Requirements
Please prepare the following screens to accommodate the above user flows and functionalities. However, don’t let yourself be restricted by the list below, you are welcome to show us your own ideas.
Dashboard (~5 screens)
Please create a layout for the dashboard that will contain the following sections/information.
Metrics: It is useful to have some kind of metrics on the main screen of a data-heavy application. Please come up with a useful way of showing some KPIs on the dashboard. You could think of metrics like status distributions, timelines, etc.
List of products and accessories: Although these two are differently handled, they are to be included in the same table with high-level data and statuses, grouped by product families (could be collapsible). The data should be searchable, sortable, filterable (let us see this feature). There will be about 30-150 records in the list (think about paging), and already published products will also be retained in the system.
Notification: Please provide a screen variation where you show the notifications “open” and show how the user can interact with the notifications (perform actions).
Bulk editing: The user should be able to edit the device details for multiple devices or accessory details for accessories at the same time as well. So provide the necessary UI elements for this function.
Device Details (~4 screens)
Most data will be imported from the MAP DB, and the user(s) will only have 5-6 manual decision points in the flow. This screen will allow the users to enter those data, and also to modify the imported ones if there is any mistake in them (only users with sufficient permissions can modify though). After modifying, entering data the user has to save the data to the working DB.
Besides the device data, we need you to create a section (probably on a separate tab of the same screen) for the task assignments along with a commenting function. Novus would like to record an audit trail of the modifications in the database as well (when, what and who edited the data). Novus is planning to shift to using Slack for company communications, so you might think about Slack integration as well for notifying people about an assigned task.
Currently, Novus does not have a graceful and easy way to connect devices and compatible accessories. We would like to create a surface (maybe another tab) where the user can set a number of properties based on what the accessories can be matched. A query in the background would populate the list of compatible accessories from the database.
Product Family Details (~2 screens)
In some cases product family data needs to be edited, so please provide a screen where this goal can be accomplished. It is also advisable to list the products under the product family concerned (however these will not change).
Please provide a function through which the user can bulk modify the related products (within the given family).
Resources
Target Audience
Product Managers and other product-related employees dealing with the product catalog of Novus.
Judging Criteria
Submission & Source Files
Final Deliverables
For submission you have to upload a zip file that contains the following 4 files:
Challenge Objectives
- Creating a web app
- 11 screens with interactions
- Desktop screens of 1366px width
Round 1
Please provide at least the following screens in your checkpoint submission.- 01 Dashboard - list of products and accessories
- 01.01 Family levels
- 01.02 SKU level showed
- 02 Device Details
- 02.01 Data entry
- 02.02 Assigning, Commenting
- 02.04 Accessory matching details
- 03 Product family details
- 03.01 Family details
Round 2
Please provide at least the following screens in your final submission.- 01 Dashboard - list of products and accessories
- 01.01 Family levels
- 01.02 SKU level showed
- 01.03 Filter function
- 01.04 Notifications
- 01.05 Bulk editing
- 02 Device Details
- 02.01 Data entry
- 02.02 Assigning, Commenting
- 02.03 Audit trail
- 02.04 Accessory matching details
- 03 Product family details
- 03.01 Family details
- 03.02 Bulk edit products (SKU level)
Project Background
- Our client Novus is a leading Telco provider that offers products (devices and accessories) online as well. To be able to maintain their online catalog they put together a system over the years based on many requirements, so they can make sure all the information that is being present in the catalog are available, correct and of good quality.
- Currently, the system is based on Excel templates and a lot of manual process. Most data comes from existing Sharepoint databases (MAP DB) and a couple of other pieces of information have to be filled in by different employees. To be able to assign tasks relating to the tables and to keep an audit trail they utilize JIRA at the moment. At the end of the process, the information has to be approved by a senior employee, so the content can go online. The data processed by the proposed system, the Novus ORDIS (Organizational Resource Document Intake System) will be saved to another working database, that feeds the online catalog. The data is not being saved back to the original source, the MAP database.
- The purpose of this project is to create an end to end web-based system, in which all these tasks can be handled.
The following roles should be available in the system. At the moment NOVUS has 1 person for accessories, 2 for device planning and at least 2 for catalog management. All together the system will have around 30 users. Each user level should have the rights of all levels below it.
- System Admin (out of scope): Manages user permissions and access.
- Super User (in scope): He is able to fully edit and delete data.
- Contributor (out of scope): Can add but not delete data from the system.
- Viewer (out of scope): Can only view data broken down to product families (they have restricted access to product families).
- Approver (in scope): Has a right to approve data by which he lets the products being launched in the online catalog.
User Story
- Let’s suppose Apple introduces the iPhone 12 and both them and other suppliers start to sell accessories for the same. The data of the devices (all variations of the new model) and the related accessories get entered into the MAP database (this is out of scope), so this is the source of information for our proposed ORDIS system.
- Jack starts his day and opens the Novus ORDIS app, as he knows that the new product has to be added to the online catalog. After a successful login, he immediately sees on the dashboard that there is a new product family with new devices and new accessories that he has to attend to, meaning typically 20 to 150 new records on the dashboard table.
- He clicks on one of the records, the iPhone 12 128GB red device, so as he opens the details page of the device. He starts to check the data already imported from the MAP database. He corrects the typos and any descriptions that are not of good quality. He also enters additional data that he knows about. Then he realizes that he doesn’t know something that has to be manually entered, so he assigns Madelene to continue filling in the data.
- Madelene fills in the missing data from other sources and assigns the next task to David, which would be image processing.
- David gets the product images from other sources and arranges image optimization for the online catalog. As a next step, he sends the images to a colleague who will deal with the image hosting.
- After this, the assignment goes to William, whose task is to fill in the accessories matching data, so the tool will be able to populate the compatible accessories.
- After finishing all the tasks, Albert gets a notification on Slack that the data is ready to be approved, so he logs into the system, and after checking that everything has been correctly filled in, he approves the product to be launched into the online catalog.
- Launching involves saving the data into the 3 downstream databases: MPM, EPC, and TBC.
The Data Structure
Family level and SKU level. For instance, Novus has a breakdown between family and SKU level at the color distinction. So “iPhone 12 – 64gb” would be a family and “iPhone 12 – 64gb – Black” would be an SKU level product. The SKU level records are identified by the WPC ID.
Device and accessory connections
Suggested record statuses: New, Started, Missing Image, Image Processing, Launching (the record will remain in this state until the launch date), Launched, Relaunch (rare, but possible), Update
Screen Requirements
Please prepare the following screens to accommodate the above user flows and functionalities. However, don’t let yourself be restricted by the list below, you are welcome to show us your own ideas.
Dashboard (~5 screens)
Please create a layout for the dashboard that will contain the following sections/information.
Metrics: It is useful to have some kind of metrics on the main screen of a data-heavy application. Please come up with a useful way of showing some KPIs on the dashboard. You could think of metrics like status distributions, timelines, etc.
List of products and accessories: Although these two are differently handled, they are to be included in the same table with high-level data and statuses, grouped by product families (could be collapsible). The data should be searchable, sortable, filterable (let us see this feature). There will be about 30-150 records in the list (think about paging), and already published products will also be retained in the system.
Notification: Please provide a screen variation where you show the notifications “open” and show how the user can interact with the notifications (perform actions).
Bulk editing: The user should be able to edit the device details for multiple devices or accessory details for accessories at the same time as well. So provide the necessary UI elements for this function.
Device Details (~4 screens)
Most data will be imported from the MAP DB, and the user(s) will only have 5-6 manual decision points in the flow. This screen will allow the users to enter those data, and also to modify the imported ones if there is any mistake in them (only users with sufficient permissions can modify though). After modifying, entering data the user has to save the data to the working DB.
Besides the device data, we need you to create a section (probably on a separate tab of the same screen) for the task assignments along with a commenting function. Novus would like to record an audit trail of the modifications in the database as well (when, what and who edited the data). Novus is planning to shift to using Slack for company communications, so you might think about Slack integration as well for notifying people about an assigned task.
Currently, Novus does not have a graceful and easy way to connect devices and compatible accessories. We would like to create a surface (maybe another tab) where the user can set a number of properties based on what the accessories can be matched. A query in the background would populate the list of compatible accessories from the database.
Product Family Details (~2 screens)
In some cases product family data needs to be edited, so please provide a screen where this goal can be accomplished. It is also advisable to list the products under the product family concerned (however these will not change).
Please provide a function through which the user can bulk modify the related products (within the given family).
Resources
- Novus branding
- Current xls template
- The flow illustrated
Target Audience
Product Managers and other product-related employees dealing with the product catalog of Novus.
Judging Criteria
- Your submission will be judged on the following criteria:
- Overall idea and execution of concepts.
- How well do the designs align with the objectives of the challenge.
- Simplicity in the overall design and user experience.
- Cleanliness of screen design and user flow.
- Out of the Box Thinking
Submission & Source Files
Final Deliverables
For submission you have to upload a zip file that contains the following 4 files:
Source.zip – All original source files.
All source files of all graphics created in vector format in either Adobe Illustrator or any similar software should be saved as editable files.
Submission.zip – PNG/JPG files
Submit JPG/PNG image files based on Challenge submission requirements stated above.
preview.png – Your preview image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72 dpi and place a screenshot of your submission within it.
declarations.txt – All your declarations and notes
This file must contain your notes if any, your Marvel prototype link, fonts used and stock images and icons used (if they were allowed).
All source files of all graphics created in vector format in either Adobe Illustrator or any similar software should be saved as editable files.
Submission.zip – PNG/JPG files
Submit JPG/PNG image files based on Challenge submission requirements stated above.
preview.png – Your preview image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72 dpi and place a screenshot of your submission within it.
declarations.txt – All your declarations and notes
This file must contain your notes if any, your Marvel prototype link, fonts used and stock images and icons used (if they were allowed).
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.