Software UX: From the chaos of numbers to an unlimited order.

Smart Revenue Software.

Task:
User Experience, Wireframes, UX consultant
Team:
Elena Roca (UI),
Daniela Arcos (Direction and Revenue Lead team)
Company:
Grupo Hotusa
Project:
Software UX design
Link to the software:
Smart Revenue
Year:
2016

1. Situation

The beginning of the idea

Smart Revenue is a tool created to help with the organization of hotel revenues. The professionals in charge of reviewing the income of a hotel must take into account both internal and external factors, this task takes too much time throughout the day. The idea of the product was from the manager of the Revenue team, Daniela Arcos. She thought why not have a single tool where it might be possible to gather excel files, reservation data, information from external websites, and much more.

2. Approach

What users needs

Being close to the Revenue team increased the process of empathize . We worked at the same office and we were very close all the time. I could watch them work with several screens, each screen with an excel file, another with the Booking web and at the end of the day it was a pretty chaos all the information that they manipulated. So, with the team we had to prioritize the content that this people has to analyze every day. And the most important but not easy, we had to see the way that this software it's going to look like.
To carry out this task I have carried out different Design Thinking methodologies as a test with users to get a first version that is accessible and functional for all users.

5 whys:
Why they need to see all that numbers?
Why is so important to check every day these information?
Why...
Why...
Why...

What if...:
What if we create the principal elements of the excel fixed?
What if you can create past events to have a resume and a future booking pronostic?
What if Smart Revenue could be a bigger tool in the future? What else would you like to add?

3. Production

Do and reDo

The project was managed by a scrum system. The idea was to define one or two sections of the software per sprint. Every little part and every wireframe was checked by the Revenue lead, and then by the back-end team and the front-end team, this process was repeated as many time was needed. With all these check I could continued with the project. My work methodology was to make quick changes and test it, I kept the communication with the teams all the time so every change that I did the could know it fast. In six month the base of the software and the UI was completed.

4. Wireframes

The process

In these stage the wireframes had to be almost perfection, I started with a pen and paper but then the final wireframe had to has all the details so the back-end team and the UI designer could start working without any comunication problems and also, in the same page. .

5. Prototype

Actions

Prototyping the actions is a crucial part of the work. I did it with Marvelapp and it was a great help to the developers with their jobs. It takes an hour to prototype the wireframes but saves a lot of time when it came the part of explain every little detail to the developer's team.

Saving space for a better visualization.
Hovers to give more information if necessary.

Accessibility.
Menu hover.
A clear dashboard.
Hovers to provide more information.
Clear elements and very visual.

All rights are reserved to Grupo Hotusa & Hotusa Hotels. Many Thanks.

Projects

Next project