Denovo
My Role
Team Members
Tools Used
Timeline
Background
The Challenge
Information Architecture
Denovo is a mobile app built to support individuals in quitting alcohol and maintaining long-term sobriety. It provides tools to track progress, set personal goals, and celebrate milestones along the recovery journey. The app focuses on motivation, accountability, and encouragement, giving users a safe digital space to stay committed. By combining progress tracking with positive reinforcement, Denovo empowers users to embrace healthier lifestyles.
I was responsible for designing the entire app experience, from product architecture to user flows and prototyping. My focus was on creating a clean, supportive, and relapse-proof interface that encourages consistency. I structured features to make progress tracking intuitive while ensuring motivation remained central to the design. The outcome was a user-centered mobile app that blends empathy with functionality to guide individuals toward sustained sobriety.
Research & Exploring the Structure
User interviews were conducted by the core team in Tennessee. While I wasn't present for the sessions, I synthesised the findings with the team to align on which workflows were essential for mobile and which were better suited to remain on desktop. This conversation became the foundation for every structural decision that followed.
With the scope defined, three structural approaches were explored:
Assessments, sessions, and goals as separate destinations linked by session IDs. Familiar, but required jumping across sections to complete one task.
Navigation simplified, bottom nav removed, but the three still lived independently. Less clutter, same fragmentation.
Everything was organised within the session itself. One entry point, one context, no jumping between sections.
Option 3 was chosen because it matched how patients naturally think about their care: in terms of sessions, not categories. If a patient wants to do anything related to one session, they go there and nowhere else. It also clarified the mobile scope — the session was the sole task we wanted to support on mobile. Everything else that felt too complex was intentionally left on desktop.
Interactive Prototype
Denovo
My Role
Team Members
Tools Used
Timeline
Background
The Challenge
Information Architecture
Denovo is a mobile app built to support individuals in quitting alcohol and maintaining long-term sobriety. It provides tools to track progress, set personal goals, and celebrate milestones along the recovery journey. The app focuses on motivation, accountability, and encouragement, giving users a safe digital space to stay committed. By combining progress tracking with positive reinforcement, Denovo empowers users to embrace healthier lifestyles.
I was responsible for designing the entire app experience, from product architecture to user flows and prototyping. My focus was on creating a clean, supportive, and relapse-proof interface that encourages consistency. I structured features to make progress tracking intuitive while ensuring motivation remained central to the design. The outcome was a user-centered mobile app that blends empathy with functionality to guide individuals toward sustained sobriety.
Research & Exploring the Structure
User interviews were conducted by the core team in Tennessee. While I wasn't present for the sessions, I synthesised the findings with the team to align on which workflows were essential for mobile and which were better suited to remain on desktop. This conversation became the foundation for every structural decision that followed.
With the scope defined, three structural approaches were explored:
Assessments, sessions, and goals as separate destinations linked by session IDs. Familiar, but required jumping across sections to complete one task.
Navigation simplified, bottom nav removed, but the three still lived independently. Less clutter, same fragmentation.
Everything was organised within the session itself. One entry point, one context, no jumping between sections.
Option 3 was chosen because it matched how patients naturally think about their care: in terms of sessions, not categories. If a patient wants to do anything related to one session, they go there and nowhere else. It also clarified the mobile scope — the session was the sole task we wanted to support on mobile. Everything else that felt too complex was intentionally left on desktop.
Interactive Prototype