AMARO is a fashion and technology company based in São Paulo, Brazil, known for its innovative approach to blending e-commerce with fast fashion trend and great experience through physical stores and e-commerce.
After years of serving users, the page containing essential product information is no longer performing well, having not been updated for over a decade. How can we improve the performance of this critical ecommerce page?
As the Lead Product Designer, my main goal was to connect the page’s potential with business and tech priorities for the quarter. I led the product designer, guiding them through each step, and advised developers and stakeholders on design choices.
I designed wireframes, prototypes, coordinated design critiques and created components that were easy to code, along with design specs.
In project management, I collaborated with fellow leaders to find improved solutions, made crucial decisions during implementation challenges, and ensured alignment of strategy and goals with stakeholders and directors.
I collaborated closely with the product designer to uncover valuable insights and translate conceptual ideas into solutions that meet customer needs and address their pain points through experiments, users feedbacks and competitive analysis.
Lead Product Designer +
Senior Product Designer
2 Weeks – Research & Initial Prototype
2 Weeks – Experimenting & Components
Figma & Figjam
Confluence & Jira
The page must showcase all essential product information in all devices.
Ensure SEO optimization for attracting
more users.
Create a page suitable for fashion products that can adapt well to other categories.
Align with the updated brand version and improved visuals over time.
In an interview with project stakeholders, we mapped out the major pain points regarding the product detail page:
As the product range expanded, the page and it’s components could no longer accommodate the quantity of variants per product.
The screen proportions were not pleasing, causing problems for users in different devices. The rank on Google was also affected by it.
The slow page loading not only affected search result performance but also led to higher user abandonment rates.
It lags behind the market, with few features and personalizations that were common among other competitors.
During the initial research phase, we gathered all information regarding user behavior within the page and the journey:
In our initial page assessment, we identified usability and responsiveness problems. The page had not been updated since 2012, while other brands had already broadened their product range, incorporating other departments.
The assessment acted as self-documentation, revealing a few key areas for improvement, mainly around usability and responsiveness. Through data collected from user feedback, recordings, and heat maps, we’ve categorized these issues in order of importance, from critical to minor.
Each department has distinct needs, with some prioritizing photos and others descriptions. The product page must effectively meet these varied requirements. To enhance and validate the provided information, my UX counterpart and I gathered insights from competitors.
Over time, we discovered that a versatile page showcasing any product from any category with consistent features boosted scalability and user trust. Maintaining uniformity across pages and elements was pivotal for a reliable and consistent design.
Users faced reachability issues on mobile, contributing to a 25% bounce rate caused by misclicks. Layout distortion across devices, including desktops, caused a 30% decrease in scrolling compared to other pages.
Customers were inundated with diverse product information, making anticipating worst-case scenarios challenging (given the constantly evolving marketplace). Therefore, we should develop scalable ways of personalize the page during seasonal campains or sales.
After identifying goals and insights, we collaborated with the design team for a Crazy 8 dynamics session to expand our solution vision. We focused on designing what was the hyphotesys that we wanted to test, also focusing on a smart Information Archteture.
Following the initial sketches, I transferred all screens into Figma to craft detailed wireframes. This allowed me to explore various scenarios even some major interaction for desktop devices and tablets. In this phase, close collaboration with the business area was pivotal to tailor specific views that aligned with the required information.
In the initial layout, we formulated several hypotheses, prompting the need for additional evidence to validate our assumptions. Hence, we conducted A/B tests, leading to insightful results leading to major changes on the design:
Clear visual hierarchy is crucial when managing large amounts of information. In A/B tests, we observed a notable increase in engagement (e.g., clicks on “Add to Favorites,” reviews) by providing greater prominence and space to buttons and titles.
We found that adding familiar information only increased interface complexity unnecessarily. Our objective in testing was to remove unnecessary details while keeping interactions clear for users.
In comparing a modal page (the old page) to a static one for general navigation, the static page emerged as the superior choice. The modal page’s loading issues hindered user engagement. Transitioning to a static page showed significant improvements in conversion rates, access, and overall interactions. This emphasized the importance of a stable and responsive interface for optimal user engagement.
Before creating extensive pages, we started with atomic elements, pinpointing what didn’t fit our design and fine-tuning for scalability during the design process.
Recognizing that clear communication with developers was crucial, we established a collaborative space where developers and designers could work in parallel. This innovative approach enabled us to deliver the redesigned page swiftly without compromising quality.
New Perspective: This streamlined collaboration marked a significant advancement in terms of speed and integration among team members. The novel development approach redefined the process of component handoffs, facilitating parallel work within the same framework.
Also a bounce rate reduced by 5% in mobile devices.
Calculated through the A/B Tests
Scanned throught axe DevTools
Were made in order to review from to the most simple scenario, to the most complex.
recreated to serve a Design system and the Product Detail Pages.
Move the arrows to the left or to the righ to check the before and after respectively.
Leading the team, I’m proud of our adaptability. As an individual contributor, navigating negotiation challenges, particularly on the critical e-commerce platform page, was key. We swiftly overcame barriers across business areas.
A crucial lesson learned: UX processes aren’t always linear. Flexibility is vital, balancing speed with ensuring proper checks for optimal outcomes.