Paolo Hospital

This was a design engagement. We shaped the product and handed it over; the build was carried out by the client's own development team

Paolo's promise is Accessible & Compassionate, and the home page had to make the first half of that literal — the four things a patient actually comes to do sit on the first screen, above everything else

Find doctors, appointments, deposit payment, select branch: four tiles, one tap each, identical on desktop and on a phone

Deep indigo on white, with a heavy rounded type for headings. Warm enough to read as care, plain enough to read as a hospital

A design handed to a team you do not sit next to is only as good as what comes with it, so the deliverable was a system rather than a set of screens

Components, states, spacing, type scale and colour tokens, documented to the point where a developer can answer "what happens at this breakpoint" without asking us

The desktop layout splits into a fixed action column and a scrolling editorial feed; on mobile the same two pieces stack rather than rearranging, so there is one mental model to build against rather than two separate designs

We have a development team we are proud of, and we are still glad to hand a design to an external one. Plenty of clients have a team already, or an agency they trust, and that is not a reason for us to walk away from the design work

It does change what we owe. We stayed with this build through implementation, reviewing what came back against the system we handed over

QC ran until delivery, not until the files were sent. A design system is a promise about the finished product, and checking that the finished product keeps it is part of the job