My Design Process

The primary goal is to grasp user needs, tackle present challenges, and cultivate a unified vision with both the team and stakeholders. Often, a nonlinear approach is instrumental to comprehend human behavior and create effective products that serve audience needs.

Discovery Phase

Design Brief

It is important to fully understand the design challenge by asking the right questions early and often. The following guideline is what I use for every project to start the discovery phase.

What are the project expectations?
  • What are the project deadlines?
  • What type of research is expected?
  • What are the expected sprint ceremonies?
What are the goals?
  • What are the business goals?
  • What is the business outcome hypothesis?
  • What is the user goals & objectives?
What are the success metrics?
  • How does it affect the user?
  • What value does it bring?
What are the risks?
  • What are the constraints or unknowns?
  • Are there any design considerations?
  • Are there any cross functional team dependancies?
What kind of feature is it?
  • Feature enhancement
  • Feature redesign
  • New feature
What is the problem level?
  • Problem complexity: Low  Med  High
  • UX Risk: Low Med High
What is the problem statement?
  • What are we building and why?
  • Are there any cross functional team dependancies?

Discovery Phase

User Interviews

Understanding the Who, What, Why, Where, When, and How equips a designer to tackle UX challenges effectively. User interactions shed light on the target audience, the core problem, decision-making motivations, potential opportunities, usage timing, and application methods.

Yet, I view this more as a dialogue than a formal interview. I've gleaned richer insights through natural conversations, ensuring a relaxed and insightful experience for the interviewee. I prepare a set of guiding questions to optimize our time together.

  1. Identify motives: Decide what you want to learn and brainstorm with team members who could provide some insight into the conversation.
  2. Create answerable questions: Break down themes and generate all possible questions, refining them based on research objectives.
  3. Avoid leading questions: Ensure questions don't suggest a preferred answer, aiming for honest responses.
  1. Create answerable questions: Break down themes and generate all possible questions, refining them based on research objectives.
  2. Use open-ended questions: Avoid yes/no questions to encourage detailed and unbiased responses, increasing the likelihood of valuable feedback.

Discovery Phase

User Personas

Personas are crafted to encapsulate varied mental models of potential users for a site, brand, or product. They offer insights into the goals, needs, and limitations of individuals, guiding decisions on services, product features, interactions, and visual designs.

Personas evolve as we uncover more insights during the project. It's essential to discern behavioral patterns among our audience, considering both their differences and commonalities. The evolving digital landscape, coupled with emerging devices, introduces complexities to UX.

Discovery Phase

Journey Map

A journey map melds personas with user flows, distilling extensive research into a vivid, digestible narrative. Such maps foster team-wide comprehension of the holistic user experience and spotlight product prospects. They encapsulate emotional nuances and specific pain areas, sparking insightful discussions and fostering user empathy, crucial for purposeful design.

Here are examples of journey maps I crafted for Burger King and Driveway, paving the way for impactful product enhancements for our clientele.

Discovery Phase

Task Flowcharts

I frequently craft these! They're indispensable for intentional design, aligning teams, and refining wireframe designs for content accessibility and clarity at every product phase.

I liken them to authors sketching plot arcs. Without them, navigating numerous pages would be daunting. They serve as visual roadmaps that capture algorithms, workflows, or customer journeys to pinpoint pivotal action stages, ensuring alignment with overarching objectives without losing sight of the primary goal.

Design Phase

Sketching & Ideation

A simple paper and pencil, or a whiteboard, can significantly enhance the development of a design solution. This cost-effective method offers substantial advantages.

I frequently sketch for brainstorming, ideation, or conveying ideas because sketches are quick and straightforward to produce. The imperfections inherent in sketching facilitate the exploration of various design options without constraints, inspiring innovative thinking outside the box.

Design Phase

Wireframes & Prototypes

I often use wireframes as visual blueprints to sketch out the basic structure of a digital product. They help me organize elements and clarify my design intentions. I make sure to add detailed notes on these wireframes, explaining interactions and technical aspects. These notes often anticipate questions and help my team work more efficiently.

I enjoy turning wireframes into prototypes. It's a great way for me to share my design vision and test out ideas. When I see these prototypes come to life, it gives me a clearer picture of how the final product will work.

Design Phase

Design Critique

A design critique is a meeting where the team provides specific and actionable feedback to enhance design solutions. I find design critiques invaluable when navigating challenges, refining UI/UX designs, showcasing work in progress, and ensuring team alignment.

While I once felt apprehensive about presenting my work for review, I soon recognized its pivotal role in the design thinking process. I typically showcase designs using online tools like Figma or Miro, inviting evaluations and comments. My approach involves a consistent format: identifying the design challenge and specifying the desired feedback. Such sessions typically involve three roles: Facilitator, Presenter, and Critic.

Delivery Phase

Design Handoff

he handoff process between Designers and Developers has consistently posed challenges, often due to discrepancies in engineering approaches. Since a universal handoff template doesn't exist, I collaborate closely with Developers to define specific handoff requirements tailored to their preferences and needs.

I strive to create the optimal design handoff for each team, adhering to the following guidelines:

  • Provide breakpoint designs for desktop, tablet, and mobile to specify the interface variances.
  • Export images in a linked folder with consistent and descriptive labeling.
  • Provide a clickable prototype if interactions need to be described with more detail.
  • Figma’s Inspect Tool: we are fortunate to have a seamless tool for providing design specs. Heavily documented padding and size measurements of every interface detail is finally a task of the past!
  • Developers typically process their assignments through user story tickets so we need to curate the design handoff for each user story to add more clarity. Developers will appreciate this extra detail so they can focus their time and effort on the actual build.
  • Use the same language that engineers are familiar with to avoid confusion.
  • Utilize design system tokens to streamline the product development process. This speeds up the build with standardized styles, variables, and components.

Delivery Phase

Design QA

Design Quality Assurance involves assessing and validating builds for design excellence, pinpointing any missed details prior to product launch. It encompasses task flows, error management, data validation, and content clarity. Early collaboration with the team is vital to integrate a Design QA process seamlessly into the development sprint cycle.

I scrutinize functionality and interactivity across various elements like buttons, forms, navigation, and animations. I deliver a prioritized list, accompanied by annotated screenshots, to  address issues efficiently — especially under tight deadlines.