NEXTPOINT – IMPORT REDESIGN

Overview

Nextpoint is a cloud-based legal technology platform specializing in eDiscovery and litigation support. The import workflow is a critical part of the platform because it is the entry point for bringing large volumes of case data into the system for downstream review, search, and analysis.

This was my first major project at Nextpoint and one of my earliest opportunities to deeply understand legal workflows, high-volume litigation data handling, and how power users worked under pressure. The existing import experience surfaced friction in several places, especially when users had to interpret incoming files, decide what type of data they were dealing with, and map that data correctly before processing.

In practice, these were not small uploads. Legal teams were often dealing with 100,000+ files at a time, the digital equivalent of truckloads of documents seen in legal dramas, only now compressed into file rooms, load files, metadata, and folders that had to be processed correctly. The redesign focused on reducing cognitive load, improving confidence, and creating a more guided import experience that better matched the realities of legal work.

The project also landed during 2020, when the pandemic accelerated the legal industry’s shift from heavily paper-based workflows toward digital-first tools and remote processing. That broader context made usability, learnability, and workflow clarity even more important for teams adapting to online legal platforms.

GIF from the beta release

Load file mapper

Goals for This Project

  • Simplify the import process to support users with varying levels of technical expertise.
  • Reduce friction in determining what type of data was being imported and how it should be processed.
  • Introduce a guided workflow that reduced errors and improved data mapping accuracy.
  • Improve clarity and navigation across a high-stakes workflow that directly affected downstream review quality.
  • Implement smarter defaults and recommendations based on detected data type.
  • Create a scalable foundation for future enhancements, including load file mapping and metadata overlays.

The Problem

The import workflow sat at the front of a complex legal process, but the experience placed too much burden on users to correctly interpret and configure their data before import. For power users handling large case datasets, even small moments of ambiguity created friction and risk.

One of the biggest pain points was mapping. Users had to understand how different incoming files should be classified, how those file types related to the platform’s structure, and how to map fields correctly so imports would behave as expected. That was especially difficult when dealing with produced data, load files, metadata, and mixed datasets at high volume.

This meant the design challenge was not simply to make the interface look cleaner. It was to reduce the learning curve, lower the chance of costly errors, and make a technically complex workflow feel more understandable and controllable for legal teams working with very large amounts of information.

Research & Strategy

As my first major project at Nextpoint, this became an important entry point for understanding how legal teams actually worked. I used interviews, workflow analysis, and usability testing to learn how power users moved through the import process, where they were getting stuck, and what decisions felt most confusing or highest risk.

This research made it clear that the pain was not only in navigation, but in interpretation. Users needed more support in understanding what kind of data they were importing, what settings were appropriate, and how to map information correctly without feeling like they had to be system experts.

The strategy centered on introducing a more guided experience, bringing important settings into the workflow at the right moment, and creating clearer decision points so users could move through imports with more confidence and less trial and error.

Design Direction

The design direction focused on making the workflow more guided, contextual, and forgiving. Rather than forcing users to jump between disconnected decisions and settings, the redesign introduced a more step-by-step import flow with clearer prompts, validation, and smarter defaults.

A major addition was the mapping wizard, which helped users better understand how incoming files and fields should align to the platform’s structure. This became a key improvement to the flow because it reduced friction around one of the most error-prone parts of importing and made the workflow feel more approachable for both experienced and newer users.

The experience was designed to support both immediate usability gains and future extensibility, creating a stronger base for later improvements such as deeper load file mapping and metadata-driven enhancements.

Impact

The redesigned import workflow improved clarity, reduced user errors, and shortened completion times for data uploads. The addition of guided steps, smarter defaults, and clearer validation helped users move through complex import tasks with greater confidence.

The mapping wizard was particularly valuable in easing one of the most difficult parts of the workflow and was very well received. Overall, the redesign improved import completion time by approximately 50% and reduced the learning curve for newer users while still supporting the needs of experienced legal power users.

The work also created a stronger foundation for future import enhancements and helped Nextpoint better support a legal industry that was rapidly accelerating toward digital workflows in 2020.

My Role

As the Senior UX Designer, I led the end-to-end design process for the import workflow redesign. I collaborated closely with product managers, engineers, and end users to ensure the solution addressed real-world legal workflows and technical constraints.

Methodologies & Responsibilities

  • User Research & Analysis: Conducted interviews and usability testing to identify pain points in the existing import experience and understand how legal power users handled data intake.
  • Workflow Design: Designed a step-by-step guided import flow with clearer prompts, validation states, and decision points.
  • Interface Design: Created wireframes and high-fidelity prototypes focused on clarity, confidence, and error prevention.
  • Mapping Experience Design: Helped shape the mapping wizard to make file and field mapping more understandable and less error-prone.
  • Iterative Testing: Ran multiple rounds of usability testing to refine interactions based on real-world usage.
  • Cross-functional Collaboration: Partnered with engineering and product teams to ensure smooth integration into the existing platform.

Key Features Introduced

  • Guided Import Workflow: A multi-step process that walks users through data selection, configuration, and confirmation, reducing errors.
  • Smart Defaults: Automatic recommendations for settings such as deduplication and DeNIST based on detected data types.
  • Load File Mapper / Mapping Wizard: A more intuitive interface for mapping DAT and CSV fields to platform schema, with validation and clearer guidance.
  • Enhanced Error Handling: Clear, actionable validation messages that help users resolve issues quickly and confidently.
  • File Room Entry Point Improvements: A more direct path from file storage into the guided import workflow.

Learnings & What I’d Do Next

This project reinforced how important it is to understand expert workflows before trying to simplify them. Legal power users were not struggling because they lacked domain knowledge. They were struggling because the product was asking them to translate that knowledge into a workflow that did not give enough guidance at the right moments.

It also showed the value of reducing cognitive load in high-consequence workflows. Making the process more guided did not reduce power. It made that power more accessible, especially for users who were newer to digital legal platforms.

If this work were to continue, I would focus on:

  • Mapping Confidence: Continue improving previews, examples, and validation around field mapping so users can catch issues even earlier.
  • Progressive Complexity: Better layer advanced options so new users are not overwhelmed while experienced users still retain speed and flexibility.
  • Workflow Continuity: Strengthen visibility into what happens after import so the connection between setup decisions and downstream outcomes is clearer.
  • Bulk Pattern Recognition: Explore smarter system assistance for recurring import patterns, especially for repeat legal workflows and similar data types.
  • Onboarding Support: Further reduce the learning curve for teams newly transitioning into digital-first litigation workflows.

Tools

Design and Research:

Figma, Sketch, Zeplin, UserTesting.com, Mural

Communication:

Slack, Zoom, Jira, Confluence