The Industrial Root
My background is in Industrial Design, where I focused deeply on ergonomics, manufacturing constraints, and how things are actually made. That mindset naturally carried into my work in digital products. I approach interfaces the same way I would a physical object, with attention to structure, modularity, scalability, and the core building materials of the web. Rather than treating screens as static visuals, I design systems that are meant to hold up in real-world conditions, balancing visual clarity with technical and platform realities.
System-First Architecture
I believe strong products come from close collaboration between design and engineering, not from handing work off at the last step. I prototype in the browser early to validate feasibility and uncover constraints, instead of relying only on static mockups. Design tokens act as a shared source of truth between Figma and the codebase, helping ensure consistency from concept to production. This turns the design system into a living foundation rather than a collection of components, so what ships aligns closely with the original intent. That philosophy shows up in how the work is structured day to day, moving through the following stages:
I begin by aligning user needs, business goals, and technical constraints. This stage goes beyond collecting requirements. It is about clearly defining the problem worth solving. By auditing the current experience and speaking directly with stakeholders, I make sure we are focused on the right opportunities before investing time in solutions.
Before moving into visuals, I focus on structure. I map information architecture and user flows early, accounting for edge cases and complex states from the start. This helps ensure the system works across real-world scenarios, not just ideal ones, and creates a solid foundation for everything that follows.
I progress quickly from low-fidelity exploration to high-fidelity design, using the design system as a framework rather than a constraint. This phase is centered on iteration and collaboration, testing multiple directions with stakeholders to balance visual clarity, usability, and technical feasibility.
Design continues through implementation. I provide production-ready specifications and work closely with engineers during development. By reviewing the final build, I help ensure interactions, responsiveness, and visual details align closely with the original intent and deliver a polished, cohesive result.
My Toolkit
I’m a lifelong learner who enjoys exploring new tools and workflows. While I adapt easily to the stack a team is already using, the following areas reflect where I tend to spend most of my time when building scalable, well-crafted products.
Agile & Execution
I view Agile not as a rigid ceremony, but as a mechanism for velocity. I thrive in cross-functional squads where design is a partner, not a bottleneck. Because I speak the language of engineering, I can unblock implementation hurdles during standups—preventing the "design vs. dev" friction that kills momentum. I prioritize shipping features to gather real data, over polishing pixels in a vacuum.