Skip to content

Case study 02 · OMALife

OMALife: Designing for clarity in complex workflows.

Exploring thoughtful interaction design, intuitive navigation and consistent digital experiences in the wellbeing space.

Company
Inner Compass Wellbeing
Role
UI/UX Designer & Front-End Developer
Period
May to August 2025
Original abstract artwork · not a product screen

01 · Project overview

Professional work, shared through approach.

OMALife is a digital wellbeing and therapy practice management platform. At Inner Compass Wellbeing, I designed and developed key experiences across it.

From May to August 2025, as UI/UX Designer & Front-End Developer, I designed and developed key experiences covering client onboarding, scheduling, telehealth, clinical notes, forms, billing, and practice management.

Wellbeing work is personal, and the tools around it shouldn’t add friction. My job sat where those two things meet: shaping interfaces that help people get through their tasks with less effort, and helping turn those designs into working screens.

Because the product is confidential, this page doesn’t show it. Instead, it explains how I think and work — with original illustrations made only for this case study.

Areas I worked across

  • Onboarding and navigation
  • Dashboards and information architecture
  • Scheduling and calendar interactions
  • Forms and reusable interface patterns
  • Design system consistency
  • Responsive interface design
  • Interaction states and prototyping
  • Design and front-end collaboration
Project
OMALife
Company
Inner Compass Wellbeing
Role
UI/UX Designer & Front-End Developer
Period
May to August 2025
Category
Product Design / UI/UX / Front-End Development
Location
Toronto, Ontario
Domain
Wellbeing and digital practice management
Type
Professional product design experience

This case study focuses on my design approach and professional experience. Confidential interfaces, proprietary information and client data have been intentionally excluded.

02 · The design challenge

Many moving parts. One calm experience.

Complex platforms ask a lot of the people using them. The design work is to make that load feel lighter.

Conceptual illustration · the same elements, organised
  1. 01

    Navigating complexity

    Many connected areas should still feel like one place, where people always know where they are and how to get back.

  2. 02

    Different tasks, one product

    Some moments are quick check-ins, others are focused work. Each needs the right amount of interface — no more.

  3. 03

    Reducing cognitive load

    Showing what matters now, and keeping the rest close by rather than on screen at once.

  4. 04

    Organising information

    Grouping related content so that scanning a screen tells you what it’s for before you read a word.

  5. 05

    Consistency across surfaces

    The same action should look and behave the same everywhere, so learning one part of the product teaches the rest.

  6. 06

    Intuitive interactions

    Controls that explain themselves through clear states, honest feedback and forgiving errors.

General considerations for complex platforms — not findings from internal research.

03 · My design approach

Understand. Structure. Design. Refine.

This is how I approach complex product work — a way of thinking I bring to each problem, not a script.

Clarify the task, the people involved, the constraints and the experience it should create.

  • What is someone trying to get done here?
  • What do they already know, and what are they unsure of?
  • What limits the solution — technically and practically?

04 · Designing for clarity

What should I look at first?

Hierarchy is how an interface answers “what should I look at first?” before anyone asks.

Overview

Project overview

In progress

Next steps

  • Review the brief
  • Gather references
  • Share first draft
Owner
Team A
Updated
Today
ContinueSave for later
Independent conceptual illustration — not an OMALife screen.
  1. Clear groupingRelated items share a container and sit closer together than unrelated ones.
  2. Readable typeA small set of sizes and weights, each with one job.
  3. Logical hierarchyOne primary action per view; secondary actions step back.
  4. Consistent spacingA shared spacing scale, so rhythm signals structure.
  5. Accessible contrastText and controls that stay legible for everyone.
  6. Understandable statesHover, focus, selected and disabled each look distinct.

05 · Building consistent experiences

The same thing should always behave the same way.

Consistency isn’t about making everything look the same. It’s about making the same things behave the same, so people can trust what they see.

  • Reusable components
  • Consistent buttons and form controls
  • Input validation states
  • Responsive behaviour
  • Interaction feedback
  • Typography and spacing systems
  • Accessibility considerations

Buttons

Hover, press, focus and disabled share one language

Input validation

Feedback appears after you leave the field, and says how to fix it

Try typing, then leave the field

Selection

Clear on, off and selected states

Notifications

Type & spacing

A small scale, each step with one job

Heading

Subheading

Body text that stays comfortable to read.

Label

4812162432
Conceptual component examples created to illustrate my approach to UI consistency. Not actual OMALife assets.

06 · From design to implementation

Designing with the build in mind.

Working across design and front-end changed how I design. Knowing how an interface will be built makes it better before it’s built.

  • Spacing

    One 4-pt scale

  • States

    Default · focus · error

  • Breakpoints

    Reflow, don’t shrink

Same component · desktop width

Conceptual diagram — illustrates a way of working, not a specific system.
  • Responsive from the start

    Designing how a layout reflows, not just how it looks at one width.

  • Component behaviour

    Thinking in reusable parts with defined states, so design and code share one vocabulary.

  • Feasibility

    Spotting what will be costly or fragile to build early, while there’s still room to choose.

  • Interaction details

    Specifying focus, loading, empty and error states, so nothing is left to guesswork.

  • State consistency

    Making sure the same state looks the same wherever it appears.

  • Collaboration

    Speaking both languages, which makes handoff a conversation rather than a document.

07 · What I learned

Lessons I carry into every product.

  1. Design systems, not screensA screen is one moment. The patterns behind it are what make a product feel coherent as it grows.
  2. Usability and functionality are partnersPowerful features only help if people can find and understand them. Restraint is part of the work.
  3. Consistency compoundsSmall inconsistencies multiply across a product. Catching them early is cheaper than fixing them later.
  4. Constraints sharpen designUnderstanding technical limits made my decisions more grounded, not less ambitious.
  5. Every state mattersEmpty, loading, error and success states are where trust is won or lost.
  6. Explain the whySharing the reasoning behind a design leads to better conversations than presenting a finished answer.

08 · Closing reflection

OMALife taught me to design for the whole system — to think about how each decision holds up across a product, in the hands of real people, and in the code that brings it to life.