CON042

Business Context

Consulting engagements are typically governed by a defined scope that establishes deliverables, timelines, and resource allocation. Clients, however, operate in dynamic environments where strategic priorities shift during the course of an engagement. The pressure to honour contracted scope while remaining genuinely useful to the client creates a persistent operational tension throughout project execution.

The Contradiction

Maintaining tight scope control protects delivery margin, consultant capacity, and contractual predictability, ensuring the firm can execute commitments without resource overrun. However, rigid adherence to the original scope risks producing deliverables that are technically complete but strategically irrelevant if the client context has materially shifted since engagement inception.

Operational Risks

A firm that enforces scope rigidly risks delivering outputs the client deprioritises, weakening renewal probability and reference value regardless of technical quality. A firm that absorbs scope expansion without governance erodes delivery margin, overburdens consultants, and establishes a precedent that contracted boundaries are negotiable at no cost.

Applicable TRIZ Principles

Principle 1 - Segmentation

The engagement scope is divided into fixed core deliverables and a governed adaptive layer with its own capacity budget and change criteria. This structural separation allows the delivery team to protect the foundational workstream while processing emerging client needs through a distinct, pre-authorised mechanism rather than absorbing or refusing them as a binary choice.

Principle 10 - Preliminary Action

Before the engagement commences, scope change protocols, trigger criteria, and cost-of-change thresholds are established and agreed with the client sponsor. This prior agreement transforms scope evolution from an unplanned disruption into a governed process, removing the in-flight negotiation burden that otherwise degrades both delivery pace and client relationship quality.

Principle 34 - Discarding and Recovering

Deliverable components that have become misaligned with the client's current strategic context are formally retired and replaced with outputs calibrated to the evolved need, without treating this as scope failure. The discarding mechanism is built into the engagement model as a legitimate and pre-costed option, preserving delivery coherence while eliminating the sunk-cost pressure that otherwise forces teams to complete irrelevant work.

Operational Playbook

Establish a two-layer scope architecture at engagement initiation, distinguishing fixed core deliverables from a governed adaptive reserve with defined capacity limits.

Draft and agree a scope change trigger document with the client sponsor before kickoff, specifying what constitutes a qualifying change and the process for activating it.

Assign a scope steward role within the delivery team responsible for monitoring alignment between contracted deliverables and current client priorities throughout execution.

Apply the discarding protocol at each major milestone review, formally retiring any deliverable component whose strategic relevance has been superseded and documenting the recovery of associated capacity.

Track adaptive layer consumption as a live project metric, flagging to engagement leadership when reserves reach a defined threshold before they are exhausted.

Conduct a post-engagement scope variance review to calibrate future adaptive layer sizing based on actual evolution rates observed across comparable engagements.

Verification Metrics

Ratio of adaptive layer capacity consumed to adaptive layer capacity reserved, measured at engagement close.

Percentage of final deliverables rated as strategically current by the client sponsor at the concluding review session.

Average time elapsed between a qualifying scope change trigger and formal team response, measured in business days across all activated change events.