Back to work

Product design · Banking

Emirates Islamic Digital UX

Turning low digital engagement into repeat usage for Emirates Islamic’s existing customers, as the only designer in an agile squad.

  • Banking B2C
  • Mobile, tablet + online banking
  • Sole designer in an agile squad
  • 20 sprints
Client
Emirates Islamic Bank
Year
2018
Role
Product Designer
Platforms
Mobile, tablet apps & online banking
Timeline
10 months · 20 two-week sprints
The Emirates Islamic website on desktop next to the EI+ mobile app login screen.

01 · Overview

Overview

Emirates Islamic Bank (EIB) is a United Arab Emirates based bank providing Sharia-compliant banking. As part of the Emirates NBD group, it serves its own base of premium, loyal customers.

Those customers were not using digital banking. I was the only designer in the agile squad formed to change that, responsible for all UX from concept to after-live support, across the mobile app, tablet app and online banking website.

02 · The problem

Low engagement, frequent complaints

Emirates Islamic’s existing customers showed low engagement with digital channels: digital user retention was below 20%. The customers who did use digital services complained often, through retail branches and app store reviews.

  1. 01Low digital engagement limited the bank’s cost-saving opportunities and revenue growth.
  2. 02Frequent complaints risked customer satisfaction and retention. Left unresolved, they meant higher operational costs and missed opportunities to grow through digital channels.

03 · Goals & objectives

Three objectives for the squad

The goal was to enhance the overall user experience and increase digital adoption among existing customers. For UX, that became three objectives.

  1. 01

    Objective 1

    Fix at least 70% of the high-impact user pain points identified by the business.

  2. 02

    Objective 2

    Increase the digital user retention rate to above 50%.

  3. 03

    Objective 3

    Increase the conversion rate of digital banking users by at least 20%.

04 · Process

UX inside a two-week sprint cycle

The squad had limited time, so the challenge was fitting UX methods into agile. After a stakeholder workshop, UX discovery happened mainly at the product backlog stage.

  1. 01 · UX discovery

    Backlog grooming

    Understood the business goal and user pain point behind each story. Validated and grouped stories, prioritised them through user story mapping, and sent a user survey when a story needed more evidence before entering a sprint.

  2. 02 · Sizing

    Sprint planning

    Assigned story points by effort, sorted stories into small, medium and large, and explained the rationale for prioritising each design deliverable.

  3. 03 · Testing

    Agile sprints

    Paper sketches for brainstorming, guerrilla testing with employees outside the squad to check each design hypothesis, and competitor analysis of similar finance products.

User story map: the squad’s three objectives across the top, the epics that serve each, and user stories below in P1, P2 and P3 rows.

User story mapping, prioritised by impact against each objective.

05 · UI design during sprints

Two design tracks, sized to the work

New features
Understand → Page flow and information architecture → Wireframes → UI design → Testing.
Minor requirements
Understand → Paper sketches → UI design → Testing.

Work designed in sprints included ATM self-withdrawal on mobile (a new feature), the NOL top-up redesign, international transfer, and spending analysis and bill payments in online banking.

International transfer on mobile, before and after the enhancement.
New digital features, cardless cash withdrawal and Noqodi payments, and financial budgeting enhancements on the tablet app.

06 · Outcomes

Retention up, complaints down

Digital customer retention
Increased from below 20% to a weekly average of 55% by sprint 20, beating the 50% target.
Customer advocacy (NPS)
Exceeded 85.
Customer complaints
Reduced to fewer than 3 per week by sprint 18.
Feature engagement
Newly introduced features showed returning and regular customer usage.

07 · Why it worked

Why the numbers moved

  1. 01Improved existing banking journeys by addressing recurring customer pain points.
  2. 02Reduced customer friction and improved the overall digital banking experience.
  3. 03Introduced customer-requested features to address unmet needs.
  4. 04Encouraged repeat usage and stronger engagement with digital banking services.
  5. 05Improved customer advocacy and reduced recurring complaints.

08 · Measurement

How we measured it

Digital customer retention
Digital traffic analytics tracking returning customers after 30 days.
NPS
Customer feedback and recommendation scores.
Customer complaints
Weekly complaint volume, monitored across sprint releases.
Feature adoption
Unique customers using newly released features.
Repeat feature usage
Customers returning to use the same features over a defined 30-day period.

Conclusion

“Twenty sprints took digital customer retention from below 20% to a weekly average of 55%, with NPS above 85 and complaints under 3 a week by sprint 18.”

The lesson I carry forward: guerrilla testing validated assumptions quickly, but a few stories still needed rework, so formal usability testing belongs inside the sprints.

Next case studies

More works

Portrait of Mohammed Rizwan

Mohammed Rizwan

Senior Product Designer and UX Lead

Location
Dubai, UAE
Experience
15+ years

Drag to swing · Click to flip

Off the clock

Rizwan wearing a blue helmet and harness in a misty mountain landscape.

Usually watching a Guy Ritchie film, planning my next trip, or chasing an adrenaline rush.

Click to flip back

LET'S TALK

Let’s build something meaningful together.

Book a meeting

Connect with me

Emailmailrazik@gmail.comPhone+971 556703127