Product Designer & aspiring Design Engineer, making complex technologysimple, systematic & human-centered

Experience5 years
PreviouslyIBM
FocusProduct Design · Systems
ApproachDesign + Engineering
Scroll to explore
Design Process

How I work.

6 steps · End to end
Process —— 01

Business understanding
before pixel one.

Design without business context is decoration. Before I explore user needs or open a design tool, I align with stakeholders on what success looks like — in numbers, not assumptions. This grounds every decision that follows.

Questions I Ask First
+
What are we trying to achieve?
+
What metric defines success?
+
What constraints exist?
+
Is this revenue, retention, or cost-saving?
0/4
Strategy Brief
AWAITING INPUT
GOAL
Objective
KPI
Success Metric
SCOPE
Constraints
DRIVER
Business Driver
PS.01 —— BUSINESS UNDERSTANDING
Building strategy brief…
Process —— 02

User research as
a decision engine.

With business goals locked, the lens shifts to users. I don't research to validate what I already believe — I research to find what I can't see yet. Each method reveals a different layer: what people say, what they do, and where the gap lives between the two.

No single method tells the full story. Triangulation does.

Research Methods
User Interviews
Surveys
Analytics Review
0 signals
Research WallAWAITING DATA
Collecting research signals…
PS.02 —— USER RESEARCH
Process —— 03

Wireframes as
thinking artifacts.

Wireframes aren't about how something looks — they're about how it works. I use low-fidelity layouts to make structural decisions fast: information hierarchy, user flow, and interaction patterns — all before a single color is chosen.

The fastest way to test an idea is to make it ugly on purpose.

Screen Inventory
Onboarding
List View
Detail View
Input Form
Confirmation
Wireframe Preview
LOADING FRAMES
Assembling wireframes…
PS.03 —— WIREFRAMES
Process —— 04

Visual design is
systems design.

I don't design screens — I design systems that produce screens. Every color, type size, and radius traces back to a token. Every component inherits from a shared vocabulary. The result is a product that scales without losing coherence.

A design system isn't a library — it's an opinion about how things should work.

System Layers
Design Tokens
Component Library
Patterns & Layouts
System SpecimenINITIALIZING
Loading design system…
PS.04 —— VISUAL DESIGN
Process —— 05

Design review as
a multiplier.

Before anything ships, the work faces the sharpest critics — the team. PMs challenge scope and priorities. Engineers flag what will break. Designers catch what I missed. Every comment is a bug caught early, not a rework caught late.

The best designs survive scrutiny. The rest improve from it.

Participants
Product Manager
Engineer
Designer
Review Checklist
Feasibility
Edge Cases
Missing States
Technical Constraints
0 comments
Review Session
AWAITING REVIEWERS
PS.05 —— TEAM REVIEW
Process —— 06

Handoff is a
conversation, not a file.

A Figma link isn't a handoff. Real handoff means every value traces to a token, every state is documented, and every interaction has a rationale. I deliver specs that engineers can implement without a single "what did you mean by this?" message.

The fewer questions after handoff, the better the handoff was.

Handoff Layers
Visual Specs
Component States
Interaction Logic
Edge Cases
Component Spec
INITIALIZING
Preparing spec sheet…
PS.06 —— HANDOFF