6.4 Pace, Multimodal Delivery & Landing Points

6.4 Pace, Multimodal Delivery & Landing Points

[!NOTE] A vocabulary-dense section: Several of the terms below are defined in the MSP glossary and are examined at recall level. Learn the distinctions precisely — particularly capacity versus ability, and tranche versus landing point.

---

Pace, Organizational Capacity, and Organizational Ability

Pace is the rate at which a programme introduces change into the organization. Pace is a governed choice, not a by-product of how fast projects happen to finish: the programme board decides how quickly the business will be asked to absorb new ways of working.

Two distinct constraints bound the achievable pace, and the exam frequently tests the difference:

• Organizational capacity — the amount of change the organization can take on at a given time, alongside continuing to run business as usual. Capacity is a question of volume: available management attention, staff time not already committed, budget, and operational headroom.
• Organizational ability — how well the organization can absorb and sustain change: its skills, change maturity, prior experience, leadership strength, and cultural readiness.

An organization can have plenty of capacity and poor ability (lots of spare staff time but no experience of transformation), or high ability and no capacity (a very capable team already fully committed to three other programmes). Both must be assessed, and the lower of the two sets the ceiling.

---

Tranches, Landing Points, and Incremental Progression

A tranche is a structured grouping of projects and other work that delivers a step change in capability. Tranches are separated by governed review boundaries at which the programme's continuing justification is confirmed before further investment is committed.

A landing point is the stable operating state the organization occupies at the end of a tranche. The distinction matters: the tranche is the work; the landing point is the state you are standing in when that work stops. A properly designed landing point means:

• Business as usual can run safely and indefinitely from that state, even if the programme were stopped there.
• Some benefits can be measured, because outcomes have actually been achieved rather than merely enabled.
• The organization has a coherent operating model — not a half-migrated one where two incompatible processes run side by side without a plan.

Incremental progression is the resulting pattern: the organization advances towards the target operating model through a series of landing points rather than a single large transition. Each landing point is an intermediate state of the target operating model.

  CURRENT STATE                                              TARGET STATE
       │                                                          │
       ▼                                                          ▼
   ┌────────┐   Tranche 1   ┌──────────┐   Tranche 2   ┌──────────┐   Tranche 3   ┌────────┐
   │  AS-IS │ ────────────► │ LANDING  │ ────────────► │ LANDING  │ ────────────► │ TO-BE  │
   │        │               │ POINT 1  │               │ POINT 2  │               │        │
   └────────┘               └──────────┘               └──────────┘               └────────┘
                            stable BAU +               stable BAU +
                            first benefits             more benefits
                                  ▲                          ▲
                            tranche review             tranche review
                            (continue / adapt / stop)

[!TIP] Exam tip: If a scenario says a programme reached the end of a tranche but operations cannot function without the next tranche also completing, the programme has not designed a genuine landing point.

---

Multimodal Delivery

Multimodal delivery is the use of more than one delivery lifecycle within a single programme. MSP does not require every project to be run the same way; it requires the delivery approach to state which mode is used where, and why.

Continual improvement deserves particular attention: in MSP it is a mode of work in its own right, typically running inside business operations after a capability has been adopted, and it is one of the mechanisms by which benefits keep growing after a tranche closes.

Choosing the mode

The delivery approach records the selection criteria. In practice the choice turns on four questions:

1. How stable are the requirements? Stable and externally fixed points towards linear; emergent points towards iterative.
2. Where is the risk concentrated? If the biggest risk is "we do not know what users need", iterate. If it is "the plant must be certified before it can operate", sequence it.
3. What does the regulatory or contractual environment permit? Some safety and public-procurement regimes require defined specifications before build.
4. What can operations absorb? Iterative delivery generates frequent change; if organizational capacity or ability is low, the programme may deliberately batch releases into fewer, larger landing points.

[!CAUTION] Common trap — mode is not maturity: A distractor may imply that iterative delivery is inherently more advanced, or that linear delivery is obsolete. MSP is explicitly neutral: the correct mode is the one that fits the work, its risk profile, and the organization's ability to absorb change.

---

Bringing It Together

Pace, landing points, and delivery mode are a single design decision, not three separate ones. A programme that selects iterative delivery for every project but has low organizational ability will produce a stream of releases that nobody adopts — outputs without outcomes. A programme that selects linear delivery for a genuinely uncertain digital service will reach its first landing point having built the wrong thing at scale.

The Structure theme therefore requires the programme to state, in the delivery approach and the delivery plan together: what the tranches are, what state the organization will be standing in at the end of each one, how fast change is being introduced, and which delivery mode each piece of work uses.