The Johan Sverdrup oil platform in the North Sea at dusk

EQUINOR · 2023–2024 · SENIOR PRODUCT DESIGNER

Modernising liquids trading for a global energy company

Modernising liquids trading for a global energy company

Modernising liquids trading for a global energy company

5x

5x

faster access to cargo data

100+

100+

people involved

30

30

interviews

Overview

Equinor’s liquids traders worked in tools from the 1990s, after two failed attempts to modernise them. I led Discover and Define for the whole liquids value chain, then designed the cargo operations hub inside a new role-based trading platform.

Equinor’s liquids traders worked in tools from the 1990s, after two failed attempts to modernise them. I led Discover and Define for the whole liquids value chain, then designed the cargo operations hub inside a new role-based trading platform.

Role

Senior Product Designer, via Olavstoppen

Senior Product Designer, via Olavstoppen

Timeline

2023–2024

2023–2024

Responsibilities

Research lead, client management, product design

Research lead, client management, product design

Research lead, client management, product design

01

The challenge

The challenge

Leadership and employees had different ideas about what needed to change, and development had started before anyone agreed on what to build. The domain was complex too: dozens of roles, each with its own workflow, all depending on each other.


Old tools. The core trading systems dated from the 1990s.


Two failed attempts. Earlier modernisation projects had stalled.


High stakes. Billions in annual revenue ran through these workflows.

Leadership and employees had different ideas about what needed to change, and development had started before anyone agreed on what to build. The domain was complex too: dozens of roles, each with its own workflow, all depending on each other.


Old tools. The core trading systems dated from the 1990s.


Two failed attempts. Earlier modernisation projects had stalled.


High stakes. Billions in annual revenue ran through these workflows.

Five problem areas: fragmented and outdated tools, siloed data, an inflexible architecture, outdated technology and inefficient processes

02

Discover

Discover

I started with the full picture and worked down, from boulders to rocks to pebbles. Through workshops I built an ecosystem map of every role in the liquids value chain, then drilled into AS-IS journey maps for each key role.


The key artefact. The journey maps did the most work in the project. They guided the interviews, aligned leadership and became the base for everything that followed.


What we delivered. An ecosystem map, AS-IS journey maps and a discovery report with key findings, in 14 weeks.

I started with the full picture and worked down, from boulders to rocks to pebbles. Through workshops I built an ecosystem map of every role in the liquids value chain, then drilled into AS-IS journey maps for each key role.


The key artefact. The journey maps did the most work in the project. They guided the interviews, aligned leadership and became the base for everything that followed.


What we delivered. An ecosystem map, AS-IS journey maps and a discovery report with key findings, in 14 weeks.

30

30

interviews

15

15

workshops

5

shadowing sessions

100+

people involved

Ecosystem map of every role in the liquids value chain, from trading through logistics to back office
Value chain journey map across planning, trading, operations and reporting

03

Key findings

Key findings

Each key finding grouped pain points and opportunities that shared a root cause across the value chain journey map.


Fourteen findings. From system fragmentation and poor collaboration to data quality and missing automation.


Different needs. Traders want control early in a deal, operators need flexibility while it runs, and accounting needs clarity at the end.


Together they set the direction for the Define phase.

Each key finding grouped pain points and opportunities that shared a root cause across the value chain journey map.


Fourteen findings. From system fragmentation and poor collaboration to data quality and missing automation.


Different needs. Traders want control early in a deal, operators need flexibility while it runs, and accounting needs clarity at the end.


Together they set the direction for the Define phase.

Summary of the 14 key findings, from system fragmentation to data quality
Chart of how uncertainty falls over a cargo's lifecycle and what each role needs along the way

04

Define

Define

Building on the findings, we ran a 45-person workshop to design the to-be map for Liquids & Shipping, using round-robin and brand-swap exercises. We ran several tables at once and kept the group away from the app-and-AI trap.


The northstar. One central hub where every role, from traders to cargo operations, risk and back office, works on the same platform, each with a dashboard shaped by their responsibilities.


For the product teams. Functional requirements written as user stories, so each team could start building.

Building on the findings, we ran a 45-person workshop to design the to-be map for Liquids & Shipping, using round-robin and brand-swap exercises. We ran several tables at once and kept the group away from the app-and-AI trap.


The northstar. One central hub where every role, from traders to cargo operations, risk and back office, works on the same platform, each with a dashboard shaped by their responsibilities.


For the product teams. Functional requirements written as user stories, so each team could start building.

Workshop tables mapping the future state with sticky notes
Facilitators presenting to workshop participants
To-be service blueprint for Liquids & Shipping, from forecast to monitoring

05

Design & Deliver

Design & Deliver

The user stories were split across product teams, one per role area. I led the Cargo Operations stream.


I ran weekly user syncs to test solutions and gather feedback, and followed Equinor’s design system so every team’s work stayed consistent.


“I have been waiting for an overview like this since I joined.” A cargo operator with 10 years’ experience, on the new table, map and timeline views.

The user stories were split across product teams, one per role area. I led the Cargo Operations stream.


I ran weekly user syncs to test solutions and gather feedback, and followed Equinor’s design system so every team’s work stayed consistent.


“I have been waiting for an overview like this since I joined.” A cargo operator with 10 years’ experience, on the new table, map and timeline views.

Team structure: one product team per role area along the liquids value chain, with Paul in the cargo operator team
List of cargoes with status and key dates
Movements view of a crude cargo, noting that inspection data was imported
Cargo details form with inline warnings on missing fields
Movements view flagging a delivery range that must be filled within three days
Animated walkthrough of the cargo operations hub, from the cargo list to cargo details

06

What changed

What changed

5x

5x

FASTER ACCESS TO CRITICAL CARGO INFORMATION

Cargo operators got one place to work, built around their role.


Profile hub. Each user sees the domain information that matters to their role.


Automation. The platform maps optimal routes and makes recommendations.


A shared direction. A northstar and requirements that every product team builds towards.

Cargo operators got one place to work, built around their role.


Profile hub. Each user sees the domain information that matters to their role.


Automation. The platform maps optimal routes and makes recommendations.


A shared direction. A northstar and requirements that every product team builds towards.