HumanBuiltAIScott Galetto
Aon/Product design/Data visualization

Rethinking how we see risk.

For Aon, I explored how a traditionally data-heavy climate risk tool could evolve into a modern, visual experience — without sacrificing the complexity underneath.

Climate models are complicated enough. The interface didn’t need to be.

Role
Product / UX / Visual Design
Focus
Data visualization, interaction design, prototyping, AI-assisted exploration
Deliverables
Product concept, wireframes, UI system, interactive states
Platform
Desktop web
Horizon composite risk view, light theme
Composite risk view · Light themeFig. 01
02 — The problem

A lot of important information. Not a lot of breathing room.

Climate-risk products need to communicate several things at once: location, hazard type, severity, time horizon, individual risk factors, and how those risks are changing.

The problem wasn’t a lack of data.

It was helping someone understand what mattered without making them decode the interface first.

COMPOSITE · 203674/100HIGH
WIND88SEVERE
FLOOD81SEVERE
WATER EROSION46MODERATE
CHANGE SINCE 2026+1210-YEAR OUTLOOK
SELECTED SITEMiami, FL25.76°N, 80.19°W
Storm-surge inundation ~9.1 ft @ 1-in-100Design gust 180 mph (3-sec)13 days/yr above 2 in. rainfall~40 km gridhorizon [2026, 2031, 2036]3 of 5 shown
SAMPLE DATA — NOT FOR UNDERWRITING
03 — A little time travel

Before we move forward, let’s go backwards.

To pressure-test the direction, I imagined what the same information might have looked like in an earlier generation of enterprise software: tabs, tables, nested controls, tiny charts and just enough gray chrome to make Windows 95 proud.

NOTE — A speculative, imagined legacy interface. Aon never shipped this. Thankfully, we’ve moved on from Windows 95.

My Risk
Reports
Recycle Bin
Imagined Windows 95-era version of the tool
Start Aon - Site Climate Risk Explorer 4:12 PM
An intentionally exaggerated trip back in time.

The data wasn’t the problem.
Finding the story inside it was.

04 — Information hierarchy

Start with the questions, not the pixels.

The interface was organized around a handful of questions someone brings to a site.

Q1Where is the site?
Q2What kind of risk am I looking at?
Q3How severe is it?
Q4How is it changing?
Q5What is driving the score?
Q6What should I investigate next?
Concept sketches, low-fi, mid-fi and interaction wireframes
Structure before styling — progressively defining hierarchy, states and interaction.Fig. 04
Hand-sketched interface on an iPad, outdoors
MAP = context
PANEL = meaning
TIME = change
ASK = exploration
05 — Sketching the experience

Before it became a system, it was a sketch.

The core layout came together around a simple relationship: geography on one side, explanation on the other. The map gives context; the panel explains what the user is seeing.

Full annotated hand-drawn concept
the whole idea, on one page
06 — The core idea

Make the map
the interface.

Instead of asking users to move between reports, tables and disconnected views, risk becomes spatial. The user can move from the national picture to a specific site without losing context.

Finished dark-mode interface
1 2 3 4
01Interactive geographyPan, zoom and click straight into a site.
02Color-coded severityCell color and size both scale with intensity.
03Site-level detailScore, trend and drivers in the panel.
04Time horizon2026, 2031, 2036 — one click apart.
07 — Visual language

Color has a job.

Risk data has never been accused of being particularly charming, and it shouldn’t be alarming either. The palette needed enough contrast to make patterns visible across thousands of geographic cells, while still supporting labels, charts, selected states and light/dark themes.

0–19Very low 20–39Low 40–59Moderate 60–79High 80–100Severe

The same risk language carries through map cells, scores, bars, badges, tooltips and comparison states.

Map cellsScoresBarsBadgesTooltipsComparison
Component and system exploration
08 — National to local

Zoom out for the pattern. Zoom in for the reason.

At the national level, the map reveals broad patterns. Moving into a hazard layer changes the question from ‘Where is risk concentrated?’ to ‘What is driving risk here?’

Composite national view
AComposite — where is risk concentrated?
Flood hazard, regional focus
BHazard layer — what is driving risk here?
Composite viewHazard-specific viewSite selectionMap tooltipRisk scoreSpecific drivers
09 — Time as interface

Risk isn’t a snapshot.

The horizon control makes time a first-class part of the experience. Rather than burying projections in a report, users can compare how a location changes across 2026, 2031 and 2036.

62→68→74
202620312036
COMPOSITE SCORE, MIAMI · SAMPLE DATA, NOT A FORECAST
Time horizon comparison view
Horizon comparison · same site, three points in timeFig. 09
Search state
10 — Search

Get me to the place I care about.

A map is great for discovery. Search is better when you already know where you’re going. It works as a direct entry point into the visualization, so nobody has to pan across a continent to find one building.

11 — Asking the data

And sometimes you just want to ask.

Not every user wants to interpret a legend, compare four hazard bars and mentally summarize a trend line. The conversational layer gives the data another interface: natural language. It sits on top of the same structured scores and drivers — an explanatory layer, not a replacement for the map.

Conversational AI interaction in use
Example prompts
“What drives the score for Miami?”
“How does it compare to Houston?”
“What changes by 2036?”

The visualization shows you what’s happening. The conversation helps explain why.

One product. Two very different moods.

Both themes share one semantic risk system. Surfaces, contrast and the direction of the ramp adapt so severe still reads as severe — whether the map sits on paper-white or near-black.

Light theme
Light
Dark theme
Dark
13 — Final experience

From data-heavy tool to explorable system.

The final concept brings location, hazard, time, comparison and explanation into one environment — allowing someone to move from ‘What am I looking at?’ to ‘Why does this matter?’ without leaving the experience.

Don’t take my word for it. Try it. Live prototype
Search a city · switch hazards · change the horizon · ask about the data Open in new tab ↗ Best on desktop
Hazard focus
Chat in use, vertical crop
Horizon comparison detail
Dark mode
Search
Hazard focus · Ask about this data · Horizon comparison · Dark mode · Search
14 — Reflection

The best visualization doesn’t simplify the data. It simplifies getting to the point.

This project was less about making climate risk look beautiful and more about making complexity navigable. The strongest design decisions came from deciding what should remain visible, what could wait, and how geography, time and explanation could work together rather than compete.

It also reminded me why I enjoy prototyping complex systems: somewhere between the raw data and the finished interface is a moment where something difficult suddenly makes sense.