Product design
We design the product itself: how it is structured, how it looks, and how it behaves when someone uses it. The work runs from the first concept through to the final interface your engineers build from.
It starts with discovery. We talk to the people who run the product, go through your analytics, and interview users. By the end, everyone agrees on the problem worth solving and what we recommend building.
From there we design two or three directions as clickable prototypes and test them with users. You review working prototypes rather than static images, so you can click through the product before anyone commits engineering time. The direction that tests best is built out in detail and tested again.
Once the design is final, we hand it over with written specs for the edge cases, and we review builds with your engineers until launch.
Service design
We design the whole journey a user goes through, including the steps that happen off screen: the emails they receive, the calls they have to make, and the work your team does by hand.
We start by mapping what users go through before, during and after they use the product. We talk to users, and to the staff who handle their requests, because staff see the problems the product doesn't solve.
Then we redesign the order of those steps and decide which belong in the product and which stay with your team. The screens are designed after that, and tested with users the same way as any product design work.
You get a map of the journey as it is today, the redesigned journey, and prototypes of the screens that change.
Design audits
If your product is already live, an audit tells you what is working, where users get stuck, and what to fix first.
We go through the product end to end, the way a user would, and note every point where people get stuck or give up. Then we check those findings against your analytics, so each problem comes with an idea of how many users it affects.
You get a written assessment and a prioritised list of fixes, each with a rough estimate of the effort involved. We then walk your team through the findings in a session, so the people who will do the work can ask questions directly.
You go into your next planning cycle knowing which problems are worth solving, and what each one is costing you now.
What you get
- A discovery summary: the problem, what users told us, and what we recommend building.
- Clickable prototypes at each stage, tested with users in English and Arabic where the product needs both.
- Final design files, built on your design system or a starter one if you don't have one yet.
- Written specs for edge cases, states and interactions.
- A handover session with your engineers, and build reviews until launch.
Every engagement is led by a senior person from start to finish.
Related work
Property Finder: Making the map the search engine. A redesign of how buyers browse listings on the map. Leads from map sessions rose from 5% to 32%.
Property Finder: Rebuilding search, app to web. The results page, rebuilt around helping people decide. Conversion rose 1.8 percentage points, tested on both app and web.
Both delivered by Rai's founders while at Property Finder.
Other services: Design systems · Brand & creative · Delivery & ops