Case study

Veriforce Design System

2019 – SaaS Product Design

Summary

When I joined Veriforce in 2018, there was no collection of common design patterns or components.

Role
UX/UI Designer
Client
Veriforce
Year
2019
Coworkers gathered around a table with laptops in a shared office.Enlarge

Image preview

Business Problem

When I joined Veriforce in 2018, there was no collection of common design patterns or components. 

The UI front-end played a fundamental role in the delay in release of products to the market. UI variations inevitably diluted the brand identity, as the company wrestled with the lack of available front-end engineering talent to keep up with demand connect databases, create the logic, and functionality, and maintain two tech stacks simultaneously. 

Under pressure to accelerate the rollout of the features they promised their clients, Veriforce hired third-party engineering and consulting agencies to augment the engineering and QA teams. Despite the extra overhead to increase time to market, the business suffered.

As a byproduct of design inconsistencies and growing tech debt, users complained that the platform was too challenging to learn to use. 

My Role

My Role in this project was to provide the company with UI design patterns, standards and UX guidelines.

User Research

  • UX Audit of the sequence of interactions existing clients and contractors needed to complete basic tasks using VeriSource and Common Hub, and identified the most common tasks and activities contractors and client users performed on the platform, be it managing user work groups or assigning new tasks and documents. 
  • Mapped out entire experience in VeriSource and Common Hub environments after observing a small set of novice users try to complete key processes. Used session screenshots to show all the defects users encountered in the production environment to the product management teammates.
  • Retired the low-engagement UI designs that did not conform to web application design conventions.
  • Developed a list of Veriforce-specific UI Standards and  web accessibility guidelines
  • Curated a list of resources referencing UX Guidelines that were related to SaaS products
  • Ideation, Prototype, and Test developing wireframes and prototypes representing the final UX Standards and markup.
  • Iteration. Review meetings with product leadership on new design patterns and identify new candidates for future adoption. Document new patterns in the system. 

Prototype Evaluation / Implementation Plan

  • UI Component Library 
    • Live code snippets Bootstrap CSS, component, and patterns, describe how they should be applied and when they should be applied.
  • Ux Guidelines
  • Accessibility Guidelines
Design-system button patterns with labeled actions and primary, secondary, and cancel examples.Enlarge

Image preview

CSS variables and a vertical-tabs page template in the design-system prototype.Enlarge

Image preview

Three-part workflow comparing an Axure component library, CSS variables, and the deployed design-system website.Enlarge

Image preview

Solution

A design system to scale design capabilities within Veriforce and save time by serving as a single source of truth for the company's product design and engineering efforts. Reduced time to market on key apps including Project Inspector and Drug Testing. Increased efficiency by helping developers improve communication of UX standards and guidelines among larger or decentralized teams.

Business Impact

  • Improved Developer experience enabling time savings for designers, developers, and product teams and better UX design and code, which improved speed to market on new products and features
  • Scaled UX/UI capability with the latest development technology while translating business and user requirements into Bootstrap CSS code
  • A shared design vision across product and engineering teams led to increased consistency in design code and brand and Increased team communication and collaboration 
  • Byproducts of the design system were more satisfied users and customers