SPRINT28 PORTFOLIO

Seoul Glow Box

Seoul Glow Box aims to address the challenge of maintaining a consistent skincare routine by providing a subscription service that delivers personalized, curated Korean beauty products directly to consumers. Each box is tailored to meet individual skin concerns and preferences, promoting a consistent and effective skincare regimen.

Product Experience

Problem Space 

Problem Statement  

How might we simplify and personalize skincare routines to enhance effectiveness and user satisfaction?

Problem Background  

The need for Seoul Glow Box arises from the complexity and inconsistency of consumers' skincare routines, often due to time constraints, high product costs, and the overwhelming choice of products.

Research Insights

User Pain Points

During our research phase, which included surveys and interviews, users expressed the challenges of maintaining a consistent skincare routine, overwhelmed by the vast market options and seeking personalization and guidance.

Supporting Data

70% of participants found maintaining a consistent skincare routine challenging, with 80% showing interest in curated skincare boxes as a solution.

Feedback

Feedback highlighted enthusiasm for a personalized, convenient skincare solution that could simplify daily routines and introduce effective Korean beauty products tailored to individual needs.

Landing on the Solution

Based on our target users' pain points, we focused on curating a subscription box that offers a personalized selection of Korean skincare products, aimed at simplifying skincare routines and addressing specific skin concerns.

Future Steps

This feedback loop will continue to inform the refinement of Seoul Glow Box, with plans to explore additional customization options and expand our product range to cater to broader skin concerns and preferences.

Learnings

Product Manager Learnings:

Mohamed Toure

Co.Lab was a very interesting experience for me because I learn about the central experience of thinking with the customer point view, understand what they try to achieve versus the solution (with the NASA exemple resonating so well with me). Also, learning about the the Job To Be Done as been beneficial in my current role and engaging impactful conversation with my product team as a data scientist.

Designer Learnings:

Designer Learnings:

Jo Sturdivant

  1. 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.
  2. 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.
  3. 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

&

  1. 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.
  2. 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.
  3. 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.

Full Team Learning