Context

Delfos Energy builds monitoring and analytics software for renewable energy assets. Operators use it to watch wind and solar plants across Europe, Latin America and North America, and to decide what to do when something in the field stops behaving the way it should.

I joined as the only designer on the product team, during a period where the platform was growing faster than the process around it. Engineering had a mature component library. Product had a backlog fed by several client engagements at once. The part that sits between them, the one that decides what gets built and why, had not been anyone's job yet.

Constraints

The users were specialists. An operations analyst watching a wind farm reads a screen the way a pilot reads an instrument panel. Density was a requirement. Making the interface simpler would have made it worse.

There was one designer. Anything I built had to survive without me in the room, which made writing things down part of the work rather than overhead on top of it.

The team was distributed. Europe, the Americas and Brazil, with most decisions happening in writing, asynchronously, in a second language for almost everyone involved.

Key decisions

The design system came first. With one designer and a growing product surface, the only way to scale is to make sure the screens someone else draws come out right. I took ownership of the system, set the rule that nothing ships with a hardcoded value, and built the documentation so a developer could answer their own question without waiting for my timezone to wake up.

Design moved in front of the ticket. I started reviewing specs before they entered development instead of reviewing screens after. That pushed the argument to the cheap end of the process and removed a whole class of rework.

Everything got written down. Specs, decisions, and the reasoning behind them. Documentation is what scales a single designer across three timezones.

I defended decisions out loud. Being the only designer means being the only person who can explain a design choice to a stakeholder, a manager or a client. I learned to put a number on what a request would cost instead of absorbing it quietly.

What it produced

Design stopped arriving at the end of the process and became part of how the team decided what to build. The system turned into the shared reference between design and engineering, rather than a file only I opened. The whole story, sunrise to sunset, is in the animated deck linked below.