What shapes design work for Qatar
In Qatar a designer is more often improving a supplier portal or a staff tool than a shopping app. That changes what good design means.
| Topic | What it means for your product | Decide early |
|---|---|---|
| Enterprise and public buyers | A few large organizations account for much of the commissioning. Their products have many user roles, long forms and approval steps | The roles, and the handful of tasks each performs most |
| Accessibility policy | A national e-accessibility policy dates from 2011, and Mada, the assistive technology center, has run programs to audit and accredit government websites. Government frameworks refer to WCAG. The sources we read are several years old, so current guidance should be checked with Mada | The conformance level your buyer expects, in writing |
| Arabic for officials and citizens | Arabic is the official language. Anything a ministry, a regulator or a Qatari citizen uses needs complete, well-set Arabic | Which user groups work in Arabic, and who approves terminology |
| English for the workforce | Engineers, clinicians, teachers and service staff from many countries work in English, often as a second language | A plain-language standard for interface text |
| Data-heavy screens | Dashboards, registers and reports dominate enterprise products. Tables and charts have to work in both reading directions | The key tables and charts, and how each mirrors |
| Procurement and documentation | Tenders specify deliverables and acceptance. Design output is judged against the document, not only by eye | The deliverables list, matched to the tender's wording |
| Personal data | The privacy law centers on consent and purpose. Forms that collect personal or sensitive details need notices people can understand | Where data is requested, and the notice at each point |
Design work we do for products in Qatar
These engagements match how large organizations in Qatar buy design: defined scope, defined deliverables.
Portal redesign
For supplier, student, patient or employee portals that users find hard to use.
- Roles and top tasks identified from data and interviews
- Navigation restructured around those tasks
- Forms shortened and staged
- Screens designed in English and Arabic
- Tested with users from each role
- Specification delivered against the tender's list
Accessibility review
For organizations preparing for an audit or accreditation.
- Key journeys assessed against the agreed WCAG level
- Checked with keyboard and screen reader in both languages
- Findings ranked by severity
- Design corrections produced
- Guidance written for developers and content editors
Dashboard and reporting design
For management and operations teams.
- Decisions the dashboard should support are listed
- Measures and their definitions agreed
- Layouts designed for desktop and tablet
- Arabic and English variants checked
- Prototype reviewed with the people who will use it
Internal tool design
For teams replacing spreadsheets or an aging system.
- Current work observed
- Steps and exceptions mapped
- Screens designed around the real sequence
- Prototype tested with staff
- Components documented for the build
What we design
Task-centered portals
Navigation and screens organized around what each role comes to do, not around the organization chart.
Accessible interfaces
Components specified to the level your buyer requires and checked with assistive technology in English and Arabic.
Forms and approvals
Long processes broken into clear stages, with saved progress, plain errors and visible status.
Dashboards and tables
Dense information made readable, with behavior defined for both reading directions.
UX audits
A structured review with ranked findings and corrected designs. Our UX audit services page describes the method.
Tender-ready documentation
Design files, specifications and reports organized to match the deliverables your contract names.
What we need from you
- The product, its user roles and what each role does most
- Tender or contract requirements for design and accessibility
- Usage data, support tickets or complaints about the current product
- Brand guidelines in English and Arabic
- Access to a few users from each role for testing
Ownership and licensing terms are defined in the project agreement.
A readiness checklist for a design project in Qatar
Before design starts
0 of 8 checkedWhat to do next
Tell us about the product, who uses it and what the contract asks of the design. We will reply with the engagement we would suggest and a deliverables list matched to your requirements. Start a conversation or book a 30-minute call.
If the product is a portal, our client portal requirements checklist helps set out roles and tasks first.
Common questions
Is web accessibility required in Qatar?
For government websites, national policy has called for accessibility since 2011, and Mada has audited and accredited sites against it. The material we read is several years old, so ask Mada or your buyer for current requirements. Private companies are generally bound only by what a contract states, though suppliers to government are commonly asked to meet the same standard.
How do you make a complex portal easier to use?
By finding the few tasks that account for most visits and making those fast. We study usage data and talk to users in each role, then rebuild navigation around tasks, shorten forms and show status clearly. Rarely used functions remain available without crowding the main screens. Testing with real users confirms whether the changes help.
Do tables and dashboards work in Arabic?
They do when designed for it. Column order reverses, text aligns to the right, and numbers keep their own direction. Charts with a time axis need a decision about which way time runs. We define these rules once in the design system and apply them to every table and chart, so that Arabic users are not left with a mirrored approximation.
Can your deliverables follow our tender's format?
Yes. We read the tender's deliverables and acceptance sections at the start and structure our output to match: the documents named, in the order asked, with the terminology the contract uses. That makes acceptance simpler for your project manager and avoids late requests for material that was produced but filed under another name.
Where to go from here
Related serviceUI/UX DesignInterface design that engineers can actually build