Engagement Scope Definition Checklist Prompt
Prompt
We're kicking off a [PASTE: engagement type] engagement with [PASTE: client name] and the scope keeps shifting. I need a comprehensive scope definition checklist and document that prevents ambiguity and scope creep from the start. Create a checklist that ensures: (1) Clear boundaries – use a two-column format explicitly stating what IS and what's NOT in scope. Be specific about systems, geographies, or functions. (2) Success criteria – define 3-5 measurable outcomes the client will see by project end. How do we know we've succeeded? (3) Team & timeline – specify our team size, client time commitment required, key milestones, and go/no-go decision gates. (4) Assumptions & dependencies – what must be true for us to succeed? What could derail us? What client resources are critical? (5) Governance structure – weekly sync cadence, steering committee composition, decision authority, and escalation protocols. (6) Change management – how do we handle scope requests that come up during delivery? Format as an interactive checklist that I can review with my delivery lead and present to the client at kick-off. Include a sample filled-in version for reference. Make it rigorous but not bureaucratic.
Why it works
Scope creep is the #1 profitability killer in services. A clear, documented scope agreement upfront prevents misalignment and reduces client friction later.
Watch out for
Being too rigid on scope early can stifle discovery. Frame it as a 'working scope' that's formally reviewed at key decision gates.
Used by
ExecutivesFounders