Ambev

Ambev is the biggest brewing company in the world and operates in 14 countries in the Americas. The giant size of the operation makes it challenging to handle the supplier, transportations, and outsource. Because of that, Ambev has a lot of internal systems for them and the suppliers to use. Therefore they begin an attempt to consolidate all of them in one system called: Connect. Our job was to draw a better experience with the Connect.

This project was done by Ana Couto Design. I was responsible for the interviews, writing the forms, analyses the results, diagnosis of Connect problems, personas, and wireframe - all with the support of AC team and under the supervision of Astrid Tempter, the head of UX in AC. Besides that, I helped the UI team drawing interfaces of some pages and making QA of visual problems with the front-end team.

One of the biggest challenges of this project was to understand and map all the users and the 15 systems used by Ambev's suppliers.

Connect has already been used before AC was contacted. At the beginning of the project, we interviewed stakeholders to understand more about the issues, their expectations, and what led to the actual status. We began to take a deep dive into the Connect and all the other tools that the suppliers use.

We interviewed  10 users, all around South America; With the insights gained in this step, we sent a form to the suppliers of 6 countries. We used half of the Ambev database. After that, we made our first diagnosis appointing a lot of questions that surpassed the Connect itself. We aligned with the stakeholder how we could tackle this.

After talking to stakeholders, we sent a new form for the other half of the database of the suppliers. The goal was to gain more insights after our first diagnosis and the validation of some hypothesis. We made a new diagnosis and traced the main guidelines and most important points that our project should consider.

We weren't able to consolidate all the 15 systems. With Ambev's dev team, we started to analyze which system could send send data to the Connect through API. After that, we were able to design a dashboard that would integrate all the possible systems. We began to make wireframes, always keeping in mind that this dashboard would change based on:
- What kind of system the users would have permission to use
- What country the user would be
Along with that, we had to think about what was useful for the user.

With the wireframes, we started validating with Ambev and producing the interfaces and front-end of the Connect. These included the institutional site, the registration, the onboarding, and even the administration of  Connect.