Interface
Design the route, then the scenery
An interface is a set of routes through tasks. We design the routes first and make them short, then make them beautiful.
Listen
Short conversations with the people who will use the product. We ask what they do today, where it hurts and what they work around. Five conversations usually reveal most of the pattern.
Write the tasks
Each task is written as a sentence a person would say: "I need to move my appointment to Thursday". These become the acceptance tests for the design.
Sketch the routes
Flows on paper or a whiteboard tool, counted in steps and decisions. If a task takes nine steps, we ask which five are really needed.
Prototype
Clickable prototypes with realistic content. Placeholder text hides problems; real names, long addresses and empty states reveal them.
Test with tasks
People attempt the tasks while we watch quietly. We note where they hesitate, not just where they fail.
Build the library
Final designs become named, documented components with states for loading, error, empty and disabled, matched one to one in code.
Accessibility is part of the brief
We design to WCAG 2.2 AA as a baseline. In practice that means sufficient contrast, visible focus, full keyboard operation, labels on every field, error messages that explain how to fix the problem, and motion that respects reduced-motion settings. We test with screen readers on both mobile platforms. We do not issue compliance certificates; we do the work and document what was checked.
What you receive
- A task map and flow diagrams
- A clickable prototype you can share internally
- A component library with usage notes
- Content guidance: tone, error wording, labels
- A record of what was tested and what changed as a result