Keep it intuitive

It can be tempting to be over-explicit in an interface and fill it with words to explain the specifics of each utility within the UI, leading to a busy interface.

Instead of this, we should optimise for intuitive use of the product. If something needs to explained specifically, is it because it's badly placed?

Visual relationship trumps verbal explanation

Whitespace as utility

Some interfaces are necessarily complex. In these situations, it can be tempting to use dividing lines, borders and container elements to partition related elements together, resulting in clutter and noise.

Instead, we should use our baseline grid to space elements with whitespace only. Sufficent, rhythmic spacing provides the partitioning needed, without the added detailing overhead.

Context over consistency

Because we have a design system, it can feel like everything needs a rule: all links have to be blue; all save action buttons have to be green. But this can lead to a clunky interface because the design system is being respected more than the user's experience.

Always put yourself in the seat of the user: is the interface harmonious; easy to scan; easy to understand? A design system will have edge cases where you might need to use a subtler link colour, or a slightly smaller font size because the context needs it.