Challenge Summary
Welcome to “Insurance Solution - Desktop Web Application UI Design Fast Challenge”. In this challenge we are looking for your creativity to conceptualize and design the UI/UX for an insurance solution to showcase the capabilities of underlying customer data management solution. You will be focused on creating how this application should look and feel. We are providing the color palette to work, please see branding section for reference.
This will be a very fast challenge with a tight deadline, that’s why we are trying to provide the best and most complete specifications; to make the problem easy to understand.
Let us know in forum if you have questions!
Workflow 1: Customer Onboarding
1) Pension Products Option
2) Customer Details
3) FATCA Customer Details
Workflow 2: Customer Data Query
8) Customer Service Executive Dashboard with Query/Filter
9) Query Results Screen
Workflow 3: Customer Persona
10) Customer Dashboard
11) Claims Section as Claimant
- Important: As part of your checkpoint submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs.
- Please ask in the Forum for a MarvelApp prototype link. You will receive 1 MarvelApp prototype for Desktop.
- Make sure to include a URL/Link to your design within your "notes.txt", Important!
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03)
Workflow 1: Customer Onboarding
1) Pension Products Option
2) Customer Details
3) FATCA Customer Details
4) Data Collected Edit & Save
5) Payment Page
6) Pension Product Contract
7) Customized Dashboard
Workflow 2: Customer Data Query
8) Customer Service Executive Dashboard with Query/Filter
9) Query Results Screen
Workflow 3: Customer Persona
10) Customer Dashboard
11) Claims Section as Claimant
12) Claims Page as Witness
13) Claim Details
- Important: As part of your final submission, you must update your submission to MarvelApp.
- Use the same MarvelApp prototype you received in checkpoint.
- Make sure to include a URL/Link to your design within your "notes.txt", Important!
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03)
Background Information
The objective for this challenge is to conceptualize the initial UI/UX of an insurance solution to showcase the capabilities of underlying customer data management solution through workflows that involve (a) customer onboarding (b) customer database querying and (c) claims processing workflow.
This requires a need to develop solutions around 3 scenarios which are explained below:
Customer Onboarding: The objective of customer onboarding is to show that based on (a) the product selected by the user, (b) domicile of the user where he intends to enter into business, and (c) the legal entity representing the bank in that region; the system can trigger an appropriate customer onboarding workflow. In this case a workflow that include FATCA related data collection processes
Customer database Query: The objective is to show that a relationship manager or customer service executive can easily query the customer database to gain insights based on customer data, customer transaction etc. For example, the customer service executive should be able to prepare an query that would prepare a list of customers who (a) have purchased “savings products” (b) and where the agreement is active, product hasn’t matured (c) where the US telephone number has undergone an update (new, change, delete) (d) the change happened between 2 specific dates and (e) the report needs to be run daily at a predetermined schedule.
Customer Persona: The objective of customer persona is to show that an insurance customer could have multiple persona when it comes to claims processing. The customer logs into the insurance portal and gets into claims processing menu. Here the customer should be able to select a profile as Claimant or Witness. As a Claimant, he should be able to see the active claims made by him. As a Witness, he should be able to see the claims made by other customers, where he is marked as a Witness. In such cases, the customer should be able to answer the questionnaire posed by the bank and record a narrative of the event he witnessed.
WORKFLOWS TO FOCUS
Workflow 1: Customer Onboarding
Step 1: The user who wants to purchase a personal pension product has selected a product after research and has come to the online portal to execute the purchase decision
Step 2: Screen 1: The user clicks on the page to select one out of the many products shown on the screen. [Screen for Customer Details].
Step 3: Screen 2: This lands him on to a page that requests for customer information. The user enters the customer information and based on the selection he has made, the system determines that another workflow needs to be triggered to collect FATCA mandated information from the customer. [Screen for Customer Details].
Step 4: Screen 3: A new workflow is triggered that where the user completes the FATCA required details are entered by the user. On completion, the user is brought back to the base flow in Screen 2. [FATCA customer details]
Step 6: Screen 4: Payment is completed through a screen that offers multiple standard payment processes [Payment Processing screen – Use standard template]
Step 7: Screen 5: The system displays the legal contract and allows a download, print, email etc. [Pension Product Contract].
Step 8: Lands into a customized user dashboard that displays the new insurance that has been purchased [User Dashboard].
Workflow 2: Customer Data Query
Step 1: The Customer Service Executive who is responsible for a set of customers can see the status of customers from a customer dashboard [Customer Service Executive Dashboard: Screen to be provided]
Step 2: The dashboard has a query/report creating facility where the user can choose select fields to filter, prepare a query; save it and schedule it.
Step 3: The user invokes the query/report creating facility from the dashboard, selects data elements from under broad categories like PRODUCT, CUSTOMER DETAILS, etc.
Workflow 3: Customer Persona
Step 1: Screen 1: The customer logs into the bank customer portal using user ID and password and sees a landing page which is a customer dashboard. [Login Screen not required mentioned just to illustrate the workflow]
Step 2: Screen2: From the landing page, the customer navigates to the Claims section from the menu and lands on a Claims processing page. Here the customer can see an old claim he has raised against an insurance which was approved and paid out. [Claims page: as Claimant]
Step 3: Screen 3: The customer selects a persona icon from the screen and changes his persona from “Claimant” to “Witness”. Now the customer can see a record that shows a claim raised by another customer (where the current customer is added as a Witness) where action is pending against the customer. [Claims page: as Witness]
Step 4: Screen 4: The customer selects the record which shows details of the incident (a car accident). The customer invokes a questionnaire from the same page to which he answers and completes [Questionnaire (Screen not required, mentioned just to illustrate the workflow)]
Step 5: The system pops up a declaration screen which asks the customer to declare that all he shared is true, and submit. The customer comes back to the claims page to see that no action is pending. [Declaration (Screen not required, mentioned just to illustrate the workflow)]
Step 6: The customer navigates out of the claims screen to the customer dashboard [Customer Dashboard: Screen to be provided (Screen not required, mentioned just to illustrate the workflow)]
Required Screens
Workflow 1: Customer Onboarding
1) Pension Products Option
2) Customer Details
3) FATCA Customer Details
4) Data Collected Edit & Save
5) Payment Page
6) Pension Product Contract
7) Customized Dashboard
Workflow 2: Customer Data Query
8) Customer Service Executive Dashboard with Query/Filter
9) Query Results Screen
Workflow 3: Customer Persona
10) Customer Dashboard
11) Claims Section as Claimant
12) Claims Page as Witness
13) Claim Details
Key Items to Focus on
- This application must look and feel modern, clean and professional.
- Make your design stand out on a first view!
- Focus on general navigation between all required screens and functionalities
- Easy and intuitive use for tech and non tech users.
- The target device for this application is Desktop Web. So you work using 1280px width as your main resolution. Height can be increased if needed.
- Do not create a logo for this web application. Use a placeholder or the word “Insurance Solution”.
- However, have in mind that some mobile screens or responsive features might be requested in future, so think Mobile First! When designing your UI.
- Work with provided color palette only. Do not reinvent colors! See branding documentation below for reference.
Branding Documentation
- Use the colors and imagery style from the following document:
- Branding:
https://drive.google.com/open?id=1QpFKbqPEsb6UAJ0z-IgD7thw5s7vnagq
- Site Layout Sample:
https://drive.google.com/file/d/15gDd6ekXw94ta7UqUy2lSqvW0Dpevs9p/
- Font is open to your criteria. Make it elegant, clean and professional
Target Users
- Insurance Customers
- Customer Executive
Target Device and Size
- Design for desktop views at: 1280px width and height adjusted and increased if necessary.
- Think Mobile First! When designing your UI.
- Use proper grid system.
Judging Criteria
- User Experience of the application/portal
- Completeness and accuracy of your UI Design
- How well your design provide a consistent user flow
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.
- Submit Marvel App for your design.
Source Files
All original source files of the submitted design. Files should be created in Adobe Photoshop, Illustrator, Sketch or XD
Final Fixes
As part of the final fixes phase, you may 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.
Stock Photography
Stock photography is allowed in this challenge. See this page for more details.
This will be a very fast challenge with a tight deadline, that’s why we are trying to provide the best and most complete specifications; to make the problem easy to understand.
Let us know in forum if you have questions!
Round 1
Submit your initial designs for checkpoint review.Workflow 1: Customer Onboarding
1) Pension Products Option
2) Customer Details
3) FATCA Customer Details
Workflow 2: Customer Data Query
8) Customer Service Executive Dashboard with Query/Filter
9) Query Results Screen
Workflow 3: Customer Persona
10) Customer Dashboard
11) Claims Section as Claimant
- Important: As part of your checkpoint submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs.
- Please ask in the Forum for a MarvelApp prototype link. You will receive 1 MarvelApp prototype for Desktop.
- Make sure to include a URL/Link to your design within your "notes.txt", Important!
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03)
Round 2
Submit your final designs plus checkpoint feedback implementedWorkflow 1: Customer Onboarding
1) Pension Products Option
2) Customer Details
3) FATCA Customer Details
4) Data Collected Edit & Save
5) Payment Page
6) Pension Product Contract
7) Customized Dashboard
Workflow 2: Customer Data Query
8) Customer Service Executive Dashboard with Query/Filter
9) Query Results Screen
Workflow 3: Customer Persona
10) Customer Dashboard
11) Claims Section as Claimant
12) Claims Page as Witness
13) Claim Details
- Important: As part of your final submission, you must update your submission to MarvelApp.
- Use the same MarvelApp prototype you received in checkpoint.
- Make sure to include a URL/Link to your design within your "notes.txt", Important!
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03)
Background Information
The objective for this challenge is to conceptualize the initial UI/UX of an insurance solution to showcase the capabilities of underlying customer data management solution through workflows that involve (a) customer onboarding (b) customer database querying and (c) claims processing workflow.
This requires a need to develop solutions around 3 scenarios which are explained below:
Customer Onboarding: The objective of customer onboarding is to show that based on (a) the product selected by the user, (b) domicile of the user where he intends to enter into business, and (c) the legal entity representing the bank in that region; the system can trigger an appropriate customer onboarding workflow. In this case a workflow that include FATCA related data collection processes
Customer database Query: The objective is to show that a relationship manager or customer service executive can easily query the customer database to gain insights based on customer data, customer transaction etc. For example, the customer service executive should be able to prepare an query that would prepare a list of customers who (a) have purchased “savings products” (b) and where the agreement is active, product hasn’t matured (c) where the US telephone number has undergone an update (new, change, delete) (d) the change happened between 2 specific dates and (e) the report needs to be run daily at a predetermined schedule.
Customer Persona: The objective of customer persona is to show that an insurance customer could have multiple persona when it comes to claims processing. The customer logs into the insurance portal and gets into claims processing menu. Here the customer should be able to select a profile as Claimant or Witness. As a Claimant, he should be able to see the active claims made by him. As a Witness, he should be able to see the claims made by other customers, where he is marked as a Witness. In such cases, the customer should be able to answer the questionnaire posed by the bank and record a narrative of the event he witnessed.
WORKFLOWS TO FOCUS
Workflow 1: Customer Onboarding
Step 1: The user who wants to purchase a personal pension product has selected a product after research and has come to the online portal to execute the purchase decision
Step 2: Screen 1: The user clicks on the page to select one out of the many products shown on the screen. [Screen for Customer Details].
Step 3: Screen 2: This lands him on to a page that requests for customer information. The user enters the customer information and based on the selection he has made, the system determines that another workflow needs to be triggered to collect FATCA mandated information from the customer. [Screen for Customer Details].
Step 4: Screen 3: A new workflow is triggered that where the user completes the FATCA required details are entered by the user. On completion, the user is brought back to the base flow in Screen 2. [FATCA customer details]
- following FATCA attributes need to be captured :
- Primary Citizenship / Place of Birth
- Residential Address
- Average Monthly Balance
- Power of Attorney on US Account
- Standing instructions (optional)
- Beneficiary information
- OR the selection in Screen 2 is Legal Entity then enter the following FATCA attributes :
- Domicile / Registered Address
- US Tax Identification Number
- Nature of Business
- Shareholding Pattern
- Average monthly investments
- CUSIP number
- The data entered is submitted.
Step 6: Screen 4: Payment is completed through a screen that offers multiple standard payment processes [Payment Processing screen – Use standard template]
Step 7: Screen 5: The system displays the legal contract and allows a download, print, email etc. [Pension Product Contract].
Step 8: Lands into a customized user dashboard that displays the new insurance that has been purchased [User Dashboard].
Workflow 2: Customer Data Query
Step 1: The Customer Service Executive who is responsible for a set of customers can see the status of customers from a customer dashboard [Customer Service Executive Dashboard: Screen to be provided]
Step 2: The dashboard has a query/report creating facility where the user can choose select fields to filter, prepare a query; save it and schedule it.
Step 3: The user invokes the query/report creating facility from the dashboard, selects data elements from under broad categories like PRODUCT, CUSTOMER DETAILS, etc.
- PRODUCTS
- Product Type = “savings products”
- Product Status = ‘Active’
- CUSTOMER DETAILS
- Contact Details
- US Telephone
- Transaction Type = ‘change’ or ‘update’ (Change here should allow user to Change a US number to NON-US number’ Update indicates, Update existing US Number)
- Transaction Date = from date; to date
- [Query Screen: Screen to be provided]
Workflow 3: Customer Persona
Step 1: Screen 1: The customer logs into the bank customer portal using user ID and password and sees a landing page which is a customer dashboard. [Login Screen not required mentioned just to illustrate the workflow]
Step 2: Screen2: From the landing page, the customer navigates to the Claims section from the menu and lands on a Claims processing page. Here the customer can see an old claim he has raised against an insurance which was approved and paid out. [Claims page: as Claimant]
Step 3: Screen 3: The customer selects a persona icon from the screen and changes his persona from “Claimant” to “Witness”. Now the customer can see a record that shows a claim raised by another customer (where the current customer is added as a Witness) where action is pending against the customer. [Claims page: as Witness]
Step 4: Screen 4: The customer selects the record which shows details of the incident (a car accident). The customer invokes a questionnaire from the same page to which he answers and completes [Questionnaire (Screen not required, mentioned just to illustrate the workflow)]
Step 5: The system pops up a declaration screen which asks the customer to declare that all he shared is true, and submit. The customer comes back to the claims page to see that no action is pending. [Declaration (Screen not required, mentioned just to illustrate the workflow)]
Step 6: The customer navigates out of the claims screen to the customer dashboard [Customer Dashboard: Screen to be provided (Screen not required, mentioned just to illustrate the workflow)]
Required Screens
Workflow 1: Customer Onboarding
1) Pension Products Option
2) Customer Details
3) FATCA Customer Details
4) Data Collected Edit & Save
5) Payment Page
6) Pension Product Contract
7) Customized Dashboard
Workflow 2: Customer Data Query
8) Customer Service Executive Dashboard with Query/Filter
9) Query Results Screen
Workflow 3: Customer Persona
10) Customer Dashboard
11) Claims Section as Claimant
12) Claims Page as Witness
13) Claim Details
Key Items to Focus on
- This application must look and feel modern, clean and professional.
- Make your design stand out on a first view!
- Focus on general navigation between all required screens and functionalities
- Easy and intuitive use for tech and non tech users.
- The target device for this application is Desktop Web. So you work using 1280px width as your main resolution. Height can be increased if needed.
- Do not create a logo for this web application. Use a placeholder or the word “Insurance Solution”.
- However, have in mind that some mobile screens or responsive features might be requested in future, so think Mobile First! When designing your UI.
- Work with provided color palette only. Do not reinvent colors! See branding documentation below for reference.
Branding Documentation
- Use the colors and imagery style from the following document:
- Branding:
https://drive.google.com/open?id=1QpFKbqPEsb6UAJ0z-IgD7thw5s7vnagq
- Site Layout Sample:
https://drive.google.com/file/d/15gDd6ekXw94ta7UqUy2lSqvW0Dpevs9p/
- Font is open to your criteria. Make it elegant, clean and professional
Target Users
- Insurance Customers
- Customer Executive
Target Device and Size
- Design for desktop views at: 1280px width and height adjusted and increased if necessary.
- Think Mobile First! When designing your UI.
- Use proper grid system.
Judging Criteria
- User Experience of the application/portal
- Completeness and accuracy of your UI Design
- How well your design provide a consistent user flow
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.
- Submit Marvel App for your design.
Source Files
All original source files of the submitted design. Files should be created in Adobe Photoshop, Illustrator, Sketch or XD
Final Fixes
As part of the final fixes phase, you may 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.
Stock Photography
Stock photography is allowed in this challenge. See this page for more details.
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.