EnterpriSe application design

Reimagining Orbixa VMS Software

Reimagining Orbixa VMS Software

Designing seamless, scalable surveillance systems trusted by government and public organizations for everyday security monitoring

Designing seamless, scalable surveillance systems trusted by government and public organizations for everyday security monitoring

Industry :

Video management software

Client :

Orbixa Vision Pvt. Ltd.

Project Overview

Customers bought a system their own teams could not run. I led the redesign that put investigation back in their hands.

Background

Orbixa Vision VMS is used by government and enterprise security teams at railways, airports and police headquarters. Operators use it to monitor live feeds and to investigate what happened after an incident. These teams are meant to run it themselves.

The Challenge

In practice they could not. One client said the interface looked like a college project. Every deployment needed long training, and when something went wrong on site, customers called our support team instead of investigating themselves. In surveillance, a delayed investigation is the failure the product exists to prevent.

What it was costing

Business cost · what Orbixa paid

Customers depended on our support team

Customers were meant to run the product themselves. Instead, every investigation waited on our support team.

~62%of support issues were people stuck on how to do something, not software failingMy 2022 estimate
Product problemFrom support insights

Recordings hard to find

  1. 1
    Event search sits inside playbackSearching by time and searching by event share one panel, so operators first work out which half of the screen applies.
  2. 2
    Two calendars for one rangeStart and end each get a full calendar, so picking one range means working two separate grids.
  3. 3
    Time set field by fieldHours, minutes and seconds are typed or nudged with tiny arrows. Slow when you need one precise moment.
Product problemFrom support insights

Jargon in error messages

  1. 1
    Raw stream addressThe operator sees the camera's technical stream address. It means nothing to them and only adds noise.
  2. 2
    Error with no next step'Device is unreachable from server !!' says what failed, but not why or what to do. So operators call support.
  3. 3
    'Trying..' with no endRecording and streaming show 'Trying..' with no time, progress or fallback, so nobody knows if it will recover.
  4. 4
    Placeholder values as dataType and Model read 'OTHER'. It looks like information but tells the operator nothing.
Product problemFrom support insights

Confusing analytics setup per camera

  1. 1
    Internal version on screenA JSON version number sits at the top of an operator screen. It's for developers, not for someone setting up a camera.
  2. 2
    Machine learning choices with no explanationModel, Backend and Confidence appear with no description, so operators guess what each choice does.
  3. 3
    Modes named like codeLearningBased, checkMotion and checkNoMotion are named like variables, not by what they do.
  4. 4
    Settings mixed togetherGeneral and analytics-specific settings sit together in collapsed panels, so operators open each one to find what they need.
Business cost · what Orbixa paid

Every contract carried a training cost and a slow go-live

Customers needed long training before go-live, and what they learned in one module didn't carry over to the next.

~30-40%more steps than competitor products for the same common tasksCounted by hand, 2022
Product problemFrom support insights

Every module had its own navigation

  1. 1
    A separate appConfiguration lives in its own app with its own top tabs. Operators switch apps to change a setting.
  2. 2
    Then sub-tabsInside a module, another row of tabs splits the page again.
  3. 3
    Then a task listA third level of choices sits in a side list.
  4. 4
    Four levels deepDrives get yet another set of tabs. It's easy to lose track of where you are.
Product problemFrom my review of the screens

Same controls work differently across modules

  1. 1
    Date typed into a fieldHere, date and time go into a text field with up and down arrows. Playback uses calendars for the same job.
  2. 2
    A second time pickerA clock icon opens yet another way to set time, in the same window.
  3. 3
    Two dropdown stylesExport Type and Export File Format are both dropdowns, but they look and behave differently.
  4. 4
    Two button stylesBrowse and Start Export use different styles, so it's unclear which one is the main action.
Business cost · what Orbixa paid

We couldn't answer accessibility requirements from international buyers

Government buyers in the Middle East and Europe ask for accessibility. We had nothing to show.

5-10%of the interface met global accessibility and usability standardsMy 2022 estimate
Product problemFrom my accessibility check

Poor colour contrast

  1. 1
    Dark blue on dark greyThe 'Trying..' status is dark blue on grey and very hard to read, especially in a dim control room.
  2. 2
    Dark green and red on blackThe summary counts use dark green and red on near-black, well below readable contrast.
  3. 3
    Tiny grey hintThe grouping hint is small grey text on grey, easy to miss entirely.
  4. 4
    Colour as the only signalDisconnected is shown only in red. People with colour vision deficiency can't tell it apart.
Product problemFrom my accessibility check

No keyboard access

  1. 1
    No visible focusMoving through the fields with a keyboard shows no highlight, so you can't tell which field is active.
  2. 2
    Options with no focus cueThe checkboxes give no sign of which one the keyboard is on.
  3. 3
    Main action doesn't stand outConnect has no focus or default style, so it doesn't stand out from the rest of the form.
Product problemFrom my accessibility check

No shared focus, error or disabled states

  1. 1
    Error as a blocking pop-upA simple validation message stops everything and must be closed before the operator can fix it.
  2. 2
    Icon looks like closeThe error icon is an X in a box, which reads as a close button, not a warning.
  3. 3
    No hint where to fix it'Select at least one event!!' doesn't say where events are selected.
  4. 4
    Fix hidden in a panelSelect Event sits in a collapsed panel on the left, with nothing pointing to it.
Product problemFrom my accessibility check

No WCAG compliance

  1. 1
    Values cut offDevice name, message and acknowledgement text are cut off, with no way to read them in full.
  2. 2
    Tiny scroll arrowsThe event message hides behind very small scroll arrows that are hard to see and hit.
  3. 3
    Bright white blockA pure white 'No image' block in a dark window causes glare and draws the eye to nothing.
  4. 4
    Low-contrast placeholderThe acknowledgement field and its actions are grey on grey and look disabled even when they aren't.
  5. 5
    Every field looks like an editable formRead-only details sit in boxed fields, so the screen reads like a form to fill in rather than a record to scan.

Research & Insights

Method 01

Competitor analysis

Benchmarked global VMS leaders for UI/UX standards

Method 02

Support insights

Interviewed 4 to 5 internal stakeholders across support and product, and reviewed recorded operator calls to identify recurring pain points

What I estimated at the time

~62%

of support tickets I reviewed were people stuck on how to do something, not software failing.

~30-40%

more steps than competitor products for the same common tasks, counted by hand.

5-10%

of the interface met global accessibility and usability standards when I checked it.

02468Create ReportAccess Live FeedExport Settings
Competitor Avg.
Current Avg.

Navigation efficiency gap

Task analysis showed that our system required significantly more steps to complete common operations compared to industry-leading competitors. This inefficiency translated directly into wasted operator time and increased error rates.

Targets we set before the build, not results

These were improvement targets derived from competitor benchmarking, set before the redesign shipped. They are not measured results. What actually happened after launch is in Outcome & Impact below.

0255075100Task CompletionError RateUser Satisfaction
Target
Baseline

EXPLORATION

Three answers to the same screen

I did not go straight to one answer. I took the same screen in three directions to find out what we would be giving up in each.

01

BEFORE

Image 1

The inherited layout

Years of features added on top of each other. The controls people used most sat among the ones they almost never touch, so operators hunted for the same things every shift.

02

EXPLORED

Image 1

The focused view

I stripped it back to the main task and moved everything else one level down. On a screenshot it looked great. Then I put it in front of our support, pre-sales and testing teams, who use this product every day.

Things they do twenty times a shift were now two steps away instead of one. I had made it easier to learn and slower to use, and in a control room that is the wrong trade.

03

CARRIED FORWARD

Image 1Image 2
1 / 2

The balanced system

This kept the calm of the focused view, but the actions operators use every day stayed in reach and the deeper tools sat one deliberate step behind.

It is the version that holds both halves of the goal, faster to learn, without taking away the power operators need.

WHAT ACTUALLY CHANGED

Fewer choices on screen, not fewer capabilities. The most frequent actions are one step away. The deeper toolset is one deliberate step behind.

DECISIONS

What I designed and what I didn't

Each of these was a choice with more than one answer. Here's what we took, what we passed on, and what it cost.

Decision 1

Decision 2

Decision 3

Decision 4

01

Fix this product, or build the system

The options

Fix VMS and move on. Ships sooner, and it's what everyone expected. Or build a design system from zero across all three products, which had the same inconsistency and the same accessibility gaps.

What we took

The system. Components, use cases, spacing and type tokens defined once. Every state, focus, error, disabled, empty, lives in the library, so accessibility is structural instead of fixed screen by screen. Developers pull from one source. QA validates against the system while modules are built, not after.

What it cost

Time on this release, and a maintenance burden we now own, including the accessibility work a mature library would have given us free. Taken because in an operator product the behaviour of the components is the product.

Image 1Image 2Image 3
1 / 3

THE THROUGH-LINE

None of these decisions were about adding more. Each one traded surface complexity for a clearer path through the task, and together they turned a crowded tool into something operators trusted at a glance.

The Challenges

Legacy technology constraints

The existing system was built on Windows Presentation Foundation (WPF), requiring careful consideration of platform limitations while pushing for modern design patterns.

Design language unification

Orbixa had multiple products with inconsistent interfaces. Creating a unified system that worked across all platforms while respecting individual product needs was complex.

Security & simplicity balance

Designing for high-security environments meant balancing strict access controls and detailed logging with the need for an intuitive, accessible interface.

Image 1Image 2Image 3
1 / 3
Image 1Image 2Image 3
1 / 3

Outcome & Impact

Slide 1
Click to zoom
Slide 1
Click to zoom
Image 1Image 2Image 3Image 4Image 5Image 6Image 7Image 8Image 9Image 10
1 / 10
Image 1Image 2Image 3Image 4Image 5Image 6Image 7Image 8Image 9Image 10
1 / 10

"The redesigned VMS helped us align our visual language across products while making the experience significantly easier for on-ground operators."

— Internal Product Owner, Orbixa Vision

KEY LEARNING

"In high-stakes environments, clarity and speed matter more than aesthetics."

"In high-stakes environments, clarity and speed matter more than aesthetics."

Designing for surveillance systems taught me that beauty in design comes from function, when operators can respond faster, make fewer errors, and trust the interface completely.

Designing for surveillance systems taught me that beauty in design comes from function, when operators can respond faster, make fewer errors, and trust the interface completely.

My Role

As Senior Product Designer, I led the end-to-end redesign of the VMS platform, from research and strategy through to final implementation and developer handoff.

Research & Discovery

—

Analyzed support insights and competitor products to identify workflow inefficiencies

—

Conducted stakeholder interviews with the support and product teams, and reviewed recorded operator support calls

—

Mapped five operator-side roles, operator, administrator, investigator, support and pre-sales, against what each is measured on and where their workflow breaks

Design & Systems

—

Redesigned core workflows including video analytics, camera management, and logs

—

Built scalable design system adaptable to Windows (WPF) and multiple products

—

Built accessibility into the design system by auditing WCAG 2.1 AA and defining focus, error, disabled, empty, and failure states, making compliance structural, not screen-specific.

Collaboration

—

Partnered with PMs to align design decisions with business goals

—

Worked closely with developers to ensure accurate implementation

—

Coordinated with QA team for usability validation and testing

Impact

—

62% of support tickets were usability issues, the number that made the business case internally

—

The design system now runs across the Orbixa Vision product line

—

The accessibility work is what makes Middle East and Europe deployment a conversation at all

Zahid Raza
Zahid Raza

Hi

Hi

Curious about the process behind the pixels?

Dive into the stories behind each project, how design decisions shaped better user experiences.

Senior Product DesignerEnterprise UXDesign Systems SpecialistNew Delhi, INAvailable for WorkVideo Management SystemAnalytic Manager10 Years ExperienceOrbixa Vision
Available for Work
LocationNew Delhi, IN
Local Time · IST—
Weather—
Find me on
© 2026 All rights reserved by ZHD

EnterpriSe application design

Reimagining Orbixa VMS Software

Reimagining Orbixa VMS Software

Designing seamless, scalable surveillance systems trusted by government and public organizations for everyday security monitoring

Designing seamless, scalable surveillance systems trusted by government and public organizations for everyday security monitoring

Industry :

Video management software

Client :

Orbixa Vision Pvt. Ltd.

Project Overview

Customers bought a system their own teams could not run. I led the redesign that put investigation back in their hands.

Background

Orbixa Vision VMS is used by government and enterprise security teams at railways, airports and police headquarters. Operators use it to monitor live feeds and to investigate what happened after an incident. These teams are meant to run it themselves.

The Challenge

In practice they could not. One client said the interface looked like a college project. Every deployment needed long training, and when something went wrong on site, customers called our support team instead of investigating themselves. In surveillance, a delayed investigation is the failure the product exists to prevent.

What it was costing

Business cost · what Orbixa paid

Customers depended on our support team

Customers were meant to run the product themselves. Instead, every investigation waited on our support team.

~62%of support issues were people stuck on how to do something, not software failingMy 2022 estimate
Product problemFrom support insights

Recordings hard to find

  1. 1
    Event search sits inside playbackSearching by time and searching by event share one panel, so operators first work out which half of the screen applies.
  2. 2
    Two calendars for one rangeStart and end each get a full calendar, so picking one range means working two separate grids.
  3. 3
    Time set field by fieldHours, minutes and seconds are typed or nudged with tiny arrows. Slow when you need one precise moment.
Product problemFrom support insights

Jargon in error messages

  1. 1
    Raw stream addressThe operator sees the camera's technical stream address. It means nothing to them and only adds noise.
  2. 2
    Error with no next step'Device is unreachable from server !!' says what failed, but not why or what to do. So operators call support.
  3. 3
    'Trying..' with no endRecording and streaming show 'Trying..' with no time, progress or fallback, so nobody knows if it will recover.
  4. 4
    Placeholder values as dataType and Model read 'OTHER'. It looks like information but tells the operator nothing.
Product problemFrom support insights

Confusing analytics setup per camera

  1. 1
    Internal version on screenA JSON version number sits at the top of an operator screen. It's for developers, not for someone setting up a camera.
  2. 2
    Machine learning choices with no explanationModel, Backend and Confidence appear with no description, so operators guess what each choice does.
  3. 3
    Modes named like codeLearningBased, checkMotion and checkNoMotion are named like variables, not by what they do.
  4. 4
    Settings mixed togetherGeneral and analytics-specific settings sit together in collapsed panels, so operators open each one to find what they need.
Business cost · what Orbixa paid

Every contract carried a training cost and a slow go-live

Customers needed long training before go-live, and what they learned in one module didn't carry over to the next.

~30-40%more steps than competitor products for the same common tasksCounted by hand, 2022
Product problemFrom support insights

Every module had its own navigation

  1. 1
    A separate appConfiguration lives in its own app with its own top tabs. Operators switch apps to change a setting.
  2. 2
    Then sub-tabsInside a module, another row of tabs splits the page again.
  3. 3
    Then a task listA third level of choices sits in a side list.
  4. 4
    Four levels deepDrives get yet another set of tabs. It's easy to lose track of where you are.
Product problemFrom my review of the screens

Same controls work differently across modules

  1. 1
    Date typed into a fieldHere, date and time go into a text field with up and down arrows. Playback uses calendars for the same job.
  2. 2
    A second time pickerA clock icon opens yet another way to set time, in the same window.
  3. 3
    Two dropdown stylesExport Type and Export File Format are both dropdowns, but they look and behave differently.
  4. 4
    Two button stylesBrowse and Start Export use different styles, so it's unclear which one is the main action.
Business cost · what Orbixa paid

We couldn't answer accessibility requirements from international buyers

Government buyers in the Middle East and Europe ask for accessibility. We had nothing to show.

5-10%of the interface met global accessibility and usability standardsMy 2022 estimate
Product problemFrom my accessibility check

Poor colour contrast

  1. 1
    Dark blue on dark greyThe 'Trying..' status is dark blue on grey and very hard to read, especially in a dim control room.
  2. 2
    Dark green and red on blackThe summary counts use dark green and red on near-black, well below readable contrast.
  3. 3
    Tiny grey hintThe grouping hint is small grey text on grey, easy to miss entirely.
  4. 4
    Colour as the only signalDisconnected is shown only in red. People with colour vision deficiency can't tell it apart.
Product problemFrom my accessibility check

No keyboard access

  1. 1
    No visible focusMoving through the fields with a keyboard shows no highlight, so you can't tell which field is active.
  2. 2
    Options with no focus cueThe checkboxes give no sign of which one the keyboard is on.
  3. 3
    Main action doesn't stand outConnect has no focus or default style, so it doesn't stand out from the rest of the form.
Product problemFrom my accessibility check

No shared focus, error or disabled states

  1. 1
    Error as a blocking pop-upA simple validation message stops everything and must be closed before the operator can fix it.
  2. 2
    Icon looks like closeThe error icon is an X in a box, which reads as a close button, not a warning.
  3. 3
    No hint where to fix it'Select at least one event!!' doesn't say where events are selected.
  4. 4
    Fix hidden in a panelSelect Event sits in a collapsed panel on the left, with nothing pointing to it.
Product problemFrom my accessibility check

No WCAG compliance

  1. 1
    Values cut offDevice name, message and acknowledgement text are cut off, with no way to read them in full.
  2. 2
    Tiny scroll arrowsThe event message hides behind very small scroll arrows that are hard to see and hit.
  3. 3
    Bright white blockA pure white 'No image' block in a dark window causes glare and draws the eye to nothing.
  4. 4
    Low-contrast placeholderThe acknowledgement field and its actions are grey on grey and look disabled even when they aren't.
  5. 5
    Every field looks like an editable formRead-only details sit in boxed fields, so the screen reads like a form to fill in rather than a record to scan.

Research & Insights

Method 01

Competitor analysis

Benchmarked global VMS leaders for UI/UX standards

Method 02

Support insights

Interviewed 4 to 5 internal stakeholders across support and product, and reviewed recorded operator calls to identify recurring pain points

What I estimated at the time

~62%

of support tickets I reviewed were people stuck on how to do something, not software failing.

~30-40%

more steps than competitor products for the same common tasks, counted by hand.

5-10%

of the interface met global accessibility and usability standards when I checked it.

02468Create ReportAccess Live FeedExport Settings
Competitor Avg.
Current Avg.

Navigation efficiency gap

Task analysis showed that our system required significantly more steps to complete common operations compared to industry-leading competitors. This inefficiency translated directly into wasted operator time and increased error rates.

Targets we set before the build, not results

These were improvement targets derived from competitor benchmarking, set before the redesign shipped. They are not measured results. What actually happened after launch is in Outcome & Impact below.

0255075100Task CompletionError RateUser Satisfaction
Target
Baseline

EXPLORATION

Three answers to the same screen

I did not go straight to one answer. I took the same screen in three directions to find out what we would be giving up in each.

01

BEFORE

Image 1

The inherited layout

Years of features added on top of each other. The controls people used most sat among the ones they almost never touch, so operators hunted for the same things every shift.

02

EXPLORED

Image 1

The focused view

I stripped it back to the main task and moved everything else one level down. On a screenshot it looked great. Then I put it in front of our support, pre-sales and testing teams, who use this product every day.

Things they do twenty times a shift were now two steps away instead of one. I had made it easier to learn and slower to use, and in a control room that is the wrong trade.

03

CARRIED FORWARD

Image 1Image 2
1 / 2

The balanced system

This kept the calm of the focused view, but the actions operators use every day stayed in reach and the deeper tools sat one deliberate step behind.

It is the version that holds both halves of the goal, faster to learn, without taking away the power operators need.

WHAT ACTUALLY CHANGED

Fewer choices on screen, not fewer capabilities. The most frequent actions are one step away. The deeper toolset is one deliberate step behind.

DECISIONS

What I designed and what I didn't

Each of these was a choice with more than one answer. Here's what we took, what we passed on, and what it cost.

Decision 1

Decision 2

Decision 3

Decision 4

01

Fix this product, or build the system

The options

Fix VMS and move on. Ships sooner, and it's what everyone expected. Or build a design system from zero across all three products, which had the same inconsistency and the same accessibility gaps.

What we took

The system. Components, use cases, spacing and type tokens defined once. Every state, focus, error, disabled, empty, lives in the library, so accessibility is structural instead of fixed screen by screen. Developers pull from one source. QA validates against the system while modules are built, not after.

What it cost

Time on this release, and a maintenance burden we now own, including the accessibility work a mature library would have given us free. Taken because in an operator product the behaviour of the components is the product.

Image 1Image 2Image 3
1 / 3

THE THROUGH-LINE

None of these decisions were about adding more. Each one traded surface complexity for a clearer path through the task, and together they turned a crowded tool into something operators trusted at a glance.

The Challenges

Legacy technology constraints

The existing system was built on Windows Presentation Foundation (WPF), requiring careful consideration of platform limitations while pushing for modern design patterns.

Design language unification

Orbixa had multiple products with inconsistent interfaces. Creating a unified system that worked across all platforms while respecting individual product needs was complex.

Security & simplicity balance

Designing for high-security environments meant balancing strict access controls and detailed logging with the need for an intuitive, accessible interface.

Image 1Image 2Image 3
1 / 3
Image 1Image 2Image 3
1 / 3

Outcome & Impact

Slide 1
Click to zoom
Slide 1
Click to zoom
Image 1Image 2Image 3Image 4Image 5Image 6Image 7Image 8Image 9Image 10
1 / 10
Image 1Image 2Image 3Image 4Image 5Image 6Image 7Image 8Image 9Image 10
1 / 10

"The redesigned VMS helped us align our visual language across products while making the experience significantly easier for on-ground operators."

— Internal Product Owner, Orbixa Vision

KEY LEARNING

"In high-stakes environments, clarity and speed matter more than aesthetics."

"In high-stakes environments, clarity and speed matter more than aesthetics."

Designing for surveillance systems taught me that beauty in design comes from function, when operators can respond faster, make fewer errors, and trust the interface completely.

Designing for surveillance systems taught me that beauty in design comes from function, when operators can respond faster, make fewer errors, and trust the interface completely.

My Role

As Senior Product Designer, I led the end-to-end redesign of the VMS platform, from research and strategy through to final implementation and developer handoff.

Research & Discovery

—

Analyzed support insights and competitor products to identify workflow inefficiencies

—

Conducted stakeholder interviews with the support and product teams, and reviewed recorded operator support calls

—

Mapped five operator-side roles, operator, administrator, investigator, support and pre-sales, against what each is measured on and where their workflow breaks

Design & Systems

—

Redesigned core workflows including video analytics, camera management, and logs

—

Built scalable design system adaptable to Windows (WPF) and multiple products

—

Built accessibility into the design system by auditing WCAG 2.1 AA and defining focus, error, disabled, empty, and failure states, making compliance structural, not screen-specific.

Collaboration

—

Partnered with PMs to align design decisions with business goals

—

Worked closely with developers to ensure accurate implementation

—

Coordinated with QA team for usability validation and testing

Impact

—

62% of support tickets were usability issues, the number that made the business case internally

—

The design system now runs across the Orbixa Vision product line

—

The accessibility work is what makes Middle East and Europe deployment a conversation at all

Zahid Raza
Zahid Raza

Hi

Hi

Curious about the process behind the pixels?

Dive into the stories behind each project, how design decisions shaped better user experiences.

Senior Product DesignerEnterprise UXDesign Systems SpecialistNew Delhi, INAvailable for WorkVideo Management SystemAnalytic Manager10 Years ExperienceOrbixa Vision
Available for Work
LocationNew Delhi, IN
Local Time · IST—
Weather—
Find me on
© 2026 All rights reserved by ZHD

EnterpriSe application design

Reimagining Orbixa VMS Software

Reimagining Orbixa VMS Software

Designing seamless, scalable surveillance systems trusted by government and public organizations for everyday security monitoring

Designing seamless, scalable surveillance systems trusted by government and public organizations for everyday security monitoring

Industry :

Video management software

Client :

Orbixa Vision Pvt. Ltd.

Project Overview

Customers bought a system their own teams could not run. I led the redesign that put investigation back in their hands.

Background

Orbixa Vision VMS is used by government and enterprise security teams at railways, airports and police headquarters. Operators use it to monitor live feeds and to investigate what happened after an incident. These teams are meant to run it themselves.

The Challenge

In practice they could not. One client said the interface looked like a college project. Every deployment needed long training, and when something went wrong on site, customers called our support team instead of investigating themselves. In surveillance, a delayed investigation is the failure the product exists to prevent.

What it was costing

Business cost · what Orbixa paid

Customers depended on our support team

Customers were meant to run the product themselves. Instead, every investigation waited on our support team.

~62%of support issues were people stuck on how to do something, not software failingMy 2022 estimate
Product problemFrom support insights

Recordings hard to find

  1. 1
    Event search sits inside playbackSearching by time and searching by event share one panel, so operators first work out which half of the screen applies.
  2. 2
    Two calendars for one rangeStart and end each get a full calendar, so picking one range means working two separate grids.
  3. 3
    Time set field by fieldHours, minutes and seconds are typed or nudged with tiny arrows. Slow when you need one precise moment.
Product problemFrom support insights

Jargon in error messages

  1. 1
    Raw stream addressThe operator sees the camera's technical stream address. It means nothing to them and only adds noise.
  2. 2
    Error with no next step'Device is unreachable from server !!' says what failed, but not why or what to do. So operators call support.
  3. 3
    'Trying..' with no endRecording and streaming show 'Trying..' with no time, progress or fallback, so nobody knows if it will recover.
  4. 4
    Placeholder values as dataType and Model read 'OTHER'. It looks like information but tells the operator nothing.
Product problemFrom support insights

Confusing analytics setup per camera

  1. 1
    Internal version on screenA JSON version number sits at the top of an operator screen. It's for developers, not for someone setting up a camera.
  2. 2
    Machine learning choices with no explanationModel, Backend and Confidence appear with no description, so operators guess what each choice does.
  3. 3
    Modes named like codeLearningBased, checkMotion and checkNoMotion are named like variables, not by what they do.
  4. 4
    Settings mixed togetherGeneral and analytics-specific settings sit together in collapsed panels, so operators open each one to find what they need.
Business cost · what Orbixa paid

Every contract carried a training cost and a slow go-live

Customers needed long training before go-live, and what they learned in one module didn't carry over to the next.

~30-40%more steps than competitor products for the same common tasksCounted by hand, 2022
Product problemFrom support insights

Every module had its own navigation

  1. 1
    A separate appConfiguration lives in its own app with its own top tabs. Operators switch apps to change a setting.
  2. 2
    Then sub-tabsInside a module, another row of tabs splits the page again.
  3. 3
    Then a task listA third level of choices sits in a side list.
  4. 4
    Four levels deepDrives get yet another set of tabs. It's easy to lose track of where you are.
Product problemFrom my review of the screens

Same controls work differently across modules

  1. 1
    Date typed into a fieldHere, date and time go into a text field with up and down arrows. Playback uses calendars for the same job.
  2. 2
    A second time pickerA clock icon opens yet another way to set time, in the same window.
  3. 3
    Two dropdown stylesExport Type and Export File Format are both dropdowns, but they look and behave differently.
  4. 4
    Two button stylesBrowse and Start Export use different styles, so it's unclear which one is the main action.
Business cost · what Orbixa paid

We couldn't answer accessibility requirements from international buyers

Government buyers in the Middle East and Europe ask for accessibility. We had nothing to show.

5-10%of the interface met global accessibility and usability standardsMy 2022 estimate
Product problemFrom my accessibility check

Poor colour contrast

  1. 1
    Dark blue on dark greyThe 'Trying..' status is dark blue on grey and very hard to read, especially in a dim control room.
  2. 2
    Dark green and red on blackThe summary counts use dark green and red on near-black, well below readable contrast.
  3. 3
    Tiny grey hintThe grouping hint is small grey text on grey, easy to miss entirely.
  4. 4
    Colour as the only signalDisconnected is shown only in red. People with colour vision deficiency can't tell it apart.
Product problemFrom my accessibility check

No keyboard access

  1. 1
    No visible focusMoving through the fields with a keyboard shows no highlight, so you can't tell which field is active.
  2. 2
    Options with no focus cueThe checkboxes give no sign of which one the keyboard is on.
  3. 3
    Main action doesn't stand outConnect has no focus or default style, so it doesn't stand out from the rest of the form.
Product problemFrom my accessibility check

No shared focus, error or disabled states

  1. 1
    Error as a blocking pop-upA simple validation message stops everything and must be closed before the operator can fix it.
  2. 2
    Icon looks like closeThe error icon is an X in a box, which reads as a close button, not a warning.
  3. 3
    No hint where to fix it'Select at least one event!!' doesn't say where events are selected.
  4. 4
    Fix hidden in a panelSelect Event sits in a collapsed panel on the left, with nothing pointing to it.
Product problemFrom my accessibility check

No WCAG compliance

  1. 1
    Values cut offDevice name, message and acknowledgement text are cut off, with no way to read them in full.
  2. 2
    Tiny scroll arrowsThe event message hides behind very small scroll arrows that are hard to see and hit.
  3. 3
    Bright white blockA pure white 'No image' block in a dark window causes glare and draws the eye to nothing.
  4. 4
    Low-contrast placeholderThe acknowledgement field and its actions are grey on grey and look disabled even when they aren't.
  5. 5
    Every field looks like an editable formRead-only details sit in boxed fields, so the screen reads like a form to fill in rather than a record to scan.

Research & Insights

Method 01

Competitor analysis

Benchmarked global VMS leaders for UI/UX standards

Method 02

Support insights

Interviewed 4 to 5 internal stakeholders across support and product, and reviewed recorded operator calls to identify recurring pain points

What I estimated at the time

~62%

of support tickets I reviewed were people stuck on how to do something, not software failing.

~30-40%

more steps than competitor products for the same common tasks, counted by hand.

5-10%

of the interface met global accessibility and usability standards when I checked it.

02468Create ReportAccess Live FeedExport Settings
Competitor Avg.
Current Avg.

Navigation efficiency gap

Task analysis showed that our system required significantly more steps to complete common operations compared to industry-leading competitors. This inefficiency translated directly into wasted operator time and increased error rates.

Targets we set before the build, not results

These were improvement targets derived from competitor benchmarking, set before the redesign shipped. They are not measured results. What actually happened after launch is in Outcome & Impact below.

0255075100Task CompletionError RateUser Satisfaction
Target
Baseline

EXPLORATION

Three answers to the same screen

I did not go straight to one answer. I took the same screen in three directions to find out what we would be giving up in each.

01

BEFORE

Image 1

The inherited layout

Years of features added on top of each other. The controls people used most sat among the ones they almost never touch, so operators hunted for the same things every shift.

02

EXPLORED

Image 1

The focused view

I stripped it back to the main task and moved everything else one level down. On a screenshot it looked great. Then I put it in front of our support, pre-sales and testing teams, who use this product every day.

Things they do twenty times a shift were now two steps away instead of one. I had made it easier to learn and slower to use, and in a control room that is the wrong trade.

03

CARRIED FORWARD

Image 1Image 2
1 / 2

The balanced system

This kept the calm of the focused view, but the actions operators use every day stayed in reach and the deeper tools sat one deliberate step behind.

It is the version that holds both halves of the goal, faster to learn, without taking away the power operators need.

WHAT ACTUALLY CHANGED

Fewer choices on screen, not fewer capabilities. The most frequent actions are one step away. The deeper toolset is one deliberate step behind.

DECISIONS

What I designed and what I didn't

Each of these was a choice with more than one answer. Here's what we took, what we passed on, and what it cost.

Decision 1

Decision 2

Decision 3

Decision 4

01

Fix this product, or build the system

The options

Fix VMS and move on. Ships sooner, and it's what everyone expected. Or build a design system from zero across all three products, which had the same inconsistency and the same accessibility gaps.

What we took

The system. Components, use cases, spacing and type tokens defined once. Every state, focus, error, disabled, empty, lives in the library, so accessibility is structural instead of fixed screen by screen. Developers pull from one source. QA validates against the system while modules are built, not after.

What it cost

Time on this release, and a maintenance burden we now own, including the accessibility work a mature library would have given us free. Taken because in an operator product the behaviour of the components is the product.

Image 1Image 2Image 3
1 / 3

THE THROUGH-LINE

None of these decisions were about adding more. Each one traded surface complexity for a clearer path through the task, and together they turned a crowded tool into something operators trusted at a glance.

The Challenges

Legacy technology constraints

The existing system was built on Windows Presentation Foundation (WPF), requiring careful consideration of platform limitations while pushing for modern design patterns.

Design language unification

Orbixa had multiple products with inconsistent interfaces. Creating a unified system that worked across all platforms while respecting individual product needs was complex.

Security & simplicity balance

Designing for high-security environments meant balancing strict access controls and detailed logging with the need for an intuitive, accessible interface.

Image 1Image 2Image 3
1 / 3
Image 1Image 2Image 3
1 / 3

Outcome & Impact

Slide 1
Click to zoom
Slide 1
Click to zoom
Image 1Image 2Image 3Image 4Image 5Image 6Image 7Image 8Image 9Image 10
1 / 10
Image 1Image 2Image 3Image 4Image 5Image 6Image 7Image 8Image 9Image 10
1 / 10

"The redesigned VMS helped us align our visual language across products while making the experience significantly easier for on-ground operators."

— Internal Product Owner, Orbixa Vision

KEY LEARNING

"In high-stakes environments, clarity and speed matter more than aesthetics."

"In high-stakes environments, clarity and speed matter more than aesthetics."

Designing for surveillance systems taught me that beauty in design comes from function, when operators can respond faster, make fewer errors, and trust the interface completely.

Designing for surveillance systems taught me that beauty in design comes from function, when operators can respond faster, make fewer errors, and trust the interface completely.

My Role

As Senior Product Designer, I led the end-to-end redesign of the VMS platform, from research and strategy through to final implementation and developer handoff.

Research & Discovery

—

Analyzed support insights and competitor products to identify workflow inefficiencies

—

Conducted stakeholder interviews with the support and product teams, and reviewed recorded operator support calls

—

Mapped five operator-side roles, operator, administrator, investigator, support and pre-sales, against what each is measured on and where their workflow breaks

Design & Systems

—

Redesigned core workflows including video analytics, camera management, and logs

—

Built scalable design system adaptable to Windows (WPF) and multiple products

—

Built accessibility into the design system by auditing WCAG 2.1 AA and defining focus, error, disabled, empty, and failure states, making compliance structural, not screen-specific.

Collaboration

—

Partnered with PMs to align design decisions with business goals

—

Worked closely with developers to ensure accurate implementation

—

Coordinated with QA team for usability validation and testing

Impact

—

62% of support tickets were usability issues, the number that made the business case internally

—

The design system now runs across the Orbixa Vision product line

—

The accessibility work is what makes Middle East and Europe deployment a conversation at all

Zahid Raza
Zahid Raza

Hi

Hi

Curious about the process behind the pixels?

Dive into the stories behind each project, how design decisions shaped better user experiences.

Senior Product DesignerEnterprise UXDesign Systems SpecialistNew Delhi, INAvailable for WorkVideo Management SystemAnalytic Manager10 Years ExperienceOrbixa Vision
Available for Work
LocationNew Delhi, IN
Local Time · IST—
Weather—
Find me on
© 2026 All rights reserved by ZHD