← Back to work

Enterprise tool · UX/Product Design

Making a high-volume research workflow easier to navigate and trust

Making a high-volume research workflow easier to navigate and trust.

  • Search UX
  • Batch Workflows
  • Dense Data
Search and vetting interface with batch upload validation, filters, and dense resultsThe job to be done
The ask

Improve search and results.

What the work revealed

The friction often happened before and after search itself.

Product direction

Design the workflow, not the query box

Strategic summary of the case study: the original request, the system underneath it, what became clear, and the resulting product direction.
My role
UX and product design for a dense, high-volume enterprise workflow.
Scope
Enterprise tool · search, batch workflows, dense data
Context
Supporting / rotating featured · Enterprise tool · UX/Product Design

01 — THE SITUATION

Where the work started.

Analysts needed to conduct consequential research using both individual and high-volume batch searches.

Context

The work included upload, validation, results review, rerunning, exporting, printing, and account management.

Constraints

The experience needed to support repeated work without hiding important detail.

03 — THE REFRAME

The request was the starting point, not the problem.

THE REQUEST

Improve search and results.

Analysts needed to conduct consequential research using both individual and high-volume batch searches.

WHAT BECAME CLEAR

Improve the full analyst workflow around preparing, validating, reviewing, repeating, and acting on research — not only the query box.

02 — Understanding the system

Understanding the system

Search and vetting interface with batch upload validation, filters, and dense results
The job to be done

Seeing the system clearly

  • The end-to-end analyst workflow: prepare, upload, validate, search, review, act, repeat.
  • Single-search and batch paths, which have genuinely different needs.
  • CSV upload and validation states, including partial failure.
  • Result review and the downstream actions findings feed into.

Design the workflow, not the query box

04 — PRODUCT DIRECTION

What that meant for the product

Each insight translated into a clearer product decision.

The friction often happened before and after search itself.

Design around the analyst job-to-be-done rather than isolated pages.

Batch work introduced validation and error-recovery needs that single search did not.

Support clear modes for individual and batch work.

Dense information needed hierarchy, not simplification that removed useful detail.

Make validation states actionable.

Repeated actions had to be efficient and predictable.

Create consistent result-review patterns and repeat actions.

05 — DESIGNING THE EXPERIENCE

Designing the experience

These product decisions became the structure of the experience.

Search and vetting interface with batch upload validation, filters, and dense results
Design the workflow, not the query box
  1. 01Single searchThe fast path for one consequential lookup.
  2. 02Batch uploadPreparing and submitting high-volume research with confidence.
  3. 03Validation and errorsProblems surfaced before analysts commit to processing.
  4. 04Results and filteringDense results with hierarchy, filters, and review state.
  5. 05Result detailEnough provenance to trust and defend a finding.
  6. 06Rerun, export, and printMoving findings into other work products.

06 — DECISIONS & OUTCOME

Key decisions

The product direction came from a few clear commitments about how the system should work.

01

Treat batch as a distinct workflow

Bulk research is not a scaled-up single search; preparation and error handling differ.

02

Surface validation before processing

Analysts should not discover input problems after a long-running job.

03

Preserve density, improve hierarchy

Simplification that removed required detail would have made the tool unusable.

04

Make repeated actions easy to reuse

The same actions happen dozens of times a day and should be predictable.

The result

What changed

01

A clearer end-to-end analyst workflow.

02

More coherent patterns across individual and batch work.

03

An enterprise UX story that demonstrates comfort with consequential, data-heavy tools.

Search is rarely just search. Understanding what people do before the query and after the results is what turns a feature into a usable workflow.

More work