Decisions the whole team can defend
Every recommendation is tied to observed behaviour rather than opinion, so debates end faster and roadmaps stop changing every quarter.
UX research
Research that turns behaviour into decisions.
We dive deep into user needs and turn insights into decisions that shape better products.
What’s included
Deliverables you can plan around.
- Stakeholder and user interviews
- Contextual research and field observation
- User personas, journey maps and service blueprints
- Usability testing and behavioural analysis
- Accessibility audits (WCAG)
- Competitive benchmarking and heuristic analysis
- Category and market landscape mapping
- Segment, buyer and use-case definition
- Regional and cultural context, Arabic/RTL behaviour across Saudi Arabia, the UAE, Lebanon and the wider GCC
- Trend and opportunity assessment
Outcomes
What changes when it’s done.
Fewer expensive reversals
A problem found in a prototype costs hours. The same problem found after launch costs a release cycle and a share of your customers.
Products that fit the region
Arabic-first behaviour, bilingual expectations, and local norms around identity, payment and trust are studied, not assumed.
How it works
A process built for clarity.
- 01
Frame
We agree the questions worth answering and the decisions they will inform.
- 02
Recruit and observe
Interviews, field observation and usability sessions with real users in Saudi Arabia, the UAE, Lebanon and across the GCC, in Arabic or English.
- 03
Synthesise
Findings become personas, journey maps and a prioritised list of opportunities.
- 04
Decide
A readout with your team that turns insight into a plan, not a slide deck that gathers dust.
The part clients rarely see and always feel
We embed ourselves in the problem before we touch a screen. We sit with your users, dig through your analytics and talk to the people who run the product day to day, mapping the workflows nobody documented and the workarounds everyone relies on.
Then we turn what we learn into decisions the whole team can defend: which journeys to fix first, which features to drop, what a first-time user needs to see in the first ten seconds.
Research built for the Middle East
Products in the region serve audiences that switch between Arabic and English mid-sentence, bank on their phones, verify identity with national ID platforms and expect services to work as well on a four-year-old Android device as on the latest iPhone. None of that shows up in a global best-practice checklist.
We run sessions in the participant’s language, recruit across Saudi Arabia, the UAE and Lebanon, and pay particular attention to how right-to-left interfaces are read, scanned and tapped. The result is evidence about your users, not users in general.
Methods we use
Moderated and unmoderated usability testing, in-depth interviews, contextual inquiry, diary studies, card sorting and tree testing for information architecture, surveys for sizing, heuristic evaluation and accessibility review against WCAG. We pick the method by the question, never the other way round.
Related work
Where this shows up.
Industries
FAQ
Questions about ux research.
How many users do you need for usability testing?
Five to eight participants per audience segment surface most usability problems in a moderated study. When you need quantitative confidence, task success rates, time on task, preference between two designs, we run larger unmoderated studies. We always recommend the smallest study that answers the decision in front of you.
Can you recruit participants in Saudi Arabia and the UAE?
Yes. We recruit through local research panels and our clients' own customer bases, run sessions in Arabic or English, remotely or in person, and schedule around regional working weeks and prayer times.
Do you test Arabic and English interfaces separately?
We test the primary-language experience first, for most regional products that is Arabic, and then the secondary one. Right-to-left layout, numerals, dates and mixed-direction text behave differently enough to deserve their own sessions.
How long does a research engagement take?
Most discovery studies run two to six weeks from kickoff to readout. We scope by the decisions the research needs to inform rather than by hours, and we agree a fixed price before we start.
How is UX research different from a UX audit?
An audit evaluates an existing product against heuristics, analytics and accessibility standards. Research studies the people who use it. The two are often combined, because an audit tells you where users struggle and research tells you why.
More services