Understanding real use
Conversations with a handful of genuine users and a look at existing statistics: where people give up, which pages loop, which questions reach support. Internal opinion comes after the evidence.
An interface can be corrected at three moments, and the price swings by a factor of a hundred. On a wireframe, moving a button takes five minutes. After development you reopen the code, redo the checks and republish. After release you must also explain the change to the people using it. Take a fleet management software vendor that had six drivers try its data entry screen before a line was written, and removed two fields out of five. That is exactly the outcome we are after.
We do not draw isolated screens. We build journeys, then the components that let you make more of them without coming back to us.
Conversations with a handful of genuine users and a look at existing statistics: where people give up, which pages loop, which questions reach support. Internal opinion comes after the evidence.
We describe the main routes before drawing anything: what the person wants to do, in how many steps, with which information in front of them at each moment.
No colour, no imagery, so structure is judged rather than looks. This is the stage where internal disagreement resolves fastest, because nobody argues about a shade of blue.
A navigable sequence put into the hands of five to eight people. Obstacles surface within an hour of sessions and are mended the same day.
Colours, type, button states, error messages, empty states and mobile versions, collected into a documented library rather than a pile of pictures.
Measured contrast, target sizes, tab order and form labels decided while drawing, following WCAG 2.1 AA and RGAA 4.1 on public sector work.
Source files, spacing and behaviour specifications, exported assets and a questions session. Your in-house team can carry on without us.
Duration follows the number of journeys and how easily users can be reached. A single screen takes days; a full business application needs several rounds.
Goals, users, technical constraints and existing measurements. We list the questions the design has to answer.
Journeys and grey wireframes, reviewed with you until the sequence feels obvious.
The clickable prototype meets real users, with a written account of obstacles ranked by severity.
Final interface, component library, documentation and a proper handover to the development team.
Five people are enough to expose most of the obstacles in a journey. Many companies skip sessions because they imagine a heavy, costly and lengthy protocol. One hour over video, during which somebody attempts a task while you keep quiet, reveals more than three internal meetings. Keeping quiet is the hardest and the most profitable part of the exercise.
You can, and many do. The cost resurfaces later as change requests during development, longer training and more support calls. On a small presentation site the saving is defensible. On a tool twenty people open every day, it is not.
Often, yes. We start from usage statistics, support feedback and a screen-by-screen review. Fixes are ranked by expected gain against effort, which lets you tackle part of the list without rebuilding everything.
Real people from the target audience: clients, staff, engineers, applicants. Not your marketing colleagues, who already know the house vocabulary and guess where to click. We help with recruitment and run the sessions remotely.
The design files with access rights in your name, the navigable prototype, the documented library, exported assets and the session write-up. All of it is usable by an agency other than ours.
By fixing the markers beforehand: task completion rate, time taken, error count, support calls on that subject. We record those values on the current version, then again after release. Without a starting figure, comparison is reduced to everyone impressions.
Describe the product or site to be designed and the people who will use it. We propose an approach and a number of rounds.
Message received
An answer follows inside one working day. Report an outage that is stopping people working and it moves ahead of everything else.
Nothing here under that name. Check the spelling, or simply choose the nearest large city instead. Since every engagement runs remotely, whichever you pick changes nothing about what we do for you.