Skip to content

Enterprise SaaS · No-code builders · Research · User experience · Visual design

Turning a hard-coded admin platform into visual, no-code builders.

Meydan Free Zone runs every licence and visa application on EZMS. How each one moved was hard-coded, so every change needed a developer. I led the admin redesign that put those rules on screen.

Role
Senior Product Designer, NetBramha. Admin track lead
Team
A design lead, 4 UX designers, 2 visual designers
Timeline
6 months, 2 weeks in Dubai, 2024
Status
Signed off and handed over, April 2024

The client. EZMS is the platform behind Meydan Free Zone: a customer portal, a staff portal, and an admin where the zone's own team builds every service.

In short. Each service's rules lived in code, spreadsheets, a slide deck and people's heads. I gave every rule a place on screen and designed the builders that let admins change them.

10 admin modules and about 700 screens, tested with two admins.

The job. Admins design the route every application takes.

Customers apply up front, staff process behind the scenes, and admins decide how every request moves between them.

Service map. Front stage: direct customers and channel partners apply for a service request (company, employee or Meydan+ services). Back stage: executives and team leads process it, operations managers monitor it and senior management approves it. Government bodies and other third parties verify when a service needs it. The admin, highlighted as my focus, creates each service, manages users and roles, tracks team and task numbers, and handles tickets.
The bird's-eye view I drew after the Dubai research. The customer and staff portals were designed by other tracks; the admin side was mine.

Seven designers, two countries.

Designers in India, stakeholders in Dubai, and weekly admin reviews.

01Design team
A lead, 4 UX and 2 visual designers. I owned Admin.
02EZMS team
Product and engineering, who owned the data model.
03Meydan teams
Reviewed every admin module, usually within two days.

My part. Senior Product Designer, admin track lead

  • Owned the admin track from research to visual design
  • Ran field interviews in Dubai
  • Planned and ran the strategic workshop and the design thinking workshop
  • Turned the research into findings
  • Information architecture and wireframes
  • Admin component library
  • Admin visual design
01Where the rules hid

Every new service needed a developer. Two weeks of research showed why.

We met every team, then looked closely at the admins who set every service up.

The research in seven steps, from brief to direction

  1. 01The briefMeydan’s three goals
  2. 02MethodsInterviews and two workshops
  3. 03People80 people, 38 sessions
  4. 04PersonaThe admin, up close
  5. 05Synthesis76 admin notes
  6. 06Findings6 admin pain points
  7. 07Direction5 pillars, 3 principles

Meydan’s brief, and the goal my track owned

1 dayto launch a new service, with no developer

Also on the brief

  • Fewer steps for customers and staff
  • Every conversation in one place
  • A dashboard for each role

Three research methods, compared side by side

A one-to-one interview at a meeting table, with the old admin on a screen behind.
User interviewsOne-to-one, plus live system walkthroughs.
Stakeholders gathered round tables during the strategic workshop.
Strategic workshopStakeholders agreed on goals and vision.
A full room of participants working in groups during the design thinking workshop.
Design thinking workshopGroup exercises on pain points and fixes.

Two weeks in Dubai, customers to senior managers

Most sessions ran in Dubai. I also sat through the old admin’s training.

days of research
11
sessions: interviews and workshops
38
people we spoke to
80
hours of sessions
70+
38 sessions, by where they ran

7 user types, admins were mine

Front stage

  • Direct customers
  • Channel partners

Back stage

  • EZMS admins (my focus)
  • Senior management
  • Operations managers
  • Team leads
  • Entry users

The admin: strong on process, held back by the tool

Persona
AdminBack stage
Digital literacy
5 out of 5
Process literacy
4 out of 5
Tool proficiency
3 out of 5
Works online
4 out of 5
Works offline
1 out of 5

Six admin pain points.

  1. A complex interface
  2. A tedious form builderNeeded a developer
  3. A workflow with no visualNeeded a developer
  4. A static dashboard
  5. Confusing terms
  6. No test environment

The brief said menus. The research said rules.

In the research readout I showed the real blocker: rules nobody could see. Meydan agreed to fix those first, and the menu got tidied too.

02What I chose to fix

We gave every hidden rule a place on screen, in words admins already used.

A zone can't launch a service in a day if its rules are hidden. Each rule needed a home the admin could see and change.

Three pillars set the direction

  1. Accuracy
  2. Efficiency
  3. User centricity
6

major pain points, each given a home on screen

What admins struggled with, how it worked before, and what it became.

Pain pointBeforeAfter
A complex interface24 menu items in one long list6 menu groups, intuitive user flow
A tedious form builderNeeded a developerSlide decks, Excel and a fee calculatorOne setup page for fields, edit rights and a fee formula
A workflow with no visualNeeded a developerRoutes hard-coded by developersA flow map, plus a step list
Confusing termsA login for each jobPlain names, and several roles on one login
A static dashboardNo record of who changed whatServices, tasks, an activity log and version history
No test environmentOnly a live versionDevelopment, testing and live versions
Part of the admin information architecture: login and first-run tour, then dashboard, service, task, user and report modules, each with its goals, actions and the design principle it supports.
Information Architecture
03Building the builders

Every rule got a screen, so no one waits on a developer.

It starts with the sidebar, then the three builders that carry most of the change: services, workflows, and users and roles.

The admin. Everything a zone runs, in one sidebar

Services and processes, content, tasks, team performance, invoices, the directory, users and roles, reports and configuration: 17 menu items, down from 24 in one long list. Organisation setup, shown here, is one of them.

Organisation setup in the new admin: the grouped sidebar on the left, appearance settings for the portal brand in the middle, and recent activity on the right.
  • Grouped by jobDirectory, user management, reports and configuration each get a labelled group, so admins scan by task.
  • A builder behind each oneServices, forms, workflows, roles and reports are made on screen. The next sections show how.
  • The brand tooLogo, colours, login images and links for every portal, changed in Organisation setup and saved.
  • Configuration in one placeOrganisation setup, administration and integrations sit together at the foot of the nav.

Workflow builder. The whole route on one map

The live flows lived in slides and code, and only developers could change them.

The workflow builder: teams connected in order on a map, with returns to the customer, release and reject endings, and a side panel with the selected team's rules.
  • Teams, in orderApprove sends the application to the next team.
  • Back to the customerReturn it for changes, then take the resubmit.
  • Two ways to endEvery route finishes in a release or a reject.
  • Rules for each teamTriggers, actions and a time limit, set on the side.
The same workflow as a step list, with permissions being set for one path.
The same builder as a step list: one team at a time, top to bottom.
Auto task flow settings: if-then conditions that send an application to a team based on the company risk score.

Rules that route on their own

Admins set if-then rules for each team, from "Configure auto task flow" in the team panel. If the company risk score is high, the application goes to S2. Low or medium goes to CS1. No developer in the loop.

Documentation sheet for the workflow builder, showing each state of the team and connector components with notes.

Written down for developers

Every state of the team and connector components, from hover to flow end, documented next to the designs so the builder could be built without guesswork.

The hard part. Every rule had to work in both views

Triggers, actions, time limits, rights, skill sets, parallel teams and returns to the customer had to behave the same in the map and the list. Only the view changes.

Every builder shows its rules

Forms, prices and access: each rule sits on screen, not in someone's head.

The form builder for a licence renewal form, with field types on the left and field properties on the right.

17 field types

In the form builder, with a desktop and mobile preview.

A fee formula: if the licence validity period and formation type match, then the fee is set, built from operations and conditions.

Fees as a formula

Worked out from what the customer fills in, not typed by hand.

Also built on the same idea: the email builder, document builder, content master and organisation setup.

User and role management. One login with many roles, instead of one per job

Team, sub-team and role replaced five words for the same idea.

The users table with backstage, consultant and customer tabs, each person's availability, status and assigned roles.
  • Staff, agents, customersEach in its own tab.
  • Who's free right nowAvailable, busy or offline.
  • Several roles, one rowInstead of one login each.
Creating a role: module access checkboxes, with an option to start from an existing role such as Admin or Manager.

Roles start from a copy

A new role can start from an existing one, then be adjusted.

Service management. Every service set up on one page, not in slides and Excel

Admins pick a category, a service and an action, then fill in the rest. The same page tells customers what to send.

Service management: a table of service types with category, description, status and jurisdiction, and a menu for each row.

Every change leaves a record. Who made it, when, and what came before.

The old admin kept no record of who changed what. Now every service and workflow keeps one, in a panel beside the work.

Three side panels: service details with an activity list filtered by users or system, a workflow activity log, and version history with saved and auto-saved versions.

3 guards against breaking live work

Where the design stops an admin before something breaks.

A warning before deactivating a team that has 30 open applications.

30 open applications

The warning before a busy team is switched off.

Closing a team: a list of its open tasks, each with a choice of who takes it over.

Work is handed over first

Closing a team lists every open task and asks who takes it.

Bulk invite from a CSV file: rows with a wrong team or role are left unticked, with a dropdown to fix each one.

Bad CSV rows fixed in place

Rows with a wrong team or role stay unticked, with a dropdown to fix them.

One library, any client's brand

Brand colours are settings, so each zone sets its own logo and colour without new code.

Pieces of the admin design library: colour palette, typography in Satoshi, buttons, form controls, status tags and the table pattern.
The visual designers built the core library. I proposed the typeface and built the admin components and the table pattern.
  • Satoshi over ArialClearer look-alike letters, and equal-width digits for fees and dates.
  • One table patternPick, filter, resize and export columns on every list.
  • Never colour aloneEvery status has a text label, like Active or Busy.
04Handed over

Signed off and handed over in April 2024. No usage data yet.

This chapter shows what was delivered and what two admins said in testing.

What was handed over

admin modules
17
desktop screens, including states
~700
review rounds on user management
6

Tested with two admins

Login
Straightforward, task completed.
Dashboard
"An extremely useful consolidation."
Service setup
Understood every data point.
Form, email and document
Tasks completed. Formula pricing cuts manual effort.
Workflow
Map view to edit, step list to start.

UI feedback report, 26 Feb 2024, with one experienced and one new admin. 12 pieces of feedback; the top ask, a short guide in each builder, was added after the test.

The flow view offers a better experience for editing and comprehending the entire flow, although it may appear complex initially.
UI feedback report, admin, Feb 2024

What I got wrong. One service shape didn't fit every client.

In testing, Meydan wanted an unused field hidden, and other zones needed process types like Suspend. The brand could change per client; the service model couldn't.

Next time I'd make the service model switchable per client from day one.

What I'd keep, what I'd change.

  1. 01Map every rule before drawing a screenThe research told us what each builder needed.
  2. 02Prototype drag and drop for realA working prototype, tested with admins from a second free zone.
  3. 03Measure time to a live serviceAgainst the one-day goal, plus developer tickets per new service.

Still open: reporting. The report builder is still greyed out.

The project, at a glance.

  1. ClientEZMS, the platform behind Meydan Free Zone in Dubai, through NetBramha.
  2. ToolsFigma for every screen, flow and the design library. A shared sheet for the research synthesis.

Next case study

A job portal (name withheld)Four job-portal products, one design system, one switch between them.

Ask-bidyut · tty1

BIDYUT-OS 1.0 · PORTFOLIO ASSISTANT

(c) 2026 Bidyut Bera

Hi, I'm AI Bidyut. I answer from my portfolio, so I may get things wrong. Pick a question or type your own.

Chats are processed by an AI provider. Don't share sensitive info.