After working as an accountant for a few years, I decided to go back to school to become a product designer. I learned about the UX/UI space from a web development course I was taking on the side. I wanted to be a part of a collaborative team to help build better experiences in the digital space.

My background led me to work at an agency in New York City called Future Forward, where I learned the ins and outs of the field and worked with multiple clients.

Next, I moved to Nashville, TN where I gained experience in the healthcare (SingleCare) and financial (Ramsey Solutions) industries as a UX/UI Designer.

Currently, I work as a full-time product designer at LPL Financial where I partner with different teams to make UX analyses and suggest design solutions for the LPL Financial webpages. I brainstorm with the team to improve engagement and retention for the LPL website.

I graduated from General Assembly, New York with a certificate in User Experience Design and received my B.A in Economics from City College of New York . I love human-centered design methods and processes. I apply these principles to my work, along with problem-solving skills.

I grew up in Guyana, South America before moving to the U.S. in high school. My ability to quickly adjust to new challenges in life comes from the experience of living in multiple cities. Because of my upbringing, I embrace all cultures and try to bring diversity into my design. I’m a big music enthusiast and play guitar often. In my free time, I enjoy going on walks with my wife, traveling to new places, and cooking my family’s recipes.

 
 

My Design Process

Design Processes unites a design team around a common language. Every company has a unique design system. Here is my design thinking and how I approach every process. 

Desktop@2x.png

Understand

What’s the problem I should be solving? It’s critical that we understand the demographics, users and business needs. User Research allows us to listen to the user, how the use the product and what would help their experience be delightful.

TECHNIQUES USED:

  • User Interviews

  • Empathy Mapping

  • Contextual Inquiry

  • Problem Exploration

  • Competitive Analysis

Define

Once we understand what we should be solving for it's time to make sure the entire team is on board. We need to analyze and synthesize our user's feedback, and make sure we're taking a goal-oriented approach, rather than a feature-approach. Our strategy must solve the problem, not just add new features.

TECHNIQUES USED:

  • Feature Prioritization

  • MOSCoW Map

  • Tech Feasibility Analysis

  • User Flow

  • Personas

  • Journey Maps

Design & Test

Then it's time to design the product using best practices. Starting the conversation with some Design Studio sketches is always the fastest method. Depending on the product solution, quality needed and timeline LoFi or HiFi Wireframes can be produced and then the Prototyping fun begins.

Using guided or unguided User Testing is paramount. We are not our users and this is the time to discover if product is function and usable.

TECHNIQUES USED:

  • Sketching

  • Design Studio

  • Prototyping

  • Usability Testing

  • Wireframing

Deliver

Then it's time to pass the information onto our developers and build this product! Producing user friendly Functional Specifications makes happy developers. Communication and working with talented developers is key to producing a fantastic product. 

TECHNIQUES USED:

  • High fidelity mockups

  • Final testing

  • Experience Walkthrough

  • Design/Zeplin Files Handoff