Luana Cavalcanti
Luana Cavalcanti
Application Overview:
Vector is a back office administration system that manages menus, products, pricing and special offers with essential reports. 
It configures integration links to flight schedules and catering operations. It contains a comprehensive crew target setting and commission system.
Vector is currently divided in 11 modules and in this project we were working on with vPOS backoffice.
 vPOS was the first ever ePOS solution on-board and is currently the biggest ever aviation point-of-sale solution in the world. ThevPOS (Point ofSale) Solution comes with both iOS and Android operating system options as well and the backoffice for vPOS is a WebApp.
Project Timeline and Research Methods
At RiM I was working on building a design system and a redesign of an application module, the project was initiated by front-end, who is currently using Semantic UI, the components of the design system would be used in our first MVP which is the redesign of Vector Back Office.
Enterprise products have very complex UX problems. There are a few reasons why this tends to be the case:
  • Enterprise products are sold to the company management team and not the users. Enterprise users can’t ditch a product because of bad UX. For instance, if your company decides to use Jira for product management, then you have no choice but to use Jira.
  • Many enterprise products have complex business logic. A product to manage the supply chain of a company is more complex than photo-sharing and that’s the case of Retail inMotion.
  • Enterprise products require users to have certain specific domain knowledge.
Problem statement:

Multiple products and modules with UX issues, which are significantly influencing how product development team are prioritising sprints and projects due to hardware and software need of upgrade.

Problem Solving Flowchart
The Solution

Our first step towards a solution was to he core functionalities vs most used features that will be used in the first redesign using micro services and design system.


I needed to know more about the user and their pain points. Our goals were to learn about: what functionalities are used most in order to focus on those functionalities for a standard product.

I started my research with putting together a KWHL chart to help keep my research on track and focused.

The KWHL chart contains notes on:

  • What do you already know?
  • What do you need to find out?
  • How will you learn it?
  • What do you hope to learn?