In large-scale agile development, many important problems are not technical in themselves, yet they have major technical consequences. Unclear roles, weak coordination, poor communication, and inherited ways of working can create non-technical debt: hidden human and organizational conditions that slow teams down, complicate decisions, and undermine system development over time.
 
This presentation shows why non-technical debt matters for IT architects and other practitioners working with socio-technical systems. Based on empirical studies of large-scale agile development, it introduces process, social, and people debt as practical concepts for understanding how human context affects architecture and delivery. The session will highlight how to identify these issues, why they matter even more in an AI-supported development environment, and what practitioners can do to improve collaboration, decision-making, and system design.