Outlined in this diagram, the research and testing steps are crucial to my process. I'm a huge believer in conducting both foundational and directional research. Foundational research referring to more general research, often times when problems are initially identified. Then using directional research to delve more specifically into the problems uncovered in the foundational research. 

 

The analysis from this research is used to define the design necessary to solve the problem. I organize my thoughts through diagrams, charts, or journey mapping and move quickly onto low fidelity wireframes (created in Sketch or drawn in a sketchbook). I find these essential to conveying my ideas and direction to the rest of my team. Pending any other necessary research, I start creating high fidelity mock-ups (created in Sketch and exported to Zeplin for development requirements). Prototyping is done on an as needed basis and can be included at any step in the process (currently I use Invision for my prototypes). 

​

The process of researching, testing, and creating mock-ups is often a circular process. Getting to know a problem in depth during the design of wireframes or prototypes often brings up further questions about the issue. This is why design critiques or any stakeholder feedback is so important to me. Constructive criticism is absolutely instrumental for skill growth and experience improvement.  (And I got a tough skin from design school!! :D ) 

​

An important aspect of my process that isn't specifically identified in the diagram is my constant contact with the project stakeholders and clients. During all appropriate aspects of the project, I am in contact with the stakeholders and clients to confirm direction, feedback, and feasibility. In my time as a dual role of UX Designer and Product Manager, I found that transparency and communication are essential for project success.

​

Review my design process in action through several example projects provided here.