Regulatory Compliance Web Application Design Concepts Challenge

Welcome to "Regulatory Compliance Web Application Design Concepts Challenge".

In this challenge, we are looking to explore design concepts for a web application that allows the Insurance Companies to understand what regulatory controls are necessary in their processes and systems for each individual Customer Journey - so that they can be compliant with the regulations.

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

• Show the flow outlined in the brief (Marvel hotspots are important)
• Desktop screens of 1366px width.

Round 1

Submit your initial designs for a checkpoint feedback
01 Baseline View
02 Change/ Amendment View 
03 View list of Uploaded Documents
04 View Rules
05 Upload All Relevant Policies and SOP’s

- As a part of your checkpoint submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs.
- Make sure to include a URL/comment the link to your marvelapp while uploading your submission
- Make sure all pages have the correct flow! Use correct file numbering. (00, 01, 02, 03)

Round 2

Submit your final designs with all checkpoint feedback implemented.
01 Baseline View
02 Change/ Amendment View 
03 View list of Uploaded Documents
04 View Rules
05 Upload All Relevant Policies and SOP’s
06 Anomaly List View
07 Anomaly Summary Dashboard ?
08 Anomaly Detailed Dashboard
09 Anomaly Remediation Dashboard

- As a part of your checkpoint submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs.
- Make sure to include a URL/comment the link to your marvelapp while uploading your submission
- Make sure all pages have the correct flow! Use correct file numbering. (00, 01, 02, 03)

Background Information:
Insurance is a tightly regulated market and there are several regulatory bodies, both Federal as well as State (e.g., FINRA, SEC, State Regulators etc.) which define mandatory regulations that each Insurance company should be compliant with. Moreover, these rules change intermittently and the insurance companies have to keep track of these changes and make appropriate modifications in their Policies and Procedures to ensure that they are compliant with the regulatory mandates and are avoiding any penalties.

In the current state, the regulatory departments and the different operational groups have no systematic way to track the regulatory changes for each of the customer journeys and as a result they are subject to exorbitant penalties.

Our Solution
Our solution introduces a Customer Journey Centric approach to Regulatory Compliance. It allows the Insurance Companies to understand what regulatory controls are necessary in their processes and systems for each individual Customer Journey, so that they can be compliant with the regulations.

Objectives
1. Visualize the baseline Regulations and amendments at each stage of a Customer Journey
2. Analyze existing Policies and Procedures and SOPs (Standard Operating Procedures) to identify any changes needed to comply with the base regulations or any amendments
3. Detect Anomalies in the existing Regulatory Control processes based on analysis of data
4. Identify corrective and preventive measures to ensure compliance

Design Considerations
- We are looking for an intuitive, easy-to-use, corporate, modern design.
- Have your designs of size: 1366 x 768px
- Branding is open to the designers

Required Designs:
Use Case 1:
View applicable regulations and relevant amendments, if any

Solution Overview
This use case will provide users with a view of the different Regulations that will impact the insurers at every step of a Customer Journey. It will also provide users with a view of the changes/amendments that have occurred for each rule. The rules will be tracked for each stage in the customer journey. 

A customer journey is a series of steps the customer experiences in his/her interaction with the insurance company. In our solution, the Rules will be tracked at a Level 2 level of granularity

User Persona:
John is working as an operation manager at an insurance company. His work is to educate the insurance agents on various policies available in the company and also lets them know the rules they need to comply while selling the policy.
- John finds the current process very difficult. Whenever there’s a change in the rule, he doesn’t get to know about them immediately and in turn, he is not able to communicate the same to the insurance agents.
- But through this "Regulatory Compliance Web App", John easily understands the required steps from a regulatory standpoint and likes that all required rules are listed based on the customer journey.
- And whenever any changes are made to the rules, John gets an alert on his app, and he replicates the alerts to the agents.
- He selects the required filter and clicks a button to view the list of rules he needs to comply with.
- He is also able to see a menu item that says “Change/Amendment View”

Detailed Requirements
Users will have 2 views “Baseline view and Change/ Amendment View”

01 Baseline View:
In the Baseline view, users will be able to choose a customer journey from a drop-down and users should be able to see the Rules affecting each stage (at a Level 2 level). There could be multiple rules affecting each stage. There could also be overlapping rules (same rules applied to multiple stages). An example is depicted for a sample customer Journey (sample_customer_journey.jpg) for understanding purposes
Example Customer Journey: Customer Onboarding
Example Product Category: Variable Annuities
Example of Stages in the Customer Journey: See the provided table

- In the Baseline view, users should be able to drill down at a granular level to see the details of each rule and the prescriptions that should be applied to comply with the rule. The following table shows the needed attributes and details of a particular rule
- The users should have a way to drill down to the right stage of the customer journey and see the impacted rules. For e.g., for the Customer Onboarding Journey, the user should be able to drill down in the following manner.
- Journey (Customer Onboarding Journey) -> Level 1 Stage(Initiate) -> Level 2 Stage (Prospective Customer Interaction) -> Rule 1 (Show the details in the table above)

Note: The Prescribed SOPs section will include descriptive text (May be 500 chars or more). The screen should be designed keeping that in consideration.

Filter
In the Baseline View, the user should be able to filter by the following criteria:
A. User selects the following
a. Product category
i. Only single product can be selected

b. Customer Journey
i. Multiple journeys can be selected
ii. Each product may have more than 10 journeys per product

c. Regulation level:
User should have the capability to toggle between Federal and State Rules. In case of State Regulations, it should have the ability to filter on the state
i. State
ii. Federal
iii. Any

d. Regulatory body
i. Up to 10 possible values – when regulation level is “Federal”
ii. All the states (two alphabet code) – when State is selected
iii. Both (i) and (ii) when Any is selected
iv. User can select multiple values

e. Date Range
i. User can specify “From” and “To” dates (format – MM/DD/YYYY)

B. User clicks on Submit Button to view the Detailed View
5. In the Baseline View, the user should be able to identify if there is a change in the associated rule.

02 Change/ Amendment View
In the Change/Amendment View, the user should be able to identify if there is a change in the associated rule. The system must show all the notices that have been released pertaining to the selected rule in the last 5 years. In the Change/Amendment View, the user should have the following filters:
a. Customer Journey
b. Regulators
c. Effective Date
d. Status of Regulation – Pending, Ratified etc

Use Case 2
Rules Extraction from insurers Policies and Procedures document

Solution Overview
Each insurer has a Policies and Procedure document to define how the insurer complies with the Regulations. Based on the polices document each functional area (e.g. Customer Onboarding) develops their own Standard Operating Procedures (SOPs). Our system should be able to extract regulatory rules from the insurers Policy documents and be able to digitize those rules.

User Persona:
Henry is an Enterprise Risk and Compliance Personnel
- He looks to update the rules affecting a particular customer journey
- He opens the "regulation web application", and sees a list of documents that were already uploaded
- He searches for the required product
- He finds the "Upload SOP" button, once he clicks on that he uploads the document
- He enters the product name, journey name, file type, file name and clicks on the Upload file button.

Detailed Requirements

03 View list of Uploaded Documents
Users should have the ability to search and see a list of all the uploaded documents. The search criteria will be based on the following:
a. Product – default set to all
b. Customer Journey – default set to all (ex: Onboarding, etc)
c. Uploaded date – defaulted to 1 year before
d. File Type
e. File Name

3. Users should have the ability to see a list page with all the searched documents. The list page should have the following attributes:
a. Customer Journey
b. Product
c. File Name
d. File Type
e. File Description

In addition, the list page should have the following buttons:
a. View Rules - View Rules Extracted and digitized from the document. As the user selects a rule, the section of the SOP from which the rule was extracted must be shown
b. Download SOP - Download the SOP locally
c. Download Report - Clicking the button will download a pdf with all the rules associated with the document
d. Upload new version – Upload a new version of the document

04 View Rules:
User should be able to see the below
- File Name
- File Type
- Rules
- Journey

Apart from the above the UI should also show the document / highlight the section of SOP document from which the rules were taken.

05 Upload All Relevant Policies and SOP’s:
Users should have the ability to upload all relevant Policies and Procedures and Standard Operating Procedures for a particular functional area. The UI should have the following fields
a. Upload File Button – To upload a SOP document
b. File Type – Can be of 2 types
a. Internal Policy and Procedures
b. Existing Standard Operating Procedures
c. File Description – Text field (100 chars) which the user doing the upload can enter. This will be a brief description of what the file uploaded is about
d. Product – Associated Product for the uploaded file
e. Customer Journey – Associate Customer Journey for the uploaded file

Expected flow
A. User selects the applicable details
B. User enters a file name
C. User clicks on the upload file button to browse and select a file.
D. The selected file is saved to system and a success message is displayed.

Use Case 3
Anomaly Detection
Anomaly happens when an agent sells a wrong policy to the customer

For example:
- Assume a 60yrs old person visits the insurance agent to get a policy
- Agent suggests a policy that is not suitable for a 60yrs old

Solution Overview
The Anomaly Detection use case will help users identify any anomalies based on the available data in the insurer’s data ecosystem. It will also help the user identify the Severity of the anomaly and the impact the anomaly may cause. The anomaly may occur if the regulations are not implemented correctly in the systems and processes. It may also occur if there are changes in the regulations.

06 Anomaly List View:
Should provide the users with a list of anomalies. The following attributes should be visible to the users
a. Customer Journey – Customer Journey where the anomaly is noticed
b. Product Group – Product Group where the anomaly is noticed
c. Level 1 Stage – Level 1 Stage of the Customer Journey where the anomaly is noticed (e.g., Initiate, Validate etc. as depicted above for Customer Onboarding Journey)
d. Level 2 Stage – Level 2 Stage of the Customer Journey where the anomaly is noticed (e.g., Prospective Customer Interaction as depicted above for Customer Onboarding Journey)
e. Anomaly Category – The category for the anomaly (Less than 10 categories will be defined). Examples are, Suitability, Know your customer, Suspicious Activity etc.
f. Anomaly ID – a unique Identifier for the Anomaly
g. Anomaly Description – A detailed description of the Anomaly (Around 200 characters)
h. Anomaly Details Button/Link – There should be a link to go to the Anomaly Details section from the Anomaly Link.

Users should have the ability to filter anomalies based on the following
a. Customer Journey
b. Level 1 Stage – Should be populated based on the Customer Journey. Will be different for each journey
c. Level 2 Stage - Should be populated based on the Customer Journey. Will be different for each journey
d. Product
e. Anomaly Category

Anomaly Details:
Users should have the ability to see the details of the anomaly on a separate screen once the user selects the Anomaly on the List page. The Anomaly Details will have 2 sections:

07 Anomaly Summary Dashboard:
Shows the summary impact of the Anomaly. The key attributes for the Summary Dashboard are:
i. Number of Customers Impacted
ii. Number of Products Impacted
iii. Number of Policies Impacted
iv. Impacted Stakeholders – Teams who are impacted due to the Anomaly (Could be multiple)
v. Impacted Systems – Systems which are impacted due to the anomaly (Could be multiple)

08 Anomaly Detailed Dashboard:
Shows the details based on the data shown on the Anomaly Summary Dashboard. This section provides the detailed data to support the Anomaly Summary shown above.
i. This should look like a detailed dashboard with multiple data fields
ii. Should highlight the rows in the data which have a discrepancy
iii. Should highlight the data elements where there is a discrepancy
iv. Should support huge volumes of data (Number of policies could be in thousands)
v. Users should have the ability to Slice and Dice the data based on the Data Fields
vi. The Data Fields in the detailed Dashboard could be different for each Anomaly

09 Anomaly Remediation Dashboard:
Add, update and view actionable steps to remediate the Anomaly. The key attributes for the remediation dashboard include
i. Remediation Description
ii. Remediation Category
iii. Responsible Group
iv. Action Owner
v. Action Approver
vi. Status - Valid values are Not started, In Progress, Complete, Decided not to pursue

In addition there should be Add/Update Buttons for users to add/update remediation steps

Important:
- Keep things consistent. This means all graphics styles should work together.
- All of the graphics should have a similar feel and general aesthetic appearance.
- Focus on User Experience / how the user interacts within the dashboard.

MarvelApp Prototype
- We need you to upload your screens to the Marvel App
- Please send your Marvel app request to csystic@gmail.com (Challenge Copilot)
- You MUST include your Marvel app URL in notes /comments while uploading (in your marvel app prototype, click on share and then copy the link & share it within your notes while you upload).

Target Audience
1. Enterprise Risk and Compliance Personnel: To understand the base regulations and amendments to rules and its impact at each step of a customer journey (Upto 50 members)
2. Business Operations Team (Across multiple functional areas like Customer Onboarding/ Servicing etc.): To understand the impact of regulation to their respective functions and update their processes to ensure compliance (Upto 5000 members)

Judging Criteria
- How well you plan the user experience and capture your ideas visually.
- Cleanliness of your graphics and design.
- Overall design, UI and user experience.
- Consistency across the UX/UI

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 Marvelapp as part of your submission.

Source Files
All original source files of the submitted design. Files should be created in Adobe Photoshop, Illustrator, XD, or Sketch!

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.