Problem Space
Problem Statement
How might we make all customer wardrobes well-organized and allow users to efficiently manage a collection of their clothing items in a digital dressing room ?
Problem Background
One of the biggest problems with traditional wardrobes is the lack of organization and visibility. Clothes, shoes, and accessories are often crammed into small spaces, making it difficult to find what you need when you need it. Additionally, it can be challenging to remember what you already own and what you still need to purchase, which can lead to buying unnecessary items or forgetting about items you already have.
Research shows that people who are disorganized or have cluttered spaces can experience higher levels of stress, anxiety, and fatigue. This is especially true in the context of a messy wardrobe, where getting dressed in the morning can become a stressful and time-consuming experience.
Research Insights
User Pain Points
Using Telegram and Facebook groups, we identified a few different categories of prospective users and did over 5 user interviews, which help us to define the problem and objective of a product. Here is some main user pain bullets and insights:
- Most interviewees at least one time in life felt decision fatigue about everyday choosing what to wear
- 65% interviewees feel that they don't have enough stuff, while their dress-room and wardrobes are full.
- All interviewees would like to know how to fix problem of forgetting about items they owned and make impulsive purchases, leading to clutter and disorganization.
Supporting Data
- A survey conducted by the National Association of Professional Organizers found that 54% of respondents feel overwhelmed by their clutter and 78% have no idea what to do with it.
- An article published in Forbes reported that the average American spends 10 minutes per day looking for misplaced items, with clothing being one of the most commonly misplaced items.
- A study published in the Journal of Environmental Psychology found that cluttered spaces, including wardrobes, can lead to increased stress levels, decreased productivity, and poorer mental health outcomes.
Feedback
Our preliminary user research to validate this problem with women 20-30 year shows, that they feel stressed about lack of organization and visibility and often feel stress about choosing what to wear and feeling that they don't have enough stuff, while their dress-room and wardrobes are full.
Future Steps
The app MVP would include a digital dress-room, separating items there by various parameters:
- item type (shirt, shoes, etc)
- brand
- price
- time and place of buying
- usability (wearing day-to day, wearing sometimes, don’t remember when I wear)
Other features, which can be integrated into the app later:
- making your dress-room public (optional);
- putting tags on your items “I’d like to change” , “This shoes need a cleaning” , etc;
- create a family-dress room;
- get a list of items you need to buy from AI, which will analyze your dress-room, tastes, budget and fashion-trends to help you make your future shopping conscious;
- get a look of the day from AI assistant, which will analyze and match your cloth with a weather.
User Flows/Mockups
User know, that he has a lot of dresses. Some of them are old, that’s why he don’t remember exactly what dresses he has in his dress-room for evening. Also he would like to get a recommendation what to wear today.
- Login the application
- Open «my dress-room»
- Choose category «Dresses»
- View his list of dresses
- Filter them by categories : «favorite», «wearing day to day», wearing sometimes», «don’t remember when I wear».
- Choose a dress he wants to wear
- Push «Get a look of the day» from AI assistant, using the dress he choose
- Get a «Look of the day», include a dress he choose, shoes, accessories, etc.
Learnings
Product Manager Learnings:
Kate Igelskaya
Co.Lab was a very interesting experience for me. Finishing it off with, I got some insights, but also I got even more questions for feature learning and self-educating. Due to a Co.Lab, I extended my product outlook, see how other colleagues work and what instruments they choose for it.
We spent a lot of time defining a problem space, redesigning our ideas into a plan, user researchers. Also, I would like to receive more leverages and recommendations about how to implement, validate the ideas and measure success. For example, how to choose and count your product metrics.
By the way, I would also like to know more about an app's monetization business model and have at least a few unit-economy classes.
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.