The Documentation Gap

Why Divergence After Agreement

Is Inevitable Without Anchoring

COMMENTARY

By Pradeep Billa                                                                       

San Antonio, Texas, USA

Abstract

Existing project failure frameworks — from PMI’s governance model to McKinsey’s execution model to the Standish Group’s CHAOS Report — locate failure in breakdown: breakdown of process, alignment, or communication. This article introduces and defines a distinct failure category they do not capture: the Documentation Gap. The Documentation Gap describes misalignment that occurs after agreement, not because of poor communication, but because implicit expectations were never converted into written artifacts before execution began. Observed consistently across dozens of ERP implementations over 19 years — in Workday, PeopleSoft, and Oracle environments — the Documentation Gap surfaces two to six weeks after the decision point, at delivery review. The article distinguishes the Documentation Gap from adjacent failure types, presents three cross-platform case studies demonstrating its mechanism, situates it within the Silent Handshake Framework alongside the Transition Gap and Assumption Gap, and identifies anchoring — a four-primitive discipline of explicit scope, assumptions, exclusions, and definitions — as the only intervention that closes it. Agreement without anchoring is temporary alignment. Temporary alignment guarantees divergence. The only control point is the moment of agreement.

Keywords:    ERP implementation, project failure, documentation gap, Silent Handshake Framework, anchoring, scope management, Workday, PeopleSoft, implementation risk, enterprise technology

Introduction

Project failure literature has a consensus explanation.

PMI frames failures as governance breakdowns. McKinsey frames them as execution failures. The Standish Group measures them in cost and schedule overruns. All three are correct about what they measure. None of them explain the failure mode that accounts for a disproportionate share of rework, eroded trust, and delivery misalignment in enterprise implementations.

The failure that happens after the decision is made. After both parties agreed. After the meeting ended with everyone nodding.

That failure has a name. It is the Documentation Gap. It is not a subset of communication failure. It is not scope creep. It is a distinct failure category, operating through a mechanism that existing frameworks do not isolate because they are not looking in the right place.

And it is not a risk. It is an inevitability, unless one specific act is performed at the moment of agreement.

More…

To read entire article, click here

How to cite this article: Billa, P. (2026).  The Documentation Gap: Why Divergence After Agreement Is Inevitable Without Anchoring, commentary, PM World Journal, Vol. XV, Issue VI, June.  Available online at https://pmworldjournal.com/wp-content/uploads/2026/06/pmwj165-Jun2026-Billa-The-Documentation-Gap.pdf

About the Author

Pradeep Billa

San Antonio, Texas
USA

Pradeep Billa is a senior enterprise ERP practitioner with 19 years of implementation experience across Workday, PeopleSoft, and Oracle HCM environments. He holds Workday Pro HCM, PMP, and PMI-ACP certifications. The Silent Handshake Framework is his original methodology for diagnosing structural failure in enterprise technology implementations. Pradeep is based in San Antonio, Texas, USA.  He can be contacted at www.silenthandshake.com