Hadi Ghanbari , Suchit Ahuja , Bokyung Lee , James Gaskin
{"title":"Who should pay for technical debt? Exploring software professionals perceptions about technical debt accountability","authors":"Hadi Ghanbari , Suchit Ahuja , Bokyung Lee , James Gaskin","doi":"10.1016/j.infoandorg.2025.100589","DOIUrl":null,"url":null,"abstract":"<div><div>Technical debt (TD) highlights the consequences of suboptimal design decisions made during Information Systems (IS) development. Despite reducing IS quality, if taken strategically and managed proactively, TD enables firms to gain a competitive advantage in the short-term. However, if taken without strategic intent and left unresolved, TD can lead to significant costs in the long-term. Previous studies mainly examine TD accumulation at the organizational level and its latent costs to the organization. However, considering the crucial role of individuals in IS development, further research is needed to provide us with a theoretical understanding of TD that is accumulated because of unnecessary shortcuts taken by software professionals without any strategic intent. To explore this costly concern, we interviewed 25 software professionals across industry domains and from all three global regions. Using accountability theory as a lens, we conducted thematic analysis and qualitative comparative analysis to uncover the participants' perceptions of responsibilities and accountability issues associated with the accumulation and management of TD. Our analysis shows that software professionals' perception of TD accountability is influenced by 1) the extent to which prospective and retrospective accountability mechanisms are established in organizations and the way they are followed (i.e., bureaucratically vs. democratically) and 2) the extent to which collective culture emphasizes the importance of ensuring software quality and promotes compliance with quality rules. Thus, we propose TD accountability as a crucial coordination and consensus building mechanism for promoting a quality culture in development teams and facilitating appropriate accumulation and management of TD in organizations. In addition to contributing to IS literature, we provide insights for organizations to coordinate the accumulation and management of TD.</div></div>","PeriodicalId":47253,"journal":{"name":"Information and Organization","volume":"35 3","pages":"Article 100589"},"PeriodicalIF":4.7000,"publicationDate":"2025-08-13","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Information and Organization","FirstCategoryId":"91","ListUrlMain":"https://www.sciencedirect.com/science/article/pii/S1471772725000351","RegionNum":2,"RegionCategory":"管理学","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"Q1","JCRName":"INFORMATION SCIENCE & LIBRARY SCIENCE","Score":null,"Total":0}
引用次数: 0
Abstract
Technical debt (TD) highlights the consequences of suboptimal design decisions made during Information Systems (IS) development. Despite reducing IS quality, if taken strategically and managed proactively, TD enables firms to gain a competitive advantage in the short-term. However, if taken without strategic intent and left unresolved, TD can lead to significant costs in the long-term. Previous studies mainly examine TD accumulation at the organizational level and its latent costs to the organization. However, considering the crucial role of individuals in IS development, further research is needed to provide us with a theoretical understanding of TD that is accumulated because of unnecessary shortcuts taken by software professionals without any strategic intent. To explore this costly concern, we interviewed 25 software professionals across industry domains and from all three global regions. Using accountability theory as a lens, we conducted thematic analysis and qualitative comparative analysis to uncover the participants' perceptions of responsibilities and accountability issues associated with the accumulation and management of TD. Our analysis shows that software professionals' perception of TD accountability is influenced by 1) the extent to which prospective and retrospective accountability mechanisms are established in organizations and the way they are followed (i.e., bureaucratically vs. democratically) and 2) the extent to which collective culture emphasizes the importance of ensuring software quality and promotes compliance with quality rules. Thus, we propose TD accountability as a crucial coordination and consensus building mechanism for promoting a quality culture in development teams and facilitating appropriate accumulation and management of TD in organizations. In addition to contributing to IS literature, we provide insights for organizations to coordinate the accumulation and management of TD.
期刊介绍:
Advances in information and communication technologies are associated with a wide and increasing range of social consequences, which are experienced by individuals, work groups, organizations, interorganizational networks, and societies at large. Information technologies are implicated in all industries and in public as well as private enterprises. Understanding the relationships between information technologies and social organization is an increasingly important and urgent social and scholarly concern in many disciplinary fields.Information and Organization seeks to publish original scholarly articles on the relationships between information technologies and social organization. It seeks a scholarly understanding that is based on empirical research and relevant theory.