14 months into a large-scale revamp project at LittleLives, I didn’t just deliver interface updates. I navigated disconnection, ambiguity, and cultural misalignment to rediscover what kind of designer I want to be.
This isn’t just a case study about UX design. It’s about self-awareness, team sensing, and the transition from “doing” design to “holding” design as a space for impact.
This case study focuses on growth. The challenges I experienced at LittleLives are common in fast-changing teams and became valuable learning opportunities. In this story, I share how I navigated those situations and what they taught me. These kinds of challenges often appear in developing product and design environments, where design is still growing and strategy is still taking shape.
Looking back on my experience, I noticed several situations that helped me grow as a designer. These moments helped me understand how product teams work and how I could improve my own approach.
Below are 4 experiences that shaped how I think about design, teamwork, and product development.
Problem: There was a strong vision for the product’s future, but much of the daily work focused on quickly delivering new features.
Cause: The team often prioritized speed in feature development, which left less time for deeper UX exploration and alignment with the product vision.
Reflection: This experience helped me realize that meaningful design impact requires alignment between product vision, business priorities, and user needs.
Problem: The product started as an MVP and continued to grow as new features were added over time. As the product expanded, it became harder to maintain a clear direction for the user experience.
Cause: Because the product evolved quickly, there were no clear milestones or metrics to guide design decisions.
Reflection: This experience helped me understand how important clear product goals and metrics are. They help teams make better decisions and create a more consistent user experience.
Problem: As the company grew and team dynamics changed, collaboration became more challenging. Communication gaps and a strong family-style culture occasionally created situations where some voices were heard more than others.
Cause: This sometimes made it harder to feel confident that ideas would be evaluated fairly, which could affect trust and open collaboration within the team.
Reflection: I learned how important it is for teams to create an environment where everyone feels heard and respected. When people feel safe to share their ideas, collaboration becomes much more effective.
Problem: Within the design team, designers often worked independently on different parts of the product. Over time, this made the team feel less connected.
Cause: As the product became more complex, there were fewer opportunities for designers to collaborate, share ideas, or learn from each other.
Reflection: This experience helped me realize how important design collaboration and leadership are as products grow. When designers work closely together, they can learn from each other and create stronger solutions.
During this time, changes in the team and ways of working created a fast-paced environment. I realized that while I couldn’t change many of the challenges around me, I could reflect on how I responded to them. Through conversations with an AI coach in ChatGPT, I was able to organize my thoughts, manage overthinking, and see the situation more clearly.
This reflection led me to think more deeply about the kind of designer I wanted to become. I realized that I don’t just want to build good products. I want to design with care, insight, and the courage to connect real human needs with product vision.
To explore this further, I began learning from the wider design community. Attending events like UXVN Conference 2024 and the UX/Product Designer – Midlevel rồi sao nữa? workshop gave me new perspectives on design and product thinking.
Through these experiences, I started shaping a clearer direction for myself. I want to contribute as a designer who brings clarity to complex problems, balances user needs with business goals, and works closely with teams to create meaningful solutions.
Looking back, I realized that the most valuable outcome of a project isn’t always the final product. Often, it’s the growth we experience along the way. This journey reminded me that design doesn’t start on the screen. It starts with how we listen, understand, and respond to complex situations.
One lesson I carry forward is the importance of speaking up. Even when conversations don’t lead to immediate change, sharing concerns with honesty can bring more clarity and openness to a team.
I also learned how important support systems and the design communities are. During this transition, friends and fellow designers helped me stay grounded and trust my abilities.
Finally, this experience encouraged me to think more intentionally about my future. I started creating a personal design roadmap to guide my growth and help me stay focused on the kind of designer I want to become.
While this chapter has ended, the lessons from it continue to shape how I approach design, collaboration, and my own development.