Complex products ask for effort.Confusing ones waste it.
I make sure your users' effort pays off.
BRAZIL
- 10+ years in design
- 7 as a product designer
10+ years in design
Intuit · HP · Lightship · Cirrus Track & Field · Softplan
- Portuguese (native)
- English (fluent)
I join the conversation before handoff, not at it.
Complex, data-heavy products.
I work with PMs and engineers from the start, while product logic, data constraints and feasibility are still open. Design that arrives after those decisions are closed can only decorate them. When the team is unsure, I test. Interviews, workshops, low-fidelity prototypes and focused usability sessions — scoped to the riskiest assumption, not to everything. I document flows, states and interaction rules so engineering and QA can build without guessing. Ambiguity is expensive, and most of it is avoidable before a single component is written.
Capabilities
Different projects show different parts of my practice. These three run through almost all of them.
Research and discovery
I use interviews, workshops, prototypes, and usability tests to clarify problems, expose risky assumptions, and align teams before expensive UI work.
Complex systems
I turn dense product logic into interfaces people understand and operate—across multi-state workflows, connected systems, and complex decisions.
Design systems
I build design systems that keep products coherent as they scale—combining components, tokens, documentation, dev collaboration, and practical governance.
What I believe
Complexity should be navigable, not hidden.
Some products can't be simplified without becoming useless. The work is to make the structure legible, not to pretend it's simple.
Edge cases are the design.
What happens when something is missing, late, or wrong is where an interface either holds or falls apart.
Patterns beat screens.
A component that solves a class of problems is worth more than a screen that solves one.
