SICC (Search and Import Client from Core)
company
Docfox
Role
UX, UI Design, Research, Wireframing, Prototyping, Customer Discovery
Tools
Figma, Miro, Shortcut, Slack,
usability tests
+6
prototypes built
+3
Design Concepts
+7
duration
+6 months
Background and Problem: 1-Pager Google Sheets Document
DocFox helps a bank open a new business bank account. This process involves the applicant for an account, or a banker on their behalf, submitting required information and documentation.
However, if a bank has an existing client on their core that was not created while using DocFox (e.g. at a time before the bank used DocFox), DocFox would have no data on such a client. Therefore, if the client applies for a new account, they would be required to upload all their information from scratch, resulting in a poor client experience.
Solution
Before the Banker creates a new application in DocFox or invites the client to create their own, the banker is first able to search for the client in the core without leaving DocFox. The banker can then create the client’s application in DocFox by importing their information from the core. The benefit of this is that when an existing client wants to open a new account, DocFox ensures that the client doesn’t have to re-enter the information the bank has on file; any data entry require from the client would just be for the new account they wish to open.
Must haves
As a banker, I must be able to search for clients in the core without needing to leave DocFox
As a banker, when viewing a business client’s core record in DocFox, I must be able to see the list of signers and owners linked to that business.
As a banker, when viewing an individual client’s core record in DocFox, I must be able to see the businesses to which that individual is linked as a signer or owner.
As a banker, when viewing a client’s core record in DocFox, I should see sufficient information that would allow me to decide if that is the record to import into DocFox.
As a banker, I must be able to select a client’s core record to import into DocFox.
As a banker, when viewing a client’s application in DocFox that was imported from the core, I must be able to see that client’s profile information, its related parties (if applicable), the products and accounts (with account numbers) the client has with the bank as well as any miscellaneous information that my bank has configured, inside DocFox in-app form.
As a banker, I do not have to collect and approve the documents that I would ordinarily have to if this application was created the “normal” way in DocFox (normal = application was created by the banker or by the client from scratch when I was invited through SFO).
As a banker, when viewing the client’s application in DocFox that was imported from the core, I
Should haves
As a banker, I must be able to search for multiple clients at once.
As a banker, I must be able to import multiple clients at once.
As a banker, when searching for a client in the core, I should be told if that client exists in DocFox as well.
As a banker, I should be able to see the exact nature of the relationship between a business and its related parties. Eg: I should see that Dean is an owner of ABC Corp, not just that Dean is in some way linked to ABC Co..
Won't haves
The ability to automatically search for a client’s existence in the core when their details are entered in the related party builder. Slated for a later release.
The ability for the bank to define which forms or documents that the bank has on file need to be updated by the client. This is slated for a later release.
The ability to “interject” and warn the banker that the client exists in the core when the banker either invites the client to self-onboard through Single-Flow Onboarding (SFO), or when the banker creates the client’s application themselves.
The ability to merge information from the core with an application in DocFox if that client already exists in DocFox but is imported from the core, nonetheless.
A guarantee that bankers will be able to search for a client in the core using the same fields across all cores. Eg: some cores might only allow us to search via name and TIN, while others only TIN.
A guarantee that bankers will be able to view the same information when viewing core search results in DocFox across all cores. Eg: some cores might only return the record’s name and address, while others just the name when searching for a client record.
Workshops
High Level User flows
SICC Timelines
SICC Wireframes
Concepts are an important part of UX design as they allow us to explore and experiment with ideas before diving into the details. Through research and ideation, I strive to develop concepts that are user-centric, intuitive, and visually appealing.
By starting with a solid concept, we can ensure that the resulting designs are not only aesthetically pleasing but also effective in meeting the needs of the user.
30 November 2022
10 January 2023
16 January 2023
Design Handoff
The insights page provides a high-level view of the performance of the team, focusing on the activity of analysts and progress towards specific goals. This type of page typically displays data and metrics related to the work of analysts, including the Security Viability, the types of analysis conducted, and the time spent on various tasks
Components and Specs
Displays data and metrics related to the number of cases or tasks that each analyst is working on, as well as their capacity to take on additional work. This can include information such as the Initial Access, Execution, Persistence and Command Control. It also shows the Analyst capacity such as their accuracy or productivity. This can help managers and stakeholders identify areas of strength and weakness and inform decisions about where to allocate resources or provide additional training.
