Overview

The brief in one sentence

Design a portfolio management feature for Clio that makes complex financial data understandable for novice investors without dumbing it down for experienced ones.

The challenge wasn’t purely visual. It was cognitive — how do you show volatility, risk exposure, sector allocation, and smart trade recommendations to someone who opened their first investment account three weeks ago, without overwhelming them into inaction?

The Problem

Information density is not the same as clarity

Research

Listening before designing

Key insight: novice users don’t need less data — they need data presented with context and intent. They want to know what something means for them, not just what it is.

Design Process

From insight to interface

Design Screens

What the work looks like

Add your Figma exports to the images/clio/ folder and update the src attributes below.

Outcome

Numbers that tell the real story

Users who previously closed the app when faced with the dashboard were now spending more time exploring — not because there was more to see, but because they finally understood what they were looking at.

Learnings

What this project taught me

Overview

The brief in one sentence

Design a trust-building feature for Amazon that reduces post-purchase anxiety, lowers WISMO (Where Is My Order) contact rates, and improves customer satisfaction without adding friction to the existing checkout flow.

The Problem

The experience falls apart after the sale

Research

Finding the trust gaps

Core insight: users didn’t need faster delivery. They needed fewer moments of uncertainty. Every step that told a user “here’s where your order is and what happens next” reduced anxiety, even if the timeline didn’t change.

Design Process

From insight to interface

Design Screens

What the work looks like

Outcome

Numbers that tell the real story

Learnings

What this project taught me

Overview

The brief in one sentence

Design a mobile shopping experience that reduces size-related return rates, increases first-purchase conversion, and builds enough confidence in fit prediction that users are willing to buy clothing they’ve never tried on.

The Problem

Uncertainty lives between the photo and the body

Research

Listening before designing

Pivotal insight: users weren’t primarily worried about whether something would look good. They were worried about whether it would feel good — fit around the shoulders, length, fabric weight. These are tactile questions no image can answer. The design task was to find proxies for touch.

Design Process

From insight to interface

Design Screens

What the work looks like

Outcome

Numbers that tell the real story

Learnings

What this project taught me

Overview

The brief in one sentence

Design a mobile learning companion for developers preparing for technical interviews that fits into the real constraints of a working professional’s day — commutes, lunch breaks, distracted evenings — while still building deep, testable knowledge.

The Problem

Most prep tools were built for people with four hours a day

Research

Listening before designing

Key insight: motivation to prep peaks at the start and collapses at “the plateau” — around 30–40% through, when easy problems are done and hard ones feel impossible. The design needed to address the plateau, not just the first session.

Design Process

From insight to interface

Design Screens

What the work looks like

Outcome

Numbers that tell the real story

Learnings

What this project taught me

Overview

The brief in one sentence

Design and develop the complete MAI Labs company website from the ground up — fully responsive, performant across browsers, and built with a reusable component system that the internal team could maintain and extend after handoff.

The Problem

A site the team can’t own

Research

Understanding before building

Design Process

From insight to interface

Design Screens

What the work looks like

Outcome

Numbers that tell the real story

The handoff was the outcome that mattered most. The team could update copy, add new team members, and post job listings without touching the codebase. That independence was the measure of success.

Learnings

What this project taught me

Overview

The brief in one sentence

Build a tool that makes WCAG 2.1 compliance findings understandable for design and development teams who have the will to fix accessibility issues but lack the knowledge to interpret technical audit reports.

The Problem

It’s a translation problem, not a willingness problem

Research

Understanding the gap

Design Process

From insight to interface

Design Screens

What the work looks like

Outcome

Numbers that tell the real story

Learnings

What this project taught me