Reading the Drift: A Practitioner Framework for the Distance Between an Organisation's Stated and Lived Systems

Writers commonly describe an organisation as though it ran on a single system, yet practitioners leading scaled delivery work inside two at once. One of them, a Stated System, shows up in org charts, written processes, planning cadences, and reported metrics. The other, a Lived System, covers where decisions actually get made, how priorities really get set, who holds which knowledge, which calendars set the pace of work, and which channels carry reliable information. This paper introduces a practitioner framework, the Drift, which defines the distance between these two systems and sets out a way to read that distance instead of trying to erase it. Drawing on Argyris and Schön’s contrast between espoused theory and theory-in-use, and on Pfeffer and Sutton’s knowing-doing gap, the framework narrows a general organisational phenomenon to scaled engineering delivery and turns it into something a leader can apply. Three diagnostic questions drive the method: what the Stated System prescribes, what the Lived System does, and who pays for the gap. Naming whoever pays converts an abstract structural feature into an actionable leadership decision. The paper places the Drift within scaled agile practice, traces how it accumulates across a program increment through side doors, dependency slips, validation queues, and status theatre, and shows its use in status reviews, escalations, retrospectives, and roadmap interpretation. This contribution stays conceptual and experience derived, with empirical validation still ahead, and the closing sections set out limitations and directions for that work.