mikal-use-case-showcase

I worked on the configuration piece of the sass application that allowed our banking customers to configure the product. This branding finished product process was also inline with our internal efforts to follow Oracles new redwood design process that involved looping in their leadership and additional design checkpoints via the redwood design methodology process. So the success criterion is that A bank can successfully build a product” and “the banks customer loves the product” and Oracles internal design process has been followed. All three criterion were met!

My role as lead designer was to work closely with leadership and Oracle’s global design committees and checkpoints, which covered both our product appeal and effective experiential MVP.

The product needed to include our Project Owners across several domains and Subject matter Experts that required to be included in the multi-tiered design checkpoints of Oracles GBU (Global Business units)

There were lots of negotiations here, as engineering did not account for harsh user experiences like dead stops with nowhere to go and fractured experiences that caused users to leave the process and come back without any previous work saved. While I was able to save a few hard stops with alerts and instructional prompts, not all, and many were left to UX debt that will be actioned at a future Date.

Custodial, trusts, and joint accounts need multiple signatures

Once contracts were signed

Once user John finished his part of the application, both received an SMS and/or email message confirming their actions and/or next steps.

Creating a way to view data

Each section is on a linEAr path, and each section has tasks to be completed