Fleet Management System

* This is a project protected by NDA, so I can’t disclose the real name of the project, the real name of the client or show compromising pictures. Every information is simulated.


A private flight transport company needs to update it’s office fleet management tool (desktop) and also create an app to collect feedback (from pilots and crew) about aircraft status among other features.

My role

My role was, as the UX element, gather requirements and needs to build the new system, and create all the necessary deliverables, from flow maps and wireframes to visuals. For the desktop system and mobile app system.

interaction flow

Two technical teams were assembled, one for the App and another for the desktop system. While both had a project manager I was the connecting bridge between the two teams as I worked both systems.

The first challenge was to make sense of all the data and requirements of the project. A few interviews were conducted to gather all the necessary material, from branding guidelines to sheets with all the data needed to make sense of the future interface. The data was analysed with the developing team and we sketched the concepts.

User scenarios were thought off to help define the systems behaviors that were sent to the product owner to collect more feedback from users. This was a challenge since we weren’t given access to the real users (busy people…) so we had to make do with what we had and a permanent contact with the product owner. Even so the profiles (pilots and crew members) were very straightforward and tangible.

It was enough to put some iterations of wireframes together. Both for the desktop system and app. Each has it’s own function and user profile even tough information crosses from one to the other.


The communication between teams and the product owner went quite well. We were in constant contact through all the sprints and phases. It was quite interesting because the two systems are interconnected but each has it’s own behaviour. The user profiles were very straightforward and that helped to focus on the objectives and interface decisions. Testing is underway and development almost complete (* will update later)