animallives.org

Animallives.org is a web application developed by Yale and NASA for scientists to track the movement of animal lives around the world. I worked alongside 3 other product designers to identify the animallives.org target audience and build a working high fidelity prototype for the next stage of development. We wore many hats as product designers for this project, working on research, information architecture, UX design, storytelling, and UI design.

Client

Yale University, NASA

Project type

Product Design

Timeline

8 months

Year

2023

Go to Process Deck Slides
animallives.org

Project Overview

Follow the lives of animals in easy, beautiful, and meaningful ways.

There is a wide breadth of animal tracking data available to scientists in large sets, but the data is often displayed in ways which lack beauty and meaningful interactions. Animallives.org aims to be the solution by presenting this data in beautiful, organized, and personalized ways to inform policy and scientific research. The Yale Center for Biodiversity and Global Change in conjunction with NASA partnered with user experience collaborators to aid in the re-imagining of the site.

Client Goals

"Identify the animallives.org target audience".
“Create a website centered around animal movement data representations that are clear, credible, aesthetically appealing, and readily actionable by users.”

Team photos! I knew little about wildlife conservation before this project, but since completion I've become emotionally invested in the issue. I credit the passionate scientists and researchers I got to work with.

Results

At handoff, we left our clients with reports, prototypes, and mockups to empower their next stage of development.

Key features mockup
Design specifications document for web developers
High-level interaction map

Research

Approach

Our team was unfamiliar with the wildlife research field. Research helped us understand the field, target animallives.org users, and  understand their needs, behaviors, and preferences.

Goals

1. Determine what our target users want from animallives.org, especially in relation to other sites and tools they might already be using to work within this problem space.

2. Extrapolate what those users might want but don’t yet realize they do given their current behaviors.

Questions

We refined our research goals into a set of clear and precise research questions that directly address our project goals:

  1. What do stakeholders expect to find on geo tracking data websites?
  2. What geotracking data is most important to stakeholders?
  3. What do our stakeholders love, if anything, about our competitors?
  4. How do research methods vary between stakeholders and projects?
  5. What is the most difficult part of animal tracking research and what can we do to help?​

Answering these research questions helped to define what terms from our project goals like “clear”, “aesthetically appealing”, and “readily actionable” mean in the context of our users and their work.

Stakeholder interviews

ur user interviews have were the backbone of our user research and by extent our product design; They have confirmed and denied some initial assumptions as well as uncovered unexpected user data trends.

We interviewed 7 participants, with a range of professions that were relevant to this project.

Affinity Mapping

We grouped quotes from each participant and found commonalities in their tone of speech, possible features, participant frustrations, goals and more. This helped us better specify our target user group by clearly sorting which themes from our interviews we could best focus on.

Key Findings

  • Few scientists use or know about geo mapping data visualization services like animallives.org and MoveBank. Currently, literature and online databases are the central place wildlife managers go.
  • We found mixed reactions on the use of citizen science within data collection platforms.
  • In design phase, find ways to creatively visualize data & prioritize storytelling within data visualizations.

Personas

Wildlife biologists
Land managers

Journey Map

To better understand our target audience, the user journey below takes us through a typical work week for Lara (a fictional wildlife biologist with similarities to our interviewees) and how animallives.org can fit in with her existing work patterns.

Competitor Analysis

We conducted a competitor analysis to better understand what product niche we can best fit into as well as what features to focus on developing first versus later. We were curious to see what features our competitors offered, and how. We  gathered images and specific design details from each platform to cross-reference all of them in a table

We wanted to present our findings in creative and stimulating ways to our client. This radar chart cross-references competitor strengths and focuses of our competitors. More importantly, it highlights  niche opportunities where they focus less.

UX Requirements Document

To Prepare for the upcoming design phase, we compared the needs and wants of users from our interviews with existing features on competitor sites to determine the “must have” and “nice to have” UX feature requirements.

Design

Organization for Early Ideating

We kicked off the design phase by creating a Figma file for our UX requirement document to organize research insights and future wireframes.

Interaction Map Flow

We constructed an interaction map flow to blueprint the app architecture. The Landing Page, Search, Explore, and Dashboard were the main page focuses.

Low-fidelity / Sketch Mockups

Iteration Progressions

We produced low, mid, and high fidelity mockups throughout our design process. Above is an iteration progression for our Species page. More details on these phases are covered in the process slides.

High Fidelity Mockups

We ultimately suggested a minimalist UI to "frame" beautiful data visualizations.

Design Rationale Document

We created a design rationale document to report  how research data rationalized design decisions. This report document highlighted our user-centric approach to the design phase, and our in depth competitive research.

UX Specifications Document

To aid developers in building the prototype, we developed a UX specification that covers all screens. This report is extremely detailed and intended to be used by web developers when designing the front end of animallives.org. For organization, we have included this in the appendix.

Usability Testing

Validation

We validated our designs by conducting virtual Zoom usability tests with our Animal Lives High Fidelity Mockup Prototypes using Figma in comparison with two competitor sites (Map of Life and Audubon Explorer). Here we compared the efficiency and excitement of our stakeholders using our prototype. This allowed for us to observe how efficiently and accurately users find information through Animal Lives so we can best receive feedback and make our final design. 

A/B Testing

Towards the end of our iterative testing phase, we ideated a new style of search based on more competitive research. We hypothesized that this new style of search would be even more intuitive than moving the “cart/backpack” to the right of the screen, because it “previewed” how data cards would appear on the map more accurately. 

Statistics and Analysis Report

After analyzing our usability testing data, we confirmed our hypothesis. We also confirmed that the app flow of animallives.org was simpler and more exciting for participants than competitor app flows.

Next Steps

Final Recommendations

Gain user trust by building a reputation for data transparency
  • Scientists we spoke with during our user research phase care a lot about data credibility. Make sure to be overly transparent about the animallive.org data modeling methodology, organization goals, and data sources for scientists who are skeptical of the webtool or the ethics of the organization and data collection strategies.
  • This content should be displayed on the landing page primarily, but should also be accessible on the webtool (ie. consider placing hyperlinks under “learn more” buttons that bring users to pdfs of data collection methodology).
Educate new users on how to use animallives.org
  • Tooltips, tutorial videos, and FAQ pages are extremely effective ways to guide new users through complex applications. We did not include these details in our prototypes, but web developers should take careful consideration of these features. Attention to new user education will drastically improve the animallives.org user experience, and may set the web tool apart from competitors in the field who do little to educate new users on how to use their tools. Keep in mind that first impressions are extremely important in UX design.
Make your complex application inviting with a landing page
  • Complex applications (photoshop, webflow, figma, etc) are extremely overwhelming for new users. We recommend Animallives.org use a landing page to invite new users who might not know what the webtool is, why it exists, or how it should be used. The landing page should be aesthetically pleasing and quick to navigate – do not expect users to spend more than 60 seconds on the landing page.
Set animallives.org apart from competitors with quicker performance
  • While we did not formally note this during our user testing and other stages as it is not relevant to a visual prototype, it was clear to our test participants, our client and ourselves that one of the most visible diminishing factors of our competitors’ user experiences was the long loading times of their web tools. Because it is being developed anew, animallives.org has the opportunity to set itself apart in a positive way by being the most responsive, quickest-loading web tool in the group of wildlife data mapping tools. 

Bonus!

Following my work with animallives.org, I returned to work as a freelance webdesigner to build the landing page using webflow. Case study coming soon!

Process Deck Slides

Other work