Ultrabot
No more room for error from airport sensors
Hidrasys SL is an important company in the aeronautical sector. They want to develop an application called Ultrabot to control the entry and exit of planes at Wakanda’s airport and verify if the data collected by its sensors is correct. To do this, they have prepared a list of the requirements that their platform must contain.
A meeting is arranged with Hydrasys’ representatives, after having analyzed their briefing. For this meeting, we will work on the deliverables corresponding to the research stage, doubts and suggestions will be raised, and mid-fi wireframes will be designed to have a first approach to share with them.
For this reason, wireframes are presented only in mid-fi, in greyscale and making use of the red and green as semantic colors.
You can read the complete Case Study in Gitbook: Ultrabot by Hidrasys →
Discover & understand
What we know so far is that data is collected by two sensors: one records landings and the other takeoffs. The data comes from a real-time API that includes: registration timestamp, flight number (99% reliability), airline (95% reliability), aircraft model (99% reliability), and number of passengers (70% reliability).
During the discovery, questions and doubts have arisen and we will clear them up during the meeting with the stakeholder.
User Research Definitions
Fictitional Persona
Given that no prior research including interviews and surveys with users has been conducted, I have created a Fictional Persona to empathize with and understand who the user is and what her pain points and needs are, which Ultrabot will be addressing.
Value Proposition Canvas
Now that we know who our user is, we will see what her joys and frustrations are, as well as her daily tasks. In this way, consider how Ultrabot will create these joys and how it will alleviate the frustrations.
MVP's needs & requirements
After working on the previous canvas, I was able to determine the MVP’s objectives, to state the value proposition, and work on the Moscow Diagram to define functionalities.
User's histories & flowcharts
For the MVP of Ultrabot, there will be two user histories: flight verification, and check of pending verifications.
Design & ideation
Information architecture
The sitemap was thought to have an easy and intuitive structure.
Use of Case
After working on the sitemap, I started sketching and ideating how the user flow could be, considering the different use cases.
Use of case 1
Verification of flight that has landed at Wakanda Airport
Use of case 2
Checking pending verifications
Conclusion
These first approaches were managed by empathizing and understanding the user’s pain points in order to give solution to their main needs.
In this way, the Ultrabot MVP will help the staff at the Wakanda Airport verify that the data collected by the sensors on the entry and exit of planes and helicopters is correct, and thus streamline, automate and centralize the work process, ensuring the user that there are no errors, and reducing the stress of performing a task manually.
On the other hand, the Ultrabot proposal has been presented in such a way that, in the future, Hidrasys could consider marketing this digital product for use in other airports.