From b5d888cc6cc6c02e5939bfabe210b4a8ac921014 Mon Sep 17 00:00:00 2001 From: "editorial-loop[bot]" Date: Mon, 18 May 2026 16:21:16 +0000 Subject: [PATCH] blog(draft): The Person Who Scoped It Left Before the Build Started --- .../2026-05-18-person-who-scoped-it-left.md | 77 +++++++++++++++++++ 1 file changed, 77 insertions(+) create mode 100644 content/blog/2026-05-18-person-who-scoped-it-left.md diff --git a/content/blog/2026-05-18-person-who-scoped-it-left.md b/content/blog/2026-05-18-person-who-scoped-it-left.md new file mode 100644 index 0000000..0d495a2 --- /dev/null +++ b/content/blog/2026-05-18-person-who-scoped-it-left.md @@ -0,0 +1,77 @@ +--- +title: "The Person Who Scoped It Left Before the Build Started" +date: 2026-05-18 +draft: true +pillar: "The Optimism Cascade" +tags: [] +linkedin_copy: | + The most expensive knowledge loss in a mid-market commerce project is not a server crash or a failed deployment. It is the quiet departure of the person who understood why the SOW was shaped the way it was. + + Pre-sales architects and solution consultants accumulate context during discovery that never makes it into the scope document. They heard the client explain why the ERP integration works a certain way. They know why the CDP was deferred to phase two. They understood the trade-offs that were made to hit a number. That reasoning shaped every line of the scope. + + Then the deal signs, and they move to the next deal. Normal. Expected. Also where the damage starts. + + The delivery team inherits a document that looks complete. They build a plan from it. They ask execution questions: how many sprints, which environment, what order. They do not ask intent questions, because they do not know what they do not know. + + Six weeks later, someone asks: "Why did we scope it this way?" Nobody in the room has the answer. The person who had it is three accounts away. + + This is not a process failure. It is a structural feature of how agencies staff work. The person who wins the deal is incentivized to move on. The person who delivers the deal is incentivized to execute what is written. The gap between those two incentives is where projects quietly break. + + The fix is a 30-minute recorded artifact before the pre-sales person rolls off. Three questions: What did the client tell us that is not in the SOW? What trade-offs did we make to hit the budget? What does the client care about most that you will not find in any requirements document? + + Almost nobody does it. There is no incentive. And the merchant does not know to ask for it, because they assume the agency is a single continuous entity. It is not. It is a sequence of people, and the seams are where projects lose their spine. + + Full post: {{url}} +--- + +Every mid-market commerce project has a moment where someone says: "Why did we scope it this way?" + +Nobody in the room knows. The person who shaped the SOW is gone. Not fired. Not disgraced. Just moved on. Promoted, rolled to another account, or quietly let go in a restructuring that had nothing to do with your project. They left behind a document. They did not leave behind the reasoning. + +This is the most common silent failure in mid-market implementations, and it almost never gets named. + +## How the gap forms + +In most agencies, the person who runs the sales cycle is not the person who runs the delivery. This is normal. It is also where the damage starts. + +During the sales cycle, the pre-sales architect or solution consultant accumulates context that never makes it into the SOW. They sat through the discovery calls. They heard the client explain why the ERP integration has to work a certain way, why the loyalty program cannot be touched until Q3, why the CEO cares about one specific reporting metric more than anything else on the roadmap. That context shaped every line of the scope. It determined what was in, what was out, and what was deferred. + +The SOW captures the what. It almost never captures the why. + +When the project kicks off, a delivery team receives the document. They read it. They build a plan from it. They ask clarifying questions, but those questions are about execution: "How many sprints for the PDP redesign?" Not about intent: "Why did we defer the CDP integration to phase two when the client's entire personalization strategy depends on it?" + +The answer to that second question lived in the head of someone who is no longer on the project. + +## Why the handoff fails even when people try + +This is not a laziness problem. Most agencies have a handoff process. There is a kickoff meeting. There are shared documents. Sometimes there is a recorded walkthrough. + +The problem is structural. The pre-sales person's job is to win the deal. Once the deal is signed, their incentive is to move to the next deal. Their calendar fills up. Their availability drops. The handoff happens in a single meeting, or a single document, and then they are gone. + +What gets lost is not the obvious stuff. The obvious stuff is in the SOW. What gets lost is the negotiation history, the things the client pushed back on, the trade-offs that were made to hit a budget number, the risks that were acknowledged verbally but never written down. The delivery team inherits a plan that looks complete but is missing its spine. + +I have watched delivery teams execute a scope perfectly and still produce the wrong outcome because they did not know why a particular decision was made during the sales cycle. They followed the letter. They missed the intent. + +## What this costs + +The cost is not dramatic. It is slow. The delivery team makes reasonable decisions that contradict unstated assumptions. They sequence work in an order that made sense on paper but ignores a dependency the pre-sales architect understood from a conversation that was never documented. They build a feature the client did not actually want because the SOW described it in language that was a compromise, not a specification. + +By the time the client notices, the budget is partially spent. The conversation shifts from "let's build the right thing" to "who is going to pay for the rework." Trust erodes. The agency looks incompetent. The client feels unheard. Both sides are acting in good faith. The failure happened weeks or months earlier, in a gap that neither side created intentionally. + +## The fix is boring and almost nobody does it + +The fix is a recorded artifact, not a meeting. Before the pre-sales architect moves on, they should produce a short document or video that answers three questions: + +1. What did the client tell us that is not in the SOW? +2. What trade-offs did we make to hit the budget, and what breaks if those trade-offs are unwound? +3. What does the client care about most that you will not find in any requirements document? + +This takes 30 minutes. It saves months. Almost nobody does it because there is no incentive. The pre-sales person is already on the next deal. The delivery team does not know what questions to ask because they do not know what they do not know. + +The merchant could demand this artifact as a condition of signing. They almost never do, because they do not know this gap exists. They assume the agency is a single continuous entity. It is not. It is a sequence of people, and the seams between them are where projects quietly break. + +## The pattern + +If you are a merchant about to sign a six- or seven-figure SOW, ask one question before you sign: "Will the person who shaped this scope be available to the delivery team for the first 30 days of the project?" If the answer is no, or if the answer is a vague "they'll be available if needed," you have a gap. That gap will cost you more than any line item in the scope. + +The person who scoped it understood your project. The document they left behind does not. \ No newline at end of file