• “Design is the intent behind the outcome—so be intentional”

  • Each step should be connected to the previous one and provide a reason why the next one is needed. My design process is driven by 4 main things: empathy, mindfulness, neuroscience, aesthetics.

  • 01. Empathy

    When building a product, I always keep the user in mind. If I can empathize, then I can advocate for a solution that people actually need.

  • 02. Mindfulness

    Intentionality goes hand in hand with mindfulness. Each step of the process, I ensure that I am solving the right problem and all design decisions are deliberate.

  • 03. Experimentation

    Testing is the essence of design. The most rewarding, validating, and humbling part of designing for me is testing out designs and getting feedback.

  • 04. Aesthetics

    Visual design is my passion. Prototyping and designing high-fidelity products brings me a lot of joy. In my work, I tend to express this job through design systems.

  • “Every project is different but will follow a basic process”

  • A process like this is rarely linear & is typically repeated multiple times before it is complete.

    In some cases, card sorting will be necessary while in others, the information architecture may already be well-defined. Though my method choice tends to differ for every project, I still follow a general process.

  • 01. Define the Requirements

    I usually begin by defining the business needs and requirements and determining the deliverables, timeline and expectations. Keep your team on the same page at all times. I like to write down my own hypothesis for what I believe the problem might be at this stage.

  • 02. Identify the issues

    In this phase, I collect information, talk to people, and explore the problem space. I will also review user reports and find out how the product was developed. I'll conduct ad hoc guerilla interviews if user research isn't feasible or time-limited.

  • 03. Interpret the Results

    During the interpretation phase, I identify the users' needs and pain points. A persona, a journey map, a storyboard, and a problem statement can all be defined or redefined. During this stage, I define our goals and metrics for success. Insights are always gained during this phase.

  • 04. Ideate over solutions

    Ideation is one of my favorite phases! I like to involve developers, other designers, stakeholders and customers in ideation sessions. This ensures that as many perspectives as possible are taken into account. I like to allow my mind to wander freely and come up with as many solutions as I can. At this stage I strive for quantity over quality.

  • 05. Prototype

    In this phase, I will create a prototype. It can be a hi-fi Figma or even an interactive website. The level of detail depends on how far along I am in the process and what I want to test.

  • 06. Test, iterate and test again

    During the final phase of design, I will test the prototype with users. Sometimes it will be a quick guerilla test, while other times it may be a full fledged usability test session. The test results will help us understand what needs to be changed and fixed.

  • How I like tocollaborate &my work style

  • I like to get information from wherever I can, and there's plenty of information out there.

    When I join my supporters in answering product questions and troubleshooting issues, I learn where users are getting stuck or even searching for other projects to find ways to improve my own.

  • 01. Involve Everyone

    I like bringing in people early in a project, communicating with them as much as possible. I talk to developers, product support agents, stakeholders, users and user researchers and bring them into the project as early as possible. I enjoy being collaborative and collecting insights from places one might not think to look.

  • 02. My Marketing Hat

    With my background as an online marketer and website developer. I speak the language of customers and the developers I work with. I think it is essential to understand and empathize with both users and my team. Knowing the root of business and how to be a developer helps me understand not only the problems the developers on my team face but I can also explain to them precisely what I want in the design.