Spot where stakeholders' expectations don't match the plan
Compares what each stakeholder expects with what the project will actually deliver, and helps you close the gaps early.
The prompt
Find where stakeholder expectations don't match my project, before it causes trouble.
What the project will actually deliver: [SCOPE, dates, quality level, budget, what is out of scope]
What each stakeholder expects: [PASTE their emails, meeting notes, requests, or describe what each has said]
Documents they've seen: [charter, proposal, slides - and what those promised]
Check each stakeholder against the plan on:
- Scope: features or outputs they expect that aren't planned, or that are planned differently.
- Timing: dates they're quoting vs our dates, and phase vs full delivery.
- Quality and level of detail: "pilot" vs "production ready".
- Their role: what they think they'll be asked to do, approve, or provide.
- Benefits: results they expect and when.
- Expectations that conflict between stakeholders.
Return:
1. Gap table: Stakeholder | What they expect | What we will deliver | Size of gap (small / medium / large) | Source of the misunderstanding.
2. Conflicts between stakeholders' expectations that only a sponsor decision can settle.
3. For each large gap: whether to change the plan or reset the expectation, and a suggested message to reset it, honest and specific.
4. Habits to keep expectations aligned: what to confirm in writing, and when.
Quote stakeholders' own words where possible. If I haven't given evidence of someone's expectation, mark it [ASSUMED] and suggest checking with them directly.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- SCOPE, dates, quality level, budget, what is out of scope
- charter, proposal, slides - and what those promised
- ASSUMED
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Write a data management plan for a grant or projectA funder-ready data management plan covering data types, formats, storage, metadata, sharing, and preservation.
- Write a project charterDefines a project's purpose, scope, objectives, stakeholders, and success criteria.
- Plan stakeholder communication and engagementWho needs to know what, when, and how — and how to keep them engaged.
- Plan a Windows imaging and laptop deployment rolloutA deployment plan for setting up company Windows devices at scale: tool choice, image and driver strategy, task sequence, testing, and rollout waves.