I design it.
Then I build it.
Eight years of turning enterprise chaos into products people don't hate using. I sketch in Figma, prototype in code, and ship with the dev team — because the best design decisions happen when you understand what's actually buildable.
I started as an engineer. That changes everything.
The activation flow had 12 steps and a 74% error rate. After three rounds of usability testing with store staff, it had 4 steps and managers were rating it 4.7 out of 5. That's the kind of problem I live for. I'm a Senior Product Designer who also builds — HTML, CSS, JavaScript, Angular Material. That dual background means I design with production in mind and collaborate with engineering without the usual friction. Eight years in enterprise UX. Based in Miami.
Selected Work
Case Studies
Three projects. Real users. Measurable outcomes.
Telecom Retail · 2024
Mobile Activation
“Staff had memorized workarounds just to survive a live sale.”
The activation flow had 12 screens, no progress indicator, and timed out mid-transaction. I ran 3 rounds of usability testing with 24 store staff and redesigned it down to 4 locked steps.
12 steps → 4. Activation time: 12 min → 4.5 min. Error rate down 74%. Manager satisfaction: 4.7/5.
Activation time
Error rate
Support escalations
Manager rating
How I Actually Work
Not a framework. Just what I've learned after eight years of shipping enterprise tools.
Embed and observe
I don't start in Figma. I sit with the team, shadow users on the floor, and find the three-click ritual everyone secretly hates. The best insights come from watching someone try to close out on a Friday at 6pm.
Design the system
Screens are easy. What matters is the component library, the pattern repository, and the rules that keep forty branches from drifting into visual chaos six months later. I build what I design — HTML, CSS, Angular Material — so handoff is never a black box.
Prototype with real data
High-fidelity prototypes loaded with actual store IDs, real dropdown counts, and edge cases that break every time. If it doesn't feel real during testing, it won't feel real when a manager is trying to finish a report before close.
Ship and measure
Launch isn't the finish line. I watch activation times, read support tickets, and iterate based on what users actually do — not what they said they'd do in a research session six weeks ago.
What I Actually Do
I sit somewhere between design and engineering — which means I can own a project from "this is broken" all the way to "it's live." Here's the toolkit I use to get there.
Product Design
- Figma
- Prototyping
- Wireframing
- Design Systems
- InVision
- Accessibility (WCAG)
UX Engineering
- HTML5
- CSS3
- JavaScript
- Angular Material
- Bootstrap
- Vuetify.js
- Responsive Design
User Research
- User Research
- Journey Mapping
- Usability Testing
- Contextual Inquiry
- Affinity Mapping
- Data Synthesis
Agile & Collaboration
- Agile Methodologies
- Scrum Framework
- Sprint Planning
- Cross-Functional Teams
- Design Handoff
- Stakeholder Communication
Creative Suite
- Photoshop
- Illustrator
Research-Driven Design
Every design decision is grounded in user research and validated through rigorous testing. I combine qualitative insights with quantitative data to create experiences that truly resonate.
Research Methods
User Interviews
In-depth qualitative interviews to uncover user motivations, pain points, and mental models that drive design decisions.
Surveys & Analytics
Quantitative research combining survey data with behavioral analytics to validate hypotheses at scale.
Usability Testing
Moderated and unmoderated testing sessions to identify friction points and optimize task completion rates.
Journey Mapping
End-to-end customer journey visualization to identify opportunities and align cross-functional teams.
Persona Development
Research-backed personas that represent real user segments and guide product strategy decisions.
A/B Testing
Controlled experiments to measure design impact and make evidence-based optimization decisions.
Strategic Thinking
Problem Framing
Defining the right problem before jumping to solutions through stakeholder alignment and research synthesis.
Systems Thinking
Understanding how design decisions impact the broader ecosystem and long-term product strategy.
Cross-Functional Collaboration
Bridging design, engineering, and business to create shared understanding and aligned outcomes.
Iterative Validation
Continuous learning loops that reduce risk and ensure solutions meet real user needs.
"Good design is not about aesthetics—it's about deeply understanding users and solving real problems with evidence-based solutions."
What People Say
From the People I Worked With
Feedback collected during research debriefs and project retrospectives. Names withheld — most of this work is under NDA.
“Damian actually came into our store and watched us work. He didn't just ask questions — he sat there during real activations and saw exactly where we were getting stuck. By the time he showed us the redesign, it felt like he'd been doing this job himself. That's rare.”
Say Hi
Whether you've got a project, a question, or just want to swap war stories about enterprise UX — my inbox is open.