Design

Design for the doorstep moment.

Every product has a moment where someone is in a hurry, slightly anxious and holding a phone in one hand. We design for that moment first.

  1. A

    Ride along

    We talk to, and where possible observe, the people who will use the product. For a delivery tool that might be a driver, a dispatcher and a customer. We ask about the last real time something went wrong.

  2. B

    Map the journey

    A journey map shows each step, who is involved, what they need to know and where they wait. Waiting points are where status design matters most.

  3. C

    Sketch the states

    For every screen we design the empty, loading, success, partial and error states, not just the happy path. This is where most products feel unfinished.

  4. D

    Prototype and test

    A clickable prototype tried by five or so real people. We watch, note hesitations and revise before any production code is written.

Accessible by default

We design to WCAG 2.2 AA: sufficient contrast, visible focus, generous touch targets, meaningful labels for screen readers, captions where media is used and motion that respects reduced-motion settings. Error messages explain how to recover.

What you receive

Research notes, journey map, tested prototype, a component sheet with every state, and a hand-off document explaining key decisions so future changes stay consistent.

Status design, a speciality

Status is the heart of any delivery or booking product: received, preparing, on its way, nearly there, delivered, problem. We define each state precisely, decide who is told and how, and write the words. Try drafting one yourself with the notification previewer.

Open the previewer