End to end modernising and enhancing a 155 years old Aussie shoes brand's online experience.
Hotjar
Miro
Figma
Userlytics
Jira
The goal was to modernise the Munro e-commerce website, which hadn't been updated for years, and make it more user-friendly as there had been no dedicated UX roles before. Additionally, the business was forming a development team to use the React framework, aiming to enhance the website's capabilities.
1. Refresh the website's design to align with current industry standards
2. Improve end to end online user experience for customers
3. Improve conversion rates at key website touch points.
Previously, there was no focus on UX in the company, and my colleagues were unfamiliar with UX methods, which I need to spend time educate them and gain their support. There was no UX design process within the company. Our UI work was split between Sketch and XD tools, leading to disorganised design files. Also, managing 11 e-commerce websites without a unified design system was challenging.
Recognising the fast-paced nature of retail fashion, I suggested a more strategic approach. Instead of diving straight into design and development, I proposed establishing better long-term design working processes. This would not only improve current workflows but also benefit the team in the future, even if I’m no longer part of the company, I also suggested to build a design system along side the redesign project, which can potentially improve the consistency and efficiency within the team.
1. NEW Implement a pilot project to integrate UX processes to be the part of development for the long them.
2. NEW Establish a design system through this pilot project for future design and develop consistency and efficiency.
3. Refresh the website's design to align with current industry standards
4. Improve end to end online user experience for customers
4. Improve conversion rates at key website touch points.
For a UX project, it's essential to have a plan to avoid chaos in our workflow and ensure we meet our deliverables. We've outlined an activity plan for the upcoming sprints, following the double diamond method.
We started by identifying issues. Being a new team, we lacked historical data on website performance. We launched surveys at critical touch points such as the product listing page, filter, product pages, checkout experience and my account. We also collaborate closely with the customer service team to identify the frustrations from the customer.
Once we collected all the data from Hotjar survey, screen recording and customer service team feedback. we began analysing raw data using an affinity diagram, consolidating findings from our recording, customer service feedback, and surveys to identify common themes and patterns.
From the consolidated findings, we can identify some insights
Filter Feature
Listing Page
Product Page
Checkout
My account
Once we got the initial insight, we conducted a competitor review to see what they do on
those related touch points
Utilising our collected data, we created a customer journey map with stakeholders during the workshop. This map outlines each step of the shopping experience and potential pain points customers may encounter.
During the workshop, it became apparent that some issues raised were somewhat subjective. To address this, we created personas using our demographic data. These personas enable us to better understand and empathise with our customers, and they will be beneficial in selecting participants for future user testing.
Recognising the many areas needing improvement on the website, we acknowledged that our resources are limited. To prioritise tasks for our first MVP (Minimum Viable Product), we employed a democratic voting activity, allowing each team member 3 votes to decide what to fix first.
Following the prioritisation, we conducted brainstorming sessions to generate ideas on resolving the identified pain points. We again used voting, with each person having 3 votes, to prioritise these ideas.
We asked participants to select their favourite ideas from the voted list and sketch out design concepts. This task was challenging for many, as it was their first time engaging in such an activity.
Before starting the design process, I review the pain points and ideas to ensure nothing is missed and identify any quick fixes through design tweaks. Instead of working in isolation, I involve our workshop group (Marketing, Customer Service, and Developers) in design review sessions. These sessions provide feedback and identify potential technical constraints.
After multiple rounds of low-fidelity reviews, we finalise our layout and basic interactions. so we can start to make the design high-fidelity, The technical constraints
User testing is crucial for validating our designs and gathering customer feedback. I created the interactive prototype based on our user testing scripts. For this project we tested with 12 participants (6 Mobile + 6 Desktop)
After consolidated the user testing result, I've iterated the design based on user's feedback. Due to urgency of go live, the production version is a before iterated version.
To achieve better consistency and speed up future development, we're incorporating reusable components into our Design System. For detailed information, please refer to the design system case study(WIP).
Marking the end of this design stage, the design handoff is a critical step to ensure the end product is as same as the design possible. After several discussions, we agreed on four essential elements for the design handoff document:
1. User flows for main interactions.
2. Prototypes
3. Note for general scenarios, edge cases.
4. Screen breakpoints for each device
This project is not perfect and has lots thing can be improve such as better prepare design review, more organise design workshop, better design handoff process etc. I wouldn't treat this as one-off project, I rather treat it as ongoing digital product(test, learn, improve).
Back to top