My Process


Why Design Thinking?

Businesses are paralyzed by the organizational costs associated with 'Change'. Design Thinking is a system which first and foremost streamlines problem solving. Its concepts are easy to adopt within a rapid period of time. Data and ideas are organized, decisions are made, and the company receives big results with minimal risks. 

Design Thinking is a mindset focused on solutions and not just the problem. When equal thought is given to People, Technology, and Business goals we can uncover truly innovative products.

How it Works for Software? 

The goal is to learn as quickly as possible. By combining 'Design Thinking' with concepts from 'Lean UX' and 'Agile Development' we can minimize waste and maximize viability for the product's health. These graphs showcase an overview of my methodology.

1: Research

Understanding the end-user's desires is crucial to the success of the user experience. Good design comes out of empathy. While "We are not our users", we still need to constantly learn more about the people who use the products we build. This phase represents the foundation for all our work.


2: Plan

Data without any insight isn't that valuable. This phase seeks to begin to cull the noise down into actionable results. By charting and recording we begin to find patterns of behavior that will instruct future solutions. This phase utilizes ideation practices to help us better understand who, how, and what we are solving for.


  • User Stories with Personas

  • User Journey Map

  • Outline the Information Architecture (IA)

  • Sketch Important Ideas

3: Create

This is the testing grounds. Ideas and assumptions are now put into something more tangible toward the finished solution. Internal teams rely on each other to iterate and improve these early designs to make them as strong as possible before they are validated by users.


4: Execute

Once the conceptual aspect of the design has been validated it is time to move into production mode. This phase is a key shift from design to technical-centric activities. Designers will produce a style guide and final assets that refine deliverables that assist engineers in their development efforts. 


5: Measure

Before any software feature is released it needs to be tested thoroughly by both internal and external resources. Setting up Key Performance Indicators also helps us track the effectiveness of our efforts as the product grows. By continuously collecting data and reflecting on past work we can make more informed decisions in the future.


  • Usability Testing

  • User Interviews/Surveys

  • Setup KPI trackers

  • Review and Store Data

And then on to the next iteration...