
WindBorne Guardian: Extreme Weather Preparedness for Utilities
- timeline
- Spring 2026
- role
- Product DesignerFrontend EngineerProduct Manager
- skills
- Product DesignFrontend Engineering0 -> 1User Research
Guardian helps power utilities get ready for storms. It turns raw weather forecasts into outage predictions for every county in the US, up to 7 days ahead. It shows which parts of a service territory are most at risk, when that risk peaks, and why, so planners can decide where to send crews before the weather hits.
Context
WindBorne's weather balloons feed a forecast model that sees storms coming days earlier than others.
But utilities don't plan in weather terms. They plan around their grid: which areas get hit, how many customers lose power, and where to send crews.
Guardian is for the utility's emergency planning team: the planning chief, the meteorologist, and the operations leads. Our job was to turn those extra days into time to prepare.
Problem
Utilities already had a dashboard for everything: weather, equipment health, crew schedules, the grid map. None showed what a coming storm meant for their grid.
So days before a big storm, a planning chief would set a weather map beside a map of their power lines and guess where to send crews. A wrong guess meant longer outages.
- Forecasts showed the weather, not its impact on poles, lines, and crews.
- Weather, equipment, and outage history lived in separate tools.
- Critical sites like hospitals were the easiest to lose track of.
Design principles
5 principles
While there is a large amount of relevant information to disclose to the users, information should have different weights in the interface, and we shall not dump all the insights to the user at once. The goal is to incorporate both high-level situational summary and deep-dive analysis without overwhelming them upfront.
We should establish the hierarchy between what the users should understand immediately when they open up the interface, and what they can click a few more buttons and investigate later.
The interface should enable instant clarity: “What is the risk? How severe? Where should I pay attention?” Other detailed explanations can go “under the hood”, allowing users to understand what inputs go into consideration, the reasoning behind how an insight is constructed, etc.
Weather information is more useful when it is translated into the operational questions users need to answer.
The Emergency Planning Chief does not need to necessarily know that a severe storm is coming. They need to understand what a storm means to their system: How many customers may experience outages? How many lines or poles may be down? How many crews are needed?
By turning weather signals into operational impact, we help users understand storm impact, plan resources, and plan actions with more confidence.
The interface is the most direct way users experience with the underlying WindBorne intelligence. To build trust, we need to be transparent, reliable, and honest about the information presented.
- “Data last updated at: Today 5PM” — reduces confusion about whether they are looking at latest information.
- Loading state when data is still loading — prevents mistaking an unfinished state for an empty/broken state.
- “Data not available” when data failed to load — clearly communicates system limitations.
- “Model estimates. Check real conditions” — sets the right expectation for model outputs.
Weather forecasts are inherently uncertain. No forecast can be 100% accurate or delivered with 100% confidence. Consequently, it is “impossible” to give the user a definite answer.
Because of this, we need to be thoughtful about how we present the predictions and recommendations to the users. We need to set the correct expectations, clearly communicating what we can reliably support today without underselling or overpromising what the system can prove.
When designing AI-powered products for Disaster Preparedness, especially for industries / user groups like utilities, who are risk-averse and conservative, we have to be careful of how we incorporate AI into their workflow and how we can make it a “glassbox” AI experience.
In order to build explainable AI, make sure we can explain:
- What data goes into the model.
- What is the output.
- How is the output generated / reasoning behind the output.
- What expectation users should have.
- Traceability so AI is accountable.
Full process
No password? Email me and I'll walk you through it.
At DTECH

Want to learn more details? Contact me for a portfolio presentation.
