Our software sucks. We're up to our necks in bugs and technical debt, yet we often seem to hit roadblocks explaining things in ways that bring about meaningful change. In this session you'll learn to gather, analyze, and interpret data in order to create effective presentations to communicate quality, technical debt, and other technical matters in ways that tell a compelling story. You’ll master how to communicate effectively with key stakeholders by taking a data-driven approach blended with storytelling techniques to bridge common gaps between development and business stakeholders. We'll cover various architectural and analytical processes that can support the decision-making process, justify paying down technical debt, tips for reducing its accumulation in the future, and focusing on improving our software in the areas that need it most.

This talk was tremendously well-received at CodeMash, StirTrek, and as an online course at Pluralsight for some time. Some of the topics of this talk found their way into my first technical book, Refactoring with C#, though that book is more focused on tactical execution in a specific language.