Information technology departments often focus conversations around “technology debt” on the need to regularly replace and update hardware and software infrastructure. However, there is another crucially important, yet often overlooked, component of technology debt – knowledge debt. Knowledge debt refers to the gap between individual knowledge and organizational knowledge about how technology systems are configured, deployed, and managed within a specific environment. When new technologies are implemented, typically individual contributors take responsibility for deployment based on their personal expertise. Over time though, those individuals’ undocumented understandings and insights into the how technology works becomes "knowledge debt" if they are not effectively converted into organizational knowledge. This knowledge debt poses huge risks as refresh projects and personnel changes occur. If individual knowledge has not been mapped to organizational systems and processes,...