Overview

Goals

  1. Determine the effectiveness of the End-to-end workflow

  2. Determine how changes in the User Interface influence user behavior

  3. Set a usability baseline and attempt to gain a holistic view of the user base and how they leverage the application

Method

Before an in-person user study, each user completed a short survey about their work and familiarity with Earthdata Search. User study sessions consisted of a short Q&A with the user, guided by the survey responses. Users were then instructed to complete a set of 3 scenarios highlighting key areas of the End-to-end workflow. As users completed the scenarios they were instructed to narrate any thoughts they were having as they were interacting with the application.

Participants

  • Amy Steiker - NSIDC

  • Amy Fitzgerrell - NSIDC

  • Sean McCartney - ARSET

  • Jessica Welch - ORNL

  • Danielle Golon - LPDAAC

  • Catalina Oaida - PO.DAAC

  • Matt Tisdale - ASDC

User Tasks

  1. Create a project containing 2 collections using spatial and temporal filters, then customize the project title, as well a data access method, and download the project.

  2. Search for a collection that allows customization, customize the options, and download the project.

  3. Create a project containing 2 collections and remove a collection while on the project page, then download the project.

Findings

Summary

Good

  • All tasks completed by users

  • End-to-end services workflow appeared to be intuitive overall

  • Excitement over improvements to the project workflow

Bad

  • Collection customization options unclear

  • Minor confusion in mechanics of collection customization


End-to-end Workflow

Changes made in the End-to-end workflow were well received. Participants commented that the workflow is “intuitive” and “seems to encourage customization.”

Project Workflow

Users responded well to the changes in the project workflow. Seeing granules, spatial and timeline in a familiar manner on the Project page seemed to improve user confidence. Actions, like renaming and removing collections, were familiar and intuitive.

Collection Customization Options

Users were routinely expecting more detailed information about what sorts of customizations could be made prior to adding the collection to a project from both the search results as well as the granules or collection details panels.

Collection Customization Mechanics

Users experienced apparent confusion around the mechanics of the customizing a collection on the project page.

Next Steps

  • Identify critical issues and file tickets in Jira

  • Refine the design of collection customization panel

  • Consider improving the display of customization options while searching


Tickets to address findings

Key Summary T Status Resolution
Refresh


  • No labels