PMI Global Summit 2026 speaker

The Silent Handshake

Agreement is not alignment. Approved scope can still carry assumptions no one validated.

The Silent Handshake is an original diagnostic framework for ERP and Workday delivery failure, built from 19 years of observing how agreements on paper quietly separate from delivery.

Explore the framework About Pradeep
A full breakout room at PMI Global Summit 2026 as Pradeep Billa presents four questions for uncovering hidden assumptions
Detroit · October 2026 Turning the framework into four questions project leaders can run before scope locks. Download the two-page field guide ↓

“ERP implementations don’t fail within teams. They fail between them.”

The Silent Handshake identifies a repeatable failure pattern: in ERP and Workday implementations, delivery failure originates between teams - at agreement and handoff points - not inside isolated technical tasks. Three diagnostic gaps explain how the pattern forms. Each creates the conditions for the next. The failure is sequential — and the handshake was never confirmed.
Diagnostic Framework

The Silent Handshake

Three failure gaps. Sequential and cumulative. Each creates the conditions for the next. Click any element to explore.

Before Decisions

Assumption Gap

When Before decision is made
Cause Implied logic, never surfaced
Visible Invisible until failure
Explore →
After Decisions

Rationale Gap

When After decisions are made
Cause Decision rationale never captured
Visible When a change request reopens a settled decision
Explore →
After Implementation

Transition Gap

When During team handoff
Cause Information lost in transfer
Visible At transfer point
Explore →
Necessary and sufficient.
Remove any one — divergence reappears.
Handshake Closure Conditions

The test is not artifact delivery. The test is whether the receiving party can demonstrate transferred understanding.

Explore →
Closure conditions
01
Assumption Gap closed
Co-authored assumption log captures unstated logic before configuration begins
Explore →
02
Rationale Gap closed
Every significant decision carries a rationale field; a new team member can explain a workaround without asking the original implementer
Explore →
03
Transition Gap closed
Operations can answer "why does this work this way" for high-risk areas without calling the implementer
Explore →

Diagnostic signal

“Agreement without anchoring is temporary alignment. Temporary alignment guarantees divergence.”
Field Evidence

Three Gaps. Three Evidence Patterns.

Anonymized implementation patterns drawn from direct observation. These are not the framework's use cases. They are the kinds of delivery failures it helps diagnose before they compound.

Assumption Gap
Context
Late-stage Workday HCM configuration, after design sign-off. Two teams operating on an agreed scope document.
Failure Pattern
Configuration built against org structure defined at project initiation. An internal restructuring, completed two months earlier, was not communicated. Both teams had signed off on the same scope. The assumption that org structure was stable through go-live was never surfaced.
Diagnostic Gap
No documented assumption tying org structure stability to the configuration design. The work was technically sound. The premise it depended on was invisible.
Practical Consequence
Full reconfiguration required six weeks before go-live. The delay did not originate in the change itself — it originated in the assumption never being named at the agreement point.
Rationale Gap
Context
Multi-phase ERP implementation, post-design-sign-off build phase.
Failure Pattern
Implementation team made daily configuration decisions — workarounds chosen, standard functionality bypassed, trade-offs accepted. The reasoning was never captured. What got documented was what was done, not why.
Diagnostic Gap
No rationale field on any significant configuration decision. A team member who joined after go-live could not explain why a specific workaround existed without finding the original implementer.
Practical Consequence
Every change request reopened decisions nobody remembered making. Technical debt accumulated not in the code but in the absent reasoning behind it.
Transition Gap
Context
Multi-phase Workday deployment, discovery-to-design handoff between two separate teams.
Failure Pattern
Discovery produced complete deliverables. Design received them. Three key configuration decisions had supporting rationale — alternatives considered, criteria used — that was never recorded. The design team made rational choices from what they inherited. Two contradicted earlier decisions for reasons absent from the handoff.
Diagnostic Gap
Handoff artifacts captured outputs, not decision rationale. No mechanism existed to distinguish load-bearing constraints from adjustable starting points.
Practical Consequence
Contradiction identified in a late design review. Downstream dependencies had already been built. Redesign required revisiting three prior deliverables.
Framework Applied

How the Framework Has Been Applied

Application contexts from direct implementation practice. Platform-agnostic — field-tested across Workday, Oracle, and PeopleSoft deployments.

Assumption Gap  ·  Workday HCM
Context
Enterprise Workday HCM deployment. Assumption Anchoring Protocol applied at scope sign-off — before configuration began.
Application Point
Co-authored assumption log completed with client HR lead. Organizational structure stability identified as an unverified load-bearing assumption before any configuration dependency was built against it.
Outcome
Assumption owner raised a pending org restructure six weeks before go-live. Configuration adjusted while the dependency was still adjustable. No full rebuild required.
Rationale Gap  ·  Oracle Global HR Cloud
Context
Multi-country Oracle Global HR Cloud deployment. Decision Rationale Protocol applied throughout the build phase across all significant configuration decisions.
Application Point
Every significant workaround and design exception captured a rationale block at the moment of decision. A new team member joined mid-project, after key configuration decisions had been made.
Outcome
New team member operationally productive within one week. No backwards archaeology. Every decision traceable without locating the original implementer.
Transition Gap  ·  Discovery → Design
Context
Multi-phase ERP implementation with two separate teams at the discovery-to-design boundary. Handoff Verification Protocol applied before design team proceeded.
Application Point
Design team demonstrated comprehension of three load-bearing constraints from discovery before handoff was confirmed. Two constraints were not transferable from artifacts alone — they required explicit verbal transfer and verification.
Outcome
No contradictions identified in design phase. Constraints that would have been invisible in an artifact-only handoff were verified before downstream build dependencies were created.
All Three Gaps  ·  PeopleSoft Migration
Context
Legacy PeopleSoft HCM to Workday migration program. Distinct discovery, design, and build teams across an extended delivery timeline.
Application Point
All three protocols applied at each major phase boundary. Assumption logs, rationale fields, and handoff verification records maintained across the full program lifecycle — not retroactively applied at go-live.
Outcome
Operations team inherited full configuration context at go-live. Routine operational questions answerable from documentation without escalating to the implementation team.
Operational Impact

What the Framework Enables

The Silent Handshake is a diagnostic instrument. These are the practitioner-level use cases it is designed to support.

01
Identify divergence earlier. Locate where delivery and intent separated, at the agreement point or the handoff before the gap compounds into rework.
02
Reduce rework caused by misaligned interpretation. Anchor intent before execution begins. Work built on anchored agreements is less likely to require reconstruction when teams later compare what was meant with what was built.
03
Prevent scope ambiguity from accumulating. Name what is included, what is excluded, and what must be true. Ambiguity removed at the agreement point does not reappear at go-live.
04
Preserve decision rationale across handoffs. Transfer context, not just outputs. Receiving teams inherit the reasoning behind inherited constraints instead of reverse-engineering them later.
05
Create explicit alignment at agreement points. Convert verbal alignment into anchored documentation at the moment shared intent still exists before it begins to diverge in silence.
The Work

A Growing Body of Work

Each piece is a standalone contribution to implementation practice. Articles appear here when published.

The Silent Handshake: Why ERP Deliverables Break Between Teams, Not Within Them

ERP failure is not a technical event — it's an organizational one. This article names the invisible space between teams and frames the three gaps that define it.

LinkedIn · Towards AI Towards AI

The Documentation Gap: Why Divergence After Agreement Is Inevitable Without Anchoring

Misalignment occurs after agreement, not because of poor communication, but because implicit expectations were never converted into written artifacts before execution began. Drawing from 19 years of ERP experience, this article introduces anchoring as the intervention that prevents post-decision divergence.

PM World Journal PM World Journal · LinkedIn

More articles publish as the framework develops. Follow on LinkedIn — linkedin.com/in/billapradeep

Start a conversation

Have something in mind?

For speaking engagements, collaborations, advisory work, media enquiries, or a thoughtful conversation about implementation practice, send a note. I read every message.

Thank you. Your message has been sent, and I’ll be in touch soon.

Your details are used only to reply to this enquiry.