Jua

Jua

Jua

Redesigning how Jua’s AI analyst answers energy traders, so each reply starts with the insight and keeps the data behind it in view.

Redesigning how Jua’s AI analyst answers energy traders, so each reply starts with the insight and keeps the data behind it in view.

← Back

The V2 redesign of an Athena answer on a laptop screen: tomorrow is 4.4 GW windier, with an annotated wind chart, the evening peak and the change by zone.
The V2 redesign of an Athena answer on a laptop screen: tomorrow is 4.4 GW windier, with an annotated wind chart, the evening peak and the change by zone.

An AI analyst for energy traders, redesigned to lead with the insight.

RoleLead Product DesignerTeamJua product team
ScopeResearch to V2 redesign
Research
InterviewsFeedback cadence
Design
UX/UIChat widgets
System
Figma libraryCalm
Stage2 of 5
Concept
Design
Prototype
Beta
Live

V2 redesign of the live Athena app, with demo data.

CompanyJua
Year2026
ToolsFigma, Cursor, Claude

An AI analyst for energy traders, redesigned to lead with the insight.

RoleLead Product DesignerTeamJua product team
ScopeResearch to V2 redesign
Research
InterviewsFeedback cadence
Design
UX/UIChat widgets
System
Figma libraryCalm
Stage2 of 5
Concept
Design
Prototype
Beta
Live

V2 redesign of the live Athena app, with demo data.

CompanyJua
Year2026
ToolsFigma, Cursor, Claude

Helping traders read a changing forecast

Helping traders read a changing forecast

Jua forecasts weather and power for energy markets, and Athena is the AI analyst that traders and meteorologists ask about those forecasts. I joined Jua as Lead Product Designer in February 2026 and worked on Athena until the end of April. The app had grown quickly through vibe-coding in Cursor, without a research, design or implementation process behind it, so it was slow, unstable and expensive to change.

Jua forecasts weather and power for energy markets, and Athena is the AI analyst that traders and meteorologists ask about those forecasts. I joined Jua as Lead Product Designer in February 2026 and worked on Athena until the end of April. The app had grown quickly through vibe-coding in Cursor, without a research, design or implementation process behind it, so it was slow, unstable and expensive to change.

Athena V1 in February 2026: a light interface with the chat on the left and a canvas of wind charts and a pressure map on the right.
Athena V1 in February 2026: a light interface with the chat on the left and a canvas of wind charts and a pressure map on the right.

My contribution

My contribution

At Jua I set up a product design process around application reviews, simplification and user research, and connected what we learned to priorities and the roadmap together with the CPO and CEO. We worked in one-week cycles. I redesigned the UI and UX, kept a modular Figma library, made React prototypes and worked directly in the app with Cursor. I also came up with the idea of putting widgets into Athena’s chat.

At Jua I set up a product design process around application reviews, simplification and user research, and connected what we learned to priorities and the roadmap together with the CPO and CEO. We worked in one-week cycles. I redesigned the UI and UX, kept a modular Figma library, made React prototypes and worked directly in the app with Cursor. I also came up with the idea of putting widgets into Athena’s chat.

After Jua, I took that chat work further in a V2 redesign of Athena’s answers, with its own design system, Calm. I made the V2 redesign with Claude and decided its colour, type and chart treatment. It uses demo data, and this page shows it next to the V1 screens for comparison.

After Jua, I took that chat work further in a V2 redesign of Athena’s answers, with its own design system, Calm. I made the V2 redesign with Claude and decided its colour, type and chart treatment. It uses demo data, and this page shows it next to the V1 screens for comparison.

Starting from the trader’s morning

Starting from the trader’s morning

I ran feedback sessions with energy traders and meteorologists, showed them changes and looked at the tools they already used. A meteorologist described a morning routine of 30 to 40 minutes in which building a dashboard through conversation was too slow, and a familiar view that was ready to read was more useful. Quantitative teams wanted forecasts and history through an API, and used conversation to investigate differences they did not expect. I organised the sessions around our weekly iterations, so each round of feedback shaped the next release.

I ran feedback sessions with energy traders and meteorologists, showed them changes and looked at the tools they already used. A meteorologist described a morning routine of 30 to 40 minutes in which building a dashboard through conversation was too slow, and a familiar view that was ready to read was more useful. Quantitative teams wanted forecasts and history through an API, and used conversation to investigate differences they did not expect. I organised the sessions around our weekly iterations, so each round of feedback shaped the next release.

Listening to users and redesigning around their needs raised perceived usability from 3/10 to an average of 7/10. The research also contributed to closed sales.

Listening to users and redesigning around their needs raised perceived usability from 3/10 to an average of 7/10. The research also contributed to closed sales.

View research session screenshot ↗

Three research findings: mornings need a ready view, production work runs on APIs, and chat is for investigating. Beside them, perceived usability from 3/10 to 7/10 and 55% less legend space.
Three research findings: mornings need a ready view, production work runs on APIs, and chat is for investigating. Beside them, perceived usability from 3/10 to 7/10 and 55% less legend space.

Putting the insight first in the chat

Putting the insight first in the chat

In V1, Athena answered in long, unstructured text with a lot of technical language, which made the main insight slow to find. I came up with the idea of putting charts, tables and interactive widgets into the chat, and shaped the answers so a trader finds the main insight first, can check the data behind it and then ask a focused follow-up.

In V1, Athena answered in long, unstructured text with a lot of technical language, which made the main insight slow to find. I came up with the idea of putting charts, tables and interactive widgets into the chat, and shaped the answers so a trader finds the main insight first, can check the data behind it and then ask a focused follow-up.

The V2 redesign follows one question a power trader might ask on a Thursday morning: what changed in German wind for tomorrow, and what should I watch? Athena answers in one sentence, 4.4 GW windier with the biggest lift in the morning, and places an annotated wind chart, the effect on the evening peak and the change by zone underneath.

The V2 redesign follows one question a power trader might ask on a Thursday morning: what changed in German wind for tomorrow, and what should I watch? Athena answers in one sentence, 4.4 GW windier with the biggest lift in the morning, and places an annotated wind chart, the effect on the evening peak and the change by zone underneath.

A V1 chat answer made of several text messages, next to the same kind of answer in the V2 redesign, which leads with one sentence and shows an annotated wind chart, three numbered points and two small widgets.
A V1 chat answer made of several text messages, next to the same kind of answer in the V2 redesign, which leads with one sentence and shows an annotated wind chart, three numbered points and two small widgets.

Giving larger analysis room on a canvas

Giving larger analysis room on a canvas

V1 already placed widgets on a canvas beside the chat. At Jua I specified that new widgets are added below the existing analysis, sized to their content, and leave the size and position of the others unchanged. In the V2 redesign, the chat builds and edits the canvas, and each numbered point in the answer matches the panel it explains.

V1 already placed widgets on a canvas beside the chat. At Jua I specified that new widgets are added below the existing analysis, sized to their content, and leave the size and position of the others unchanged. In the V2 redesign, the chat builds and edits the canvas, and each numbered point in the answer matches the panel it explains.

The V1 workspace with chat and widgets, next to the canvas in the V2 redesign, where three numbered points in the chat match the wind, residual load and zone panels.
The V1 workspace with chat and widgets, next to the canvas in the V2 redesign, where three numbered points in the chat match the wind, residual load and zone panels.

Comparing models hour by hour

Comparing models hour by hour

Traders compare several model runs at once. In V1 every line carried a long technical label with its model, run time and location, so the legend was hard to scan and took space from the chart. At Jua I grouped the forecasts by model, run and location in an interactive legend, with shorter dates and labels that expand on hover. This cut the vertical space used by legends by 55%.

Traders compare several model runs at once. In V1 every line carried a long technical label with its model, run time and location, so the legend was hard to scan and took space from the chart. At Jua I grouped the forecasts by model, run and location in an interactive legend, with shorter dates and labels that expand on hover. This cut the vertical space used by legends by 55%.

The V2 redesign takes the comparison further by placing wind, regional changes, residual load and model spread on one delivery-hour axis. A trader can follow 18:00 down through every signal and see that the evening relief, residual load falling from 27.1 to 22.7 GW, sits exactly where the models are already 7.2 GW apart.

The V2 redesign takes the comparison further by placing wind, regional changes, residual load and model spread on one delivery-hour axis. A trader can follow 18:00 down through every signal and see that the evening relief, residual load falling from 27.1 to 22.7 GW, sits exactly where the models are already 7.2 GW apart.

A V1 model deviation chart whose legend repeats long labels with model, date, time and location, next to the V2 redesign, which aligns wind, change by zone, residual load and model spread by delivery hour.
A V1 model deviation chart whose legend repeats long labels with model, date, time and location, next to the V2 redesign, which aligns wind, change by zone, residual load and model spread by delivery hour.

Keeping a quick check on the phone

Keeping a quick check on the phone

On a phone, each insight becomes its own card in the thread, led by the value that changed. A follow-up opens the model comparison for the evening, and the trader can set an alert for the next run without leaving the conversation.

On a phone, each insight becomes its own card in the thread, led by the value that changed. A follow-up opens the model comparison for the evening, and the trader can set an alert for the next run without leaving the conversation.

Three phone screens: the answer as cards led by +4.4 GW, the evening peak and model spread, and a follow-up with evening wind by model and an alert for the 12 UTC run.
Three phone screens: the answer as cards led by +4.4 GW, the evening peak and model spread, and a follow-up with evening wind by model and an alert for the 12 UTC run.

Creating Calm for long analytical answers

Creating Calm for long analytical answers

Calm is the design system behind the V2 redesign. It keeps Jua’s pink bright and mixes it into black, dark purple and dark blue for the surfaces. In charts, pink always means the newer run or the change, dashed lilac is the previous run and violet is disagreement between models, so a trader learns the code once and reads it on every screen.

Calm is the design system behind the V2 redesign. It keeps Jua’s pink bright and mixes it into black, dark purple and dark blue for the surfaces. In charts, pink always means the newer run or the change, dashed lilac is the previous run and violet is disagreement between models, so a trader learns the code once and reads it on every screen.

Calm’s accent and surface colours, the table of chart marks and what each one means, and the diverging scale for hourly change by zone.
Calm’s accent and surface colours, the table of chart marks and what each one means, and the diverging scale for hourly change by zone.

Widgets inside the chat have no outlines, and secondary data such as the previous run and the model range stays quieter, so the change itself stands out. I raised the faintest text, such as axis ticks, from about 3:1 to above the usual 4.5:1 contrast on every surface, and kept numbers together with their units.

Widgets inside the chat have no outlines, and secondary data such as the previous run and the model range stays quieter, so the change itself stands out. I raised the faintest text, such as axis ticks, from about 3:1 to above the usual 4.5:1 contrast on every surface, and kept numbers together with their units.

Close-ups of the V2 redesign: the delivery-hour view on a laptop, the evening model spread, and the wind card on a phone.
Close-ups of the V2 redesign: the delivery-hour view on a laptop, the evening model spread, and the wind card on a phone.

Testing the V2 redesign with traders

Testing the V2 redesign with traders

In research, speed remained a concern for time-sensitive morning work, and the V2 redesign does not solve that on its own. The next step is to put these screens in front of traders during their morning routine and see whether an answer that leads with the insight saves them the time a conversation costs.

In research, speed remained a concern for time-sensitive morning work, and the V2 redesign does not solve that on its own. The next step is to put these screens in front of traders during their morning routine and see whether an answer that leads with the insight saves them the time a conversation costs.

The idea of combining conversation with structured choices started earlier, in my KBC appointment-booking concept.

The idea of combining conversation with structured choices started earlier, in my KBC appointment-booking concept.