BONUS: 5‌ CHECKPOINTS AWARDED WORTH ‌$100‌ EACH

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to the Novus Partner Onboarding App Design Challenge.

Our leading telecom client, Novus offers several different apps to its customers. For these apps they use authentication from the same source. A dedicated team (the authentication team) at Novus is dealing with the implementation of authentication. They need a new onboarding tool that will educate their internal partners (partner team) about this process.

CHALLENGE OBJECTIVES
  • To create UI screens for a web application in desktop format.
  • To provide a seamless flow to complete user goals.
  • To explore the best way to convey the team’s message.

Round 1

Please provide the following screens for checkpoint along with your clickable Marvel prototype with hotspots.
  • 1. Landing screen 
  • 2. Additional screens (optional) if you decide to break up the layout
  • 4. FAQ article

Round 2

Please provide the following screens with checkpoint feedback incorporated for final review along with your clickable Marvel prototype with hotspots.
  • 1. Landing screen 
  • 2. Additional screens (optional) if you decide to break up the layout
  • 3. Process video opened state
  • 4. FAQ article
  • 5. Admin variation with links to upload/replace images/videos

APPLICATION OVERVIEW
 
  • The purpose of the web app is to help educate the different internal teams/partners on the process needed to engage the authentication team. 
  • The app should suggest which workflows are followed, and the timelines expected for the tasks carried out by the team. 
  • Steps to be followed by the internal teams/partners must be clearly stated and easily understood. 
  • The app will be created in SharePoint, so please research the capabilities of the tool. 
  • The client is already using SharePoint for many other applications, so the global top navigation will be the same throughout these applications (sample attached). 
 
AUDIENCE
 
Tech savvy Product Managers, Project Managers, and Engineers at Novus, whose purpose is to implement or modify authentication in their new or existing app.
 
PERSONA
 
Name: Michael
 
Occupation: Product Manager at Novus.
 
Goals:
  • Launch a new app to Novus customers.
  • Make the new app comply with both Novus and overall security standards.
 
Frustrations:
  • Doesn’t know the process to engage the team
  • Doesn’t know where to start implementing authentication.
  • Doesn’t have enough information about the capabilities / features supported by Authentication
  • Doesn’t know who to contact. 
  • Cannot plan ahead due to lack of information.
 
Wants:
  • Provide resources for his team to learn about the Authentication team 
    • Capabilities supported by the authentication product 
    • Process to engage the team 
    • Information about teams capacity, backlog and roadmap
  • A seamless experience.
  • Clear step by step goals.
  • Clear KPIs, metrics.
 
USER STORY
 
Michael is leading his team that creates a new app for Novus’ customers. As all Novus apps, this one needs authentication as well. 
 
Michael is planning the development of the app and would like to account for the authentication implementation as well. As this is the first time he has to add this feature to his product he opens the Novus Partner Onboarding app, where he can find all the necessary information about the process. 
 
Browsing through the app Michael is confident about the timelines and the steps he has to take to get his job done.
 
DESIGN GOALS & PRINCIPLES
 
  • Easy to use interface
  • The style should be suitable for an internal enterprise setting
  • Branding should be considered
 
EXPLORATION SCORE
 
Creativity: 4
1: barely new ideas
10: a utopic product with features not proven to be able to be fully implemented
 
Aesthetics: 8
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: 7
1: don’t care at all about the branding just functionality
10: without a properly branded product there is no success
 
GLOSSARY
 
  • OKR: Objectives and key results is a framework for defining and tracking objectives and their outcomes.
  • SLA: A service-level agreement is a commitment between a service provider and a client. Particular aspects of the service – quality, availability, responsibilities – are agreed between the service provider and the service user.
  • LOE: level of effort is a support-type project activity that must be done to support other work activities or the entire project effort. It usually consists of short amounts of work that must be repeated periodically. Examples of such an activity may be project budget accounting, customer liaison, or oiling machinery during manufacturing.
 
SCREENS/FEATURES
 
Using content from the provided sample wireframe screen and the roadmap diagrams, design a Web Application solution that is a framework the Authentication Team can use to meet the Partner User’s “Wants” (described above). Imagine how the Authentication Team could upload their information to help the Partner User move forward with gathering information, engaging the Authentication Team, and planning his development project. 
 
Please be sure your design includes content from the following screens/sections in some manner. Client is open to your suggestions about the structure of the app. It can be one screen, or multiple screens spreading through tabs if you think that would convey the content better. For sample content please refer to the asset files attached.
 
1. News and Announcements
The content of this section will be fed from already existing systems. It contains the following sub sections:
  • Approved projects in the respective quarter
  • Announcements
  • Key Statistics: for instance, the system has a great uptime, that can be shown to the user. Please visualize this.
  • SLAs would show the current expected duration of certain tasks the team can be engaged for. This will depend on the current workload of the team.
 
2. Secure ID road map / OKR
The road map will show the plans of the team for the coming quarters. This will be represented either in a table format that is editable and the team will change periodically or a static image (samples attached) that can be uploaded on a regular basis. We are fine with any one of the above options. Do not forget to check the SharePoint capabilities for this upload.
 
3. Quick Links
These links would take the user to already existing contents in the system, so you just need to show these links.
 
4. Processes
To explain the processes the Authentication Team uses, they can upload a video and a static image to show a workflow. This is an important section, as it will help the Partner User develop their own goals and expectations. These videos and images will contain the steps and flows the partner team will go through while cooperating with the Authentication Team. Do not overthink this section though. We need a framework that could be used for the different processes. Do not forget to check the SharePoint capabilities for this upload. The following processes will be explained in the app:
  • New CAPEX Initiatives - for new implementations
  • Operational Enhancements - for existing implementations
  • Strategic / R&D - for Research & Development
  • Pre-Planning / T-Shirt size LOE - for support activity
 
5. FAQ
A FAQ section will also help the user to understand how he can work together with the team. Please provide a state where we can see the answer to a question. There will be approximately 10-15 articles that might contain text and images to answer the questions. 
 
6. Navigation
The global navigation should be the same as what the client is already using (sample attached). Though you are free to rearrange the content outlined on the wireframe. 
 
BRANDING GUIDELINES
 
  • Follow Novus branding guidelines (attached)
 
DESIGN ASSETS
The below items have been attached.
 
  • Partner Onboarding Concept Wireframe - A single screen showing examples of the content required throughout this app. This file should be used as basic reference only, as the functionality and workflow in your solution will vary.
  • Global navigation sample
  • Roadmap samples
 
FINAL DELIVERABLES
 
  • All original source files
  • Create files in Adobe Photoshop, Adobe XD or Sketch.
  • Marvel Prototype - 
    • Upload your screens to Marvel App.
    • Send your marvel app request to pere.viktoria@gmail.com
    • Include your Marvel app URL as a text file in your final submission. Label it “MarvelApp URL”.

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.

How To Submit

  • New to Studio? ‌Learn how to compete here
  • Upload your submission in three parts (Learn more here). Your design should be finalized and should contain only a single design concept (do not include multiple designs in a single submission).
  • If your submission wins, your source files must be correct and “Final Fixes” (if applicable) must be completed before payment can be released.
  • You may submit as many times as you'd like during the submission phase, but only the number of files listed above in the Submission Limit that you rank the highest will be considered. You can change the order of your submissions at any time during the submission phase. If you make revisions to your design, please delete submissions you are replacing.

Winner Selection

Submissions are viewable to the client as they are entered into the challenge. Winners are selected by the client and are chosen solely at the client's discretion.

ELIGIBLE EVENTS:

2020 Topcoder(R) Open

Challenge links

Screening Scorecard

Submission format

Your Design Files:

  1. Look for instructions in this challenge regarding what files to provide.
  2. Place your submission files into a "Submission.zip" file.
  3. Place all of your source files into a "Source.zip" file.
  4. Declare your fonts, stock photos, and icons in a "Declaration.txt" file.
  5. Create a JPG preview file.
  6. Place the 4 files you just created into a single zip file. This will be what you upload.

Trouble formatting your submission or want to learn more? ‌Read the FAQ.

Fonts, Stock Photos, and Icons:

All fonts, stock photos, and icons within your design must be declared when you submit. DO NOT include any 3rd party files in your submission or source files. Read about the policy.

Screening:

All submissions are screened for eligibility before the challenge holder picks winners. Don't let your hard work go to waste. Learn more about how to  pass screening.

Challenge links

Questions? ‌Ask in the Challenge Discussion Forums.

Source files

  • Layered PSD files created in Adobe Photoshop or similar
  • AI files created in Adobe Illustrator or similar
  • Sketch
  • Adobe XD

You must include all source files with your submission.

Submission limit

Unlimited

ID: 30126014