SIREN - protect endangered marine animals

SIREN - protect endangered marine animals

WEB APP / MOBILE APP · B2B · ENVIRONMENTAL

SIREN - protect endangered marine animals

WEB APP / MOBILE APP · B2B · ENVIRONMENTAL

Introduction

Co-designed a new experience that improved clarity and accelerated the validation of observations for two user groups. In Cameroon, megafauna such as whales and sea turtles face threats from poaching, bycatch, and habitat loss.

IMPACT

As of 2022, the SIREN app has facilitated the collection of over 10,000 observations in Cameroon. This extensive data collection has led to the legal protection of five marine mammal species in the region. Siren is used across ~30 countries and is sponsored by National Geographic for three years in a row.

Project timeline

Nov 2023 - May 2023 (11 months)

my role

  • Mobile application and webapp

  • Competitive analysis

  • Heuristic evaluation

  • Redesign

  • Usability testing

Team

  • x3 UX Designers

  • x1 Project Lead

  • x5 Engineers

  • x1 Field Assistant

Tools

Figma
Miro
Gitlab
Slack

The challenge

Inefficient and incomplete tools for marine data documentation and analysis

Inefficient and incomplete tools for marine data documentation and analysis

Fishermen initially recorded data manually. AMMCO built an app and web platform, but it was unintuitive and lacked key features. The goal was to create a user-friendly app for offline data capture and streamline the web app for better usability, accessibility, and data management.

SIREN citizen science project: involvement of fishermen in the conservation of aquatic biodiversity. Source

the solution

The app allows fishermen to report anomalies for research, which are analysed and sent to government bodies to address the issue

The app allows fishermen to report anomalies for research, which are analysed and sent to government bodies to address the issue

We developed an app for fishermen to capture photos of anything unusual, like multiple dead fish in one area. This data is then uploaded through the app and sent to the webapp for analysis by researchers.

We developed an app for fishermen to capture photos of anything unusual, like multiple dead fish in one area. This data is then uploaded through the app and sent to the web app for analysis by researchers.

PROCESS AND INSIGHTS

research

We discovered 2 user groups: fishermen and researchers

We discovered 2 user groups: fishermen and researchers

We conducted primary research with three of our target users - fishermen - and reviewed previous research of the interviews held with the our second target users - researchers. Here’s what we discovered:

design - mobile app

Problem A: Fishermen face time constraints and challenging conditions like wind and low visibility. Designing for scalability: bulk upload and real-time progress tracking

Problem A: Fishermen face time constraints and challenging conditions like wind and low visibility. Designing for scalability: bulk upload and real-time progress tracking

How can we ensure fishermen at sea in windy, rainy, and unfavourable conditions can upload observations as quickly as possible?

With all the necessary preparation in place, I began designing a feature to help fishermen quickly upload observations to the webapp. Previously, users could only upload one observation at a time, which was cumbersome. The new feature streamlines this by allowing multiple observations to be uploaded at once.

Select and upload multiple observations at once

The initial design showed actions like "Upload" and "Delete" in a top bar but lacked a "Cancel" button.

The improved version adds "Cancel" and checkboxes for bulk selection. We replaced the tertiary buttons with icons to enhance usability and quick recognition, accommodating non-native English speakers and challenging fishing conditions. This change helps capture more observations efficiently and saves fishermen time.

Monitor real-time progress

Fishermen need to track uploads, especially with limited connectivity at sea. The initial design used toast notifications, which were easily missed, obstructed the "Add Observation" button, and risked accidental cancellations.

The final design replaced them with a visible circular progress loader and a cancel option for delayed or mistaken uploads.

design - Web app

Problem B: Researchers manage large datasets, but the previous web app lacked essential features like filtering, validation, and search, slowing progress and reducing government resolution of habitat degradation, where time is critical

Problem B: Researchers manage large datasets, but the previous web app lacked essential features like filtering, validation, and search, slowing progress and reducing government resolution of habitat degradation, where time is critical

I conducted a thorough evaluation of the design using Nielsen's 10 usability heuristics, identified areas for improvement, and prioritised issues based on severity using a 0-4 scale to reflect the importance of each issue.

Heuristic analysis of the current platform using a rating scale between 0-4.

0: Not a usability problem; 1: Cosmetic problem; 2: Minor usability problem; 3: Major usability problem (important to fix); 4: Imperative usability problem (must fix)

Evaluating competitor navigation, data presentation, filtering, and map interaction features allowed us to differentiate our products

Evaluating competitor navigation, data presentation, filtering, and map interaction features allowed us to differentiate our products

This project was new territory for our design team, making it challenging to find direct competitors, but we succeeded. We also analysed indirect competitors like Google Maps and Airbnb for valuable insights. I've only written notes for the navigation and table sections.

Analysing the map and list views of both direct and indirect competitors, including examples like iNaturalist, Airbnb, and Global Fishing Watch shown in the picture.

Competitive analysis table. Abbr.: D - direct competitor. I - indirect competitor.

Ideating the solution: We needed an intuitive way to filter, search, and validate observations

Ideating the solution: We needed an intuitive way to filter, search, and validate observations

We then moved on to designing the webapp, which was a highly collaborative effort among all three designers. My contributions focused primarily on the global top navigation, as well as key features within the table and observation modals.

Designing the map and list view involved collaborative discussions, where we explored various options, provided reasoning for our choices, and ultimately reached a consensus.

Improving data discovery through grouping, contextualising, and streamlining filters and search

Improving data discovery through grouping, contextualising, and streamlining filters and search

Researchers focus on observation type, species, and location first. How can we streamline the process to help them quickly locate, review, and validate the right observations while minimising time spent?

We developed the top global navigation for the web app by exploring various design options and gathering feedback from stakeholders. In the final version, we simplified the design by removing unnecessary features. This streamlined the navigation to four key features: filters, search, date, and new observation creating a more intuitive interface.

1: Grouping related elements improves discoverability and reduces cognitive load;
2: Contextualising actions within the table reduces clutter and confusion;
3: Placing Filters and Search together creates a logical flow for quicker data discovery.

DEV handoff

Overcoming remote engineering challenges in Cameroon: Using PDFs instead of Figma for design acceptance criteria

Overcoming remote engineering challenges in Cameroon: Using PDFs instead of Figma for design acceptance criteria

All our software developers were based in Cameroon, which posed challenges due to poor internet connectivity, preventing us from relying solely on Figma for behaviour and component specs. Without a dedicated business analyst, we wrote the acceptance criteria ourselves. To address these issues, we created detailed PDFs to outline the design behaviour and requirements.

usability testing

Usability testing led to retroactive fixes

Usability testing led to retroactive fixes

Usability testing was done post-development to meet the Sea Turtle Convention deadline. Testing earlier could have avoided retroactive fixes and saved time and resources.

Interviews

We had six Zoom interviews with participants from Cameroon and the UAE. The UX team rotated roles as moderators, note-takers, and observers during the remotely moderated, recorded sessions. Each hour-long session was divided into eight sections, focusing on error tracking, impression tasks, and exploratory tasks. Using the "think aloud" protocol, we minimised interaction to observe participants' natural behaviour.

Identifying patterns and prioritising key issues from interview data

We documented interview insights as sticky notes in Miro, initially categorising them by section to capture participant experiences. Next, we rearranged the notes into non-section-specific groups and added problem statements alongside potential solutions for each.


Finally, we prioritised the most significant issues by allocating three stars each to the problems we found most critical.

Findings: Participants struggled with discoverability, findability, and contextual awareness

Findings: Participants struggled with discoverability, findability, and contextual awareness

Coming up with initial suggestions based on insights from the usability sessions

Coming up with initial suggestions based on insights from the usability sessions

Users struggled to find how to switch between map and list view

The drop-down menu was hard to find, making it challenging for users to switch between views. Initially, we experimented with a toggle for switching between map and list views and explored using tabs to organise different observation types for easier access.

The majority of users found it difficult to locate the observation drawer

To improve the findability of mini cards, which previously required users to click the observation button in the toolbar, we implemented a simple, easy-to-develop solution: having the mini cards open by default, inspired by platforms like Airbnb.

Slow loading times with large amounts of data

The map experienced slow loading times for users. To address this, we explored grouping observations into clusters instead of displaying all data simultaneously. This solution is still in progress.

Current: PDF guide; Future: interactive onboarding experience

Current: PDF guide; Future: interactive onboarding experience

We initially aimed to avoid creating a guide/user manual, relying on the web app's intuitiveness. However, we discovered that some users are not as tech-savvy and require instructions. Currently, this is a PDF guide, but in the future, we might transform it into an interactive onboarding experience.

The Word document guide for new users on how to use the web app.

Next steps

Next steps

Fishermen may enter errors like typos, mismatched descriptions, or blurry photos, which researchers must investigate. Artificial Intelligence 🤖 could provide instant species identification and photo quality checks, prompting corrections and saving researchers time, speeding up the process for government review.

Fishermen volunteer to record observations which may affect the quantity and quality of data. To address this, we could introduce gamification strategies 🎯 like leaderboards to showcase top contributors and implement monthly challenges to foster engagement. Partnering with National Geographic could also add value by offering special badges or rewards that recognise their commitment to conservation.

Design active onboarding to replace the user manual.

Reflections

Reflections

This project was incredibly exciting. However, due to budget constraints as an NGO, we had limited resources, resulting in a small development team and a prolonged development process.

The language barrier between the UX team and developers hindered communication, and we primarily relied on the project link for collaboration, a practice we began to change towards the project's conclusion.

Unfortunately, we shipped the product to production without conducting usability tests beforehand. This decision had significant repercussions, as certain elements, such as the toolbar in the map and list view, require a complete redesign.

Pictures from the field

Pictures from the field

Thanks for scrolling all the way!

Thanks for scrolling all the way!

Thanks for scrolling all the way!

Thanks for scrolling all the way!

Thanks for scrolling all the way!

Let's get in touch!

Email↗ / LinkedIn↗ / CV

© 2024 Andrea Munteanu V3.1 — third time’s the charm?

Let's get in touch!

©

Let's get in touch!

Email↗ / LinkedIn↗ / CV

© 2024 Andrea Munteanu V3.1 — third time’s the charm?

Let's get in touch!

©

Let's get in touch!

Email↗ / LinkedIn↗ / CV

© 2024 Andrea Munteanu V3.1 — third time’s the charm?