Serving Time Downstream
The people who write scopes that survive have almost always been on the receiving end of one that didn't. It is the least discussed qualification in the profession and close to the most reliable.
Everything in Level 1 can be learned from a book, this one included — except the instinct that stops you writing a sentence you will not be there to defend. That instinct is not taught. It is acquired by being the person who inherits the consequence: the service delivery manager, the implementation lead, the onboarding engineer, the account's technical escalation point. Someone who has spent a year in one of those seats prices differently, writes differently, and is markedly harder to pressure into vagueness by a colleague who wants the deal signed this quarter.
| What downstream teaches | Where the lesson actually lands |
|---|---|
| What an underestimate costs | Being the one doing a fourteen‑hour job that was sold as two, and explaining the overrun to a customer who was quoted the two |
| Why "the other team will document it" is a lie | Running an onboarding against an undocumented estate, where every ticket becomes an archaeological dig and first‑call resolution collapses in week one |
| Why exclusions matter more than inclusions | Inheriting a bespoke line‑of‑business application nobody scoped, supported anyway because the customer assumed it was covered |
| Why the narrative outranks the paperwork | Sitting with a customer who was told something different in a meeting you weren't in, and discovering that what they were told is what you are being measured against |
| Why a solution review is not bureaucracy | Being handed eight hours for a job that takes two days, on a site nobody visited |
| Which promises are cheap and which are expensive | Watching a single throwaway commitment in a pre‑sales meeting turn into a three‑year support obligation with no revenue attached to it |
If you don't have the scars, go and get them deliberately
This is not an argument that you must have done a delivery tour before you are allowed to do this job. It is an argument that the gap is real, closeable, and almost nobody bothers to close it. Each of these costs a day or less:
What you are buying with that day is not knowledge — you could be told all of it in ten minutes. It is the flinch: the small involuntary reaction when you are about to write "configuration of the environment" and something in you objects.