Surface adjacent requests and scope-creep risks
Anticipates the adjacent asks likely to arrive during delivery, names which fall outside the defined boundary and why, so exclusions are deliberate rather than reactive.
In / outAgreed scope + prospect context + engagement type → list of likely adjacent requests + documented out-of-scope rationale for each
You might say…
“Scope creep never announces itself — I'd rather draw the fence explicitly now than defend it under pressure mid-engagement.”
What it does
Anticipates the adjacent asks likely to arrive, names which fall outside the boundary and why, so exclusions are deliberate not reactive. Used while drawing scope. Single judgement call spotting latent creep.
Trigger: Use while defining scope boundaries to proactively identify latent expansion risks and document them before they become mid-engagement disputes.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation