How we design

Eight principles. Not preferences, but decisions with engineering and product consequences.

This is the standard we hold our own work to.

Clarity

Make the complex legible.

We cannot simplify a plant, a fleet, or a supply chain. We can make it understandable. Order the information, and show what the decision needs rather than everything the system holds.

Context

Design for the shift, not the demo.

The same job looks different in a maintenance bay, a vehicle cab, and a planning office. Role, task, and environment shape the interface, not personal preference.

Consequence

Design the failure first.

A missed inspection or a wrongly scheduled technician costs real money, and sometimes safety. Where being wrong is expensive, design the wrong path before the happy one.

Trust

Show the working.

When the software recommends or decides, it explains itself. State confidence honestly, keep actions reversible where you can, and never leave someone unable to say why.

Consistency

One product, not forty.

A customer moving between our applications should not have to learn our org chart. The design system is how we keep that promise, and it only holds if every squad uses it.

Evidence

Decide with customers, not about them.

Every significant decision traces back to something a customer said, did, or struggled with. Until it has been tested with them, a strong opinion is still a hypothesis.

Craft

The detail is the product.

In enterprise software, the table, the empty state, and the error message are the work, not decoration around it. Craft is doing them properly even when nobody outside the team will ever notice.

Agency

Know whose decision it is.

A tool does exactly what’s asked of it. An agent acts toward a goal on someone’s behalf, inside limits we set on purpose. Either way, the person stays in charge: they can direct it, interrupt it, and switch it off, and the interface has to make all three obvious, not just possible.