| Note | Day | Purpose |
|---|---|---|
| 1 | Wed | Article launch pointer |
| 2 | Fri | Standalone insight (scoping language) |
| 3 | Sat | Anchor phrase quotable |
New piece live today.
A consultant lost two clients in the same quarter. The first engagement she stretched — effort-based work spread across six months when it needed eight focused weeks. The second she compressed — compounding work promised in 60 days when the outcome needed six months to land.
Both clients were right to leave. Both scoping conversations were wrong for the same reason.
The piece has three interactive tools: a clock check for your last engagement, a phrase decoder for your scoping language, and a simulator where you scope a fictional project and get a verdict.
Your Scoping Conversation Is Setting the Wrong Clock
[article link]
"You should see results within 90 days."
For an operations manual, that's honest. The work compresses with effort. Ninety days is conservative.
For a market repositioning, that's a promise the physics can't keep. Positioning compounds through accumulated credibility. Ninety days is when the seeds get planted — not when they bloom.
The most professional-sounding phrases in your scoping conversation might be the ones embedding the wrong timeline. The words don't change. The transformation type behind them does.
I wrote about this (with an interactive decoder for 8 common scoping phrases): [article link]
A $32,000 engagement delivered every deliverable on time. The client terminated at day 60.
The scope was perfect — on the wrong clock.
Every transformation runs on one of three clocks. Most scoping conversations ignore which one. That's the gap between solid work and frustrated clients who can't name what went wrong.
[article link]