DANA KYB Workflow

At preliminary question, DANA provides basic question, I think the one that will dictate whats the next question is:

1. Business Type: Different type would need more or less information they need to provide, for example a individual business may not need (and likely dont have) a business documents from states, a UBO list, or any formal document. While a PT should be expected to provide this kind of information

2. Business Industry: A more compliance industry should provide more document, for example a financial service company may need to provide business license, business activity, even a senstive document like transaction report
3. Average daily transaction: the bigger the transaction, the bigger the opportunity for DANA. And interesting to look at the range they provide is weirdly specific, there may be regulation in place for it.

Unfortunately, I can't go more in depth since the server is throwing an error 😅. But yeah most of KYB workflow should follow a waterfall method where the logic and sets of question should be built based on previous answers.

In the meantime let me built a more UX friendly screens for DANA Enterprise KYB workflow.

The first one is user Business Profiling/Identity question, where it basically asks basic profile that every business wether is individual or PT should have. In here I add icons and more CTA on the left panel. Also add "Licensed by OJK" terms to make the registration form more trustable.

Also adding a customer support section on the upper right side so user can get help directly. Since my lines of thinking if a user already regist an account and want to fill the registration form, that's basically a 80% hit rate potential customer, adding a customer support for this part will make the onboarding more seamless and in return more customer.

2nd screen is the "Operational" information form, whereby DANA will use this information to dictate which features the dashboard would provide, and of course pricing. In there I also add a guide on what's to be expected on the next step if user choose certain options, this to provide more clear expectations on why we need this information. Same for the progressive profiling card.

3rd Screen is the same thing, but looking deep dive into the transactions part. I want to emphasize more icons but not too overwhelm to make the screen more UX friendly.

The 4th and last screen provides summary of the application user filled. In there we also provide terms & condition at the last part. By putting the Terms & Conditions to the final summary screen, we minimize early friction and improve completion rates while still ensuring users review all critical information before submission.

That's it for study case, I think there's many things that DANA Enterprise form can improve on especially on the UI part. Learnt alot about KYB workflow also, let me provide more things that I learnt regarding KYB workflow but not related to DANA:

1. How much u want to sacrifice the UX in change of the safeguards? Fraud detection, anomaly, and compliance is a core thing in the KYB, but how much more document request u can put until the user overwhelm? I think its an important question to ask especially if the requirements is not needed by the regulatory.
2. Ask the right question at the right time When we need additional information from user? when we need manual review or automated approval? For example business with < IDR 1 Million revenue per day may not need a transaction report document.
3. Vendor bottleneck Im thinking there will be many verifications needed in this KYB, like to verify a identification number, document, etc. What I don't want is to use many vendors that it creates a bottleneck, dependency, and potential data inconsistency on the pipeline.

That's all folks, hope it can helps anyone who reads this. See ya 👋