This subtopic involves the recognition that the complexity of a system, regardless of its learning efficacy, is a primary barrier to adoption. Administrative friction is the mental and logistical effort required for those supporting learning (like faculty or trainers) to deploy and manage a new tool or program.
Application Example: A high-friction solution might require teachers to use a novel, isolated data set, log into a new tool, and manage separate user accounts. The learning engineering practitioner mitigates this friction by prioritizing solutions that integrate seamlessly with existing Learning Management Systems (LMS) and other learning platforms, and minimize the need for extra training or manual data reconciliation. The learning engineering team uses human-centered design and iterative agile methodologies for design and improvement of a tool’s administrative interfaces, just like for developing the learner experience.