Redesigning a RegTech Case Creation Experience
How we redesigned an enterprise-grade B2B product to decrease complexity and improve productivity
Company: Opus
Role: UI/UX design
Year: 2018–2019
Context
After years of continuous development, the product had become bloated with a bad user experience. Additionally, after an acquisition, the company had rebranded. We embarked on an overhaul of the product’s front end, improving the user experience and updating the branding.
Challenges
The product was originally created with one client in mind. The side-by-side layout worked well for that client’s requirements but was awkward for most client workflows. Data input requirements varied greatly from client to client so adopting this layout to other clients proved difficult. It also presented other design challenges early on. No matter where we placed the CTA, it never felt intuitive. Product enhancements created complications that were hard to resolve within the side-by-side layout.
After nearly 10 years in production, the product had become slow, bloated, and inefficient. It was time to take a step back and re-evaluate…
Solution
With a history of feedback from clients and a good understanding of the variable requirements with which potential clients would approach us, I began wireframing to flesh out the general structure. It quickly became clear that using a sidebar to contain the entity list/hierarchy tree would be a huge improvement.
Adding status icons alongside entity names provided a consistent overview of the scope of the investigation/case.
Provided quick navigation to all entities in the investigation/case.
Can be used on the Create Case screen and the Workbench, keeping consistency and simplicity throughout the application.
I prototyped a quick-add feature that would allow users to enter the name of the entity directly in the sidebar without being required to add any additional information.
Separating the case and entity information input forms required us to go back to basics and ensure the whole team was on the same page regarding navigation of the workflow.
I explored a few ways to lay out the entity information form. We ultimately decided this direction wasted too much screen space. Users frequently wanted the content to be more dense.
Final Solution
