Work

My previous experience as an engineer allows me to speak the language of my teammates, I can communicate needs and take into account possible technical limitations.

I thrive within constraints, a systems approach is very much engrained in my way of thinking. So design systems (using them and building them) are pretty much how I’ve been spending my time as of late.

From holistic to granular views, my curiosity for all dimensions of product development helps my awareness when coming up with solutions.

I’ve started my Accessibility journey for the last couple of years, overseeing audits and implementing changes suggested by them. It’s been very challenging, and I’m learning a lot through it.

Adapt or die. I learned to thrive in uncertainty (which wasn’t easy for me), asking the most questions I can, and figure my way to…

Understand the problem first. We can’t produce meaningful solutions if the problem’s not crystal clear to the team.

There’s no I in TEAM… I have no pretension that I know all or even most of the answers, I rely on my teammates to create the best possible solution together. Communication is key.

…but there is an I in ITERATION. Perfect will always be the enemy of great, but I know we can do better and better each time.

1. Research: I find out the most I can about the problem or opportunity space: what are competitors doing about it, what do people want (if they even know).
2. Guidelines: pick the guiding principles that will help us make decisions along the way, and come together as a team.
3. User Flow: Learn more about the people we wanna serve, and start thinking about how our solution will help them achieve their goals.
4. Explore: Look for partial or full existing solutions to look for a starting point, or see what we don’t wanna look/feel like. Sketch, wireframing.
5. Design: Pick a direction we wanna go on, work on the visuals and interactions. Prepare everything for…
6. Handoff: Work closely with engineering to ensure our vision come together and implement something great!
7. Iterate: Once we have stuff in prod we see how it behaves, then find places on which we can improve.