Frame 2059.png

<aside> 💼 My Role UX Designer

</aside>

<aside> 🤝 The Team 1x UX Designer 1X Frontend Engineer

</aside>

<aside> 🕘 Duration 2.5 months

</aside>

<aside> 📐 Tools Used Figma Storybook

</aside>

<aside> 🌟 My Key Contributions Design System Workflows Ceremonies

</aside>

<aside> <img src="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/1a8d9cb6-277e-48cf-acbb-5b49b9d445f7/Frame_2058.png" alt="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/1a8d9cb6-277e-48cf-acbb-5b49b9d445f7/Frame_2058.png" width="40px" /> Disclaimer: This case study contains detailed technical information specific to Figma.

</aside>

How it all started

My first consulting engagement was for a mobile app product - Healthy365. It is a government backed app with over 500k+ MAU. The main goal of the app is to encourage change in user behavior to make healthier lifestyle choices through gamification and rewards.

The ecosystem covers the end user experience (H365) and the business user experience (Business Admin Portal and Event Organiser App)

Frame 1.png

Ecosystem of Healthy365

<aside> ⚙ H365 – Users can participate in events, track their steps, and earn rewards.

</aside>

<aside> ⚙ BAP – A platform to help business and partners create and manage content in H365.

</aside>

<aside> ⚙ EO – A toolkit to assist event organisers in manage events and roadshows.

</aside>


Observation and problems

It was an exciting opportunity to apply and develop my skills in Design System. I took the opportunity to make our design workflow more efficient and organised. After a month on the engagement, I observed these challenges:

<aside> 🚨 Design system's components were not properly maintained for a year.

</aside>

<aside> 🚨 Poor file management causing Figma to be slow and clunky.

</aside>

<aside> 🚨 Designers were detaching components to form a new design.

</aside>