Before after the client site scope push
Explain how a scope boundary improves when DESC, broken-record, and fogging are sequenced deliberately.
Ravi is asked to add an uncontracted security audit to Friday's client-site deliverable while his project manager watches. Before: Ravi over-explains the constraint and the client hears room to negotiate. After: Ravi acknowledges urgency, names the scope impact, and offers a change path. The opening changed from apology to fogging: Ravi accepts the true point that the audit would help, which lowers heat without conceding the unscoped demand. The middle changed to DESC: he describes the new audit request, expresses the delivery risk, specifies the change-request path, and names the consequence of adding scope now. The close changed to a…
Sign up free: one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in