01 — SUBSERVICE
User Research
Interviews, surveys, competitor analysis, journey mapping and usability testing, so decisions rest on evidence instead of opinion.
02 — INTRO
The cheapest time to be wrong is before you build.
Every product argument inside a company, which feature first, what the homepage says, why users drop at step three, has an answer sitting outside the company, with users. Research goes and gets it. A small, well-run study is startlingly efficient: five to eight interviews surface most major usability issues, and a week of evidence regularly saves a quarter of misdirected build.
We match the method to the question. Interviews and surveys expose what users are trying to do; competitor analysis shows the patterns they already expect; journey maps locate exactly where your current experience loses them; usability tests watch real people attempt real tasks on your product or prototype. Findings arrive as a prioritised, plain-language report with personas and a recommended fix order, evidence your whole team can act on, not a binder that gathers dust.
03 — WHAT'S INCLUDED
What's included
Interviews & surveys
Recruited, scripted, run and synthesised.
Competitor analysis
The patterns your users already expect, mapped.
Journey mapping
Every step, emotion and drop-off point in the current experience.
Usability testing
Real users on real tasks, recorded and scored.
Personas & report
Prioritised findings in plain language with a fix order.
Decision workshop
We walk the team through what to do with it.
04 — PROCESS
Process
- 01
Frame
The questions that matter.
- 02
Recruit
The right participants.
- 03
Run
Interviews, tests, surveys.
- 04
Synthesise
Patterns and priorities.
- 05
Act
Fix order agreed with the team.
06 — FAQ
FAQ
How many users do we really need?
A small study with 5 to 8 users surfaces most major issues. Larger samples serve quantitative questions like pricing or segmentation.
How long does a study take?
A focused study runs about 2 to 3 weeks from framing to findings.
Can you research a product that doesn't exist yet?
Yes. Interviews, competitor analysis and prototype tests all work pre-build; that's when research pays back most.