I’m a full-stack product designer who speaks engineering and thinks in systems.

Project one

A one-sentence dsframing of the project: who it was for, what it had to achieve, and the shape of the outcome — enough that a skimming reader knows whether to stay.

sdadas

The problem

Two or three paragraphs of situation: the state of the product before the work, the user pain it produced, and why now. Ground it in something observed — a support-ticket theme, a funnel number, a research session — rather than opinion.

A second paragraph for the constraint that shaped everything: the deadline, the legacy system, the platform rule. Naming the constraint early is what makes the later decisions read as decisions.

Goals

• The primary user outcome, phrased as a change in behaviour.
• The business result that outcome was expected to move.
• The quality bar — accessibility, performance, brand.

Process

1. Research: what was looked at and who was spoken to.
2. Exploration: the directions tried, and what killed the losers.
3. Validation: how the surviving direction was tested.

The solution

What shipped, described as the user meets it. Lead with the flow, not the screens; the images below carry the pixels.

A detail worth zooming into

One subsection per design decision that deserves its own heading — the interaction model, the empty state, the edge case that shaped the happy path.

Where the work touched implementation, show it — a token, a config, an API shape. Code earns its place when the design decision lives in it:

:root[data-theme="dark"] {
  --panel: #33302d; /* one card step off the page base */
}

Outcome

A closing paragraph: what the numbers meant, what was learned, and the one thing that would be done differently next time.

Project two

A one-sentence framing of the project: who it was for, what it had to achieve, and the shape of the outcome — enough that a skimming reader knows whether to stay.

Role

Product designer

Timeline

Jan – Apr 2026

Team

1 PM, 2 engineers

Tools

Figma, Next.js

The problem

Two or three paragraphs of situation: the state of the product before the work, the user pain it produced, and why now. Ground it in something observed — a support-ticket theme, a funnel number, a research session — rather than opinion.

A second paragraph for the constraint that shaped everything: the deadline, the legacy system, the platform rule. Naming the constraint early is what makes the later decisions read as decisions.

Goals

• The primary user outcome, phrased as a change in behaviour.
• The business result that outcome was expected to move.
• The quality bar — accessibility, performance, brand.

Process

1. Research: what was looked at and who was spoken to.
2. Exploration: the directions tried, and what killed the losers.
3. Validation: how the surviving direction was tested.

The solution

What shipped, described as the user meets it. Lead with the flow, not the screens; the images below carry the pixels.

A detail worth zooming into

One subsection per design decision that deserves its own heading — the interaction model, the empty state, the edge case that shaped the happy path.

Where the work touched implementation, show it — a token, a config, an API shape. Code earns its place when the design decision lives in it:

:root[data-theme="dark"] {
  --panel: #33302d; /* one card step off the page base */
}

Outcome

A closing paragraph: what the numbers meant, what was learned, and the one thing that would be done differently next time.

Project three

A one-sentence framing of the project: who it was for, what it had to achieve, and the shape of the outcome — enough that a skimming reader knows whether to stay.

Role

Product designer

Timeline

Jan – Apr 2026

Team

1 PM, 2 engineers

Tools

Figma, Next.js

The problem

Two or three paragraphs of situation: the state of the product before the work, the user pain it produced, and why now. Ground it in something observed — a support-ticket theme, a funnel number, a research session — rather than opinion.

A second paragraph for the constraint that shaped everything: the deadline, the legacy system, the platform rule. Naming the constraint early is what makes the later decisions read as decisions.

Goals

• The primary user outcome, phrased as a change in behaviour.
• The business result that outcome was expected to move.
• The quality bar — accessibility, performance, brand.

Process

1. Research: what was looked at and who was spoken to.
2. Exploration: the directions tried, and what killed the losers.
3. Validation: how the surviving direction was tested.

The solution

What shipped, described as the user meets it. Lead with the flow, not the screens; the images below carry the pixels.

A detail worth zooming into

One subsection per design decision that deserves its own heading — the interaction model, the empty state, the edge case that shaped the happy path.

Where the work touched implementation, show it — a token, a config, an API shape. Code earns its place when the design decision lives in it:

:root[data-theme="dark"] {
  --panel: #33302d; /* one card step off the page base */
}

Outcome

A closing paragraph: what the numbers meant, what was learned, and the one thing that would be done differently next time.