Planbit is a design-led project done in collaboration with General Assembly, working alongside a team of designer and developer to demonstrate a 1 -> 0 product design workflow in formulating evidence-based design outcomes.
Context
I contributed to the overall design process and oversaw aspects related to product scoping, user flows, wireframes, rapid prototyping, and usability testing.
Additionally, I conducted user research, facilitated co-workshops, and contributed in synthesising research findings to produce viable ideas.
Details
Time Frame:
Apr 23 – Dec 23
Role:
UI/UX Designer, Usability Researcher
Tool:
Figma, Miro, Trello, Zoom, Slack, Illustrator
Problem Discovery
People are not invested in their habits enough to stay committed.
While conducting early interviews with our potential users (graduates & early professionals), many of them expressed difficulty in maintaining a consistent routine while juggling their academic and professional expectations. Typically, they would start a new routine together only to be abandoned by everyone weeks later. This sparked a question –
My Solution - PlanBit
A gamified, personal and reflective take on cultivating self-motivation.
The Process
Subject-matter research showed the effective use cases of the ‘Hook’ model to increase people’s investment in forming habits.
Fairly new in behavioural science, we naturally started with a deep-dive into literature research on habitual frameworks, particularly the Hook model. This model has been widely referred to when developing habit forming products. As a good starting point, we would later validate this finding further via user interviews.
UI UX Design
Emphasising progress through a visual, personal, and reflective experience 🌳
The final MVP product
Onboarding + SignUp
Creating & Tracking Goals
Skipping Habits
Supporting Off-days and Edge Cases
Project Takeaways
A deeper understanding of ideas when placed within context, and not just in vacuums.
The project naturally started off as a research heavy project into behavioural science. We initially spent 80% of our time conducting literature research that were eventually found not relevant towards our MVP requirements after further validation and testing with our users.
It was through contextual insights and user interviews that proved to be equally, if not more valuable, in identifying opportunities and ideas that direct the generation phase.