Principles

A shared way to think about design, so teams make better decisions for the people who use their products.

Eight principles

What we check every design against, from the first sketch to the final detail.

  • 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.

    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.

Working with design

Design is a problem-solving discipline: working out which problem is worth solving, for whom, and what the right answer looks like. For product managers and engineering leads, start here: what design does, when to bring it in, and how to get a designer.

Our process

Design starts at framing. Framing is the one stage where changing direction costs nothing.

  1. Agree the problem worth solving, and a direction everyone can commit to.

  2. Research with real people, map the journey, build prototypes.

  3. Decide how it behaves, what could go wrong, and who stays in control.

  4. Test the real thing with real people, before and after it ships.

  5. Components from the Helix design system, plus AI behaviour and testing.

  6. Watch how it is used, and feed that back into framing.

And back to framing

  • Understand what design does and how it helps us solve the right problems.

  • See how design contributes at every stage, from early discovery to delivery.