UI/UX Design
UX Research & Testing
Find out whether people can actually use your idea before you pay to build it — with prototypes and real sessions, not opinions.
What this actually is
Cheap, fast validation before a single line of production code is written.
UX research and testing is the cheapest part of the process and the one most often skipped. We define what the test has to prove and who it has to be run with, build a clickable prototype that feels real enough to use, then sit with people while they try to complete the task.
Sessions are watched and recorded, so your team sees the hesitation rather than reading our summary of it. That matters when you are testing a pattern borrowed from a Western product that your users have never encountered. Findings go straight back into the design and get fixed before a developer touches it.
How we work
Four steps, in this order.
Script
Define what the test needs to prove, and with whom.
Prototype
Clickable prototype good enough to feel real.
Test
Sessions with real users, watched and recorded.
Iterate
Findings folded back into the design before build starts.
What you get
Every engagement hands over these.
- A test script tied to the decisions you need to make
- A clickable prototype of the flows under test
- Session recordings with the moments that matter time-stamped
- A findings report ranked by severity, with design fixes applied
Who it’s for
This is usually the right fit when…
- You are about to commit a development budget to a flow nobody outside the team has tried.
- Your team disagrees about how a feature should work and the argument keeps going in circles.
- People sign up and then never come back, and analytics tells you where but not why.
Questions
The things people ask before starting.
How many people do you test with?
Enough to see the same problem happen more than once, which is fewer than most people expect and depends on how many distinct user types you have. We agree the number with you when we write the script, based on who actually has to be covered — not on a rule of thumb.
Can we test with our own staff or friends?
You can, and it is better than testing with nobody, but treat the results carefully. People who know you already know what the product is meant to do, so they skip past the exact confusion you are trying to find. Where it matters, we recruit participants who match your actual users.
What if the testing shows the whole idea does not work?
Then you found that out at the cost of a prototype rather than a build. That is the point of doing it here. More often the idea holds and a few specific steps are where people fall over, which is a much easier problem than discovering it after launch.
Can you test a product that is already live?
Yes. With a live product we test the real thing instead of a prototype, which removes the guesswork about whether the prototype was faithful. It works well alongside whatever analytics you already have — the numbers tell you where people leave, the sessions tell you why.
Have a project in mind?
Tell us about your project, study or idea — and let's see what's possible.
Get in touch