Founded in 1979 in Belo Horizonte, capital of the state of Minas Gerais, MRV Engineering is one of the most traditional companies in the state and one of the largest construction companies and land developers in Latin America.
In the awakening of digital transformation across traditional sectors, the company realised it was essential to make changes on its products and processes in order to succeed in an ever-changing world. In partnership with dti digital, the company started its own digital revolution.
At the time I was a full-time UI/UX Designer at dti digital, and worked on various projects across other of the company's clients. When MRV started putting in motion the internal changes, I was called to be a part of a large team that would be responsible for a number of digital products.
In my time there I assisted e-commerce products such as Meu MRV, Kit Acabamentos and MRV Marketplace - the former two in which I was responsible for the illustrations and visual communication; helped in the development of initial conversational flows in chatbots and was the Designer in charge of MRV Preços, one of the largest and more challenging B2B projects of this client.
More information about some of the accomplishments between MRV and dti digital can be found here (PT-BR).
MRV Preços is an in-house solution designed to facilitate the process of enterprises pricing, replacing the old system that was based on outdated technology and sets of complex and decentralised spreadsheets.
The pricing process for enterprises involves numerous criteria to be taken into account, such as the calculation of profit margins, distortions in the viability of the construction works, general characteristics of the properties (area, location, position, etc.), taxes and much more. For years, MRV has relied on manual processes and a highly trained team to ensure that its property prices are profitable and competitive in the market.
The chosen approach to this project was to conduct a Design Sprint as a first step, to understand the problem, the users and the right direction for the solution. The development process was based in agile methodologies, therefore having MVP cycles being delivered every few sprints.
Our team had the following structure: