Design at the stable door
Research and interface design that starts with how the work is actually done.
Observe a real morning
We begin by watching. With permission, we shadow a morning routine in person or over a video call, and keep a simple log: every moment information is written down, looked up, asked for, or lost. That log becomes the backbone of the design, because it shows where software would save time and where it would only add friction.
Design for each role separately
Rider or groom
Needs speed, large targets and no surprises. Usually on a phone, often outdoors, sometimes in gloves.
Yard manager
Needs the whole picture, quick filters and confidence that nothing is missing before planning tomorrow.
Owner
Needs a clear, regular summary in ordinary language, without having to learn the system.
Administrator
Needs permissions, exports and an audit trail that make the system safe to rely on.
Prototype the smallest useful loop
We do not design every screen at once. We pick the most frequent routine, design it as a clickable prototype and put it in the hands of two or three people who will use it. Their hesitations decide the next revision. Only when that loop feels natural do we design outward to the rest of the product.
Words and charts carry the design
Labels follow your vocabulary: if your yard says "lot" or "canter", so does the software. Charts are designed with captions that state their source, time window and known gaps. We avoid colour-only meaning, cluttered dual axes and decorative gauges that suggest more certainty than the data supports.
Accessibility from the first sketch
We design to WCAG 2.2 AA as a working standard: sufficient contrast in bright daylight, text that scales, full keyboard support on the web, and screens that make sense to a screen reader. Outdoor use raises the bar further, so we test key screens on a phone in sunlight before sign-off.