TECHNOLOGY SERVICE · 09
Product & UX Design
Research, interaction design and design systems aimed at removing the expensive uncertainty before engineering starts. For teams about to commit a budget to a platform, and for existing products where adoption has stalled.
Talk to the people who will be blamed if it fails
Requirements gathered only from management describe the process as it is supposed to work. The dispatcher, the nurse, the warehouse supervisor and the branch clerk know what actually happens, including the workarounds that keep the operation moving. Field sessions with those users, on their own screens, produce the constraints that matter.
Findings are reported plainly, including the ones that contradict the original brief. That conversation is cheaper now than after the build.
Prototype the risky screen, not the easy one
Prototyping effort goes to whatever carries the most uncertainty: the dense operational table, the approval chain, the exception path that decides whether staff trust the system. Clickable prototypes are tested with real users early, and the ones that fail get changed while changing them costs a day.
- Clickable prototype of the highest-risk workflows
- Usability sessions with the staff who will use it daily
- Written decisions on what was changed and why
Arabic is not a translation layer
Bilingual products need layout mirroring, correct numeral handling, name and address forms that suit local conventions, and typefaces that carry both scripts without one looking like an afterthought. Designing both directions together from the first screen costs far less than retrofitting, and it shows in how the Arabic interface reads.
A design system your developers will keep using
Design systems fail when they exist only in a design tool. Ours are delivered as coded components alongside the design library, with tokens, states and accessibility behaviour defined in both places. Contrast, focus order and keyboard operation are checked against WCAG 2.2 AA as part of the work, which matters for public sector procurement in particular.
What you get
- Research findings from sessions with real users, with recordings where permitted
- Journey maps covering the exception paths, not only the happy path
- Clickable prototypes of the highest-risk workflows
- Usability test results with prioritised changes
- Design system as a component library plus coded components
- Bilingual Arabic and English layouts, checked in both directions
- Accessibility annotations and a WCAG 2.2 AA conformance check
- Developer handover with specifications and design tokens
Typical outcomes
3-5 weeks
Research to a tested, buildable prototype
8-12
Users interviewed in a typical discovery
WCAG 2.2 AA
Accessibility target for delivered interfaces
Stack we use
Questions
Yes. Design engagements are sold standalone and the output is written to be handed to your own engineers or another supplier, including coded components where you want them.
For most internal systems, eight to twelve interviews across the affected roles surfaces the great majority of usability problems. Beyond that, effort is better spent testing a prototype than gathering more opinions.
Layout, typography and interface strings, yes, working with native Arabic speakers. Long-form marketing copy and legal text are better written by a specialist translator, and we brief and review rather than pretend otherwise.
Normally yes. Existing brand assets become the foundation, and we extend them into the interface patterns, states and accessibility rules that brand guidelines rarely cover.
Related
Next step
Start with a 20-minute call.
Tell us the roles you need filled, the system you need built, or both. You will speak to someone who has done the work, and leave the call with a route forward.