Understanding the Three-Phase Framework

Imagine you have been asked to take a customer problem from a vague request all the way to a working system that people rely on every day. Someone has to decide what the job actually is. Someone has to prove the result is good enough. Someone has to get the result running in the customer's real environment. The practical question is whether one person should carry all of that, or whether the work should be split among several people.

The three-phase frame is the tool that makes this question easier to think about. It breaks the work into three named stretches and lets you see what each stretch demands. The rest of this article traces the frame step by step, then uses it to judge who should own which stretch.

The frame divides the path from a vague request to a working system into three phases that run in order: scoping, validation, and delivery. Scoping comes first and settles what the job actually is. Validation follows and tests whether the result is good enough. Delivery comes last and gets the result running in the customer's real environment.

The frame is about what each stretch demands, not only about the calendar. When you know which phase you are in, you know what questions to ask, what evidence to gather, and what counts as finished. That is why the frame is practical at the level of a single task as well as at the level of a whole project.

The source gives each phase a distinct skill profile, and the easiest way to hold them together is to compare them side by side. Scoping is heavy on Echo skills. Validation is heavy on Delta skills, with a strong eval mindset. Delivery is also heavy on Delta skills, with deployment, integration, and operational strength. The labels Echo and Delta are used in the source as names for skill groupings, and this article uses them exactly that way without expanding on them further.

Notice the pattern. Scoping sits on its own in the Echo grouping, while validation and delivery both lean on Delta skills but emphasize different parts of that work. Validation asks whether the result holds up under an evaluation mindset. Delivery asks whether it runs reliably once it is inside the customer's systems. Keeping these emphases separate is what lets you tell which phase a task belongs to when it is unclear.

The source offers a hypothetical project to trace through the frame one step at a time. A logistics company wants a system that flags delayed shipments. At each stage, ask what kind of work is happening. The walkthrough below is an original illustration built on the phase definitions above.

A frame is useful in two different settings, and the source treats them together rather than as separate ideas. The first is the everyday work itself. Knowing your current phase tells you which questions to ask, which evidence to collect, and when the stretch is finished. The second is organizational. When a group needs to discuss who does what, a shared set of phases gives everyone the same vocabulary. A team that says a task is still in validation is communicating something precise.

The source is measured in its answer to the opening question. A single FDE can sometimes cover all three phases. Still, the source concludes that a small team with role differentiation is often the better arrangement. The reasoning follows from the skill profiles: scoping, validation, and delivery each draw on a different emphasis, so one person who is strong in one area may be thin in another.

Judging between the two comes down to whether one person's skill profile covers the emphasis of every phase the project needs. When it does, a single practitioner can carry the work. When one phase needs a skill profile that the person lacks, role differentiation becomes the stronger arrangement. The source does not provide a fixed headcount rule, so the judgment depends on the specific work in front of you.

The source notes that different phases support different pricing structures. It states that this topic will be taken up later, in Chapter 17, so this article does not develop it. The link is still worth noticing: because each phase has its own kind of work, the phases are a natural place to think about how that work might be charged for. You should expect the detail to arrive in the later chapter rather than here.