Lifestyle Recommendation Platform

Instead of showing pyramid-style recommendations, I proposed a more straightforward approach due to time constraints and prioritization of Feature 2.

I proposed using the search function to meet the project's time constraints. However, if we had more time, we would have explored the "sort by" option further to ensure that users could easily find the reward option they were looking for, improving the overall user experience.

Limited by time constraints, the dark mode feature couldn't be fully implemented. However, user testing preferred dark mode, particularly at night, as it reduces eye strain. We acknowledge its significance and will continue to explore ways to optimize this feature in the future.

Given the time constraint, I played a critical role in the prioritization process by collaborating with the project manager and engineering team on day 1 to define project goals and requirements based on user needs and business objectives.Through this process, I influenced the team to prioritize features that would impact the user experience that met the needs of our target users

We streamlined communication and alignment by focusing on two key functions: credit card recommendations and tailored lifestyle benefits. I suggested researching and creating wireframes on Miro to ensure a user-centered approach. I also suggested rapidly testing and gathering feedback so we could create a final interface that was technically feasible and goal-oriented.

To understand which questions to include, I researched how other companies assist customers in selecting the best credit card. This led me to formulate questions that could extract information about a customer's lifestyle and habits. Interestingly, most questions revolved around the same benefits, such as travel, hotels, cash-back rewards, and no annual fees.

We began by brainstorming and outlining the overview. I recommended using Miro to visually represent the project scope to ensure clear communication and alignment among the team.

However, I was concerned that there may still be some potential for miscommunication, so I quickly created wireframes in collaboration with the engineering team to convey the project vision and get their input. This approach allowed us to move toward a high-fidelity, user-centered, and technically feasible design.

While the engineering team was developing Feature 1, I kicked off Feature 2 based on the ideas generated from our discussions. I regularly sent prototypes and gathered feedback on my designs during this time.

I struggled to build the vision and get opinions from engineers during the ideation phase. Only some of the team members shared. I immediately discussed it with the PM. Rather than broadly ask them ideas, I narrowed it down to specific questions: Where should buttons or card options be placed on the page? We successfully have more feedback, leading to a satisfactory product!

Scrum helped our team grow and progress through daily stand-ups, weekly sprints, and retrospectives. The daily stand-up and retrospective benefited our team because they helped us update progress and solve problems together immediately. For example, when front-end engineers had difficulty extracting pictures from Figma, I immediately taught them how to do it. This technique tightened accountability and ensured the product deliver on time without flaws.

In my collaborative work experience, I've learned the power of effective design communication. I showcased how my designs improve user satisfaction and drive successful project outcomes through compelling presentations. I got team buy-in and sought feedback. Clear communication and collaboration are vital in achieving unique project goals, and I'm committed to applying these skills as a designer.