User research
Video interviews with people from your real audience, plus analysis of analytics and support queries.
Companies usually come to design once they have a measurable problem: users who never finish a booking, staff spending ten minutes on a two-minute task, customers phoning to do something the website already allows. At that point new colours will not help; you need to see where people get stuck and why. Take a chain of physiotherapy clinics in Seville adding online appointments. Older patients cannot find the confirm button, and younger ones leave when asked to register. Those two findings, which come from watching six people use a prototype, are worth more than any internal opinion.
Each design cycle produces concrete deliverables your team can use without Apply. These are the usual ones.
Video interviews with people from your real audience, plus analysis of analytics and support queries.
A step-by-step account of the main tasks: the user's goal, the steps, the information needed and where people drop out today.
Greyscale layouts turned into a Figma prototype, enough to test the journey before any coding.
Sessions with five to eight participants per profile, recorded with consent, and a report of issues ranked by severity.
Final visual design covering colours, type, states, error messages and mobile layouts, organised as a component library.
Contrast, touch sizes, focus order and labels decided to WCAG 2.1 AA and, for public projects, UNE-EN 301549.
Specifications, exported assets and reviews of the built product so the end result matches what was tested.
One full cycle, from interviews to a tested prototype, normally takes a few weeks. Larger projects are split into several cycles, one per journey.
Video interviews with real users plus a review of analytics and support queries to locate where people get stuck.
Greyscale layouts of the main journey turned into a clickable Figma prototype, without spending time on visual styling yet.
Five to eight people try to complete specific tasks on the prototype while we observe. Problems are fixed between one session and the next.
Finished interface, a documented component library and a session with the developers to clear up questions before they code.
Users say one thing and do another. In a survey, almost everyone claims to prefer registering so their details are saved; in practice, many leave the moment a registration form appears. So major decisions are taken by watching people use a prototype, not by asking what they would prefer. An interview explains the why; a test session reveals the what.
That depends on the number of journeys and test sessions. A single journey, such as a booking or sign-up, takes a few weeks; a whole application is split into cycles. We quote per cycle at €75 per hour + VAT, so you can stop after any of them.
No. Sessions run over video call: participants share their screen from their own computer or phone and use the prototype in their normal setting. It is easier for them and more realistic for the findings.
Five to eight people from the real audience are enough to find the main problems in a journey. Where profiles differ sharply, say patients and reception staff, a small group of each works best.
Yes, that is the usual set-up. We deliver a component library in Figma with specifications and hold sessions with your developers during implementation, so the final product matches what was tested.
It is. Contrast, touch target size, keyboard order and form labels are decided at design stage to WCAG 2.1 AA. On public sector projects we also apply UNE-EN 301549, the standard Real Decreto 1112/2018 refers to.
Describe what needs designing and who will use it. We will suggest a method and the number of rounds it needs.
Your request is with us
Expect an answer within one working day. A reported fault that has halted your team is handled first.
No match found. Try another spelling, or go with the closest provincial capital: every job is done remotely, so the location makes no difference to what we deliver anywhere in Spain.