Turn a Vague Boundary Into Options

Eli receives a vague request to support a client workshop next week. He has limited capacity and needs to avoid creating an undefined promise that eats recovery time. Clarify scope, timing, and ownership, then offer a menu of feasible support. The common trap is a mushy boundary: I can try to help a little. It sounds cooperative but creates a promise with no limit. Step 1 Scope: identify the actual support types - agenda review, live framing, follow-up memo. Scope turns help into visible deliverables. Without it, the request can expand indefinitely. Step 2 Timing: separate next week's workshop from…

Sign up free — one personalized lesson every day, matched to your role and goals.

Already have an account? Sign in