top of page

Viewpoint Legacy

Review – 2.png

Overview

 

The Viewpoint eDiscovery platform is a comprehensive solution for legal and compliance document review, combining advanced analytics with an intuitive user experience to support litigation, investigations, and regulatory workflows. The platform includes a modern, web-based application alongside two legacy on-premise products, Review and Processing, with the long-term goal of consolidating all functionality into the browser-based Web platform. This transition is incremental and requires careful planning to maintain user continuity.

​

Viewpoint Review, the most widely used product in the suite, is also the most outdated, presenting a significant usability and design gap compared to the Web experience. Users encountered inconsistent workflows, legacy UI patterns, and limited accessibility compliance. The challenge was to modernize the interface, bridge the gap between the on-premise and Web platforms, and improve usability,while working within the constraints of an aging technology stack and limited development resources.

​

This effort required balancing design modernization with practical implementation considerations, ensuring continuity for existing users while supporting a gradual transition to the next-generation Web platform. My work focused on creating a scalable, accessible, and visually consistent UI that could be efficiently developed and deployed. To achieve this, I conducted comprehensive design audits to identify inconsistencies and accessibility gaps, then developed user flows and wireframes to streamline workflows and clarify layouts. I reorganized navigation and action menus, prioritized high-frequency actions through improved visual hierarchy, and created interactive prototypes to gather iterative feedback from stakeholders and developers. All design decisions were documented in epics to guide development, and a final post-QA audit ensured the implemented UI aligned with design standards, accessibility requirements, and user needs. This update needed to be addressed in two stages:

Modernize (Low Risk / High Impact)
  • Update typography, spacing, and color usage to align with the Web UI design system

  • Standardize core UI components (buttons, inputs, tables, modals) using shared visual patterns

  • Improve visual hierarchy to highlight primary actions and reduce cognitive load

  • Simplify layouts by grouping related controls and removing redundant or low-usage elements

  • Improve accessibility where feasible (contrast, focus states, readable font sizes, keyboard navigation)

  • Clarify labels, terminology, and microcopy to match Web UI language

Bridge (Parity Without Backend Changes)
  • Align navigation structure and menu organization with the Web UI where technically possible

  • Match placement and prominence of primary actions to reduce relearning during migration

  • Reorganize workflows visually without altering underlying system logic

  • Add inline guidance, tooltips, and messaging to clarify legacy behaviors

  • Improve error and system messaging for clarity and consistency with the Web UI

  • Ensure visual and interaction consistency across Review and Processing modules

To ensure this work delivered meaningful improvements without creating unnecessary risk, clear constraints and a disciplined execution process were established from the outset. By defining what to intentionally avoid, the team prevented over-investment in a legacy platform and maintained alignment with the future Web UI. A structured, collaborative execution and validation approach, grounded in documentation and cross-functional review, ensured that all changes were practical, buildable, and measurably improved usability while preserving continuity for existing users.

Intentional Constraints and What to Avoid
  • Do not introduce new workflows or features that will not exist in the Web UI

  • Avoid backend-dependent interactions that exceed legacy technical capabilities

  • Limit enhancements to shared, reusable components rather than one-off custom designs

  • Do not over-invest in complex UI patterns that cannot be carried forward

  • Defer advanced accessibility features requiring backend changes until Web migration

Execution and Validation
  • Conduct UI and accessibility audits to identify inconsistencies and high-impact opportunities

  • Define user flows and wireframes for priority tasks only

  • Create interactive prototypes to validate changes with stakeholders and developers

  • Document design decisions and constraints clearly in epics and tickets

  • Perform post-QA audits to ensure implementation matches design intent and usability goals

Markup.png
Chart 2.png

UI Modernization and Transition Flow

​

An evaluation of the legacy product interface revealed several usability challenges and design shortcomings that were negatively impacting user efficiency, accessibility, and visual consistency. To address the identified usability and design issues, I led a series of focused design initiatives to improve consistency, accessibility, and workflow efficiency:

Identify Context and Constraints
  • Confirm product is legacy on-prem with planned sunset

  • Validate that Web UI is the long-term target

  • Document backend and resource limitations

 
Gather Research Inputs
  • Review user feedback, support tickets, and usage data

  • Conduct UI and accessibility audits

  • Compare on-prem UI against Web UI patterns

  • Collect stakeholder and engineering constraints

​

Identify High-frequency Workflows and Pain Points
  • Flag outdated UI patterns and accessibility gaps

  • Document inconsistencies between on-prem and Web UI

  • Prioritize issues based on user impact and effort

  • Classify Actions

 

Modernize (Low Risk and High Impact)
  • Update visual hierarchy, spacing, typography, and color

  • Standardize core UI components to align with Web UI

  • Simplify layouts and reduce visual clutter

  • Improve accessibility within technical constraints

 

Bridge (Parity Without Backend Changes)
  • Align navigation structure with Web UI where possible

  • Match placement and prominence of primary actions

  • Reorganize screens visually without altering logic

  • Update terminology and microcopy for consistency

Design and Validation
  • Create user flows and wireframes for priority tasks

  • Build interactive prototypes

  • Review designs with stakeholders and developers

  • Iterate based on feasibility and feedback

 

Documentation and Handoff
  • Document design decisions and constraints in epics

  • Provide clear specs and behaviors for development

  • Align with QA on validation criteria

 

Implementation Review
  • Conduct post-QA UI audit

  • Validate accessibility, consistency, and usability

  • Confirm alignment with Web UI patterns

 

Outcome
  • Improved usability for current users

  • Reduced relearning during Web migration

  • Modernized UI without over-investment

  • Stable, scalable transition path forward

The UI modernization and transition work resulted in a more intuitive, visually cohesive, and accessible on-prem experience that aligns closely with the future Web platform. By systematically addressing high-impact usability issues, standardizing components, clarifying workflows, and aligning visual and interaction patterns with Web UI standards, the project reduced cognitive load, minimized user frustration, and improved task efficiency. Intentional constraints ensured no new unsupported workflows were introduced, preserving continuity for existing users while providing a scalable foundation for migration. Clear documentation, iterative validation, and cross-functional collaboration ensured that all improvements were feasible, consistent, and measurable, ultimately enhancing usability, reducing support needs, and smoothing the path toward full Web parity.

© 2026 Elisabeth Larkin-Gorman

bottom of page