Design thinking has emerged as a means of solving problems by focusing on the perspective of the customer to better determine the user’s application requirements. A major complaint with the Waterfall System Development Methodology is the difficulty gathering all requirements up front prior to development, making it hard to implement customer change requests later in the development cycle. Alternatively, the Agile Development Methodology allows for constant system revisions and improvements, potentially making it hard to budget and plan for the completion of a system. This paper looks at integrating Design Thinking into the traditional Waterfall and Agile system development methodologies. Using the Design Thinking components of empathize, define, ideate, prototype, and test leads to improvement of both the developer and customer experience.