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
Design a process that allows Service Providers to efficiently create and manage legal documents, and enables Service Consumers to easily review and accept their Terms and Conditions.
Problem
Legal documents, Policies, and Agreements all grant users permission to access specific data. This can make it unclear how they differ from one another and when each option should be used.
Wireframes
Based off of assumptions, wireframes were designed which allowed a Service Provider 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
Based off of assumptions, wireframes were designed which allowed a Service Provider 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
Based off of assumptions, wireframes were designed which allowed a Service Provider 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.
Design System
As a new startup, there was no existing design system in place. To ensure consistency across teams, a custom design system was created and developed. A bespoke design library was chosen over solutions like Vuetify to allow greater flexibility and avoid limitations as the product scaled.
Design System
As a new startup, there was no existing design system in place. To ensure consistency across teams, a custom design system was created and developed. A bespoke design library was chosen over solutions like Vuetify to allow greater flexibility and avoid limitations as the product scaled.
Design System
As a new startup, there was no existing design system in place. To ensure consistency across teams, a custom design system was created and developed. A bespoke design library was chosen over solutions like Vuetify to allow greater flexibility and avoid limitations as the product scaled.
Testing and Feedback
After applying the design system and user testing the flow, the following key issues were identified:
The MVP needed to be fully responsive, as most users accessed it on mobile and tablet.
It was unclear whether users were signing up as a Service Provider or Service Consumer, especially when using provider branding.
Users needed a clear way to log out during onboarding after joining an organization.
Payments needed to be supported in the first release, with Stripe selected.
A Plan page was required for clearer product selection.
Users struggled to understand the difference between Legal Documents, Subscriptions, and Policies, despite all granting access.
Testing and Feedback
After applying the design system and user testing the flow, the following key issues were identified:
The MVP needed to be fully responsive, as most users accessed it on mobile and tablet.
It was unclear whether users were signing up as a Service Provider or Service Consumer, especially when using provider branding.
Users needed a clear way to log out during onboarding after joining an organization.
Payments needed to be supported in the first release, with Stripe selected.
A Plan page was required for clearer product selection.
Users struggled to understand the difference between Legal Documents, Subscriptions, and Policies, despite all granting access.
Testing and Feedback
After applying the design system and user testing the flow, the following key issues were identified:
The MVP needed to be fully responsive, as most users accessed it on mobile and tablet.
It was unclear whether users were signing up as a Service Provider or Service Consumer, especially when using provider branding.
Users needed a clear way to log out during onboarding after joining an organization.
Payments needed to be supported in the first release, with Stripe selected.
A Plan page was required for clearer product selection.
Users struggled to understand the difference between Legal Documents, Subscriptions, and Policies, despite all granting access.
Platform Split
After testing and incorporating user feedback, decisions were made to improve clarity and usability:
Unified document structure
Legal documents, policies, and agreements were consolidated into a single table. Because they all serve the same purpose (granting user access) they were grouped under a new category called Licenses.Clear role separation
The portal was split into two distinct experiences: Admin and End User, with a clear and intuitive switch between the two.Improved document visibility
A document status badge was introduced to clearly communicate the current state of each document.Multi-organization support
Users belonging to multiple organizations can now switch between organizations to view the relevant documents.Rebrand decision
At this stage, the product was rebranded from Metrics Matter to Veriam.
Platform Split
After testing and incorporating user feedback, decisions were made to improve clarity and usability:
Unified document structure
Legal documents, policies, and agreements were consolidated into a single table. Because they all serve the same purpose (granting user access) they were grouped under a new category called Licenses.Clear role separation
The portal was split into two distinct experiences: Admin and End User, with a clear and intuitive switch between the two.Improved document visibility
A document status badge was introduced to clearly communicate the current state of each document.Multi-organization support
Users belonging to multiple organizations can now switch between organizations to view the relevant documents.Rebrand decision
At this stage, the product was rebranded from Metrics Matter to Veriam.
Platform Split
After testing and incorporating user feedback, decisions were made to improve clarity and usability:
Unified document structure
Legal documents, policies, and agreements were consolidated into a single table. Because they all serve the same purpose (granting user access) they were grouped under a new category called Licenses.Clear role separation
The portal was split into two distinct experiences: Admin and End User, with a clear and intuitive switch between the two.Improved document visibility
A document status badge was introduced to clearly communicate the current state of each document.Multi-organization support
Users belonging to multiple organizations can now switch between organizations to view the relevant documents.Rebrand decision
At this stage, the product was rebranded 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.
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.
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.
