1
<Insert Picture Here>
NGP Lending Origination
FS GBU UX Team
June, 06, 2011
Introduction
• The purpose of this document is to visualize the NGP
Lending Origination Product where a banker (product
manager or business analyst) re-models the business
process and customizes the application capture
screens
Assumptions:
• The storyboards presented are for illustrative purposes only and do not represent
all interactions that could take place.
• The personas used in the storyboards may vary once they have been defined.
3
Our Understanding
• No single Originations process/ product? will ever be robust or
flexible enough to provide a proper out of the box product for the
full range of target banks.
• Variance in size, process, risk taking... will all require a product
to be customized to integrate with a banks existing processes.
• Banks want to quickly implement changes to their business logic
or improve the customer experience to respond to market shifts.
• For which they seek flexible, easy customizable & less time
consuming solutions thus increasing productivity and reducing
operating costs.
• That can allow the bankers from creating attributes to adjusting
and administering credit policy to overall strategic business
process management
4
Banker Background & Scenario
Name: Scott Brown
Role: Product Manager: My Bank Small Business Lending Services
Scenario:
Forwards a process specification document to John Smith detailing the new business
process for small business loans along with a changes to me made on application capture
screens as per the feedback gathered during user testing.
Name: John Smith
Role: Business Analyst, My Bank Lending Services
Scenario:
In a meeting with Scott, John prepares white board sketch to visualize the new business
process model and discusses the change s to be made on the application capture screens to
improve the user experience.
Note: These personas are used for this storyboard only and are fictional and not been based on market research.
5
Business Process Improvement
• Create new business process for small business loan
• Create automated verification and processing for small business loans
• Mandate manual verification and processing for high value loans
6
1. Load Project
Storyline
John launches Originations to create a new
business process for the small business
loans.
He clicks on the Load Project action; which
opens the Select Project dialog window.
He then selects MyBank Small Business
Loans project from the list and clicks on the
Open button.
Banker Experience
TBA
7
2. Display Default Process & Templates
Storyline
John is presented with the default process
that is applied to the product and a list of
process templates that can be applied to
small business loans products.
John reviews the system-provided
templates and realizes that none of them
are appropriate for the process that he has
finalized with Scott.
Banker Experience
TBA
8
3. Create New Business Process
Storyline
He decides to create a new process for the
product
He clicks on Create New Business Process
action from the Actions menu to create a
customized process
Action launches a New Business Process
dialog; which allows john to specify a name
for the customized process.
He specifies the name, product type,
region which will help him find the right
workflows to fit his needs.
Banker Experience
TBA
9
4. Add Sub-Process - Application Capture
Storyline
John is presented with an empty canvas
and a palette to add process blocks that
can be used to create a new business
process for Small Business Loans.
Process shapes in the palette are
categorized in to different categoriesApplication Capture, Verification, Approval,
Processing.
John drags a block to the canvas from the
Application Capture shape category.
Application capture block contains two
shapes- Create Application and Submit
Application.
Banker Experience
TBA
10
5. Add Sub Process - Auto Verification
Storyline
John drags Auto Verification block to the
canvas from the Application Verification
shape category.
Newly added block displays shapes for the
steps that are required for the loan
application verification.
Banker Experience
TBA
11
6. Add Sub Process - Manual Verification
Storyline
Because the process they decided on
requires two types of verification,
depending on the loan size which is >100k,
John drags the manual one on as well.
John then selects Manual Verification block
from the Application Verification category
and adds it below the Application Capture
block that he has previously added.
Banker Experience
TBA
12
7. Add Condition for Auto Verification
Storyline
John selects the Submit Application shape,
displayed in the Application Capture block
and clicks on Add Condition action from the
Actions menu.
Action adds a Condition icon below the
shape and displays a connector.
John selects the connector and links it with
the Auto Verification block.
Banker Experience
TBA
13
8. Add Condition for Manual Verification
Storyline
John adds an additional condition on the
Submit Application shape.
Action adds a Condition icon below the
shape and displays a connector.
John selects the connector and links it with
the Manual Verification block.
Banker Experience
TBA
14
9. Apply Rules to Conditions
Storyline
John Selects the condition, added for Auto
Verification and clicks on the Edit Condition
action from the Actions menu.
Action launches the condition editor dialog
which displays condition choices based on
the various attributes of the loan
application.
John selects Loan Type as a condition and
then selects Auto Loan as a value.
Rule Description area immediately displays
a comprehensible description of what he
has selected.
John reads the description and clicks on the
OK button to apply the condition.
Banker Experience
John is very impressed at how he was able
to create rules exactly the same way he
created rules in Outlook.
The familiarity with the process made him
feel more comfortable in his ability to apply
complex branching logic to his process
without the need to write any code (or wait
a week to involve the IT department).
15
10. Completed Business Process
Storyline
John completes the end-to-end process
and adds all required conditions
To verify the process and conditions, he
clicks on the Verify Process action from the
Actions menu
Banker Experience
TBA
16
11. Specify Preview Role & Platform
Storyline
John selects the ‘Customer’ role and
platform as ‘PC’ to preview the application.
The application preview changes
depending on the role and platform
selected
Banker Experience
TBA
17
12. Verify Business Process & Application
Storyline
John is presented with the application
screens as if he were a user applying for a
new loan.
Preview mode display the
application as it will be seen to
the applicant including the
bank logo, navigation etc.
He enters dummy data for all the different
branching possibilities he has created, and
sees that his business process is
presenting everything according to the rules
he specifies.
As he runs through the predefined screens,
he notices that there are changes that he
would like to make to the UI to make it more
compatible with their other product
applications.
He then closes the preview mode to make
UI customizations to the screens.
Banker Experience
John is impressed that all the CSS
Stylesheets for the bank have already been
applied to the screens...
18
User Objectives
• Customize Company Information Page: Add ‘Organization
Type’ component to the page from Oracle Component
Repository
• Customize ‘Organization Type’ component: Add ‘Cooperative’
& ‘Other’ fields to the component
• Create New Page: ‘Getting Started’ to give an overview of
loan application process to applicants
19
1. Customize User Interface
Storyline
John sees the list of available steps in the
‘Apply for Loan’ process and clicks on
Company Info to customize.
Banker Experience
TBA
20
2. Customize Company Information Page
Storyline
In the Edit Page mode, John is able to add,
remove or modify any components on the
page. Default components such as
Customer Support, Company Information,
Learn appears as a part of the template.
These options will only be
seen to the admin in the
edit mode
He clicks on 'Add' to open Oracle
Component Repository
Banker Experience
TBA
In edit mode the existing
components turns editable
by which the admin can
remove or modify the
component
In edit mode blank
components get added to
the page as per the layout
thus allowing the admin to
add more components to
the page from Oracle
Component Library
Note:
At this stage we are only planning to
allow the user to select from predefined
fields. Future versions should consider
a full UI page forms edit capability, but
we need to confirm that this is within
the extensibility model available)
21
3. Add Component from Repository
Storyline
On clicking 'Add‘ in previous screen, he
gets a list of all the components from the
Oracle Component Library.
He selects 'Organization Type' component
to be added on the page.
Banker Experience
TBA
22
4. Display Component Added
Storyline
'Organization Type' component gets added
to the page. However John finds that he
needs to add some additional fields to the
component. He is able to customize the
component.
He clicks on 'Edit Component' icon to bring
up the component properties.
Banker Experience
TBA
The component gets
displayed with the
customizable content
23
5. Customize Component
Storyline
A list of all the fields associated with
‘Organization Type’ component is
displayed.
John is able to choose the fields to be
displayed/ removed from the page.
He selects Co-operative & Other to be
displayed on the page.
Banker Experience
TBA
Other tabs allows the
banker to change the
properties of the
component
Other tabs allows the
banker to change the
properties of the
component
24
6. Display Customized Component
Storyline
The 'Organization Type' component gets
updated with the additional fields.
John previews the application once again
before going ahead with further
customization.
He selects Preview Application from the
Actions menu
Banker Experience
TBA
25
7. Preview Application after Customization
Storyline
John previews the application as it will be
seen to the applicant.
The only change remaining is to add one
more step in the entire process to give
applicants an overview of the application
process.
Banker Experience
TBA
26
8. Create New Page
Storyline
John selects ‘Add New Page’ from the
Actions menu.
He enters the page properties and choose
a layout for the page.
Once done with the initial setup, he reorders the page so that it appears as the
first page in the application.
He does that by selecting the Manage
option.
Banker Experience
TBA
27
9. New Page Added
Storyline
Page Wizard gets updated
with the new page
A new blank page called 'Getting Started is
added as the first page in the process.
John can now add a customized message
on this page by adding relevant
components from the Oracle Component
Library (Refer Slide 21) and further
customizing the look and feel of the
component (Refer Slide 23).
Once the content is added John takes a
final preview of the new page in context
with the rest of the pages in the process.
Default component s are
displayed
Banker Experience
Area to add new
component from the
Oracle Component Library
TBA
28
10. Preview Application
Welcome message gets
added on landing page
Storyline
Once satisfied with the customizations,
John closes the preview and saves the
entire process.
Banker Experience
TBA
29
11. Preview Available Process
Storyline
John goes back to the initial list of available
processes to select and sees it in the list of
available process.
John is now satisfied that the new page is
now reflected in the business process along
with the other UI changes that are done .
Before logging off from the product he
once again Saves the changes made and
clicks Sign out
Banker Experience
TBA
30