원문정보
초록
영어
Digital platforms have gained prominence across various domains and industries by offering generativity and flexibility. In contrast to a vast number of benefits brought by digital platforms, the growing problem of digital debt accrual while embedding a digital platform into an organization’s digital infrastructure and associated work processes has attracted increasing organizational concern and recent academic attention. Drawing on technology affordance theory and paradox theory, this paper examines how the affordances and constraints of a digital platform are leveraged to contribute to gradual digital transformation. The findings of this in-depth case study identify different types of affordances that foster digital transformation: minimum viable product development, cloud-based collaboration, and low-code/no-code development. This study also identifies the constraints of a digital platform, which are different types of digital debt: design debt, capability debt, and technical debt, that may hinder digital transformation. This study discusses the paradoxical tensions that arise from the affordances and constraints of a digital platform and the potential paradox management strategies to navigate those tensions and achieve gradual digital transformation. This research provides insights for scholars, managers, and organizations to better understand the dynamics of leveraging digital platforms in facilitating digital transformation.
목차
Ⅰ. Introduction
Ⅱ. Conceptual Background
2.1. Technology Affordances and Constraints Theory
2.2. Digital Platform, Affordances, Constraints, and Digital Debt
2.3. A Paradox Lens for Understanding Digital Debt Accrual
Ⅲ. Research Methodology
3.1. Data Collection
3.2. Data Analysis
Ⅳ. Findings
4.1. Affordance 1: Minimum Viable Product Development
4.2. Digital Debt 1: Design Debt
4.3. Paradoxical Tension 1: ImprovedCustomer Experience vs. Fragmented Internal Operations
4.4. Potential Paradox ManagementStrategies for Tension 1
4.5. Affordance 2: Cloud-Based Collaboration
4.6. Digital Debt 2: Capability Debt
4.7. Paradoxical Tension 2: ContestedSystem Ownership vs. Long-TermIntegration Costs
4.8. Potential Paradox Management Strategies for Tension 2
4.9. Affordance 3: Low-Code/No-Code Development
4.10. Digital Debt 3: Technical Debt
4.11. Paradoxical Tension 3: Speed of Innovation vs. Long-Term Scalability
4.12. Potential Paradox Management Strategies for Tension 3
Ⅴ. Discussion and Conclusion
5.1. Theoretical Implications
5.2. Practical Implications
Ⅵ. Conclusion
