Case 01Farsight · BaxEnergy, a Yokogawa company

KPI Creator

Every new performance indicator used to arrive with a BaxEnergy programmer, sitting beside the client, writing the formula for them. My job was to design the module that let clients do it themselves. With it, clients stopped needing the engineer, and the engineers got back the hours they had spent writing other people's formulas.

RoleLead Designer
PlatformFigma + Claude
DeliverablesFigma files + HTML/React prototype
1Before

Every formula came with a person

A KPI is a formula built on a machine's raw signals, like rotor speed or temperature, that shows what the raw feed hides. Clients needed them. Few could write one. So in the old product an engineer came too, every time. The engineer was the workaround for the software.

Nobody set me a support target. Getting that engineer out of the room was my own goal. We never reached zero support (I doubt any tool does), but I designed every screen that follows against that goal.

Before Client Support request BaxEnergy engineer Formula KPI Required, every time After Client 1 · Define KPI 2 · Define Logic 3 · Validate KPI Self-service: the engineer is gone from the path
  1. Client
  2. Support request
  3. BaxEnergy engineer
  4. Formula
  5. KPI
  6. The engineer was required, every time.
  1. Client
  2. 1 · Define KPI
  3. 2 · Define Logic
  4. 3 · Validate
  5. KPI
  6. Self-service: no engineer on the path.
The path, before and after. Drawn for this page.
2Two routes

An expert and a beginner, on the same screen

Some users write their own formulas. Others never will, and they shouldn't have to.

Where everyone starts: two ways in. Quick Examples at the top, for the beginner. The Expression field below, for the expert. Recorded from the working prototype.
3Quick Examples

The shortcut shows its work

Beginners start from Quick Examples: pick a ready-made formula and it fills the form, after showing you the maths. By the fifth time you can read it; by the sixth you can change it. It's a ramp that ends in the editor.

Quick Examples, played through. Recorded from the working prototype, built on the Farsight design system. The formula is on screen before Apply touches anything.
4Getting it wrong

Telling people they're wrong, without making them quit

People get a formula wrong, often more than once, before they get it right. A typo stops the chart, so you notice. A bad filter doesn't stop anything: you get a believable line drawn from half the data. So I made the preview list what it left out, and why, before you save. From one real preview run:

972Datapoints included
915Excluded by filters
1887Sampled in the window
The Preview Area in the design
        file: 972 of 1887 datapoints included, 915 excluded by conditions. Under the daily chart,
        the results table marks each row Included or Excluded, and every excluded row names its
        reason: Turbine not available, or Windspeed below threshold.
Every excluded datapoint gives its reason in words. The run these three numbers come from, in the design file. Words, because an error code would send the user back to an engineer.
Change a setting and the preview reruns, before you save anything. Daily, then weekly, then monthly: the counts, the line and the rows all follow. Recorded from the working prototype.
5Hindsight

What I'd do differently

  1. Say where the formula broke.The module tells you a formula is incomplete, but not where. An expert with a misplaced bracket ends up back at support, the one trip the module was built to cancel. It's the first thing I'd fix.
  2. Watch clients as well as colleagues.Everyone I saw use it worked at BaxEnergy. I'd put it in front of a client in the first week, and ask for usage data from day one, so I could turn "no complaints" into a number.
  3. Keep a picture of the before.I have no screenshot of the old way. With one, this case would open with two images instead of an argument.