Interfaces
Screens shaped by the job, tested by the people who do it.
Watch first
Every interface project starts with observation. We watch the task as it happens today, note every workaround and ask what goes wrong on a bad day. The bad day matters most: software that only works when everything goes to plan will be abandoned the first time it does not.
Prototype, then test with real hands
We build clickable prototypes of the most frequent task first and test them with two or three real users. We watch where they hesitate, then revise. A few rounds of this costs days and saves months.
- 1
Paper sketches of the task as it should feel.
- 2
Clickable prototype of the core path.
- 3
Tested by two or three real users.
Words are part of the interface
Labels in your vocabulary. Error messages that say what to do next. Buttons named for what they do: "Save inspection", not "Submit". We write the interface text ourselves and review it with you.
Accessibility as a fixing, not a finish
We design to WCAG 2.2 AA: contrast that holds up in daylight, keyboard navigation, screen reader labels, text that scales and controls large enough for gloved hands. These are checked at prototype stage and again before release.
Design systems that survive handover
We hand over a small, documented component library: buttons, forms, tables, messages. It is sized to your product, not a sprawling kit, so future changes stay consistent.