EasyFit
EasyFit reduces time spent on purchasing clothes by sorting them by style, fit, and comfort.
Problem Statement
How might we reduce the amount of time spent purchasing clothes that fit and are comfortable for the buyer
Problem Background
For many people, buying clothes is a high priority, driven by various reasons such as emotional satisfaction, body changes, or style updates. As a result, they invest a lot of time in searching online for the article that fits their needs. This process often involves browsing through a large selection of items, trying on multiple pieces, and dealing with inconsistent sizing across different brands. Additionally, shoppers may encounter issues such as limited stock, where the desired size or style is unavailable. This extensive search process can be frustrating and time-consuming, leaving buyers dissatisfied and exhausted. The challenge lies in efficiently finding clothing that meets personal preferences and needs without wasting time or facing frequent disappointments.
User Pain Points & Research Insights
After interviewing 6 people I identified a few main pain points:
- Fashion customers waste a lot of time searching for a matching item. 67% of the people reported spending at least 15 hours a month searching for clothes, and 100% of them would like to reduce this time.
- Brands independently define clothing sizes, leading to variations across brands. All interviewed individuals reported experiencing disappointment when they discovered that an article they liked didn’t fit them. Additionally, all of them claimed to have experienced this at least once every couple purchases.
Supporting Data
A Salsify survey conducted in the USA with 1,397 participants and in the UK with 1,303 participants revealed that 25-31% of online consumers spend 30-60 minutes in their search.
93% of clothing returns are due to incorrect sizing or fit.
A Yopto survey demonstrates that 79% of clothing shoppers who returned items did so because they were dissatisfied with an item’s fit or quality.
Landing on the Solution
Based on our target users’ pain points, we knew we wanted to work on the following features:
- Surveying users to identify their favorite style and the occasion they are planning to wear the item for
- Understanding customer’s body measurements
- Filtering the clothes by store availability
- Sorting clothes based on prices
Learnings
Product Manager Learnings:
Ronit Serkin
Designer Learnings:
Designer Learnings:
Jo Sturdivant
- Adapting to an Established Team: Joining the team in week 6 of 8 was challenging, as I had to quickly adapt to existing workflows, dynamics, and goals. This mirrors real-world situations where you often integrate into teams mid-project, and flexibility is essential.
- Work-Blocking for Efficiency: With only two weeks to complete the project, I learned the importance of a structured work-blocking system. This approach allowed me to manage my time effectively and meet deadlines under pressure.
- Making Data-Driven Design Decisions: Unlike my past projects, I had to rely on research conducted by others. This was a valuable experience in using pre-existing data to guide design decisions, helping me focus on the core insights without starting from scratch.
Developer Learnings:
Developer Learnings:
Vanady Beard
&
As the back-end developer, I learned how important it is to create efficient and reliable systems that support the entire application. This experience also taught me the importance of optimising the database and ensuring the backend is scalable and easy to maintain.
Developer Learnings:
Stephen Asiedu
&
As a back-end developer, I've come to understand the importance of being familiar with various database systems and modules. This knowledge enables me to build diverse applications and maintain versatility in my work. I've also learned that the responsibility for making the right choices rests on my shoulders, guided by my best judgement.
Developer Learnings:
&
Developer Learnings:
Maurquise Williams
&
- Process of Creating an MVP: Developing a Minimum Viable Product (MVP) taught me how to focus on delivering core functionalities balancing between essential features and avoiding scope creep.
- Collaboration in a Real-World Tech Setting: This experience taught me how to collaborate efficiently in a fast-paced tech environment, keeping the team aligned and productive, even while working remotely across time zones.
- Sharpening Critical Thinking and Problem-Solving Skills: This experience honed my ability to think critically and solve problems efficiently. By tackling challenges and finding quick solutions, I sharpened my decision-making and troubleshooting skills in a dynamic, real-world setting.
Developer Learnings:
Jeremiah Williams
&
All in all this experience was very awesome I learned that in coding with others being transparent is key
Developers Learnings:
Justin Farley
&
I learned how important communication is when working with a team. Communication provides understanding, advice, ideas, and much more. While working with the product team, I’ve found that communication keeps everything flowing smoothly. Working with a team also showed me that every member brings something different to the table and we all have to work together in order to align and meet our end goal.