Let’s talk

Back to writing

Design Systems

The first thing I decide when designing a component

Before I choose a layout, I ask what someone needs to read, decide, or do next.

Imagine I’m designing a booking card. On a large screen I can fit the traveller’s name, tour date, payment status, and four actions on one line. On a phone, that same card can quickly turn into a pile of buttons. This is where I ask what someone is actually trying to do with it.

If the booking is waiting for confirmation, I’d make Confirm booking easy to find. I’d keep the date and payment status close because they affect that decision. An occasional action, like downloading an invoice, can be quieter and still easy to reach. GOV.UK’s Design System gives similar advice about competing primary buttons, and WCAG’s target-size guidance is a useful check when I’m fitting controls into a small space.

The version in the mockup is only one version

I’d draw the card again with a very long name, a missing date, and a failed save. What happens if I tap Confirm twice because the connection is slow? Can I tell that something is happening? If it fails, can I retry without entering the details again?

Then I’d try the component with a keyboard and larger text. If I need to explain where the next action has gone, I’ll revisit the layout. That work makes the component easier to use and makes it much clearer for another developer to implement.

Have something in mind?

Let’s talk.

Tell me what you’re building. Let’s find the right way to bring it to life.