Negotiate a scope change using impact evidence

A useful client request can still be outside the accepted scope. Saying yes silently converts uncertainty into delivery risk; saying no without analysis discards possible value. The professional response is an impact record with choices.

Build the decision artifact

Restate the requested outcome and why it matters. Trace changes to architecture, data, identity, testing, security, operations, schedule and acceptance. Estimate a range tied to dependencies. Offer choices: defer, fund a separate phase, replace an existing deliverable or decline. Record the authorized decision before work changes.

The commercial leadership lab makes the artifact inspectable with authored inputs:

from leadership_cases import scope_change_case

result = scope_change_case()
assert result["range_not_point"] is True
assert result["silent_expansion"] is False
assert result["current_contract_changed"] is False
assert result["request"]["decision"] == "defer"

Autonomous supplier creation adds an 8–13 day range, three controls and a new business owner. The fixture presents three options and defers the change. Current scope remains unchanged until a sponsor decides otherwise.

Protect the decision from weak evidence

Do not inflate estimates to discourage change or understate them to preserve goodwill. Show evidence and uncertainty. If replacing a deliverable, identify exactly which acceptance criterion moves; otherwise the plan has expanded despite the paperwork.

Keep these artifacts for review:

• change request and intended benefit
• impact by architecture, control and schedule
• options with trade-offs
• decision, approver and revised baseline if accepted

This practice aligns with the discovery, productisation, client enablement, technical leadership and capstone sequence in the FDE for Professionals course. The course link describes the pathway; the local scenario is fictional and does not claim a client engagement, investment result, hiring decision or certificate.

Practice task

Take a request for one new write-capable tool. Produce three options and name the test, owner and recovery work each introduces.

Continue learning

This article is part of the Commercial judgement and delivery leadership sequence. Use the neighbouring tasks when you need the prerequisite or the next application.

• Review the prerequisite or neighbouring task in Run a client discovery workshop with conflicting stakeholders.
• Continue with Design a technical due-diligence checklist for an AI pilot.

Reference: The Scrum Guide.