Ocean By Data case study

Ocean By Data - System and UX architecture

DESCRIPTION :Ocean by Data was designed to be a modern interface for ocean intelligence, but what counts as modern is changing, and fast. The last decade was defined by data visualization platforms, with carefully curated pages, filters, and visual stories that helped people explore data without needing to be experts. That model still matters, and it will remain essential for transparency, accountability, and shared reference. Yet it is increasingly clear that we are entering a new paradigm for data distribution. A paradigm built around conversation rather than navigation, thanks to LLMs.
CHALLENGE : To make the platform adaptive. A conversational layer could guide users to better questions, flag missing context, propose relevant comparisons, and surface uncertainty explicitly. It could help bridge the gap between scientific nuance and policy urgency, offering explanations calibrated to the user’s role while always preserving the underlying sources, assumptions, and methods. In this model, charts and dashboards become the receipts. The conversation produces a claim; the visuals and metadata show how that claim was built. .
NOTE : Some details have been simplified/modified due to NDA.

CONTEXT

CHALLENGES

ROLE & TASKS

CONTEXT

● Ocean data is distributed across multiple platforms such as Copernicus Marine Service, NOAA, and EMODnet.
● Existing platforms often prioritize data access over usability and clarity
● Diverse audience: policy-makers, scientists, NGOs, public
● Increasing need for ocean data in climate and policy decisions

CHALLENGES

● Highly complex and scientific datasets are difficult for non-expert users to interpret.
● Lack of consistent visualization standards across platforms.
● High cognitive load due to fragmented indicators and interfaces.
● To balance scientific accuracy with simplicity.

ROLE & TASKS

Role

Product UX UI Designer

Tasks

● Platform benchmarking and comparative analysis
● Information architecture and visualization strategy
● User flows, dashboards, and indicator views

Research & Structure

User needs and platform observations were used to define a structured approach to organizing and presenting ocean indicators.

Target Audience & User Requirements

User Group	Core Requirements
Policy-makers	High-level executive summaries, trend forecasting, and actionable insights for decision support.
Scientists	Granular access to raw datasets, specialized filtering parameters, and technical metadata documentation.
General Users	Simplified data storytelling through intuitive, high-readability visualizations and interactive infographics.

All groups require high data interpretability despite varying levels of technical expertise.

Strategy & Analysis

The platforms reviewed provide high-quality and scientifically validated data.
The analysis focuses on how this data is structured and presented, rather than the quality of the data itself.

01. Goals

● Simplify access to ocean indicators
● Enable comparison across datasets
● Improve readability of visualizations
● Prioritize interpretation over raw data

02. Benchmark

Comparative analysis:
Copernicus, NOAA, EMODnet, GOOS, OBIS, +10.

FOCUS AREAS:

→ Indicator variety
→ Visualization methods
→ System usability

03. Insight

- Complex ocean data requires gradual exploration
- Users can approach the data from different entry points and levels of detail
- A consistent structure supports understanding across indicators

1. A progressive approach to data exploration.
2. Dedicated flows (Policymakers / Analysts).

Information Architecture

The platform ecosystem is divided into two primary entry points: a Policy Makers Section for high-level summaries and a Tools engine for deep data exploration.

From this point, the architecture branches into two specialized modules: Reports, which apply filters to generate a final Report, and Maps, which use a filtering layer to produce a Result Panel. Supplementary Feed and Alert modules provide real-time updates that interlink directly back to these core outputs.

Navigation Funnel

Both pathways follow a unified functional hierarchy:
Indicator Groups → Indicators → Sub-indicators.

Module Outputs

● Reports: Filtered data → Final Report
● Maps: Filtered data → Result Panel

Supplementary Feed and Alert modules provide real-time updates that interlink directly back to core outputs.

Interface sketches

● Two complementary ways of exploring the data

● User Flow

Design System & Data Visualization

Here are the core UI components along with key data visualizations used in the final report of the indicator.

UI components

Data Visualization

Due to the volume of data, charts are designed as interactive elements rather than static images.

The examples shown are illustrative; in the final system, visualizations are generated from official datasets.

Design Specification & Interaction Documentation

The primary deliverable of this project is a structured design document detailing interaction logic, information architecture, and interface layouts.
The following sections outline key parts of the system, including page structures, interaction patterns, and responsive behavior across desktop and mobile views.