ComplyGlobal provides global compliance solutions. Its SaaS based platform helps companies govern and track domestic and global regulatory requirements in real-time to manage compliance risk.
The company was in the early stages, focusing on launching the first version of their product. They wanted to design their client-side SaaS platform from the ground up and needed guidance with overall business and product strategy, information architecture, user experience and design. The product was intended to be an all in one global compliance SaaS based solution.
The interface focused on five key areas: compliance management, reporting, organizational infrastructure, secure file repository, and knowledge base.
The Master Plan
Simple and clear visualization of the breadth and complexity of the business requirements were at the core of this project.
Companies with subsidiaries in multiple countries deal with complex compliance requirements and idiosyncratic processes to achieving that compliance. Much of the process is manual, requiring specific paperwork to be filed on the ground in some cases.
The goal was to create a SaaS platform to support and execute global compliance across multiple entities in various countries.
The initial prototype the company had created before bringing us on board was over 130 pages.
The management team had mapped out the core functionalities and business logic. A programming team built the prototype to support these specs, but there was no UX/UI role inserted between the business team and the programmers.
We were brought on to organize and design the interface from the ground up with the prototype as a jumping off point.
The diagram to the right shows the ah-ha! moment after working with the prototype during discovery. Essentially, the whole system revolved around Entity Creation. In this, the various functionalities needed to revolve around an individual company or subsidiary.
This led to proposing that the KPI/Analytics Dashboard be the "30,000 foot view" of a single entity, and that a user would manage only one entity at time. This greatly simplified the approach in the prototype, which tried to feed across entities into the Dashboard.
- Content and usability requirements
- Stakeholder interviews
- Information architecture
- User flows
- Visual design
- Quality Assurance + Testing
The complexity of the business requirements were astounding. It was one part KPI/Analytics Dashboard, one part iCal, one part Dropbox, one part Asana. The prototype was helpful during discovery to distill the product down into its core sections.
Additionally, this approach resolved multiple issues in the business logic for roles and permissions. Roles and permissions were approached from the back-end side - creating roles based on the lowest common denominator of user access across multiple entities. Single entity management created a reduction of roles from 12 to 3.
SYSTEM AND USER NOTIFICATIONS
BUSINESS ENTITY RELATIONSHIPS
Once the core UI strategy was approved, we moved into visual design, which included all the primary and secondary screens, in addition to interaction states. All told it was close to 100 page designs.