From messy problem to interface people love.
Most of what I've designed didn't start as a clean brief — it started as a confusing workflow, a stakeholder's complaint, or a legacy tool nobody wanted to touch.
This is the sequence I default to when a problem hasn't been shaped yet.
Research before pixels
I sit with users, stakeholders, and the workflow itself — through moderated testing and interviews — before I open Figma.
When research isn't valued yet, I've had to pitch it: at Telecom Argentina, this meant proving ROI to an IT-driven team that initially saw testing as a waste of time.
Build the skeleton first
Paper sketches and low-fidelity wireframes let a team align on structure fast, before anyone commits to pixels.
Then I build the real system: Figma variables and tokens, component libraries, and flows that hold up across desktop, tablet, and mobile.
Design for handoff
A design system only works if engineering can pick it up without asking questions.
I document every decision.
My CS background makes this handoff genuinely frictionless.