UNDOCUMENTED AGREEMENT

When conversations quietly turn into expectations no one formally agreed to.

What this pattern is

A decision is discussed.

It sounds reasonable.
No one objects.

But it’s never clearly documented or confirmed.

Later, it shows up as an expectation.

What this usually looks like

• “We talked about this already”

• “I thought we agreed to include that”

• “Wasn’t that part of the plan?”

• Work gets added without a clear decision

• No one can point to where it was approved

Why this happens

Conversations feel like alignment.

But without documentation, there is no shared reference point.

Each person walks away with their own version of what was decided.

What this causes

• Confusion about what was actually agreed

• Work expanding without visibility

• Tension between teams and stakeholders

Not because people are careless.

Because nothing made the agreement explicit.

First move to stabilize it

Separate conversation from commitment.

If something matters:

👉 write it down
👉 confirm it
👉 make it visible

Clarity doesn’t happen in conversation alone. Join PM Clarity.

[Join here]

← Back to Pattern Library

If this keeps happening, it often turns into Project Story Drift—where different versions of the project start showing up depending on who you ask.
→ See Project Story Drift

This is also how Scope Drift starts—small decisions get treated like agreements, and suddenly the work has changed without anyone naming it.
→ See Scope Drift

One way to stabilize this is to re-anchor to a clear source of truth—because if the agreement isn’t documented, it’s not something the project can reliably execute against.
→ See Contract Source of Truth

If you’re already seeing the impact, this becomes part of Project Stabilization—separating what was actually agreed from what was assumed.
→ See Project Stabilization

This shows up a lot in inherited projects—where decisions were made informally, but you’re now expected to manage the outcome.
→ See Inherited Projects