The polite-disaster manual
Scope Creep
Anatomy of a slow-motion disaster
For the PM who can feel the work changing before anyone is ready to admit the project has changed.
Scope creep rarely kicks down the door. It arrives as a reasonable sentence, a harmless clarification, a quick addition, a “while we’re already here” request, and a room too tired to make the tradeoff visible.
This book lives in the dangerous early zone before formal change control wakes up. It shows how ambiguity becomes work, how politeness becomes permission, and how good PMs get buried carrying decisions no one made out loud.
Read it before the next “small ask” starts looking around for load-bearing walls.
Get the book
PDF download.
PDF $9.99
Not sure yet?
Read the free sample first.
If the voice lands, the book belongs on your desk.
A field manual for spotting the “small ask” before it becomes a weekend.
Why this book works
Most scope advice starts after the change has already become official.
Scope Creep starts earlier.
It lives in the dangerous zone where the request still sounds small, the tradeoff has not been named, the deadline has not moved, and everyone is pretending the project can simply absorb “one quick thing.”
That is where the book earns its place.
It does not treat scope creep as a paperwork problem. It treats it as a project survival pattern — a slow chain of polite asks, vague assumptions, helpful intentions, tired approvals, missing tradeoffs, and quiet rework that changes the project before anyone admits the project has changed.
This is the book’s core move: it gives project managers a small-ask early-warning system.
You are not just reading stories about runaway scope. You are learning how to spot the moment a harmless request starts looking around for load-bearing walls.
The book trains you to notice the early warning signs before the change log wakes up:
“Can we just add one small thing?” The project has been invited to absorb a decision without a tradeoff.
“It should not take long.” Someone has estimated the effort using optimism and no calendar.
“While we’re already doing this...” A new requirement has entered the room wearing a fake moustache.
“I assumed that was part of it.” The scope was defined. The approval was inferred. The work arrived anyway.
“Let’s not overcomplicate this.” The consequence has noticed the conversation and is being asked to leave.
That is the value of the book. It gives project managers language for the dangerous early zone where scope creep is still pretending to be cooperation.
It is funny because the requests are real.
It is useful because the hidden work behind them is real.
And once you learn to hear the small ask, scope conversations start sounding very different.
This is the book for catching the polite sentence before it becomes hidden work, weekend recovery, and another project plan quietly pretending nothing changed.
Lines you may want to underline
A few quick hits from the book’s operating system: the kind of lines that make PMs laugh first, then quietly remember a meeting.
“Scope creep rarely arrives looking dangerous. It arrives politely.”
“If the work changed, name it.”
“A document can name the work once. It cannot defend that meaning every time someone says just.”
Field tool from the book
How the small ask becomes work
Scope creep becomes expensive while it still sounds reasonable. This is the path from harmless sentence to hidden delivery obligation.
What project people recognize in these pages
PMTales books are built to land fast: the laugh first, the wince second, and the better language after that.
“I have lived this exact small ask, right down to the polite wording.”
“The book makes scope drift visible before it becomes a formal crisis.”
“Useful language for saying no without sounding like the person who hates helpful ideas.”
This belongs on your desk if
- You have accepted a small change and later discovered it had cousins.
- You keep seeing work added through implication rather than decision.
- You need language that names drift without sounding difficult.
- Your project’s real scope is being rewritten in emails, side conversations, and tired nods.
Inside the slow-motion disaster
- Why reasonable people keep rewriting the work without calling it a change.
- The language that lets everything through: small, quick, obvious, harmless, strategic.
- How assumed approval turns into delivery obligation.
- Scripts for turning assumptions back into decisions before the project absorbs them.
D.B. Trench
D.B. Trench writes PMTales for the project managers, delivery leads, analysts, and quiet realists who have watched polished status language drift away from the work underneath it. The books turn familiar project chaos into sharp stories, field language, and practical survival tools.
Questions before you buy
Get the book before the next meeting proves it was not satire.
For the PM who can feel the work changing before anyone is ready to admit the project has changed.
Scope Creep
Anatomy of a slow-motion disaster
PDF $9.99
Home · Start Here · Blog · Armory · Academy · Books · Origins · Dispatch · Free Resources © 2026 PMTales