The Thursday Dispatch Issue #002 - “It Should Be Simple” Is Not an Estimate
- 7 days ago
- 2 min read
D.B. Trench - Top posts from this week
“It Should Be Simple” Is Not an Estimate
The story, the practical guide, and one sentence to use before a “simple” change quietly eats the plan.
Hi —
This is your Thursday Dispatch from the project front lines, where a small change has just walked in carrying a confident estimate from someone who does not have to deliver it.
This week’s warning phrase:
“It should be simple.”
Lovely.
Optimistic.
Completely unsupported by evidence.
Sometimes the thing really is simple. Sometimes the code change takes five minutes, everyone updates one field, the test passes, the release continues, and somewhere a project manager briefly believes in sunlight again.
But “simple” has to earn the title.
It does not get it for free because someone said the sentence confidently near a slide deck.
Scope Creep Month on PMTales
We are in the middle of a four-week field series on small asks, soft agreements, and the quiet rewrite of the plan.
Scope creep is this month’s specimen. After this, the field reports move into meeting fog, ownership drift, stakeholder pressure, status theatre, and the other wildlife of modern delivery.
This Week on PMTales
Missed the week’s field reports? Start here.
Read the story first: The Five-Minute Change That Took Three Weeks
A late label change. One “just wording” request. A data-definition argument. Reporting. Training. Testing. Approvals. Three weeks gone.
Use the practical guide next: Why Small Scope Changes Create Big Project Damage
The field manual version: why small changes should be judged by what they touch, not how quickly someone describes them.
The Phrase That Means Trouble
“It should be simple.”
What it sounds like:
“This is probably quick, and we should not overcomplicate it.”
What it often means:
“I am estimating the visible part and hoping the invisible parts behave themselves.”
That is not an estimate.
That is a weather forecast made indoors.
One Sentence to Steal
Use this when someone says a change should be simple:
“It might be. Let’s confirm what it touches before we treat it that way.”
That sentence does not reject the request. It simply asks the project to earn the word simple.
From the Armory: Scope Defense Bundle
If the small changes are already piling up, the Scope Defense Bundle gives you the practical field tools for handling scope pressure without sounding like you personally declared war on progress: Start Here Guide, Weekly Scope Review Sheet, Change Impact Snapshot, Boundary Scripts Pack, Escalation Brief Template, Scope Drift Tracker, Tradeoff Log, and Complete Print Workbook.
Fillable PDFs · Printable PDFs · Excel trackers · Complete workbook
Story Route
Prefer the longer field tale? The Scope Creep book is the story-led companion for this kind of slow-motion project disaster: small asks, soft agreements, and harmless language rewriting the work.
Next week in the Dispatch:
The phrase that turns unclear ownership into everyone’s problem.
It usually starts with:
“The team will handle it.”
Pack snacks.
— D.B. Trench
Comments