Scoping in Consulting Engagements
Standard consulting moves from scoping directly to a statement of work and a delivery timeline.
Two Teams, One Scoped Task
Imagine two consulting teams that have just finished scoping the same piece of work. Both have a clear picture of what the task involves, and both now have to decide what to do next. Scoping is the shared starting point, so the real question is what each team does at the step after it.
What do you think happens?
Both teams have finished scoping the same task. What would you expect the next step to be?
Reveal answer
Standard consulting moves from scoping directly to a statement of work and a delivery timeline. FDE motion asks, in a structured way, whether the scoped task is the most valuable thing to do before delivery begins.
Most people's first instinct is to move toward delivery, with paperwork and a schedule. That instinct describes the standard path, but not the path that defines FDE motion. The difference appears at the very next step after scoping.
The source frames this next step as the feature that separates the two approaches. FDE motion is distinguished from standard solutions consulting by its validation phase. The rest of this article follows the two paths step by step so you can see exactly where they split and why the split matters.
Tracing the Standard Path
Begin with the standard path, since it is the familiar reference point. Scoping happens first. Once scoping is complete, the next step in standard consulting is a statement of work and a delivery timeline. The work moves forward from the scoped task into an agreed plan for delivering it.
Notice what the standard path does not contain. Its step after scoping is about how to deliver the scoped task. The source does not describe this path as stopping to question whether the task is worth doing. The transition from scoping to a statement of work is the direct next move.
Where the FDE Path Diverges
The FDE path begins the same way. Scoping comes first. The difference appears at the next step. In FDE motion, the next step is to ask, in a structured way, whether the scoped thing is actually the most valuable thing to do. The question is not a casual check. It is a deliberate step built into the process.
Read the diagram left to right in each branch. Both branches begin at scoping. The standard branch moves into planning documents. The FDE branch moves into the value question, and only after the signals from that question does it reach the commitment to delivery. The two paths share a starting point and separate at the first step after it.
What the Validation Phase Asks
The source describes how the value question gets answered. It is answered through a small set of activities that produce hard signals, before the team commits to delivery. The validation phase is the stage that carries those activities. Its job is to assess the value of the scoped task before the team moves into delivery.
Comparing the Two Paths Side by Side
Placing the two paths next to each other makes the difference concrete. Both start from scoping. After that, the standard path moves to a statement of work and a delivery timeline, while the FDE path moves to the value question, then to hard signals from validation, and only then to a commitment to delivery.
Worked Example: A Scoped Data Migration
The following illustration is invented for teaching purposes. It is not drawn from the source and does not describe any real engagement. Its only purpose is to let you trace both paths on a concrete scoped task.
Tracing one scoped task down both paths
Two teams have both finished scoping the same task: migrating a customer reporting dataset to a new system. Trace what each team does next.
- 1Standard team after scoping
The team moves directly to a statement of work and a delivery timeline. The next step is about how to deliver the migration.
- 2FDE team after scoping
The team asks, in a structured way, whether migrating this dataset is the most valuable thing to do. This question is a deliberate step in the process.
- 3FDE validation phase
A small set of activities runs and produces hard signals. The source does not specify these activities, so the example does not name them.
- 4FDE commitment
Only after the signals have been gathered does the team commit to delivery. The decision stayed open until that point.
Both teams shared the same starting point at scoping. They separated at the first step after it: the standard team wrote a statement of work, while the FDE team asked the value question and committed to delivery only after validation.
Mistakes When Reading the Two Paths
Common mistake Assuming the step after scoping is the same in both paths
Why it failsThe paths share scoping, but they split at the first step after it. The standard path goes to a statement of work and a delivery timeline. The FDE path goes to the value question.
Do this insteadName the step after scoping separately for each path.
Common mistake Treating validation as a review that happens after delivery has been committed
Why it failsThe source stresses that validation comes before the team commits to delivery. It is a gate, not an after-the-fact check.
Do this insteadPlace validation ahead of the delivery commitment when you trace the FDE path.
Common mistake Listing specific validation activities as if the source named them
Why it failsThe source only says validation is a small set of activities that produce hard signals. It does not list them.
Do this insteadDescribe validation by its structure and purpose, and do not invent a specific list of checks.
Common mistake Concluding that the standard path is careless about value
Why it failsThe source only describes what the standard path does next. It does not say the standard path is wrong to deliver, only that it does not contain the structured value question at that step.
Do this insteadDescribe the standard path by what it contains, and avoid judging it beyond the source.
Practice Tracing a Scoped Task
Take a scoped task of your own choosing, or use a generic one such as a new reporting feature. Write the step that follows scoping on the standard path, then write the step that follows scoping on the FDE path. Finally, state where the two paths diverge and why the FDE path places the value question before commitment.
Hints
- The paths share the scoping step, so start your trace there.
- The standard path's next step is a statement of work and a delivery timeline.
- The FDE path's next step is the value question, answered through validation before any delivery commitment.
- Explain the ordering by asking what can be changed once a commitment already exists.
Key Takeaways
- Standard consulting moves from scoping directly to a statement of work and a delivery timeline.
- FDE motion shares the scoping step, then splits at the next step by asking in a structured way whether the scoped task is the most valuable thing to do.
- The validation phase answers that question through a small set of activities that produce hard signals, and it happens before the team commits to delivery.
- The source does not list the specific validation activities, so they should be described only as producing hard signals.
- Placing the value question before commitment keeps the decision open until the signals have been gathered.