Company: Magalu - Magazine Luiza
Product: B2B, SaaS, Web application
Areas: Developer tools, Marketplace, Retail
Year: 2019
I worked at Magazine Luiza (One of the biggest retailer companies in Brazil) as UX/UI Designer, and my challenge there was to Design from scratch the ecosystem of the MaaS Platform (Magalu as a Service). The MaaS platform is formed by two applications: the MaaS Console and the Maas Account. The MaaS Console is a marketplace for retail services that will allow Magazine Luiza and other retail stores to sell digital or physical services online (free services too) to small retailers integrated on their own e-commerce, paying based on the demand used, like Firebase do it for back-end cloud services.
As a UX/UI Designer in this project, my responsibilities were to design Tasks and User Flows, User interfaces, and Interactive Prototypes. I worked alongside a Product Owner and the Development Team that started to build it, composed of a Teach Lead, QA engineer, four Front-end developers, and two Back-end developers.
The Maas Console has two views, one is Public and the other is Registered.
At the Public view, the main challenge was to show the services available to hire and authenticate users integrating with the MaaS Account application because without authentication it wasn't possible to hire any service, just browse the relevant information, like details about the service, images, technical documentation of how to integrate, and plans offered.
At the Registered view, and with an organization associated, the main challenge was to transform a complex and extensive service registration process into a clear and descriptive experience for the users and organizations wanting to sell their services in the MaaS Console and hire services from others as well.
The Product owner provided the high-level Epics with the business goals. Together with the Tech Team, we broke the epics into user stories and requirements and generated the acceptance criteria for each one.
Based on the user stories I started the design process by drawing the Task Flow to have a high-level view of the main tasks that the users could do at the MaaS Console, either Public and Registered views, and how they related to each other.
After understanding the Tasks relationship, it was time to get into the details of each one and design the user flow for the possible scenarios. To do that I create two proto-personas: Owner and Associated.