Summary
I started as a designer, became a developer, and eventually transitioned into UX and Product Design. Along the way, I discovered that the most valuable skill wasn't design or development - it was learning how to solve problems from different perspectives.
Today, I combine design, development, leadership, and AI to create meaningful solutions and better user experiences.
Designer to Developer
For years, I introduced myself as a developer, even though I originally started my career as a designer.
After learning to code on the job, my roles gradually became more focused on development. While I enjoyed development and appreciated the opportunities it created, I continued collaborating closely with UX and graphic design teams, creating assets, wireframes, and prototypes while contributing to design discussions.
Although I enjoyed development, those experiences reminded me how much I enjoyed solving design problems and thinking about user experiences. Eventually, I earned a UX certification and transitioned into my first dedicated UX and Product Design role.
As my development career progressed, I had opportunities to mentor and lead other developers. I regularly reviewed progress, defined success criteria, and guided projects from concept to completion.
I also relied heavily on prototypes to communicate functionality and user flows, helping teams align around a shared vision. Throughout my career, I focused on improving efficiency, reducing ambiguity, and fostering collaboration across departments.
Rather than simply handing work off to another team, I preferred staying involved until the work was completed successfully. Many of these habits eventually became an important part of my UX practice.
Transitioning from Developer to Designer
One of the biggest differences I discovered between development and design was how success is measured.
A design can look beautiful and still fail to meet business goals or solve the wrong problem.
This shift in thinking changed how I approached projects. I learned that achieving business goals was often more important than visual perfection, making sketches, user flows, and low-fidelity wireframes more valuable than polished mockups.
I also discovered that stakeholders often trust what they can see and interact with. To build confidence in the design process, I would create a single polished screen that demonstrated the intended visual direction while continuing to work through ideas using sketches and wireframes.
When design decisions were disputed, I would create A/B prototypes and allow stakeholders to interact with each option. Experiencing a design firsthand often communicated its strengths and weaknesses far better than a discussion or static screen.
My development background influenced my design process as well. My work was highly structured and component-based, which made implementation easier but sometimes required me to consciously separate technical constraints from creative exploration.
Discovering AI
As AI tools became more capable, I began integrating them into my daily workflow. Initially, I made the mistake that many people make: I allowed AI to do much of my thinking. While it was fast, it often produced generic results that lacked intention and strategic thinking.
Over time, I learned to treat AI as a collaborator rather than a replacement. As a sole designer, AI helped fill areas where I was lacking, particularly when it came to brainstorming, exploring different approaches, and validating ideas. Rather than doing the work for me, it became a creative partner that strengthened my thinking and accelerated my workflow.
Today, I use AI throughout my design process, from research and ideation to content creation and rapid prototyping. My background in graphic design also helped me work effectively with generative AI tools. AI rarely produces the exact result I want on the first attempt, but tools such as Photoshop allow me to refine and customize the output until it aligns with my vision.
Over time, I developed an AI-driven workflow that combines design thinking, development knowledge, and creative exploration.
Where I Am Today
Throughout my career, I have been a designer, developer, mentor, leader, UX designer, product designer, and AI advocate. As AI continues to blur the boundaries between disciplines, that question has become even more complex.
Over time, I realized that my value does not come from a single title. Design taught me empathy. Development taught me execution. Leadership taught me collaboration. AI taught me how to extend my capabilities.
Today, I no longer focus on fitting into a specific role. Whether I am designing, building, mentoring, or experimenting with AI, my goal remains the same: to solve problems, communicate ideas, and create meaningful experiences.