What is the difference between UI design and UX design?+
UX design (User Experience design) is the practice of designing how a product works and how users move through it information architecture, user flows, interaction patterns, and the overall experience. UI design (User Interface design) is the practice of designing how the product looks the visual presentation through colour, typography, spacing, iconography, and component design. In practice, the two disciplines are deeply interdependent. Most professional design practices including ours address both UX and UI as a unified discipline rather than treating them as independent activities.
How do you approach UX for a brand new product versus an existing product?+
New products require a discovery-led approach: user research to validate the product addresses a genuine need, information architecture and user flow design from scratch based on research, and prototype testing to validate before development. Existing products require an audit-led approach: analytics review and usability testing to identify specific experience failures causing business metric problems, targeted redesign addressing those failures, and measurement of whether redesigns produce predicted improvements.
How long does a UX design engagement take?+
UX audit of an existing product (heuristic evaluation + analytics review + 5-8 usability test sessions + recommendations): 3-4 weeks. Full UX redesign of a significant product surface (research, IA redesign, wireframing, prototype, usability testing, visual design): 8-16 weeks. Design system development: 6-12 weeks. For ongoing design partnership retainers, we work in 2-week sprint cycles with defined deliverable scope for each sprint.
What tools do you use for UI/UX design?+
Primary design tool: Figma (wireframing, high-fidelity UI design, prototyping, component library development, design system documentation). User research: UserTesting.com, Lookback, Maze (usability testing), Hotjar, Microsoft Clarity (session recording, heatmaps), Optimal Workshop (card sorting, tree testing). Project communication: Notion (research documentation, design rationale). All final assets delivered through Figma's developer handoff features.
Do you conduct user research in multiple languages?+
Yes for products with international user bases, we conduct user research in the languages of the specific user populations. We have research and facilitation capability in English, Arabic, and Urdu, and work with specialist research partners for other languages where required. User research in the user's native language consistently produces more authentic, more detailed, and more useful insights because barriers to articulating nuanced experience observations are lower.
Can you work with our existing design system?+
Yes we work within existing design systems where they exist, extending and adapting them for specific design challenges. Where an existing system has gaps, inconsistencies, or component needs, we document proposed additions and modifications and seek alignment with the team responsible for the design system before implementing changes. We do not create parallel design patterns that diverge from an existing system without deliberate agreement.
How do you handle design handoff to development teams?+
We deliver design files in Figma with the completeness professional handoff requires: all components annotated with their properties and states, spacing and sizing specified using design system token values, interactive prototype links for interaction pattern documentation, and a handoff review session with the development team to walk through design decisions and implementation implications. For teams using Storybook or similar, we structure Figma component libraries to map directly to the component architecture the development team uses.
How do you prioritise what to design or redesign first?+
We prioritise based on impact-effort framework applied to the product's specific situation: identifying design changes most likely to improve business metrics that matter most for the product's current stage (conversion for acquisition-stage, retention for established, support cost reduction for scaled), assessing development effort, and sequencing changes in order of highest impact-to-effort ratio. High-impact, low-effort changes first. High-impact, high-effort changes get detailed design and testing before development investment.
How do I get started?+
Book a free UI/UX audit. We review your current product's analytics, conduct a heuristic evaluation of the interface, and provide a prioritised list of the top 5-8 experience problems most likely causing the business metric issues you're experiencing. The audit produces immediate, actionable insight regardless of whether you proceed to a full design engagement. No commitment required at the audit stage.