Viewpoint Legacy

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 releases with a focus on highest impact and available resources.

Actions Taken

To address these challenges, I led a structured modernization effort grounded in research, system analysis, and iterative validation. The work was organized into four key action areas:

Conducted UI audits and analyzed Review and Processing modules to identify usability and consistency issues.
Reviewed user feedback, support tickets, and usage data to surface key pain points and workflow friction.
Identified high-frequency tasks and mapped inconsistencies between legacy UI and the modern Web design system.
Evaluated accessibility gaps against WCAG standards and aligned findings with technical and engineering constraints.

Modernized UI foundations by updating typography, spacing, color, and standardizing core components.
Improved usability by refining visual hierarchy, reducing clutter, and increasing accessibility within platform limitations.
Aligned navigation and workflow structure with Web UI patterns while maintaining existing backend logic.
Enhanced clarity and consistency through updated messaging, tooltips, and standardized interaction patterns across modules.

RICE Prioritization

The following RICE assessments illustrate how I evaluated and prioritized initiatives based on user impact, supporting research, implementation effort, and strategic value.

Align navigation structure with Web UI (4.14)

Reach (10/10)

Every screen, workflow, and future feature relied on the shared component library and UI guidelines.

Impact (2.5)

Improved design consistency, accessibility compliance, development efficiency, and long-term maintainability across the platform.

Confidence (95%)

Supported by interface audits, accessibility reviews, engineering collaboration, and repeated implementation across multiple projects.

Effort (7)

Required extensive auditing, documentation, component creation, and cross-functional adoption.

Match placement of primary actions (4.14)

Reach (10/10)

Every screen, workflow, and future feature relied on the shared component library and UI guidelines.

Impact (2.5)

Improved design consistency, accessibility compliance, development efficiency, and long-term maintainability across the platform.

Confidence (95%)

Supported by interface audits, accessibility reviews, engineering collaboration, and repeated implementation across multiple projects.

Effort (7)

Required extensive auditing, documentation, component creation, and cross-functional adoption.

Reorganize workflows visually (3.9)

Reach (10/10)

Every screen, workflow, and future feature relied on the shared component library and UI guidelines.

Impact (2.5)

Improved design consistency, accessibility compliance, development efficiency, and long-term maintainability across the platform.

Confidence (95%)

Supported by interface audits, accessibility reviews, engineering collaboration, and repeated implementation across multiple projects.

Effort (7)

Required extensive auditing, documentation, component creation, and cross-functional adoption.

Inline guidance and tooltips (3.69)

Reach (10/10)

Every screen, workflow, and future feature relied on the shared component library and UI guidelines.

Impact (2.5)

Improved design consistency, accessibility compliance, development efficiency, and long-term maintainability across the platform.

Confidence (95%)

Supported by interface audits, accessibility reviews, engineering collaboration, and repeated implementation across multiple projects.

Effort (7)

Required extensive auditing, documentation, component creation, and cross-functional adoption.

Error and system messaging improvements (3.60)

Reach (10/10)

Every screen, workflow, and future feature relied on the shared component library and UI guidelines.

Impact (2.5)

Improved design consistency, accessibility compliance, development efficiency, and long-term maintainability across the platform.

Confidence (95%)

Supported by interface audits, accessibility reviews, engineering collaboration, and repeated implementation across multiple projects.

Effort (7)

Required extensive auditing, documentation, component creation, and cross-functional adoption.

Cross-module consistency alignment (2.57)

Reach (10/10)
Every screen, workflow, and future feature relied on the shared component library and UI guidelines.

Impact (2.5)

Improved design consistency, accessibility compliance, development efficiency, and long-term maintainability across the platform.

Confidence (95%)

Supported by interface audits, accessibility reviews, engineering collaboration, and repeated implementation across multiple projects.

Effort (7)

Required extensive auditing, documentation, component creation, and cross-functional adoption.

Prioritization Summary

The work clusters into a clear hierarchy based on user impact, migration risk reduction, and implementation effort. Prioritization favors initiatives that most directly improve day-to-day usability in high-frequency workflows and reduce cognitive friction during the transition from legacy Review to the eDiscovery platform. These were then grouped into two releases:

Release 1

Workflow clarity (highest impact on daily use)

Align navigation structure and menu organization with eDiscovery UI.
Match placement and prominence of primary actions.
Reorganize workflows visually without changing backend logic.
Add inline guidance, tooltips, and messaging to clarify legacy behaviors.
Improve error and system messaging for clarity and consistency with eDiscovery UI.

Release 2

System-wide consistency (foundational, longer-term value)

Ensure visual and interaction consistency across Review and Processing modules.
Establish long-term UI consistency across the platform.
Reinforce design system alignment and improving scalability across modules.

Document Review

Email Analyzer

Document Review, Old UI

Dashboard, Old UI

Email Analyzer, Old UI

1/1

Release 1: Core Workflow and Interaction Alignment

Overview

This release focuses on improving the core usability of the legacy Review experience by aligning navigation, actions, and workflow structures with the modern eDiscovery UI. The goal is to reduce cognitive friction during high-frequency tasks and support a smoother transition between legacy and Web-based experiences without modifying backend logic.

Problem Statement

Users interacting with the legacy system experience confusion and inefficiency due to inconsistent interaction patterns, unclear action placement, and misaligned navigation structures compared to the Web platform. These issues increase cognitive load, slow task completion, and require users to repeatedly reinterpret system behavior.

Strategic Rationale

This release was prioritized because it directly impacts how users complete daily tasks across the platform. By aligning navigation, actions, and workflow presentation with established eDiscovery UI patterns, the system reduces relearning costs and improves task efficiency during the migration period. These changes deliver immediate usability improvements without requiring backend modification.

Proposed Framework

A structured UI alignment framework that focused on improving navigation, action hierarchy, and workflow clarity while maintaining existing backend logic and system constraints.

Align navigation structure and menu organization with eDiscovery UI patterns.
Match placement and prominence of primary actions to reduce relearning.
Reorganize workflows visually without changing backend logic.

Add inline guidance, tooltips, and messaging to clarify legacy behaviors.
Improve error and system messaging for clarity and consistency with eDiscovery UI.

Validation Approach

Validation was conducted through iterative usability testing, prototype reviews, and cross-functional stakeholder feedback to ensure improvements were both feasible and effective within legacy system limitations.

Usability testing focused on task completion and navigation clarity.
Prototype validation of updated workflows and interaction patterns.

Stakeholder and engineering review for feasibility within constraints.
Iterative refinement based on QA feedback and edge-case behavior.

Outcome Goals

This release was expected to improve task efficiency, reduce cognitive load, and increase alignment with the eDiscovery UI, resulting in a more intuitive and consistent user experience across core workflows.

Reduce cognitive load during core workflows.
Improve task completion speed and accuracy.
Decrease user confusion when transitioning between systems.

Increase consistency with eDiscovery UI interaction patterns.
Improve clarity of system behavior and error states.

Summary

Release 1 delivers immediate, high-impact usability improvements by aligning how users navigate, act, and interpret system behavior. It serves as the primary driver of migration readiness and day-to-day workflow efficiency improvements.

Release 2: System Consistency and Cross-Module Standardization

Overview

This release focuses on improving visual and interaction consistency across the Review and Processing modules. While Release 1 addresses core workflow alignment, this phase ensures that improvements are standardized across the broader system to reduce fragmentation and improve long-term maintainability.

Problem Statement

Inconsistencies between modules create a fragmented user experience, where similar actions behave or appear differently depending on context. This increases cognitive load, reduces predictability, and undermines the effectiveness of prior UI modernization efforts.

Strategic Rationale

This release was prioritized to ensure that improvements introduced in earlier phases scale across the entire product ecosystem. Without cross-module consistency, users continue to experience variability in interaction patterns, reducing the effectiveness of navigation and workflow standardization efforts.

Proposed Framework

Establish a unified design framework that ensures visual and interaction consistency across both the Review and Processing modules. Standardize navigation, layouts, components, terminology, and user workflows to create a cohesive experience, reduce cognitive load, shorten onboarding time, and enable users to move seamlessly between modules while improving long-term scalability and maintainability.

Validation Approach

These changes were validated through iterative usability testing, stakeholder review, and QA feedback to ensure feasibility, consistency with system constraints, and measurable improvements in user experience.

Cross-module UI audits to identify inconsistencies.
Comparative analysis of interaction patterns across workflows.

Stakeholder validation of consistency standards.
QA review to ensure uniform implementation across modules.

Outcome Goals

The intended outcomes of this release focused on improving usability, reducing cognitive load, and ensuring consistent interaction patterns that support efficient task completion and a smoother transition toward the Web platform.

Improve consistency across all modules.
Reduce user confusion caused by inconsistent patterns
Strengthen alignment with Web UI design system.

Improve maintainability of UI standards across teams.
Support long-term scalability of the platform.

Summary

Release 2 establishes system-wide consistency across modules, ensuring that UI improvements are not isolated but instead reinforced across the entire platform. This creates a more predictable, scalable, and maintainable experience that supports long-term product evolution.