Odyssey - Bank Ops App Design Challenge Part 1

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

Register
Submit a solution
The challenge is finished.

Challenge Summary


Welcome back to the Odyssey challenge series! In this challenge, we need your help to create a new look and feel for the Bank Ops portal (web app) that will be used by Odyssey employees to help their customers get the best service and create a strong relationship with them. 

Please read the challenge specification below and let’s discuss and post any doubts or questions in the challenge forum!

Round 1

Submit your initial designs for checkpoint feedback
02) Dashboard Screen
03) Search Screen
04) Customer Details Screen
06) Global Settings Screen
  • 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 declaration file
  • Make sure all pages have the correct flow. Use the proper file numbers, (1, 2, 3, etc.)

Round 2

Submit your final designs with all checkpoint feedback implemented 
01) Login Screen
02) Dashboard Screen
03) Search Screen
04) Customer Details Screen
05) Account Maintenance Screen
06) Global Settings Screen
  • 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 declaration file
  • 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


CHALLENGE OBJECTIVES

  • Create UI screens and UX interactions for Odyssey Bank Ops Portal based on the user story and branding guidelines
  • Create 6 Screens Feature + all required interactions for the Bank Ops App
 

BACKGROUND OVERVIEW

  • Our goal in this project is to create strong direct relationships with our customers. We want to provide everything - a blended bank, preferential banking for their family, and open to non-banking services via our digital app
  • This project currently split into two phases:
    • Phase 1, focused on the customer platform - the goal is to create two banking applications for the Odyssey customers, Odyssey Online Banking (Responsive Web App), and Odyssey Mobile Banking (Hybrid Mobile App in iOS and Android) - COMPLETE
    • Phase 2, focused on the employee platform - the goal is to create a Banking portal application for the Odyssey employees that will be able to help and assist their customers - ON PROGRESS
  • In this challenge, we will create the initial look and feel/design base for the Bank Ops application (following the design from phase 1) and create several user stories and features for the application  
 

TARGET AUDIENCE

  • Bank Employees (Bank Ops Agent and Bank Ops Manager)
  • Bank Ops Agent can be various type of position, from Customer Service, Operational, etc
 

PERSONA

  • Name: Reggie Stallone 
  • Occupation: Odyssey Bank Customer Service
  • Goals: Easily apply Bank Policy globally and Helping customers to solve any queries or problems as fast as possible 
  • Frustrations: The current system in place not easy enough to be used (a lot of dependency with 3rd party app, etc)
  • Wants: System that fully integrated and easy enough to be used
 

DESIGN CONSIDERATION

  • Consistency - MUST strictly follow our Branding Guidelines
  • Accessibility - MUST follow and pass WCAG accessibility standards. You are allowed to change some colors or layout if it can increase the accessibility. You can use the Inclusive design approach for this. Some example of inclusive design: Inclusive Design Principle or Microsoft Inclusive Design
  • Follow the naming convention in the approved design. For example, as much as possible, only capitalize the first letter of two words format such as “Personal information”. Two letters can be capitalized if they belong to abbreviations such as “Secure PIN” or “User ID”.
  • Modern, Simple, and Clean design
  • Reduce the number of interactions required from users as much as possible
  • Use color or great visual comparison to highlight a comparison of important information
  • Intuitive for the user; should never be left asking "what do I do next?"
  • Easy viewing for pages that may be over overcrowded with information
 

CHALLENGE FORUM

  • If you have any doubts or questions regarding challenge requirements, please ask in our challenge forum 


EXPLORATION SCORE

In terms of expectations, we would like to measure the concept against the following in the one to ten scales:
  • 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: 7
    • 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: 10
    • 1: don’t care at all about the branding just functionality
    • 10: without a properly branded product there is no success
 

SCREEN REQUIREMENTS

01) Login Screen
  • User Story “BO_US_1”
  • The Bank Ops agent should be able to click Bank Ops App for SSO so that they can successfully login to the Bank Ops portal.
  • Please read the complete detail requirements from the user story

02) Dashboard Screen
  • The Bank Ops agent will see this screen after successful login 
  • This screen should show all features for the Bank Ops agent according to their access
  • Show list of pending actions for the Bank Ops agent, log history, and any other relevant information for them

03) Search Screen
  • User Story “BO_US_3” and “BO_US_5” 
  • The Bank Ops agent should have the  ability to launch a customer search screen and search for any registered OLB/MB customer (searching customer/person)
  • The Bank Ops agent should be able to search any account based on defined search criteria (searching bank account)
  • Please read the complete detail requirements from the user story

04) Customer Details Screen
  • User Story “BO_US_4”, “BO_US_13”, “BO_US_18”, “BO_US_19”, and “BO_US_20”
  • The Bank Ops agent should have the ability to select a Customer record from customer search results so that I can view the selected customer's profile 
  • The Bank Ops agent will have the ability to view and De-activate a Mobile device linked to a customer's login credentials
  • The Bank Ops agent will have the ability to check the in-session activity (last login / log out / etc.) of the customer for the purpose of managing the session audit
  • The Bank Ops agent will have the ability to Disable a Customer's login credentials
  • The Bank Ops agent should be able to view the customer's access level and signature group 
  • Please read the complete detail requirements from the user story

05) Account Maintenance Screen
  • User Story “BO_US_6”, “BO_US_13”
  • The Bank Ops agent should be able to view the corresponding details of the searched account in the 'Account Maintenance' screen
  • The Bank Ops agent should be able to view the account access level and signature group 
  • Please read the complete detail requirements from the user story

06) Global Settings Screen
  • User Story “BO_US_7”, “BO_US_8”, “BO_US_9”, “BO_US_10”
  • The Bank Ops agent should be able to set the “limit per transaction type per day” at the bank-level so that the total of each transaction for the transaction type should not exceed the set limit for users in that segmentation.
  • The Bank Ops agent should be able to set the “daily user limit” for a customer per day at the bank-level so that sum of all daily transactions across all the accounts should not exceed the set limit for the customer.
  • The Bank Ops agent should be able to set the “daily account limit” for a customer so that sum of all daily transactions across all the accounts should not exceed the set limit set on that account
  • The Bank Ops should be able to set the “daily user account limit” for a customer so that sum of all daily transactions by a customer cannot exceed the limit set for the selected customer on that particular account.
  • Please read the complete detail requirements from the user story


DOCUMENTATION 

  • Please find the links in the challenge forum:
    • Odyssey - Online Banking design for Customer (Branding needs to be followed)
    • Odyssey - Bank Ops User Story
 

BRANDING GUIDELINES

  • Follow Odyssey Branding Guidelines 


TARGET DEVICES

  • Web App: 1440px Width with Height adjusting accordingly
 

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)
 

SUBMISSION AND SOURCE FILES

Submission File
  • Submit JPG/PNG image files based on Challenge submission requirements stated above
  • MarvelApp link for review and to provide feedback
  • The 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
 
Source Files
  • All source files of all graphics created in either Sketch (Primary Tool Recommendation), Adobe XD, or Figma and saved as an editable layer
 

FINAL FIXES

  • As part of the final fixes phase, you may be asked to modify your graphics (sizes or colors) or modify overall colors

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.

Challenge links

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

  • Sketch
  • Adobe XD
  • Figma

You must include all source files with your submission.

Submission limit

Unlimited

ID: 30170305