Analysis Pages
Seventeen analysis pages, read by engineers and executives on the same screen. Before I could design them I had to learn how a turbine turns wind into power.
A strip for the executive, charts for the engineer
An asset manager asks why an hour earned less than it should. A performance engineer asks which turbine is off its curve. So every page runs in one order: headline numbers first, for the reader who won't open a chart, then two or three charts per screen, with room between them. Experts can live with simplification, as long as nothing is missing: they'd rather have too much information than too little.
I drew the power curve as a bell. It's an S.
Clients used to need a BaxEnergy engineer beside them to understand these analyses. The
maths was the CEO's and the data the BI team's; my job was charts a client could read alone.
That meant learning the physics first: kilowatts versus kilowatt-hours, turbulence, and why
wind reaching a turbine hundreds of metres behind another arrives messy
.
For the first chart on the first page, I pictured a bell. The curve is an S: nothing below cut-in, a climb, a flat top, then shutdown when the wind could damage the machine. Too little wind is bad, and so is too much. The best of it sits in a Goldilocks zone in between.
Corrected twice, better both times
Yaw deviation is the gap between where the wind comes from and where the turbine points. My first version was one line of angles over time, and to me that was enough.
Version 1 · one chart
A developer asked, Why not show the nacelle turning?
I didn't think it was needed.
We talked it through, and I changed my mind.
Version 2 · the nacelle, turning
In this case, the developer was right.
Version 3 · every angle
Two weeks became two or three days
The first page took one to two weeks, most of it learning, and I showed the team every draft early. Then a client pulled fifteen analyses forward and I ended up in charge of all of them, with the BI team. The design system was in code by then, so I changed how I worked:
- BriefI write it; Claude explains the concepts I don't know yet.
- PrototypeClaude builds it in HTML, already on the design system.
- Into FigmaClaude writes the screen into Figma through MCP.
- Fine passI adjust by hand: spacing, hierarchy, detail.
- Back to codeClaude reads the frame and corrects the HTML.
- Two artefactsFigma and HTML at the same fidelity, with the error states Figma hides.
All seventeen pages are live. Clients now read these analyses without an engineer beside them. When a turbine stops reporting, we leave the gap in the chart. We don't invent data.
What I'd do differently
- Sit with an engineer before the first sketch.My first power curve was wrong because I hadn't understood it yet. An hour with someone who reads these curves every day would have saved the draft.
- Test each chart on a month of real data before launch.The nacelle drawing worked for a single moment and fell short once people read a whole month. We found that out after launch, which is the expensive time to find things out.
- Decide how to measure it before shipping.Seventeen pages are live and I never saw usage data or test results. I'd agree what to measure with the team before the first page went out.