ICS — bilingual

ICS — Product Design & UX

ICS.

Bilingual Arabic/English data and reporting interfaces

Product design and UX for NGO and UN-agency platforms: data entry, dashboards and reporting built to read correctly in both Arabic and English, with right-to-left treated as a first-class direction rather than a mirrored afterthought.

Duration
—
Tools
Figma
Team
—
Year
2026

📋Overview

Data and reporting interfaces for NGO and UN-agency platforms — the systems field teams use to record what happened, and that programme staff use to report it upward.

One of those platforms is Givy, shown alongside ICS in the header.

The defining constraint was language: these products are used in Arabic and in English, often by the same organisation on the same data, so both directions had to be first class rather than one being a mirrored copy of the other.

👩‍💻Who it is for

Field and programme staff entering data, often on poor connections and under time pressure, and the coordinators and agency reviewers who read the reports that come out of it.

⚡️The Challenge

Bilingual products usually fail in the same way: the interface is designed in English, then flipped. Numbers, dates, units, mixed-direction strings and dense tables are exactly where that flip breaks down — and reporting interfaces are made almost entirely of those things.

The design problem was to make one system that reads correctly in both directions, with no second-class language — and to keep data entry fast enough that field staff do not route around it.

Bilingual Audit — Where the Mirror Breaks

🔍Designing both directions at once

Every screen was designed and reviewed in Arabic and English side by side, so a layout that only worked in one direction never reached build. Direction-dependent decisions — alignment, iconography, progress and sequence, table column order — were settled as rules rather than per screen.

💡Design principles

  • RTL is a direction, not a translationLayout, flow and reading order mirror; numerals, units and chart axes follow their own conventions rather than flipping blindly.
  • Dense data needs structure, not shrinkingReporting tables earn their density through hierarchy, grouping and sticky context — not smaller type.
  • Entry built for the fieldShort, resumable forms that tolerate interruption and weak connectivity, because the alternative is paper.
One Layout, Two Directions

FLOW 01

Data entry

Forms shaped around what a field worker actually collects, in the order they collect it, with validation that explains itself in the language being used rather than translating an English error.

Data Entry — Arabic
Data Entry — English

FLOW 02

Dashboards

Overviews that answer the coordinator's standing questions first — what changed, where, and what needs attention — with charts and legends that hold their meaning in both directions.

Programme Dashboard

FLOW 03

Reporting

Report building designed as a repeatable task rather than an export button: saved configurations, consistent structure, and output that stays legible once it leaves the product as a document.

Report Builder & Output

FLOW 04

The bilingual system

Type scales, spacing, icon sets and component rules documented for both languages, so a new screen is correct in Arabic and English by construction instead of by review.

Bilingual Component Rules

📊What shipped

  • One product, two directionsArabic and English treated as equals, with direction rules settled once and applied system-wide.
  • Field-tolerant data entryShort, resumable forms built for interruption and weak connectivity.
  • Reporting as a repeatable taskSaved configurations and consistent output structure, legible after export.

🌟Design the harder direction first

Starting in Arabic rather than retrofitting it surfaced the layout decisions that actually break under mirroring — mixed-direction strings, numerals, table order — while they were still cheap to change.