This project was the beginning of the new business banking vertical that the company was taking. Docfox wanted to provide a fast and simplified way to onboard complex businesses as well as individuals
The banking space has many different journeys of opening an account as an individual consumer, but for businesses, this is a lot more challenging. At the time of this project, there was a gap in the market for doing customer due diligence for onboarding businesses, we saw this gap as an opportunity in the market to create a different stream of revenue.
The product's current flow allowed a bank to request profile details and then once that was fulfilled another email was sent out to request documents
This was solved for a SaaS company that specialised, at the time, in KYC (know your customer) for both consumers and businesses.
KYC Compliance product, servicing both South Africa and USA
Product Manager
Engineers
Me - Product Designer
One business quarter to deliver a minimal viable product.
The product is great for collecting and storing documents if we already have the company's/individual's details stored, but we need a way to collect information and corroborate documents in one flow when a client is applying for an account.
As a team, we were aware of the constraints that the existing architecture, this product has been built over many years and it simply was not viable to deliver a product as well as refactor old code. This meant making some calls that would allow us to break into the market within the given time constraints as well as avoiding refactoring the entire code base
The product is sold to different financial institutions across Africa and America.
Each institution has slightly different approaches and rules to its account application, and within an institution, each application has a slightly different set of information to collect.
This means the solution needed to be highly configurable.
The business need was to break into the market, which meant that we needed to get this done in a certain amount of time.
Company Statement
I started by interviewing the Product Manager & asking what they had found out in their research.
We went to our existing customers to find out where the product was lacking, and they informed us that the product was good for storing the documentation electronically, but the collection was really hard to do at the moment.
We researched what other banks were doing globally and found the parts where we thought the journey was lacking.
We found out that there are not many online tools that allow a business to be onboarded seamlessly & that businesses needed to open accounts in the branches.
Once we got the insight, we moved on to user flows. The product managers came to me with a basic idea of how the flow should work.
Now, with a better idea of what the expectations were, I created a detailed user flow with the technical constraints and user in mind. I took these to the product manager and we made some changes, thereafter taking it to the engineers to find out if the flow is possible given the constraints. There were a few changes to the flow they suggested & we went back & forth.
I used the user flow as a base to come up with wireframes, along with the PM, we decided to create the ‘ultimate’ user journey for the entire flow knowing that it may not be possible in the timeline. I iterated on the wireframes until we were all satisfied.
Once we all agreed we moved on to customer discovery with the lo-fi wireframes, getting early input from the customers would provide great insight before getting too deep into the UI.
This was a continuous process…Once we had confidence we moved onto medium fidelity & repeated customer discovery until we were satisfied with the reactions.
I consulted with engineers & confirmed if the “big idea” could be done. Unfortunately, the concept we were hoping to get into wasn’t possible with the constraints the current architecture had. The way we stored documents did not allow a user to upload a document inside of a form.
Along with the product manager, we began to cut the scope for an MVP & worked out a release plan for future iterations.
It is as important to get engineering feedback earlier on as the users. The engineers ultimately will be able to say how difficult a caution is to implement & whether it is possible to get done in the expected timeline.
The sales team were able to land a lot more deals by having this as an added feature.
Addressing the issue of verifying a business's authenticity and structure through data collection.
Finding a solution to authenticate both businesses and individuals.
One of the significant projects that I tackled early on in my career.
Copyright © 2023 clarevah - All Rights Reserved.
We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.