Veriam

Project

Legal Documents

My Role

Senior Product Designer

Industry

SaaS

Timeline & Status

2024

Overview

Veriam (previously Metrics Matter) is a newly formed SaaS company focusing on Identity and Access Management, Licensing, Billing, Contracting and Payments. Assigned legal documents grant access and permissions to view particular data. In order to do this, the legal documents need to be added and managed by a Service Provider and accepted by a Service Consumer.

Goal

Create a process that allows a Service Provider to easily add and manage legal documents as well as easily allow a Service Consumer user to to accept the Terms and Conditions of the legal documents.

Problem

Legal documents, Policies and Agreements all give the user permission in some sense to view particular data. The assumption is that it can be confusing when trying to understand the difference between them and when to use which option.

Wireframes

Based off of assumptions, wireframes were designed which allowed a Service Provider user to manage and assign legal documents. A user with Service Consumer rights could then accept and subscribe to said terms and conditions. At this stage it was all based on one platform and the type of user you were determined what you saw.

Wireframes

Design System

Because it was a brand new start-up there was no existing Design System in place. In order to create consistency between the two teams a Design System was designed and developed. It was decided to create a custom design library over something like Vuetify because of the customisability and the issues we might run into at a later stage.

Design System

Testing and Feedback

The Design System was then applied to current wireframes. The flow was then user tested and feedback was gathered. The feedback we received was that:

1. The designs needed to be fully responsive as users were using mobile & tablet devices more than expected for the MVP.

2. It wasn’t apparent enough what platform the users were signing up with (Service Provider or Service Consumer), especially when the product was using a service providers branding.

3. The user needed a way to “Log out” once they had joined with an organisation during the onboarding flow otherwise they will be stuck.

4. We needed to accept payments for this first version. (Stripe was used)

5. A plan page needed to be added to this first version.

It was still confusing what the difference was between Legal documents, Subscriptions and Policies where when all three grant access to users.

Testing and Feedback

The Design System was then applied to current wireframes. The flow was then user tested and feedback was gathered. The feedback we received was that:

1. The designs needed to be fully responsive as users were using mobile & tablet devices more than expected for the MVP.

2. It wasn’t apparent enough what platform the users were signing up with (Service Provider or Service Consumer), especially when the product was using a service providers branding.

3. The user needed a way to “Log out” once they had joined with an organisation during the onboarding flow otherwise they will be stuck.

4. We needed to accept payments for this first version. (Stripe was used)

5. A plan page needed to be added to this first version.

It was still confusing what the difference was between Legal documents, Subscriptions and Policies where when all three grant access to users.

Platform Split

After testing and gathering user feedback it was decided to split the platform into two, a Service Consumer portal and a Service Consumer portal.

Firstly the SP portal where Legal Documents could be added and managed.
The second was a SC portal which would allow users to accept the terms and conditions of the said legal documents which would allow them access to specific data.
It was also decided that because essentially Policies, Subscriptions and Legal Documents all have the same underlying principle of granting a user access that they would all be grouped under what is now called Licenses.

NB: At this point the decision was made to rebrand from Metrics Matter to Veriam.

Platform Split

After testing and gathering user feedback it was decided to split the platform into two, a Service Consumer portal and a Service Consumer portal.

Firstly the SP portal where Legal Documents could be added and managed.
The second was a SC portal which would allow users to accept the terms and conditions of the said legal documents which would allow them access to specific data.
It was also decided that because essentially Policies, Subscriptions and Legal Documents all have the same underlying principle of granting a user access that they would all be grouped under what is now called Licenses.

NB: At this point the decision was made to rebrand from Metrics Matter to Veriam.

Final Design

The final design after incorporating the platform split and the new different flows. The first two slideshows showcase a Service Consumer. The second two slideshows showcase a Service Provider.

Final Design

The final design after incorporating the platform split and the new different flows. The first two slideshows showcase a Service Consumer. The second two slideshows showcase a Service Provider.

Reflection

In retrospect more work should have gone into understanding the naming conventions used. Also I would have looked more into whether the platform split was the right solution.

Reflection

In retrospect more work should have gone into understanding the naming conventions used. Also I would have looked more into whether the platform split was the right solution.