Fiteo: Design an Outfit Builder
Problem Overview
Fiteo is a retail media company that “intends to elevate the shopping experience for brands and retailers by guiding their customers on what to buy.”
My team was tasked with conceptualizing the outfit builder interface that Fiteo would seamlessly integrate into current e-commerce platforms.
Fiteo did not conduct any previous research or development on the outfit builder, however they did have certain goals they wanted from it:
Suggest outfits to users based on a specific system.
Give the user creative freedom to build any type of outfit.
Outfit builder will be in an “artboard” form like Pinterest
Incentivize users to share their creation on social media
Defining the audience
To strengthen their sales pitch when meeting with businesses, Fiteo wanted us to research what type of user would use an outfit builder the most.
Through extensive research, my team and I came to the conclusion that Gen Z would be the perfect end users for the outfit builder.
I created a detailed explanation that can be found here.
User Personas
How might we?
To empathize with user needs, we brainstormed different “how might we” statements to decide what our top priorities were.
“How might we optimize the outfit builder to provide tailored recommendations, adapt to fashion trends, and boost user engagement and conversions?”
Ideate
User Flow
This user flow provides an outline for the team to be able to focus on the important stages of the outfit builder to design.
Wireframes
With this wireframe, we eliminated ambiguity and promoted collaboration, allowing us to discuss and iterate on design decisions based on a common reference point.
User Testing
My team and I built a prototype based off the wireframes and tested it with 10 different users.
Response
Revise
When synthesizing the responses, the initial version of the outfit builder was not good at keeping our user engaged on the outfit builder. Most users mentioned that it was too cluttered and felt overwhelmed when adding clothes
Updated interface
Prototype
Wrap Up
With this final prototype in hand, Fiteo now has a robust foundation on which to build and expand. It is our hope that this collaborative effort will lead to the creation of a remarkable user experience that not only meets but exceeds their users' expectations. We look forward to witnessing Fiteo's journey as they bring their vision to life and continue to prioritize user-centric design in their product development.
Throughout this project, we have incorporated invaluable user feedback, addressed various pain points, and fine-tuned the design to align with Fiteo's objectives and user expectations. This prototype represents the culmination of extensive research, design thinking, and user-centered design principles.
What are the goals?
Team
Maximillian N, Wendy L, Anna S, Josh S
Timeline
5 months
Tools
Figma, FigJam, Notion
Roles
User Research, UX Design, Prototyping
Lessons Learned
Always ask questions.
In our design process, we encountered numerous challenges at the beginning because we lacked a clear understanding of what we were expected to create. We learned the importance of actively seeking clarification through asking questions. Rather than relying on assumptions, we realized that it is crucial to inquire about any uncertainties, gather necessary information, and make informed decisions based on a shared understanding.
Create a list of responsibilities for each team member.
Implementing a task distribution system proved to be highly beneficial in enhancing our efficiency. By creating a detailed list outlining the specific responsibilities and roles for each team member, we were able to streamline our workflow and complete tasks more quickly. We leveraged a project management tool called Trello to help us organize and track progress, ensuring that everyone had a clear view of their assigned tasks and deadlines.
Prioritize in-person communication.
We discovered that face-to-face discussions have numerous advantages when it comes to sharing ideas and fostering creativity. While relying solely on messaging platforms, we encountered challenges such as misinterpretation and delays in response. However, when we switched to phone conversations or in-person meetings, we experienced improved communication efficiency and effectiveness. Being able to communicate in real-time allowed us to bounce ideas off each other, brainstorm collaboratively, and resolve any issues or concerns more swiftly.
Incorporating a question-driven mindset, establishing clear responsibilities, and emphasizing direct communication channels greatly contributed to our design process.