App redesign and improvements

B2B Native App

Task:
Research, improvement, user interface design, style guide creation
Team:
Product owner,
Tech lead developer
Company:
Vincle Internacional
Product:
Native B2B App
Year:
2018-19

1. Introduction

About the product and my task.

The product is a native b2b application, its purpose is to offer a platform to large clients in the world of Retail and HORECA to organize their own clients, carry out face-to-face activities such as surveys and sales, and keep track of commercials and end clients. My main task was to detect all the points of improvement of the application from the accessibility, the interface and to propose improvements in the medium and short term. It was not an easy task to adapt to a product already made and working since each decision must be taken with firmness and certainty since changes involve time, money and coordination between the company and the client.
Here we will see the process and methodology that I have used as the conclusions and future improvements.

2. Discover

How to effectively detect everything that needs to be done?

The main task in this case is to obtain the most information not only on the operation and purpose of the product but also on what the business interests of the company are in order to provide more accurate improvements to business objectives. On the other hand, it was necessary to work on a better work methodology to incorporate the UX / UI profile within the product team in an effective and functional way in the long term. To complete these main tasks, I have spent many hours researching the product with my own hands, organizing meetings with key profiles within the company and proposing visits to clients to learn first-hand about the needs of the end user.

3. Planning

Scoping the improvement.

In order to organize myself, I have created a 6-month plan with the steps to follow, in this way the entire team could be aware of what it was doing, what was going to be presented over time.

4. Methodology

Lean UX.

In order to cover all the short-term objectives, the best plan to follow was to implement the Lean UX methodology. Give agile results to small problems, monitor all tasks, maintain constant communication with the entire team and validate each step with the team leaders. In this way, I have not only been able to learn more about the product, but also about the technology used and how the entire team works to be able to apply improvements from my perspective.
This methodology was a success since the entire team felt part of the solution and involved in all decisions. Not because we are the designers of the product we have to have the last word, working as a team listening to everyone's opinions and suggestions led us to better, faster and more satisfactory results.

5. Research

Knowing the user is the key.

To deliver the right solutions to a product as complex as this, he had to get to know the real users closely. That is why with the team we managed to go out with the users to carry out small tests. These tests consisted of observing users in a normal working day, without interrupting them to collect information and have a real database. From these tests, user journeys, empathy maps, people, pain points to be solved and real knowledge of the business were obtained.
Importance of user journeys and empathy maps: The users of this product are in the street carrying out different activities with their clients, it is essential to know the journey perfectly and provide them with solutions as well as the context in which they are.

6. Style guide

Consistency and new look & feel.

The designs were not consistent like the programmers' code, there was no component library, much less a style guide. The opportunity to create a basic library of components was taken to also improve the look of the application and give it a modern look.
The system used to create this new online style guide was Atomic design since it was what most assimilated to the developers' way of programming, where each element is made up of controls. At this point it was very important to maintain the contending interaction with the programmers, each style, control and element was agreed together and called in the same way both in the sketch symbols and in the code classes.
Currently this guide is kept alive and saves us hours in the exchange of designs and developments.

8. Results

.

The product is currently being improved but it already has a database of real users, a plan for more outings with users, a complete online style guide, and a fully coordinated workflow.
It is not an easy task to be incorporated into a fully developed product and to be able to make an improvement, my conclusions are always to maintain communication with the team, ask many questions, always want to know more and not be afraid to face improving things.

All rights are reserved to Vincle internacional. Many Thanks.

Projects

Next project