//Case study / Weather Guarantee

//Case study / Weather Guarantee

Weather Guarantee

Weather Guarantee

Weather Guarantee

Designing a parametric weather product from zero -
no existing UI to redesign, no direct precedent to copy.

SCOPE

Zero-to-one, UX & UI

ROLE

Sole designer, defining UX & UI from zero

SPECIFICS

B2B2C parametric weather cover

YEAR

2026 - ongoing

WEATHER IS AMBIGUOUS.

WEATHER IS AMBIGUOUS.

WEATHER IS AMBIGUOUS.

THE TRIGGER ISN'T.

THE TRIGGER ISN'T.

THE TRIGGER ISN'T.

The idea behind parametric cover is refreshingly simple: hit a measured threshold, get paid, no claims form and no waiting to hear back. The hard part is everything before that moment. A threshold only feels fair if people understand how it was measured and how it was set, well before they ever need it to trigger - so the real design question wasn't the payout logic, it was how to explain a number someone didn't choose clearly enough that they'd trust it upfront.

The idea behind parametric cover is refreshingly simple: hit a measured threshold, get paid, no claims form and no waiting to hear back. The hard part is everything before that moment. A threshold only feels fair if people understand how it was measured and how it was set, well before they ever need it to trigger - so the real design question wasn't the payout logic, it was how to explain a number someone didn't choose clearly enough that they'd trust it upfront.

MEASURED, NOT ASSESSED. FAIR, NOT ARBITRARY. · MEASURED, NOT ASSESSED. FAIR, NOT ARBITRARY. · MEASURED, NOT ASSESSED. FAIR, NOT ARBITRARY. · MEASURED, NOT ASSESSED. FAIR, NOT ARBITRARY. · MEASURED, NOT ASSESSED. FAIR, NOT ARBITRARY. · MEASURED, NOT ASSESSED. FAIR, NOT ARBITRARY. · MEASURED, NOT ASSESSED. FAIR, NOT ARBITRARY. · MEASURED, NOT ASSESSED. FAIR, NOT ARBITRARY. · MEASURED, NOT ASSESSED. FAIR, NOT ARBITRARY. · MEASURED, NOT ASSESSED. FAIR, NOT ARBITRARY. · MEASURED, NOT ASSESSED. FAIR, NOT ARBITRARY. · MEASURED, NOT ASSESSED. FAIR, NOT ARBITRARY. · MEASURED, NOT ASSESSED. FAIR, NOT ARBITRARY. · MEASURED, NOT ASSESSED. FAIR, NOT ARBITRARY. · MEASURED, NOT ASSESSED. FAIR, NOT ARBITRARY. · MEASURED, NOT ASSESSED. FAIR, NOT ARBITRARY. ·

Partner example - illustrative

RAINFALL > 50MM TRIGGERS FULL PAYOUT

Partner example - illustrative

WIND SPEED > 60KM/H PAYS €100

One system

CONFIGURABLE TRIGGERS, VALUES, RESOLUTION TYPES

Partner example - illustrative

RAINFALL > 50MM TRIGGERS FULL PAYOUT

Partner example - illustrative

WIND SPEED > 60KM/H PAYS €100

One system

CONFIGURABLE TRIGGERS, VALUES, RESOLUTION TYPES

A payout tuned to one measured threshold can miss what the user actually felt ruined their day. The trigger is fixed well ahead of the trip and doesn't move with conditions - which is what makes it fair, not a moving target, but that fairness has to be explained clearly up front.

First move: research and discovery, not visuals. The hardest single question was how the weather condition is measured, and how to explain that to a non-expert - the model easiest to defend statistically isn't necessarily the one a user can understand at the point of purchase.

Zero to one, start to finish.

Discovery, product logic, flows, IA, UI - shaped from the ground up for a product that didn't exist yet.

Discovery, product logic, flows, IA, UI - shaped from the ground up for a product that didn't exist yet.

DiscoveryStarting from the logic, not the screen

Before any screen existed, there was market research and a real discovery phase: understanding how parametric weather cover could work, then defining the product logic itself.

TrustDesigning for trust in an ambiguous domain

Weather cover isn't a familiar kind of insurance, so the design had to teach as it went - trading technical jargon for plain, self-explanatory copy people could trust before they bought.

ValidationTesting without direct users, again

No direct line to the end customer meant leaning on the people closest to them instead - support teams hearing the real questions, and partner reps speaking for their customers.

Edge casesDesigning for the awkward paths

One case mattered most: a payout with nowhere to go. I designed a flow so a missing payout detail becomes a one-time step, not a dead end.

Trade-offs, not decoration.

Decision
Decision

Scoping a first version, not the full ambition

The full product logic outgrew the available time. Rather than hold the product back, I scoped a focused first release that stands on its own - structured so nothing forecloses what comes next.

Decision
Decision

Reusing the system, not reinventing it

A real advantage carried from the existing library: the token-based design system and theming approach already existed, so this product didn't start from a blank canvas visually - zero-to-one on the product logic, standing on an established system for visual consistency and speed.

Honest call
Honest call

Unreleased, and that's the honest status

The UX flows are defined and in active development. This project stretched me most in product analysis - a long, genuine discovery phase, mapping unhappy paths and pressure-testing the logic before committing to a direction.

No Name Creative

Olya Mitso

© 2026 No Name Creative.