Paper Type

Complete

Abstract

This study examines how path dependence in differently configured low-code/no-code platforms unfolds. Drawing on 30 interviews across multiple LC/NC platforms, the study reveals that technical and cognitive dependencies intensify through reinforcing mechanisms such as abstraction, opacity, and specialization, while balancing practices partially counteract them. In advanced configurations, dependencies are redistributed, with technical dependencies evolving into cognitive dependencies embedded in routines and mental models. The findings advance LC/NC research by explaining how specific platform characteristics (such as visual modeling, templates, and proprietary abstractions) generate distinct technical and cognitive dependencies. We map how these characteristics interact with organizational practices to shape how developers experience and manage dependency, extending prior LC/NC research beyond adoption and productivity concerns. Second, we reshape classic assumptions in dependency theory by shifting where dependencies occur, proposing a shift from dependency on technical artifacts to a dependency on abstraction and cognitive routines.

Paper Number

1527

Comments

SIG ADIT

Download

Share

COinS
 
Aug 15th, 12:00 AM

Unpacking Path Dependence in Low-Code/No-Code Platforms: Configurations of Technical and Cognitive Dependencies

This study examines how path dependence in differently configured low-code/no-code platforms unfolds. Drawing on 30 interviews across multiple LC/NC platforms, the study reveals that technical and cognitive dependencies intensify through reinforcing mechanisms such as abstraction, opacity, and specialization, while balancing practices partially counteract them. In advanced configurations, dependencies are redistributed, with technical dependencies evolving into cognitive dependencies embedded in routines and mental models. The findings advance LC/NC research by explaining how specific platform characteristics (such as visual modeling, templates, and proprietary abstractions) generate distinct technical and cognitive dependencies. We map how these characteristics interact with organizational practices to shape how developers experience and manage dependency, extending prior LC/NC research beyond adoption and productivity concerns. Second, we reshape classic assumptions in dependency theory by shifting where dependencies occur, proposing a shift from dependency on technical artifacts to a dependency on abstraction and cognitive routines.