Case 02Farsight · BaxEnergy, a Yokogawa company

The Farsight Design System

I was hired to design screens. I built a design system anyway, as one designer with no mandate, no engineering time and no power to block a single release.

RoleLead Designer, Design Ops
FocusHow the team works
TeamOne designer
1The argument

Ant Design is built to sell things

Nobody was worried, and fair enough: the product was pre-sale, so the mess wasn't losing deals. My argument was fit. Ant comes from Alibaba and is made for shopping pages: roomy buttons, round corners, type that grabs attention. Farsight was made for control-room video walls, where each module gets one screen in a bank of them.

Ant's chrome takes up too much space relative to the content.

A domain-verification step
            built from stock Ant Design parts: a two-step progress bar, a heading, DNS and
            HTTPS tabs, a grey panel holding four text fields with copy buttons, a warning
            line, and Back and Verify Domain buttons.
Ant, as it came. Stock parts from the design file. The frame takes more room than the four short fields inside it.

The Product Owner pushed back hardest, sure a design system was about looks. I was arguing for consistency, and for the trust people give a product that has it.

2Proof

I made the case with screens

I started with tighter components, then built real screens from them that fit more and read better. I carried them up the chain until the head of R&D bought in; that person later became CTO, which is why the work survived. I couldn't block a release, so I negotiated: ship the simple version now, apply the system after. To sell a new pattern, I pointed at one everyone already knew from Excel, PowerPoint or Figma.

One component, finished. Seven types × four sizes × six states: 168 variants. Click to pause.
3Adoption

An hour a day with the door open

One habit got the system adopted: Design Hour, an open Teams room, every day. Developers dropped in with whatever design question was blocking them, and the others listened.

A week view of a calendar
        from 9 to 11 in the morning. Design Hour sits in every weekday column from 9:30 to
        10:30. Tuesday's slot is lifted and open: Design Hour, an open room to bring whatever
        design question is blocking you, 9:30 AM to 10:30 AM, every weekday, a Teams meeting
        open to everyone, and a Join button.
Every weekday at 9:30. Drawn for this page in the Farsight design system.

While one asked a question, the other listened. And then each one saw the problem they had, and I helped solve it.

It worked both ways: the senior front-end engineers used the same hour to check my work. As the only designer, I had no other review.

4Where it landed

They stopped asking me what colour to use

I wrote down the alarm severities, the colours for wind, solar and battery, and the spacing steps, and the questions stopped. I stopped building components and started assembling them, and spent the time on what a page should do. I never got engineers assigned to the system, so when Claude Code arrived I built its Storybook myself.

Nobody has to ask which red. The blue ramp, neutrals, statuses, energy and alarm severities, each with its token. Made for this page from the design system. Click to pause.
5Hindsight

What I'd do differently

  1. Build our own system instead of dressing up Ant.We customised Ant until it no longer looked like Ant, but it was still underneath, and we fought it on every change. If the call had been mine, I'd have built our own. It wasn't.
  2. Ask for protected time from the start.I squeezed the system in between feature work, which is why it took so long. I'd negotiate a fixed share of my week for it before building the first component.