Noor Al Mamzar Medical Center

A bilingual, multi-specialty site that has to earn trust twice.

Noor Al Mamzar runs dental, laser hair removal, dermatology, and plastic surgery under one roof, for a Dubai audience that moves between Arabic and English day to day — a different brief from a single-language clinic. Every heading, stat, and call to action needs to carry the same confidence in both directions, not read like a translation bolted onto an English layout.

The scope was design only: a system fully specified in Figma for another team to build, with no chance to sit through development and catch the small stuff — which pushed more of the decision-making into the file itself than usual.

Put the proof and both ways to act before the scroll.

With four specialties and two languages competing for the same header, the hero had to do three jobs at once: say who the clinic is, show the numbers that back it up, and offer both ways to get in touch — without turning into a wall of competing claims.

A sage-and-cream palette, warmer than the clinical blues this category defaults to.

Instead of the brighter clinical blue-greens most other practices in this category use, the identity leans on a muted sage green against a warm cream surface — closer to a wellness-spa palette than a hospital one, while still reading clean against the near-black ink used for body copy.

The palette stays narrow — one sage ground, one cream surface, three supporting greys for hierarchy — so four very different treatments, from dental to plastic surgery, can share it without any one needing its own color story.

One continuous photo splits in two; on mobile, it becomes two separate portraits.

On desktop, the "Request a Call Back" and "Chat on WhatsApp" cards sit side by side over a single continuous photograph that runs behind both of them — one image doing double duty for two different calls to action. On mobile, that photo isn't just resized: it's replaced with two independently cropped portraits, each toned to match its card — a warm, light crop behind the call-back form, a darker, moodier crop behind WhatsApp — a deliberate rebuild for the stacked layout, not a shrunk version of the desktop photo.

Delivered as a build-ready system, not a set of screens.

With no WordPress or Elementor build in scope this time, the deliverable was a fully specified Figma file: component variants for every repeating pattern — the stat tile, the service card, the two-CTA hero — both language directions laid out side by side, and type, spacing, and color documented as reusable tokens, so a separate development team could build it without needing to guess.

A few calls that read as UX decisions, not decoration.

Looking back at it with a UX eye, three decisions do more work than they look like they do:

Two calls to action, repeated — never a third competing with them.

Book Now and WhatsApp stay the only two actions across the page — repeated at the hero, after the services carousel, and again in the dedicated call-back section — rather than being joined by a third or fourth competing CTA, so the decision stays binary wherever a visitor lands.